Latest update made the OS Login screen not boot up properly as I restarted the laptop after the update. Black screen as I can’t even do anything. Was forced to do a hard shutoff and use an earlier snapshot to keep it stable.
Should I hold off updating for a while until the bug is patched?
How do we know there is a bug?
How was the update performed?
What did the update look like?
What was updated?
From where I sit there is no problem. Fully updated and running the 7.0+ kernel. Reboots fine. But maybe with some more details we could find out what is wrong here.
If in doubt then the link produced from a bugreport has general info for sharing;
sudo cachyos-bugreport.sh
Same issue with kernel 7.0, plasma-login-manager only show a black screen. No issue when booting on LTS kernel.
Edit : Issue appear only on my laptop (Ryzen 5 PRO 5650U) , gaming pc is fine.
I had the same problem only on my ThinkPad T14 G2 laptop with the same APU.
It’s an issue with the amdgpu driver:
journalctl -b -1 -p 3
Apr 19 09:21:26 hovertank kernel: Bluetooth: hci0: Reading supported features failed (-16)
Apr 19 09:21:30 hovertank kernel: amdgpu 0000:07:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Apr 19 09:21:30 hovertank kernel: amdgpu 0000:07:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Apr 19 09:21:30 hovertank kernel: amdgpu 0000:07:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Apr 19 09:21:30 hovertank kernel: amdgpu 0000:07:00.0: [drm] *ERROR* dpcd_set_link_settings:1122: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed
Apr 19 09:21:30 hovertank kernel: amdgpu 0000:07:00.0: [drm] *ERROR* dpcd_set_link_settings:1127: core_link_write_dpcd (DP_LANE_COUNT_SET) failed
Apr 19 09:21:30 hovertank kernel: amdgpu 0000:07:00.0: [drm] *ERROR* dpcd_set_link_settings:1155: core_link_write_dpcd (DP_LINK_BW_SET) failed
Apr 19 09:21:31 hovertank kernel: amdgpu 0000:07:00.0: [drm] *ERROR* dpcd_set_link_settings:1122: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed
Apr 19 09:21:31 hovertank kernel: amdgpu 0000:07:00.0: [drm] *ERROR* dpcd_set_link_settings:1127: core_link_write_dpcd (DP_LANE_COUNT_SET) failed
Apr 19 09:21:31 hovertank kernel: amdgpu 0000:07:00.0: [drm] *ERROR* dpcd_set_link_settings:1155: core_link_write_dpcd (DP_LINK_BW_SET) failed
Apr 19 09:21:32 hovertank kernel: amdgpu 0000:07:00.0: [drm] *ERROR* dpcd_set_link_settings:1122: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed
Apr 19 09:21:32 hovertank kernel: amdgpu 0000:07:00.0: [drm] *ERROR* dpcd_set_link_settings:1127: core_link_write_dpcd (DP_LANE_COUNT_SET) failed
Apr 19 09:21:32 hovertank kernel: amdgpu 0000:07:00.0: [drm] *ERROR* dpcd_set_link_settings:1155: core_link_write_dpcd (DP_LINK_BW_SET) failed
Apr 19 09:21:33 hovertank kernel: amdgpu 0000:07:00.0: [drm] *ERROR* dpcd_set_link_settings:1122: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed
Apr 19 09:21:33 hovertank kernel: amdgpu 0000:07:00.0: [drm] *ERROR* dpcd_set_link_settings:1127: core_link_write_dpcd (DP_LANE_COUNT_SET) failed
Apr 19 09:21:33 hovertank kernel: amdgpu 0000:07:00.0: [drm] *ERROR* dpcd_set_link_settings:1155: core_link_write_dpcd (DP_LINK_BW_SET) failed
Apr 19 09:22:16 hovertank plasma-login-greeter[1206]: Socket error: “QLocalSocket: Remote closed”
Apr 19 09:22:16 hovertank dbus-broker-launch[1058]: Activation request for ‘org.freedesktop.nm_dispatcher’ failed.
Apr 19 09:22:16 hovertank dbus-broker-launch[1058]: Activation request for ‘org.freedesktop.nm_dispatcher’ failed.
Apr 19 09:22:16 hovertank dbus-broker-launch[1058]: Activation request for ‘org.freedesktop.nm_dispatcher’ failed.
Apr 19 09:22:16 hovertank dbus-broker-launch[1058]: Activation request for ‘org.freedesktop.nm_dispatcher’ failed.
having the same problem right now and I think the problems is this:
abr 19 10:07:22 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
abr 19 10:07:23 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
abr 19 10:07:23 kernel: [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:055b:a8aa:390b:006d DST=ff02:0000:0000:0000:0000:0000:0001:0003 LEN=75 TC=0 HOPLIMIT=255 FLOWLBL=917966 PROTO=UDP SPT=5355 DPT=5355 LEN=35
abr 19 10:07:23 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
abr 19 10:07:23 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dpcd_set_link_settings:1122: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed
abr 19 10:07:23 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dpcd_set_link_settings:1127: core_link_write_dpcd (DP_LANE_COUNT_SET) failed
abr 19 10:07:23 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dpcd_set_link_settings:1155: core_link_write_dpcd (DP_LINK_BW_SET) failed
abr 19 10:07:24 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dpcd_set_link_settings:1122: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed
abr 19 10:07:24 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dpcd_set_link_settings:1127: core_link_write_dpcd (DP_LANE_COUNT_SET) failed
abr 19 10:07:24 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dpcd_set_link_settings:1155: core_link_write_dpcd (DP_LINK_BW_SET) failed
abr 19 10:07:25 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dpcd_set_link_settings:1122: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed
abr 19 10:07:25 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dpcd_set_link_settings:1127: core_link_write_dpcd (DP_LANE_COUNT_SET) failed
abr 19 10:07:25 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dpcd_set_link_settings:1155: core_link_write_dpcd (DP_LINK_BW_SET) failed
abr 19 10:07:26 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dpcd_set_link_settings:1122: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed
abr 19 10:07:26 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dpcd_set_link_settings:1127: core_link_write_dpcd (DP_LANE_COUNT_SET) failed
abr 19 10:07:26 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dpcd_set_link_settings:1155: core_link_write_dpcd (DP_LINK_BW_SET) failed
abr 19 10:07:26 kernel: amdgpu 0000:03:00.0: [drm] enabling link 0 failed: 15
abr 19 10:07:26 dbus-broker-launch[1010]: Activation request for ‘org.freedesktop.nm_dispatcher’ failed.
abr 19 10:07:26 NetworkManager[1013]: [1776604046.4275] dispatcher: (14) failed (after 0.001 sec): Could not activate remote peer ‘org.freedesktop.nm_dispatcher’: activation request failed: unit is invalid
abr 19 10:07:26 dbus-broker-launch[1010]: Activation request for ‘org.freedesktop.nm_dispatcher’ failed.
abr 19 10:07:26 dbus-broker-launch[1010]: Activation request for ‘org.freedesktop.nm_dispatcher’ failed.
System info:
Kernel: Linux 6.18.22-1-cachyoss
WM: niri 25.11 (Wayland)
CPU: AMD Ryzen 7 5700U (16) @ 1z
GPU: AMD Lucienne [Integrated]
Today morning i saw black screen too, but problem was in .profile file with empty path catalog, but i understand this too late, i delete all login manager and make fish for autologin plasma directly.
I think closing the laptop and opening it got me to look at the login screen. That might have fixed the buggy graphic driver.
Actually closing the lid and reopening worked for me as well as crazy as that is. I wouldn’t call this “stable” though.
Still a workaround for now.
Same exact issue after updating my Ryzen 5800H laptop to the latest kernel. The lid-closing temporary workaround seems to work for now.
This issue may have to do with KDE sddm
Same issue with a Lenovo ThinkPad P14s. Radeon 7 PRO 5850u with integrated graphics.
Wasn’t SDDM replaced?
I’m experiencing the same issue when running the Bore kernel 7, yet everything works fine with the default kernel. There are no errors appearing in the boot logs. I am running custom build desktop ryzen 5800x, GTX 1080
I have the same issue but it seems to match this thread more closely.
Posting details there to keep things consolidated.
On my Thinkpad T14 Gen 2 AMD the latest Kernel Version 7.0.3-1-cachyos is working as expected again 
Maybe for your devices it’s working too?
Latest update fixed the login screen issue.