On Thu, Jun 4, 2020 at 12:50 PM Richard Shaw <hobbes1069@xxxxxxxxx> wrote: > > Responding to the list instead of personal... > > On Thu, Jun 4, 2020 at 1:33 PM Marius Schwarz <fedoradev@xxxxxxxxxxxx> wrote: >> >> Am 04.06.20 um 15:04 schrieb Richard Shaw: >> > Is there someone that can help me convert my Fedora install from GRUB >> > to systemd-boot and actually get it where kernel updates won't break it? >> > >> How did you get your Fedora on that Surface if grub does not work? > > > It will install fine, just not boot. Now when I say install "fine" I can't choose the installer at boot, I have to boot windows then do: > Updates & Security -> Recovery -> Advanced > > Let it "shutdown" to the chooser screen and pick the whatever the alternative boot option is. This tells me that the bootloader is in the correct location, but that (a) the Fedora boot entry in NVRAM isn't persistent, (b) the firmware is ignoring the boot entry in NVRAM, (c) the firmware expects to find a specifically name bootloader. All of these are firmware bugs. I don't think sd-boot helps in this case. I'd say pick either sd-boot or GRUB, it's hard enough to figure this stuff out without having two bootloaders. I think you have to figure out what the firmware wants. Either rename the boot entry; or rename shim.efi to bootmgfw.efi (I think) or possibly both. Or alternatively maybe the firmware's built-in boot manager will let you choose. Sometimes it's called boot selection or change boot order. Not every UEFI implementation has a built-in boot manager but most do. -- Chris Murphy _______________________________________________ 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
