** Description changed: + [Impact] + Some firmwares may fail to populate LoadOptions in EFI in a way that shim understands, including only the extra options rather than the full BootEntry. + + [Test case] + Attempt to boot a system on a BootEntry that requires extra options, such as when running firmware updates via fwupdate. + + [Regression Potential] + The information passed by some firmwares may look as though it is a simple UCS-2 string although it contain extra information, and thus cause a failure to boot due to unrecognized LoadOptions when shim attempts to boot. The default boot process does not include LoadOptions at all, but this may adversely affect fwupdate or running MokManager. + + ---- + Using the applications such as fwupdate and efibootmgr to set the device path for the second stage path is not working on some platforms. The second stage set is not working after commit 3322257e611e2000f79726d295bb4845bbe449e7 on https://github.com/rhinstaller/shim for those which load option only have one string. This is due to some versions of BDS, on loadoption we only get: 00000000 5c 00 66 00 77 00 75 00 70 00 78 00 36 00 34 00 |\.f.w.u.p.x.6.4.| 00000010 2e 00 65 00 66 00 69 00 00 00 |..e.f.i...| 0000001a
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581299 Title: shim: set second stage not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1581299/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
