After updating via pacman -Syu, I get the black screen pictured. The computer boots into emergency mode. I have rebooted into a snap from before the update and everything works, then I update and it happens again. I waited a week to update again and the problem persists leaving me at an older version with over 200 updates waiting. System history: All same hardware from the initial install 8+ months ago except recently changed to NVIDIA from AMD. I have followed the migration completely and even removed lib32 AMD things that stayed afterwards and nvidia-smi shows that things are hooking correctly.
Hardware: 7800x3D, 64gb 6000 ram, Asus Astral Rtx 5080
OS: Cachy (obv) DE: hyprland
Here is the log gathered by cachy-bugreport.sh as I don’t have internet while in the cli even though I’m hard lined.
EDIT: here are errors that i’m not seeing in the log so i don’t know if i ran the log correctly or the right time since this is what i see if i’m in that emergency mode journalctl
Found the solution though I’m not sure exactly which of these things was the final fix. Shout-out to Pete in the SOS discord who guided me through all of the things.
First I made a liveusb of CachyOS. If you have one already good job! Then booted inside and opened the command line.
I ran “sudo cachy-chroot” then chose my btrfs partition to auto mount and said NO to mounting anything else.
Then ran pacman -Syu linux-cachyos
I noticed the mkinitcpio error that I had been getting for a while so after some digging we found that my MODULES had “…” in a couple places.
Running “sudo nano /etc/mkinitcpio.conf” I removed all “…” and any spaces added between the next or previous entry. Saved the doc and then ran “sudo pacman -Syu linux-cachyos linux-cachyos-headers”
There were no errors so I rebooted and all is right in the world again! Hope this helps
It was most likely /etc/mkinitcpio.conf, with the pacman install commands only playing a role due to effectively running sudo mkinitcpio -P.
The “failed to find module” error message in your screenshots are a big hint towards this. The kernel image was incomplete/broken.
Big question is how your mkinitcpio.conf got to be broken in the first place. System updates shouldn’t be changing that file. Did you recently blindly merge/replace mkinitcpio.conf from pacnew by any chance?
I did not but I am faintly remembering a setup for maybe hyprland that had me adding a line for MODULES 6-8 months ago and I thought you myself “having ellipsis seems weird but ” I was (and am still) so new to Linux. Idr exactly where it came from though but I think I maybe added that? Otherwise idk what to tell you it was a long time ago and for weeks if not months I’ve had issues with mkinitcpio erroring with updates and I thought limine was having an issue. Didn’t pursue which is probably why it finally crapped itself.
Tldr: maybe I added it following a tutorial? IDK and idr
First, I restored the system using the latest snapshot. CachyOS booted up again. Afterward, I disabled Secure Boot in the BIOS.
Then, I applied the full update once more. CachyOS booted normally again after the update. It turned out to be due to Secure Boot, so the problem is resolved—at least for now.
” I was (and am still) so new to Linux. Idr exactly where it came from though but I think I maybe added that? Otherwise idk what to tell you it was a long time ago and for weeks if not months I’ve had issues with mkinitcpio erroring with updates and I thought limine was having an issue. Didn’t pursue which is probably why it finally crapped itself.