On Fri, Apr 30, 2021, 6:58 AM Richard Ryniker <ryniker@xxxxxxxxxxx> wrote:
After upgrade from F33 to F34, the newly-installed kernel was not the
default to boot. I had to explicitly select the F34 kernel in lieu of an
older F33 kernel at boot time. This was a surprise for me (I expected
the last kernal installed to become the default), but it may not be
germane in your situation.
______________________________
This sounds like a grubenv grub.cfg disconnect. The usual cause it's running 'grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg' after upgrading to Fedora 34. But we might have a rare bug with converting from the old to new (same as BIOS) location.
What do you get for
grub2-editenv list
If the default kernel listed is correct, but isn't used as a default, do:
grep configfile /boot/efi/EFI/fedora/grub.cfg
Possibly related are a few reports of grub> prompt following upgrades.
--
Chris Murphy
_______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-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/test@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
