You are not logged in.
I just updated my graphics card, and performed a BIOS update as part of that process. After that update, my arch_grub EFI entry failed to show up in the firmware boot options/menus. In order to boot, I needed to copy my .efi file to the fallback path (/boot/EFI/BOOT/bootx64.efi). This is working, but I'm wondering if I have any other options I'm not aware of.
I'm using grub/uefi/gpt.
Motherboard is a Gigabyte GA-Z77-D3H Rev 1.0, with the Gigabyte 3D BIOS (Dual-UEFI) version F22. With version F14 and my new graphics card, the system doesn't get to the POST or show the BIOS screen, but F14 does show the arch_grub .efi entry in the boot menu with my old graphics card. With F22 and the new graphics card, the system does the POST and I can get to the BIOS screen/setup, but the arch_grub .efi entry doesn't appear as a bootable option.
As I mentioned, I got the system to boot into Arch by copying the arch_grub .efi file to the fallback path and then selecting the UEFI boot option for the drive, itself (so it's finding it like you would on a UEFI-bootable USB drive), but that feels pretty inelegant. Does anyone have any suggestions or insight or pointers to something I may be overlooking?
Last edited by philotomy (2017-12-08 15:36:53)
Tu ne cede malis sed contra audentior ito!
Offline
Certain UEFI implementations have a tendency to simply clear out their NVRAM entries on update (and only actively readding the Windows EFI, if present). So you'd simply have to add the relevant EFI variable entry again (by rerunning the relevant GRUB install command for example).
Last edited by V1del (2017-12-08 14:22:59)
Offline
Thanks, that got me sorted out. Seems obvious after you pointed it out. ![]()
Tu ne cede malis sed contra audentior ito!
Offline