http://bugzilla.opensuse.org/show_bug.cgi?id=999818 http://bugzilla.opensuse.org/show_bug.cgi?id=999818#c1 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gtettamanzi@gmail.com, | |jreidinger@suse.com Flags| |needinfo?(gtettamanzi@gmail | |.com) --- Comment #1 from Josef Reidinger --- Yes, this options are wrong. Can you please attach yast logs? So I can see why this powerpc only options are used in this case. https://en.opensuse.org/openSUSE:Report_a_YaST_bug#I_reported_a_YaST2_bug.2C... thanks -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=999818 http://bugzilla.opensuse.org/show_bug.cgi?id=999818#c3 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mchang@suse.com Flags| |needinfo?(mchang@suse.com) --- Comment #3 from Josef Reidinger --- ah, my fault, it is not only for powerpc. Michael - can you please check why it failed? Code to detect when this removable and no-nvram to use is at https://github.com/yast/yast-bootloader/blob/master/src/lib/bootloader/grub_... maybe we need to limit it even more? or detection is wrong and there is better way to recognize it. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=999818 http://bugzilla.opensuse.org/show_bug.cgi?id=999818#c5 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |agraf@suse.com Flags| |needinfo?(agraf@suse.com) --- Comment #5 from Josef Reidinger --- (In reply to Michael Chang from comment #4)

Hi Josef,

In efi, the --removable covers the case of --no-nvram. Here what it does to get installation on removable disks.

1. Copy efi loaders to default loader path on ESP 2. Prevent modifying EFI boot variables, then firmware will boot the default loader on this (removable) disk.

So it's fine to replace

cmd << "--no-nvram" << "--removable" if removable_efi?

With:

cmd << "--removable" if removable_efi?

For PowerPC, specifying --removable to grub2-install basically triggers error because it only available on EFI. You can still use --no-nvram to prevent from updating nvram, ie, for not changing the default boot device for OFW.

Thanks.

Ok, so it will be fixed by removing --no-nvram? Alex as you are author of this change, can you please verify it as I do not want to break your change for aarch64? Thanks -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=999818 http://bugzilla.opensuse.org/show_bug.cgi?id=999818#c6 --- Comment #6 from Alexander Graf --- (In reply to Michael Chang from comment #4)

Hi Josef,

In efi, the --removable covers the case of --no-nvram. Here what it does to get installation on removable disks.

1. Copy efi loaders to default loader path on ESP 2. Prevent modifying EFI boot variables, then firmware will boot the default loader on this (removable) disk.

So it's fine to replace

cmd << "--no-nvram" << "--removable" if removable_efi?

With:

cmd << "--removable" if removable_efi?

In EFI, --removable means "install the binary at the removable location" while --no-nvram means "Do not update the nvram with a new entry" (which would fail if no nvram is available). So nack for the change. The actual problem is deeper. For some reason we're running the efi code on a system that does not see efivars. That should not happen on normal systems. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=999818 http://bugzilla.opensuse.org/show_bug.cgi?id=999818#c8 Gary Ching-Pang Lin changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(glin@suse.com) | --- Comment #8 from Gary Ching-Pang Lin --- (In reply to Michael Chang from comment #7)

(In reply to Alexander Graf from comment #6)

...

(In reply to Michael Chang from comment #4)

OTOH We can also make a quick fix in shim-install to provide the --no-nvram parameter then it did not fail. The question here is that shim package is not updated in TW for a while and I think we are waiting new image gets signed by MS. (But who knows how long it will take).

Gary, did you have comment for that ?

I informed Johannes to request a new signature last week. It could take a week to a month, depending on the code review. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=999818 Gary Ching-Pang Lin changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jsrain@suse.com |glin@suse.com -- You are receiving this mail because: You are on the CC list for the bug.