When you first installed EOS did you do a regular (not Nvidia) install and then install the drivers after?
You may be missing the nvidia-hook package from the EOS Repo, it is included when you do an Nvidia install of EOS or run nvidia-inst.
I’m encountering the same issue as OP.
Ran a system update via yay, rebooted to a blank screen. No systemd-boot menu.
Tried an EFI boot by selecting the systemd-bootx64.efi file directly, but the issue persisted.
Among the packages updated were linux linux-lts linux-firmware systemd systemd-libs and various nvidia packages. Though I don’t see how it could be an nvidia issue.
After chrooting, I tried sudo reinstall-kernels, reinstalling the kernels, and downgrading one of the kernels to the version I had before the update. Nothing worked.
My suspect is the systemd efi file, but I don’t know how to deal with it.
1 Like
Disabled legacy boot from BIOS options and was able to boot successfully.
Still don’t know what the culprit package is.
1 Like
Ok, great to know, thank you!
When booting from the install medium, I always selected the NVIDIA install for the latest cards. And the problem persists even after manually running nvidia-inst.
As I wrote earlier, I’m not even sure it’s an NVIDIA problem anymore, since everything runs fine after replacing systemd-boot with GRUB.
This is a systemdboot issue. Somthing is wrong with it as my system is back to normal with grub. It survived an update.
I had legacy bios turned off on my cmp the second time i got hit with this. So anyways back to grub and all is well it seams.
That is pretty unlikely I think. More likely it is something to do with initrd creation that was fixed in migrating to grub.
Not sure. This bug came up on a fresh install of eos using systemdboot as well. I went through the steps rebuilding with dracut. Rebuilding systemdboot. Booting to a blank screen no matter what.
Fresh install of eos with grub and it survied a kernelupdate. Ill leave it be for now.
1 Like