On Mon, Feb 11, 2019 at 6:19 PM Chris Murphy <li...@colorremedies.com> wrote:
> On Sun, Feb 10, 2019 at 2:21 PM Richard Shaw <hobbes1...@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. > Well, I was pretty frustrated at that point :) But there are some things that would make it easier... For one, why did my PARTUUID change? I used gparted and moved both /boot and /boot/efi over to the new disk. The UUID was unchanged, and I had no idea that EFI used PARTUUID. Also, why does efibootmgr silently act like it's working? I tried "changing" an entry and it exited like it worked but couldn't because efivars was still mounted RO... I can't remember what I did but a different command (maybe remove?) was the one that got me the hint that I needed to remount efivars as RW. Thirdly... I wasn't sure if partitions in EFI start with 0 or 1 and it I couldn't find ANYWHERE that said one way or the other... Thanks, Richard
_______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
