I also got this grub problem yesterday and after finally mounting the EFI partition of EoS via mount partition /mnt/boot/efi and then grub-install, it worked.
Then this morning it stopped working… I did a yay -Syu(upgrade and install) appimagelauncher, which took 30 minutes but it worked, i was able to run curseforge and play with that. So i thought maybe it again updated to the faulty grub version, so i went and redid what i said above, but nothing… i tried both manually and via efibootmgr -o xxxx,zzzz,yyyy setting my boot order and via my mobo, all i got was an EoS selection menu that shows EoS to launch, fallback, and Windows Boot Partition(not sure why its there), both of the top options either freeze or somehow show a windows screen of system recovery(might be due to the fact that Win 10 put its bootloader onto the exact same EFI partition of my EoS, WTF Microsoft !?), or option B i get grub rescue mode.
I even used grub-mkconfig if that would help following all these discussions. I have no idea what to do.
show ls /boot/efi/EFI from your installed system (inside chroot) not sure what is causing your freeze now… but if it would be the same issue you would boot into firmware setup without showing grub boot menu at all… do you have windows and eos on the same drive and using the same ESP?? (fat32 boot partition?)
ls /boot/efi/EFI output is:
boot endeavouros endeavouros-1442 Microsoft
And no Windows is on a Kingston SSD drive while EoS is on a Samsung NVME drive, the boot manager of Windows though is on nvme partition 1 the EFI parition though. Why ? Ask Microsoft. So far there were no issues between the 2 OSes, unless you want to count how buggy and unresponsive Windows was sometimes, especially yesterday when i was trying to use Rufus to put EoS image onto my USB Stick so i can attempt to repair it, file transfers were not happening, stuck at 0%, Rufus crashed everytime until a third reboot and such, very weird.
I’ve just downloaded the new grub update from unstable branch and it seems - so far - to have fixed everything. No out of memory errors and the theme displays correctly!
One thing I got out of this situation is that Arch needs more people running testing, probably from derivative distros too.
But I sure hope people from their side communicate in a more friendly manner. Maybe it was just one person.
Wait so ending with 4 is the latest version, but grub-install does only ending with 3… how do i update to that one ? Type it’s name ?
grub-install VERSION ?
I don’t think this is a grub issue. If you have the menu, then grub is working well (as far as i know).
I think you have to install your kernels again because your initramfs might not be generated correctly.
I think they already have the bad grub and ran grub-install once.
