http://bugzilla.opensuse.org/show_bug.cgi?id=999818
http://bugzilla.opensuse.org/show_bug.cgi?id=999818#c7
Michael Chang
(In reply to Michael Chang from comment #4)
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.
Looking into grub2-install again, the --removable parameter really implies the same effect as --no-nvram. The common check in creating efivars like this: if (!removable && update_nvram) grub_install_register_efi ... And I also did the test with running grub2-install and --removable along really did not create any efivars. But to be on safe side, I agree with specifying --no-nvram as code or meaning could change in the future, but currently it really looks redundant to me when used together with--removable. 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 ?
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.
OK. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.