I successfully arch-chrooted to resolve this on both my Arch desktop and EndeavourOS laptop, but can’t get the Grub splash to show on my EOS install even though it successfully shows on my Arch install. I’m happy that I can boot, but I’d like to be able to select my LTS kernel if necessary in the future. Any help would be greatly appreciated. Thanks!
I just updated and after i restarted my pc it wouldn’t let me go into the linux boot just the system menu. This is an emergency for me because my lapyop has some important logins for applying for jobs and stuff like that.
I’ve had a lot of problems with grub also. I wiped my system a number of times. Fresh installs weren’t any better. Having it boot wasn’t the problem. Having it not do the same again if updating grub was a problem. Now it seems to be okay and i have no idea what i did but Ive updated grub a number of times and it’s been working now. I installed other kernels and it’s booting without issue so far. If it comes back with updating i don’t know.
I’ve had it boot to UEFI screen, or boot to grub rescue or boot to out of memory error. I even reinstalled numerous times. Finally now it seems more stable. Not sure why.
I tried rEFInd a long time ago and it was OK.
But currently - after a fresh install - I converted to systemd-boot by following instructions of @dalto in another thread.
I chose systemd-boot because it is simpler than Grub and rEFInd, easier to maintain and fix, less prone to problems because of its simplicity.
It is worth trying despite it does not support booting to earlier snapshots. But I feel better and safer with systemd-boot.
Why does this Grub issue only occur on UEFI systems? How do you know fwsetup is invoked? I have an old problem that I described here, UEFI Grub and BIOS Grub in parallel i.e. I can only start EndeavorOS Grub after switching to legacy only mode in the BIOS. Could this problem after the Grub update affect me?