On Tue, Feb 4, 2014 at 9:15 AM, Chris Adams <linux@xxxxxxxxxxx> wrote: > Once upon a time, Matthew Garrett <mjg59@xxxxxxxxxxxxx> said: >> …and configure the UEFI boot options, which you can't do because you're >> not running under UEFI and so have no access to UEFI runtime services. > > That's probably the biggest flaw in the whole UEFI setup - you can't > access it unless you boot using it, and you can't boot from it unless > you access it to configure it. It makes switching to UEFI (or the > old-time common practice of installing to a drive in one machine and > then moving it to another) difficult (at best). There are at least two ways to hack around this. You can boot from a live UEFI image, chroot in, and do the magic incantation to get GRUB to install itself, or you can call your bootloader "bootx64.efi" (IIRC) and try to convince your firmware to load it. I think that half the difficulty here is that UEFI is annoying and the other half is that both GRUB2 and efibootmgr are miserable. TBH, I've never had much trouble convincing UEFI to load an image -- most of the trouble is convincing GRUB2, once successfully running, to do anything useful. (The Debian/Ubuntu approach regenerating grub config all the time is nicer here, but it still sucks. I'm anxiously awaiting BootLoaderSpec and something that isn't GRUB or GRUB2 to make a lot of the unpleasantness go away.) > > I have a friend that worked for a BIOS vendor and now for a CPU vendor > that I think helped write some of the UEFI spec - I need to bug him on > that one. :) > -- > Chris Adams <linux@xxxxxxxxxxx> > -- > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
