https://bugzilla.novell.com/show_bug.cgi?id=809038
https://bugzilla.novell.com/show_bug.cgi?id=809038#c9
--- Comment #9 from Michael Chang
Created an attachment (id=529547) --> (http://bugzilla.novell.com/attachment.cgi?id=529547) [details] Output of "efibootmgr -v" with secure boot enabled.
This is the "efibootmgr -v" output when secure boot is enabled.
Interesting that we see boot config feed to windows loader via the command options .. Boot0004* Windows Boot Manager HD(1,800,fa000,a0547a0a-57c0-405d-b6b9-a01ca4839f0f)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}... ................ My guess, when secure boot enabled, windows will protect it's boot config from altered and refuse to boot if any validation failed. When chainload by grub2 (or any other chainloader ..) without a explicit bcd passed it refused to process .. So we don't know how to fix this as apparently we can't debug proprietary software to know what the hell they are doing. -- 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.