After updating to linux-cachyos 6.19.0-2, my system can no longer boot into KDE/SDDM. The boot process hangs on the loading spinner and the machine becomes unresponsive. No TTY switch works (Ctrl+Alt+F2/F3 etc.).
Booting with LTS 6.18.10-2 works fine and reaches KDE normally.
My hardware is:
Motherboard: Gigabyte X870E AORUS MASTER
BIOS: American Megatrends (AMI) F9e, Release Date 2025-09-18
GPU: Sapphire Pulse RX 9070 XT
It is working with “pcie_aspm=off” (I have not try to disable it in BIOS).
I can try to attach “journalctl” output (if it working, I’m new here)
But I guess the important parts are:
“[drm] REG_WAIT timeout … optc401_disable_crtc …”
“Failed to setup vendor infoframe on connector HDMI-A-1: -22”
I have the same problem.
GPU AMD 9070XT, CPU i7 14700k, Motherboard MSI z690 A pro DDR4, KDE Plasma, dual boot Limine. The screen freeze after the choice in Limine.
I reverted to the previous version and it works.
Same issue here. Upgrade from 6.18.9-3 to 6.19.0-2, booted to constant loading spinner. Can ssh in, system reboots, same spinner. Choose previous snapshot, boots fine.
B550M-DS3H/AMD5-5600G/RX-6600/KDE 6.5.5
EDIT: Just ran same update on my Thinkpad T450s (i5-5200U) with no issues.
It booted for me, but sound was broken, also one of my two monitors was “out of range” and didn’t turn on. Booted LTS kernel and everything was fine. Rebooted back to 6.19.0-2 and it suddenly was working. So now I’m not sure if to keep using it or reverting back. Don’t like the feeling of not knowing what went wrong.
9800X3d, 3080 Nvidia gpu, asus rog strix x670e-e
EDIT: Is there a command or some log that can show me what actually went wrong so I know if i should rollback with snapper or just stay on this kernel?
Yep, can confirm I have the same problem after the update. I can boot just fine on LTS and use it ( 6.18.10 ), but 6.19 is stuck at that loading circle.
Ryzen 5 5600 and Radeon RX5700, AB350 Gaming.
If it helps, this is my journal log:
❯ journalctl -b -1 -p 3 -x
feb 14 14:01:22 cachyos kernel: usbhid 1-1:1.3: couldn’t find an input interrupt endpoint
feb 14 14:01:22 cachyos kernel: usbhid 1-2:1.3: couldn’t find an input interrupt endpoint
feb 14 14:01:49 cachyos systemd[1]: Failed to start Terminate Plymouth Boot Screen.
░░ Subject: A start job for unit plymouth-quit.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit plymouth-quit.service has finished with a failure.
░░
░░ The job identifier is 305 and the job result is failed.
feb 14 14:01:55 cachyos systemd[993]: Failed to start KDE Window Manager (Login Manager Versio>
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 64 and the job result is failed.
feb 14 14:01:55 cachyos plasma-login-greeter[1023]: This application failed to start because n>
Available platform plugins are: eglfs, lin>
feb 14 14:01:55 cachyos plasma-login-wallpaper[1024]: This application failed to start because>
Available platform plugins are: eglfs, l>
feb 14 14:01:55 cachyos systemd-coredump[1029]: [🡕] Process 1023 (plasma-login-gr) of user 959>
I think I may have found the solution to this ( or at least for my system ).
So I randomly pressed, when booting into 6.19 and having the infinite circle, CTRL+ALT+every F buttons from 1 to 7. F1 doesn’t to anything, the others stop the circle, BUT, with F2 pressed multiple times, I could boot into CachyOS. After that I did a sudo pacman -Syu and reboot, buut that still didn’t completely fix it.
What I effectively did was to remove the splash parameter in the cmdline of the CachyOS limine.conf file, and voila!
I can boot into CachyOS 6.19 kernel, from which I’m writing this response as well.
Hey, same problem here with a GMKTEC K8 plus.
I am using ly as a session manager.
I saw the infinite loop in the spinner.
I remove quiet and splash from cmdline and it works! The system is working !
Maybe is a problem/conflict betweeen Plymouth and the amdgpu. Or something like that.
Yeah, the plymouth splash seems to be the culprit.
Deleting splash by pressing E to edit at the limine boot let me boot with 6.19. Then editing the limine.conf using the instructions from here [Tutorial] Disable or Remove Plymouth (boot splash) ,
(I used the 2nd method)
Edit /etc/default/limine and place options on the KERNEL_CMDLINE[default]+= line, creating it if necessary.
Afterwards to update limine: sudo limine-update
I also have the same issue, but I don’t know why. After selecting the kernel in limine, the loading circle appears after a minute or so and hangs after a minute.
I tried the solutions posted here: removing ‘splash’ or ‘splash’+’quiet’ from the cmdline and it did not work for me. It still hangs. Pressing CTRL+ALT+Fkeys didn’t work
I tried (by mistake) linux-cachyos-bore 6.19.0-1 and it behaved the same.
Removing ‘quiet’ showed that I might have the same issue as @Codijack: nvme driver failed (if i understood correctly)
Same issue here after the update to 6.19.0-2. RX 7900 XTX, AMD CPU.
Boot animation shows up fine, then I get a black screen with the little white spinner and it just stays there forever. Can’t switch to any TTY either. LTS kernel boots perfectly on the same install.
Dug through the journal logs from the failed boot and found what’s happening:
simpledrm grabs /dev/dri/card0, then amdgpu loads on card1
Plymouth never quits - plymouth-quit.service just times out after 20 seconds
SDDM starts but kwin keeps spamming Failed to open /dev/dri/card1 device (Device or resource busy) until it gives up
The weird thing is on the LTS kernel, simpledrm and amdgpu load the same way, but Plymouth actually lets go of the device and everything proceeds normally. Something about the handoff is broken in 6.19.
So like stated it is Plymouth. I do not need it anyway. However, I tried “splash” with the new release (6.19.2-2-cachyos) and GRUB. Still does not working.
Had a similar issue — removing splash alone didn’t fix it for me. After checking the boot logs, I found AMD IOMMU errors causing xHCI and SATA controllers to fail. Added iommu=soft amd_iommu=off to the kernel cmdline in Limine and it booted right up.
Not sure if it’s the same root cause as the Plymouth issue, but figured I’d share in case anyone else hits IOMMU-related boot failures on 6.19.2.
For Intel systems, I think the equivalent would be iommu=soft intel_iommu=off.
I have nothing productive to say here. But I am a total noob to linux and been using Cos for 2 weeks now and never felt so free. Before I update I always copy the Konsole into Gemini and ask if its save. Today gemini told me to hold off for another 24hrs and linked me to this specific forum post. I feel like I have a guide to the internet and can fully enjoy linux worry free.
Always appreciated to show love about Cos. I would suggest not to update too fast and keep a regular eye out on the forums (update-issues pop up fast enough) and AI sometimes is a fluke
