You are not logged in.
Hello everyone,
I used to run a gen4 AMD and upgraded to an gen5 AMD processor and thus had to switch motherboard (
GIGABYTE X870E AORUS Elite)
When putting in my M2 NVME drives in the per manual positions the motherboard boots up and cant find a bootable device. Even though there is one in /efi/EFI/GRUB/grubx86.efi on the harddrive. I can boot from it by putting in an arch linux usb stick and run EFI shell and run the said grubx86.efi file mentioned above. Is there anything I can do so I don't have to boot from a USB stick every time when I actually have the bootable device plugged in and it seems to work perfectly fine when ran manually through the EFI shell.
Thanks,
--Andromeda
Offline
if, at all, it should be (and likely is) named x64 rather than x86 - although for custom entries you can name the file whatever you want
note: <ESP>/EFI/<anything else but BOOT> is a non-standard part - so its up to the specific firmware implementation if it scans for any other efi files than <ESP>/EFI/BOOT/BOOT<platform>.EFI (where platform is "X64" on x86-64 systems)
so what your new board is missing is just a proper boot entry - which can be set manual by using efibootmgr or let grub do it by grub-install - or you could just copy/move your grubx86.efi to the default path and name it properly
Offline
Thank you for the information, would it be possible to link that file to /efi/EFI/BOOT/BOOTX64.EFI?
What additional arguments and flags do I need to use for efibootmgr and grub-install for them to fix it? I'm not too experienced with those softwares.
EDIT:
After some googling around I decided to run:
```run0 grub-install --target=x86_64-efi --efi-directory=/efi --bootloader-id=GRUB --removable```
followed by:
```run0 grub-mkconfig -o /boot/grub/grub.cfg```
Adding the removable flag writes a bootable file to (ESP)\EFI\BOOT\BOOTX86.EFI
Now my system boots from the harddrive again, thought I'd leave that here if anyone else runs in to the same issue. Thanks so much for your help!
Last edited by andromeda87 (2025-07-24 04:33:34)
Offline
Now my system boots from the harddrive again
\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline
Thank you for the information, would it be possible to link that file to /efi/EFI/BOOT/BOOTX64.EFI?
no because uefi spec require ESP to be FAT32 and fat doesn't know about symlinks - that's a posix-fs feature
Offline
grub-install --target=x86_64-efi --efi-directory=/efi --bootloader-id=GRUB --recheck
Removable is irrelevant for your case.
And yes, you can manually: :: ln -s /boot/esp/EFI/GRUB/grubx64.efi /boot/esp/EFI/Boot/BOOTX64.EFI
I have my esp mounted at /boot/esp, modify accordingly.
A problem to do what everybody else does without questioning. A danger to go against the way things are just because. Too much or too little, ivory towers of perfection or functional mess... Balance is what this world needs. Selective, not the middle ground. Objectivity and idealism, but within a pragmatic scope. - Minimalism is achieved through efficiency, not deficiency.
Offline
I doubt that this actually works with a proper fat32 partition - fat doesn't support symlinks - neither does uefi
Offline
I am sorry, got stupid for a minute. You are correct. no symlink. Copy.
A problem to do what everybody else does without questioning. A danger to go against the way things are just because. Too much or too little, ivory towers of perfection or functional mess... Balance is what this world needs. Selective, not the middle ground. Objectivity and idealism, but within a pragmatic scope. - Minimalism is achieved through efficiency, not deficiency.
Offline
@Andromeda - can you do me a favor? I have the same motherboard and I can't boot the Arch ISO. Can you please download the latest ISO, burn it to a USB drive, and see if you can boot fully into it? I'd really appreciate it.
Offline