Second monitor black screen

General
1

Hi,

Today I installed CachyOS on my desktop as alternative to test it out.

And after entering suspend or lock screen automatically when in inactivity, the second monitor came back in a black screen.

I tried going back into lock screen again and came back, didnt do anything.

After changing refresh rate multiple times, it came out of black screen.

I know that on PopOS similar issue could have been related to DPMS, but it doesnt seem to be the case here.

❯ xset q
...
DPMS (Display Power Management Signaling):
  Server does not have the DPMS Extension

Any idea what could cause this?

After writing this, paying attention, I had the refresh rate set to 144hz, but after checking it out when it went black screen, it was 60hz, whatever it was, could have reset it. Just not sure why.

2

Could you provide hardware info?

Also, sudo cachyos-bugreport.sh and share the link here

3

What exactly do you need on hardware info?

From that command, doesnt seem to have what you would need.

Because it happened today, and I didnt immediately reported here and I have rebooted already. Log doesnt seem to include that timeline.

Regardless, here you go. 44c93b7

4

It happened again, I run the command, but on the timeline, the only difference was this.

set 21 21:39:13 pc-desktop NetworkManager[801]: <warn>  [1726965553.1001] platform-linux: do-add-ip6-address[2: fe80::2179:41f7:ff70:abc7]: failure 13 (Permission denied - ipv6: IPv6 is disabled on this device)
set 21 21:39:15 pc-desktop NetworkManager[801]: <warn>  [1726965555.1003] platform-linux: do-add-ip6-address[2: fe80::bc79:e885:1c35:694f]: failure 13 (Permission denied - ipv6: IPv6 is disabled on this device)
set 21 21:39:15 pc-desktop wireplumber[2388]: wplua: [string "alsa.lua"]:182: attempt to concatenate a nil value (local 'node_name')
                                              stack traceback:
                                                      [string "alsa.lua"]:182: in function <[string "alsa.lua"]:175>
set 21 21:39:17 pc-desktop NetworkManager[801]: <warn>  [1726965557.1014] platform-linux: do-add-ip6-address[2: fe80::3cf0:d8dd:f747:d379]: failure 13 (Permission denied - ipv6: IPv6 is disabled on this device)
set 21 21:39:18 pc-desktop systemd[1415]: dbus-:1.2-org.gnome.Shell.CalendarServer@4.service: Failed with result 'exit-code'.
set 21 21:39:19 pc-desktop systemd[1415]: dbus-:1.2-org.gnome.Shell.CalendarServer@5.service: Failed with result 'exit-code'.
set 21 21:39:19 pc-desktop gnome-shell[1784]: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.gnome.Shell.CalendarServer': unit failed
                                              
                                              Stack trace:
                                                asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
                                                @resource:///org/gnome/shell/ui/init.js:21:20
                                                
set 21 21:39:19 pc-desktop gnome-shell[1784]: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.gnome.Shell.CalendarServer': unit failed
                                              
                                              Stack trace:
                                                asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
                                                @resource:///org/gnome/shell/ui/init.js:21:20
                                                
set 21 21:39:19 pc-desktop gnome-shell[1784]: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.gnome.Shell.CalendarServer': unit failed
                                              
                                              Stack trace:
                                                asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
                                                @resource:///org/gnome/shell/ui/init.js:21:20
                                                
set 21 21:39:19 pc-desktop gnome-shell[1784]: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.gnome.Shell.CalendarServer': unit failed
                                              
                                              Stack trace:
                                                asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
                                                @resource:///org/gnome/shell/ui/init.js:21:20
                                                
set 21 21:39:19 pc-desktop gnome-shell[1784]: Can't update stage views actor unnamed [StBin] is on because it needs an allocation.
set 21 21:39:19 pc-desktop gnome-shell[1784]: Can't update stage views actor panelActivities [Gjs_ui_panel_ActivitiesButton] is on because it needs an allocation.
set 21 21:39:19 pc-desktop gnome-shell[1784]: Can't update stage views actor unnamed [Gjs_ui_panel_WorkspaceIndicators] is on because it needs an allocation.
set 21 21:39:19 pc-desktop gnome-shell[1784]: Can't update stage views actor unnamed [Gjs_ui_panel_WorkspaceDot] is on because it needs an allocation.
set 21 21:39:19 pc-desktop gnome-shell[1784]: Can't update stage views actor unnamed [StWidget] is on because it needs an allocation.
set 21 21:39:19 pc-desktop NetworkManager[801]: <warn>  [1726965559.1014] ipv6ll[e9a71b86bc751e48,ifindex=2]: changed: no IPv6 link local address to retry after Duplicate Address Detection failures (back off)
set 21 21:39:29 pc-desktop NetworkManager[801]: <warn>  [1726965569.1018] platform-linux: do-add-ip6-address[2: fe80::5342:6ecf:153e:13a7]: failure 13 (Permission denied - ipv6: IPv6 is disabled on this device)
set 21 21:39:29 pc-desktop NetworkManager[801]: <warn>  [1726965569.1018] l3cfg[74b7c83e12bc85ec,ifindex=2]: unable to configure IPv6 route: type unicast fe80::/64 dev 2 metric 1024 mss 0 rt-src ipv6ll
set 21 21:39:31 pc-desktop NetworkManager[801]: <warn>  [1726965571.1019] platform-linux: do-add-ip6-address[2: fe80::5ec2:2a2a:59a:9367]: failure 13 (Permission denied - ipv6: IPv6 is disabled on this device)
set 21 21:39:33 pc-desktop NetworkManager[801]: <warn>  [1726965573.1021] platform-linux: do-add-ip6-address[2: fe80::c786:d025:7463:d12e]: failure 13 (Permission denied - ipv6: IPv6 is disabled on this device)
set 21 21:39:35 pc-desktop NetworkManager[801]: <warn>  [1726965575.1024] platform-linux: do-add-ip6-address[2: fe80::2179:41f7:ff70:abc7]: failure 13 (Permission denied - ipv6: IPv6 is disabled on this device)
set 21 21:39:37 pc-desktop NetworkManager[801]: <warn>  [1726965577.1026] platform-linux: do-add-ip6-address[2: fe80::bc79:e885:1c35:694f]: failure 13 (Permission denied - ipv6: IPv6 is disabled on this device)
set 21 21:39:39 pc-desktop NetworkManager[801]: <warn>  [1726965579.1028] platform-linux: do-add-ip6-address[2: fe80::3cf0:d8dd:f747:d379]: failure 13 (Permission denied - ipv6: IPv6 is disabled on this device)
set 21 21:39:41 pc-desktop NetworkManager[801]: <warn>  [1726965581.1029] ipv6ll[e9a71b86bc751e48,ifindex=2]: changed: no IPv6 link local address to retry after Duplicate Address Detection failures (back off)
set 21 21:39:51 pc-desktop NetworkManager[801]: <warn>  [1726965591.1032] platform-linux: do-add-ip6-address[2: fe80::5342:6ecf:153e:13a7]: failure 13 (Permission denied - ipv6: IPv6 is disabled on this device)
set 21 21:39:51 pc-desktop NetworkManager[801]: <warn>  [1726965591.1033] l3cfg[74b7c83e12bc85ec,ifindex=2]: unable to configure IPv6 route: type unicast fe80::/64 dev 2 metric 1024 mss 0 rt-src ipv6ll
set 21 21:39:53 pc-desktop NetworkManager[801]: <warn>  [1726965593.1034] platform-linux: do-add-ip6-address[2: fe80::5ec2:2a2a:59a:9367]: failure 13 (Permission denied - ipv6: IPv6 is disabled on this device)
set 21 21:39:54 pc-desktop sudo[20726]:  user : a password is required ; TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/true
set 21 21:39:55 pc-desktop NetworkManager[801]: <warn>  [1726965595.1036] platform-linux: do-add-ip6-address[2: fe80::c786:d025:7463:d12e]: failure 13 (Permission denied - ipv6: IPv6 is disabled on this device)
set 21 21:39:57 pc-desktop NetworkManager[801]: <warn>  [1726965597.1048] platform-linux: do-add-ip6-address[2: fe80::2179:41f7:ff70:abc7]: failure 13 (Permission denied - ipv6: IPv6 is disabled on this device)
set 21 21:39:59 pc-desktop NetworkManager[801]: <warn>  [1726965599.1050] platform-linux: do-add-ip6-address[2: fe80::bc79:e885:1c35:694f]: failure 13 (Permission denied - ipv6: IPv6 is disabled on this device)

And the refresh rate did not reset this time.

5

Seems to be definitely related to going into lock screen due to inactivity.

Another thing I noticed today when that happened, after going back to try and log in, the background of the login screen of the monitor that was on, while the other in black screen, was black, but the wallpaper are not black.

Whoever if I manually lock, the actually blurred wallpaper will be there.

It’s just another thing that could provide clue of why.

I had another experience not of black screen, apparently, if you lock screen, the other will appear black blurred background rather than the wallpaper. Maybe it’s a bug.

6

Something I did try and resolve on PopOS before.

sudo systemctl stop nvidia-suspend.service
sudo systemctl stop nvidia-hibernate.service
sudo systemctl stop nvidia-resume.service
sudo systemctl disable nvidia-suspend.service
sudo systemctl disable nvidia-hibernate.service
sudo systemctl disable nvidia-resume.service
sudo sed -i '2 i exit 0' /usr/bin/nvidia-sleep.sh

It seem to have relation to /usr/lib/modprobe.d/nvidia-sleep.conf and NVreg_PreserveVideoMemoryAllocations=1, so, not sure of the draw backs of not having the recovery in place.

Just read this on a wiki

Suspend/wakeup issues 
Enable the services nvidia-suspend.service, nvidia-hibernate.service and nvidia-resume.service, they will be started by systemd when needed.

Add nvidia.NVreg_PreserveVideoMemoryAllocations=1 to your kernel parameters if you haven’t already.

As previously mentioned, suspend functions are currently broken on nvidia-open-dkms due to a bug, so make sure you’re on nvidia-dkms.

https://github.com/NVIDIA/open-gpu-kernel-modules/issues/472

If cachyos are with the open-dkms, then that could be why. @ptr1337

I just tried it out, it went from wayland to x11, I cannot put the monitor at the highest refresh rate and ulmb2 is now active. It seem to have affected the system env vars too. Clearly not the solution expected.

7

Yes, the Hardware Detection will default to the open driver if supported. That is intended since suggested by NVIDIA to us.
The Closed Source driver wont recieve much testing anymore, therefore we dont use it. Since there is already a bug, it should be hopefully fixed in 565

8

I have found a fix and it seems to work.