[SOLVED] Emergency mode after fresh installation

Issues & Assistance
1

Hi there!

I’m new to CachyOS, although I’ve been using Linux for about 20 years now, especially Arch. Now I wanted to give CachyOS a chance on my laptop.
Unfortunately although running the system from a bootable USB doesn’t seem to be a problem on my MSI notebook (Intel 13th gen. CPU + iGPU + nVidia GeForce 4090L dGPU) with a proprietary driver, after successful installation I end up in a console with emergency mode. I don’t know what is going on, as lsmod shows that nvidia module is up and running, DRM also is on. SDDM service is enabled but dead (I’m trying to login to KDE Plasma on Wayland session). The only error journactl -xb gives me is this

“CachyOS kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2”

I would greatly appreciate any help.

Thx

2

That error doesn’t seem to be something that could cause you to boot to emergency mode tho. See [SOLVED] Issue with loading regulatory.db at boot / Newbie Corner / Arch Linux Forums. Is there anything else in the logs?

3

Hello naim!

I think there is nothing more in the logs, but what I’ve discovered is that CachyOS live USB boots into X11 session instead of Wayland, and that’s maybe the main and crucial difference

“[liveuser@CachyOS sddm.conf.d]$ echo “$XDG_SESSION_TYPE”
x11”

4

That’s probably unrelated, since it’s reaching emergency mode first before it reaches SDDM, i.e. before loading a graphical environment. That said, without any logs I can’t really help further. You could try some of the tips from the forum I’ve shared earlier, but if that doesn’t work I’m stumped.

5

Are there any particular information/logs, that would be helpful besides journactl?

6

dmesg, but usually it has the same information as journal. Providing the full log could be helpful tho.

7

The problem, and hence the solution, turned out to be trivial. Whole issue was with two Windows 11 partitions not mounting during booting process (wrong UUIDs?). I guess something went wrong during installation when I decided to mount those partitions and their entries have been added to fstab.
It’s solved now.