https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c5
Andrey Borzenkov
If I edit "grub.cfg" and change "linuxefi" to "linux" and "initrdefi" to "initrd", then I can boot with secure-boot enabled.
This seems to be either a grub2-efi bug with "linuxefi" or a kernel bug that is triggered when called from the efi interface.
There is also possibility of something wrong with shim (grub2 calls into shim to verify signature). Could you try 1. Boot using shim when secure boot is disabled in firmware? In this case shim should skip signature verification. 2. Boot using installed grub.efi directly but using linuxefi/initrdefi when secure boot is disabled in firmware? In this case we skip calling into shim completely but still use the same Linux kernel EFI stub to invoke it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.