On 7/9/25 6:11 PM, Chris Adams wrote:
Once upon a time, Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> said:
On Wed, 2025-07-09 at 20:10 -0400, Sam Varshavchik wrote:
Chris Murphy writes:
I'm able to fix this with efibootmgr, but... what a swig of sour milk.
That pretty much describes my kneejerk reaction about a decade ago when I
first read about secure boot, and how great it is to have each boot stage
signed by an all-mighty cert.
Nothing Chris wrote about actually has anything to do with Secure Boot,
really. It's just about how the UEFI boot manager works.
Different Chris, but... it sounds like Windows gets a "fallback"
position for when the firmware has no boot entries; is there a way to
get Fedora into that position instead (in a dual-boot setup)? Or is it
a case of the firmware just explicitly looking for the Windows loader?
Fedora should be in the fallback position and it will create a boot
entry for itself if it gets run like that. It's possible that the BIOS
specifically looks for windows if there are no boot entries. I worked
on a laptop once that would always "fix" the windows boot entry if it
wasn't there or was modified.
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
