A grub> prompt means GRUB wasn't able to find the grub.cfg. 1. On x86_64, reinstall the bootloader(s) by: sudo dnf reinstall shim-* grub2-efi-* sudo grub2-mkconfig -o /etc/grub2-efi.cfg * In no case should grub2-install be used on UEFI. 2. Check GRUB_ENABLE_BLSCFG=true is set in /etc/default/grub 3. grub2-mkconfig -o /etc/grub2-efi.cfg * On Fedora 33 /etc/grub2-efi.cfg->/boot/efi/EFI/fedora/grub.cfg * On Fedora 34 /etc/grub2-efi.cfg->/boot/grub2/grub.cfg 4. On Fedora 34, there is a /boot/efi/EFI/fedora/grub.cfg but it's a simple four line file that merely forwards to the real one at /boot/grub2/grub.cfg. In case this stub file was accidentally stepped on by using grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg it can be fixed by: sudo dnf reinstall grub2-common This reruns the f33->f34 upgrade script that will move /boot/efi/EFI/fedora/grub.cfg to /boot/grub2/grub.cfg, and then create the proper forwarding /boot/efi/EFI/fedora/grub.cfg stub file. 5. Another possible source of difficulty is the bootorder and boot entry stored in NVRAM. The bootorder should have the boot number for the Fedora entry first in the list. And the Fedora entry should point to the EFI system partition and path to shimx64.efi or shim.efi. Boot order can be reset by: efibootmgr --bootorder $xxxx Where $xxxx is the four digit boot number for the Fedora boot entry. No other entries need to be specified but you could optionally add a fallback entry, e.g. --bootorder 0006,0002 -- Chris Murphy _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-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/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
