On 2024-06-23 04:29, Tim wrote:
On Sat, 2024-06-22 at 23:54 -0400, Frank Bures wrote:
This is what my efibootmgr returns:
root@ryzen:/# efibootmgr BootCurrent: 0002 Timeout: 1 seconds BootOrder: 0002,0000,0001 Boot0000 Fedora HD(1,GPT,e8838c34-c364-4347-afb7-1c516782b114,0x800,0x12c000)/\EFI\FEDORA\SHIMX64.EFI Boot0001 Fedora HD(1,GPT,e8838c34-c364-4347-afb7-1c516782b114,0x800,0x12c000)/\EFI\FEDORA\SHIM.EFI0000424f Boot0002* Fedora HD(1,GPT,e8838c34-c364-4347-afb7-1c516782b114,0x800,0x1f4000)/\EFI\FEDORA\SHIM.EFI0000424f
I have no idea where the *424f files came from or why one of them has the highest priority.
The "BootOrder: 0002,0000,0001" line tells you the priority. First it'll try the last one. Then it'll try the first one. Lastly it'll try the middle one.
Of course, if one of the entries tries to boot, that going to be a success as far as the motherboard's handover is concerned. Even if Linux then fails to *continue* booting.
It's more a case of "any response?" rather than "successful."
Thanks.
I think I found the problem.
I followed
https://fedoraproject.org/wiki/GRUB_2?rd=Grub2#Updating_GRUB_2_configuration...
and then I tried to run grub2-emu
I get the list of installed kernels OK, but any choice for boot returns
error: ../../grub-core/loader/emu/linux.c:319:cannot find kernel file /vmlinuz-6.9.4-200.fc40.x86_64.
and the same error for initramfs. Please note the dot at the end of the line, is it normal?
No matter which kernel I choose, I get the error that kernel file was not found. All kernel files are in /boot and have correct permissions.
I checked UUIDs of /boot, /boot/efi and / and they are all correct.
I think this is the original problem that causes boot ending in grub prompt.
Any advice would be greatly appreciated.
Thanks Frank