Black screen after display disconnection (wayland + nvidia)

Hi !

Here is what I believe is happening: When my screen is turned off for a long enough time, my display goes in stand by mode, and it can’t recover an active screen afterward. In case the computer goes fully to sleep, this issue doesn’t come up.

System:

  • CPU: AMD Ryzen 9 7950X3D
  • GPU rtx 4080 SUPER
  • DE: Plasma 6 (wayland)
  • DM: sdd (also tried ly)
  • Bootloader: systemd-boot
  • HDMI 2.1

What I have tried:

  • sudo systemctl enable nvidia-suspend.service
  • sudo systemctl enable nvidia-hibernate.service
  • sudo systemctl enable nvidia-resume.service
  • Creating /etc/modprobe.d/nvidia.conf with:
    options nvidia NVreg_PreserveVideoMemoryAllocations=1
  • Adding nvidia_drm.modset=1 to the boatloader (/boot/loader/entries/*.conf)

This allowed me to resume from sleep without problem, but the display shutdown issue still persist.

Happening on HE with Legion Go (so no nvidia shenanigans going on) too. If the screen turns off due to inactivity in Power Management settings, the screen stays off even when it should wake up after activity was detected

same situation with 5950x +4090, even i turn on pc with screen off.

Try the LTS kernel. The nvidia drivers and the 6.11 kernel is busted and I have yet to find anything to fix it.

Same issue there sadly

What I have done to tide me over is adjust the Power Management settings to directly sleep after some inactivity, and only dim the screen instead of turning it off.

Hi ! I use the same workaround for the moment. I was hoping the latest kernel and driver update would solve the issue, but it is still there.

It is really annoying when working with a KVM switch…

I am completely losing my mind with this issue.

If the sleep is manually triggered, resuming works as expected.

If the computer falls a sleep after the timer (or sleeps long enough?) When reaching the logging screen inputting the right password doesn’t work.

Switching user and login in also freezes the screen completely.

That does in fact sound a lot like the other thread that I linked to this one. I would assume it’s two different issues that come into play one after the other but I’m not quite sure.

Every kernel and nvidia driver update I give it a shot but still nothing…

Just found this thread. I’m having same issue still with 6.12 and latest drivers. Guess I will continue to use the LTS kernel.