Can’t relate, arch testing never broke in years. Without manual maintenance.
If it where arch, but its manjaro. Somehow during the last kernel update the grub info was not changed to point to the current kernel names…still pointed at the old kernel…and that had been replaced. After figuring all that out in chroot, fix was as simple as changing a single line in that grub file
Yet another Majaro L? Not one to dunk on random distros, but I’ll always make an exception for Manjaro
Only the morons that turn on AUR despite being warned against it ever have problems on Manjaro.
The dangers of relying on a prebuilt system which is maintained … lets just say not state of the art.
Also, would grub-hook be an option?
sudo init 0 because yolo
chroot has all the power to fix it, but my mental state cant handle it
„Wheres that fucking pendrive again?”
Reminds me of that time I updated my UEFI firmware which automatically re-enabled secure boot which caused my Nvidia driver to fail to load on boot because Nvidia doesn’t sign them so I was stuck with the noveau(spelling?) driver which would crash when I tried to log into my DE. What an adventure figuring that out was. Oh, and the cherry on top: updating the firmware didn’t fix the initial issue I was troubleshooting.
Ugh, I just went through the same thing last week. Let’s just say that checking if secure boot had been turned back on was NOT one of the first 500 things that came to mind during troubleshooting.
I know this is a day old and most people who would have seen this already have moved on, but this is a simple fix. In fact if you have secure boot enabled, the Nvidia driver installation will detect it and start the signing process. If you don’t have secure boot enabled, then it will skip it. I think having secure boot enabled and properly signing your drivers is good to not end up in that situation again. Though I understand how annoying it can be too. Sigh
