Bug ID | 990650 |
---|---|
Summary | shim.efi with two signatures does not boot with SecureBoot enabled on recent ASUS laptop. |
Classification | openSUSE |
Product | openSUSE Distribution |
Version | Leap 42.2 |
Hardware | x86-64 |
OS | SUSE Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | Bootloader |
Assignee | jsrain@suse.com |
Reporter | bpesavento@infinito.it |
QA Contact | jsrain@suse.com |
Found By | --- |
Blocker | --- |
Created attachment 685586 [details] DMI decode for ASUS N551JW Testing Leap 42.2 Alpha3 on ASUS N551JW I had to install with SecureBoot disabled. The installed system didn't boot with SecureBoot enabled until I stripped the second signature from shim.efi according to the procedure outlined in https://en.opensuse.org/openSUSE:UEFI This is mainly to document that a recent firmware from a major manufacturer still has the "single signature" restriction, contrary to common belief (see attached DMI decode). Personally, I can live without SecureBoot. The same problem affects Leap 42.1 (current shim.efi are the same AFAIK). Further info here: https://forums.opensuse.org/showthread.php/519105-Unable-to-test-Leap-42-2-Alpha-with-SecureBoot-enabled