On Sun, Feb 10, 2019 at 2:21 PM Richard Shaw <hobbes1069(a)gmail.com> wrote:
efibootmgr -B 0001 (which was the fedora entry)
and then
efibootmgr -c -d /dev/sda -p 1 -l "EFI/fedora/shim.efi" -L Fedora
then it worked...
NOTHING ABOUT THIS IS INTUITIVE!
It's not intuitive, it's also not self-describing. But there is a
(massive) spec that describes the intended behavior. The end result
is, with UEFI comes with a stick, and with BIOS you're left on your
own to learn you need a stick and then find it.
Anyway, another option is you can remove all the boot entries (for
operating systems, you can leave device entries). The spec defines
that if none of the NVRAM boot entries point to a bootable system,
then the firmware starts looking on the ESP (there are rules for the
order of ESP checking), for a BOOT directory, and blindly executes the
BOOT<arch>.EFI found there. On x86_64, the BOOTX64.EFI is actually
shim.efi which has the ability along with fallback.efi to add the
proper Fedora entry to NVRAM if one doesn't exist already.
--
Chris Murphy