On Mon, Apr 4, 2016 at 10:11 AM, Martin Ueding <lists@xxxxxxxxxxxxxxxx> wrote: > Hi Chris, > > Am 03.04.2016 um 21:42 schrieb Chris Murphy: >> So reboot a few times and check 'efibootmgr -v' to see if >> you start getting accumulating boot entries again or not. > > Sadly, they keep accumulating. After the first boot I had 32 Fedora > entries, then a couple of rounds got me to 35 and now I am at 37. I wonder if this is an NVRAM garbage collection problem. That is, you deleted all Fedora entries, rebooted, and after reboot you found 32 Fedora entries? I'm willing to bet they just re-appeared due to improper (or slow) garbage collection. It might just be delayed, so try deleting them all again, and waiting a while (?no idea 1 minute? 10 minutes?). I'd also try a power off cold boot rather than a reboot and see if that makes a difference. That you keep seeing more entries being added is a bug. I'm just not sure whether it's a bug in shim or the firmware. Off hand I'd say it sounds like the firmware itself isn't honoring boot order, otherwise it wouldn't be falling back to EFI/BOOT/BOOTX64.efi, it would use the path to shim given in the first boot order entry, and therefore an additional entry wouldn't be added to NVRAM. It maybe be worth filing an upstream bug with all the details (make/model, firmware version, shim version) https://github.com/rhinstaller/shim/issues I'd suggest trying to understand the problem better and get it fixed, either with an even newer firmware update, or if upstream has any ideas. Failing that, if the hardware doesn't support Secure Boot or you aren't using it, it should be possible to remove EFI/BOOT/* and copy EFI/fedora/grubx64.efi to EFI/BOOT/BOOTX64.efi along with its grub.cfg, and now the firmware will use GRUB directly, since it seems to only depend on the fallback bootloader no matter what's in NVRAM. That's kinda ugly and it might break, I don't actually know where grubx64.efi is looking for grub.cfg, I think it looks in the same directory as the bootloader. A gotcha is you'll probably want to create a new link from /etc/grub2-efi.cfg to this new location, otherwise any kernel updates will have grubby looking to modify the grub.cfg in the old location, and you won't see new kernels in the GRUB menu. -- Chris Murphy -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
