At this point I downloaded a copy of the firmware and started poking at it. But the evidence seemed pretty strong - given two identical boot entries, one saying "Windows Boot Manager" and one not, only the first would work. There's no reason at all for the firmware to be parsing these strings. This is used by the firmware when it's presenting a menu to users - instead of "Hard drive 0" and "USB drive 3", the firmware can list "Windows Boot Manager" and "Fedora Linux". And it broke.Įvery UEFI boot entry has a descriptive string. Finally we tried just taking the Windows entry and changing the descriptive string. We spent a little while comparing the variable contents, gradually ruling out potential issues - Linux was writing an entry that had an extra 6 bytes in a structure, for instance, and a sufficiently paranoid firmware implementation may have been tripping up on that. The most interesting observation was that the Fedora boot option didn't appear in the firmware boot menu at all, but Windows did. ![]() Secure Boot was quickly ruled out, but this could still have been a number of things. UEFI installs on Windows worked perfectly. It booted Fedora UEFI install media fine, but after an apparently successful installation refused to boot. A (well, now former) coworker let me know about a problem he was having with a Lenovo Thinkcentre M92p.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |