One Monitor Doesn't Wake from Sleep Mode

lyntux · 2020-10-24 18:04:17

I'm running KDE on a system with an Nvidia GPU. After an update a few weeks ago one of my monitors occasionally doesn't wake from sleep mode. To be clear, my computer doesn't go to sleep, or hibernate, just the monitors sleep to save power. This happens at least 50% of the time after the monitors go to sleep.

Things that temporarily fix the issue:

Unplugging power or the HDMI cable to the monitor and plugging it back in to force detection works to fix the monitor.
I have also noticed that if I wake up the monitors to do something when the monitor is not working then letting them go to sleep again will sometimes fix the problem as well.
Logging out causes the problem to resolve itself on the log in screen as well.

I'm on a modern kernel, 5.9.1, and running the latest Nvidia drivers. I saw the post on the home page about Nvidia and Linux 5.9, but I don't expect that has anything to do with my problem. I'm just doing basic desktop and web tasks in KDE.

I'm not sure what to do/check next to start resolving this problem.

CheeseEBoi · 2020-11-01 22:43:05

I have had the exact same issue on XFCE. My display port monitor seems to work fine yet the HDMI will sometimes just not turn back on. Either way, I'm pretty sure it is a direct kernel issue rather than anything else.

Using linux-lts for now, if that advice helps.

Last edited by CheeseEBoi (2020-11-01 22:43:32)

Smoerrebroed · 2020-11-02 06:19:55

Same issue here. Putting the system in standby and waking it up right afterwards usually helps.

lyntux · 2020-11-02 23:53:24

Still don't have a solution for this yet. I'm just powering my monitor down and back up to get my system to re-re-detect it and get it working again. Hopefully, some can make a suggestion as to what's causing the issue.

CheeseEBoi · 2020-11-03 15:30:45

I would like to amend my statement earlier as I realized that this also occurs on the lts kernel. Can it be confirmed that everyone in this thread/having this issue is using NVIDIA?

supa · 2020-11-26 03:12:40

Yes, happens to me using nvidia and Mate.

Started roughly a month or so ago for me.

Still happening for me with updates from today.

$ pacman -Q linux
linux 5.9.10.arch1-1

$ pacman -Q nvidia
nvidia 455.45.01-2

$ pacman -Q mate-panel
mate-panel 1.24.1-1

01:00.0 VGA compatible controller: NVIDIA Corporation GP108 [GeForce GT 1030] (rev a1) (prog-if 00 [VGA controller])

Last edited by supa (2020-11-26 03:18:36)

V1del · 2020-11-26 09:18:58

Try disabling HardDPMS with e.g. /etc/X11/xorg.conf.d/20-nvidia.conf

  Section "OutputClass"
    Identifier "nvidia"
    MatchDriver "nvidia-drm"
    Driver "nvidia"
    Option "HardDPMS" "false"
EndSection

Last edited by V1del (2020-11-26 09:21:14)

supa · 2020-11-26 14:42:51

V1del wrote:

Try disabling HardDPMS with e.g. /etc/X11/xorg.conf.d/20-nvidia.conf
  Section "OutputClass"
    Identifier "nvidia"
    MatchDriver "nvidia-drm"
    Driver "nvidia"
    Option "HardDPMS" "false"
EndSection

Thanks for this but initial testing doesn't appear to have helped for my problem. I'm now also not sure I'm having the same exact problems as others as unplugging and replugging HDMI does not fix it for me. I need to ctrl+alt+f2 and then ctrl+alt+f7 to get my video back.

I've also confirmed it's picked up the option:

$ grep DPMS /var/log/Xorg.0.log
[ 49230.273] (**) NVIDIA(0): Option "HardDPMS" "false"
[ 49230.670] (==) NVIDIA(0): DPMS enabled
[ 49230.672] (II) Initializing extension DPMS

Last edited by supa (2020-11-26 14:43:44)

Zeioth · 2020-12-04 21:43:54

I also suffer this issue on nvidia with I3 using two monitors, one DP and one HDMI. The HDMI is the one that doesn't turn on unless I do F2-F7. If I switch the ports of both devices, the one to fail is always the HDMI.

Can someone confirm if the issue fixes by using 2 DP cables instead of HDMI+DP?

Last edited by Zeioth (2020-12-04 21:55:01)

Zeioth · 2020-12-04 22:14:01

[deleted]

Last edited by Zeioth (2020-12-04 22:24:15)

wildnux · 2020-12-22 03:20:21

I have this issue with 5.4.84-1-lts kernel as well. In my case, I have thunderbolt to 2 displayport split adapter. One monitor never comes back up from sleep and I have to unplug and plug the thunderbolt adapter out and back in.

t54r · 2021-01-16 20:11:25

Same issue with the following specs:
5.10.7 kernel
xmonad as WM
2x DP, Nvidia graphics card.
If both the displays go into power saving mode doing things won't wake them, but the system underneath is active (I can for example run shutdown now, and the PC will power off).
Going to the x-less terminal helps
I can also disable the displays from xrandr and enable them again and they will start working again - but I need to power them on/off in xrandr, simply changing the geometry won't help.
If I power off and then power on one of the displays, the same thing happens, but only to it.

olivos22 · 2021-02-10 22:52:59

Same problem here, I just change the orientation of my monitor that isn't responding in Display Configuration to make it work again.

thrtx · 2021-03-11 10:40:41

I'm having the same issue as well:

i3 on laptop with two external screens. One screen will not wake from sleep. I kill X and login again and it picks up my xrandr command from .xinitrc. The offending monitor will not wake from it's own sleep mode, unless I wake it manually (via power switch) and then run startx quickly.

I should mention I have hybrid graphics (NVIDIA/Intel) on a laptop, and with one external monitor it worked fine. I think I didn't have a problem in the past because I was only using the Intel for the external monitor. The second external monitor most likely uses the discrete graphics GPU so this is probably an NVIDIA issue the same as others in the thread.

$ pacman -Q linux
linux 5.11.4.arch1-1

$ pacman -Q nvidia
nvidia 460.56-4

Edit: current workaround is to wake monitor from sleep via its power button before I wake computer. If I wake the computer before the monitor goes back to sleep it seems fine.

Maybe there's a problem with the power down on the nvidia driver such that it fails to send a wake up signal in time?

Last edited by thrtx (2021-03-11 23:51:50)

thrtx · 2021-03-19 06:51:49

I think this issue might be related to the following thread:

https://bbs.archlinux.org/viewtopic.php?id=261225

if you run:
$journalctl -p 3 -xb

look for:

kernel: snd_hda_codec_hdmi hdaudioC0D2: Monitor plugged-in, Failed to power up codec ret=[-13]

NOTE: make sure the problem has occurred in the current boot otherwise it may not show up in journalctl.

t54r · 2021-04-21 09:15:06

Running

xset s off

fixes the issue for the duration of the X Session for me, so I've added it to my .xinitrc

Ninpo · 2022-02-18 01:34:45

Apologies for the necro but this is the first time in a long time I've had a solid hit searching Google for this problem.

I've been plagued by this for years, I even jumped from Arch to Gentoo to see if the problem went away (it didn't) nor did it go away with a change of graphics card. I did have an Nvidia 760 I now have a 1660. Proprietary nvidia driver.

However my issue is not hdmi related. On the old card I had 2x DVI and 1x DP and on the current one it's all DisplayPort. Dell P2715Q is the monitor that is always affected by the issue where after a few days of uptime, the monitor won't wake up from sleep. My own solution is to ctrl+alt+f1 then back to X, log in and run the xrandr configuration for my monitors in ~/.xprofile again, this usually restores the monitor to normal and re-arranges my i3 screens correctly.

Eventually the monitor won't even wake up with this approach. It might respond again if I power cycle it or reconnect the DP connection but eventually the only longer term solution is to restart X as xrandr starts returning invalid display mode 3840x2160. Then I'll have a few days of waking up fine before the whole cycle begins again.

Current nvidia driver is 510.47.03 on kernel 5.15.19 but it's happened across so many nvidia driver versions in all the 4xx releases and kernels as far back as I can remember I don't think it matters. I'm using Plasma with i3 as my WM if that's of any relevance.

I have a usb webcam of a logitech variety connected, I don't use the sound on the graphics card or have anything connected to the card beyond 3x DP devices. 2 Dell, 1 ThinkVision.

I actually wonder if it's a monitor firmware issue since the only constant in all this is the Dell P2715Q on displayport and it's been on both normal and the micro connector variety. Perhaps some monitors and nvidia have some issue here?

Last edited by Ninpo (2022-03-14 20:03:54)

usui · 2022-02-18 09:45:50

Hi Ninpo,

I had this issue today for the first time even though I've been using Arch for many years. I often have the issue that the screens are incorrectly arranged after coming out of standby (but they all work) which I usually
resolve by running:

[xxxxx]$ xrandr --output DisplayPort-1 --left-of DVI-0 --auto

I have 2 HDMI and 1 DP monitors connected and the DP failed to wake up this time (3x Dell U2311H).
I initially tried to switch to the virtual console but this didn't affect the DP monitor.
The way I got out of it was by forcing all my monitors to shut off with this command:

[xxxxx]$ xset -display :0.0 dpms force off

My screens became black but when I hit Ctrl+ALT+F3 I had output on all three screens.
When I returned to X with Ctrl+ALT+F1 all three monitors continued to work.

Just thought you'd like to know.

Regards,

Usui

thrtx · 2022-02-28 22:21:17

This problem seems to have gone away in the latest update.

Not sure if this will be shared by people with similar setups, but I can now sleep/resume my laptop with hybrid graphics and both external monitors will wake up properly.

nvidia 510.54-2
linux 5.16.10.arch1-1

Last edited by thrtx (2022-02-28 22:22:06)

FrostedCookies · 2022-03-14 19:46:07

I also have this problem.
OS: I am using 5.16.14-arch1-1 and the nvidia package using 510.54, on KDE/xorg
HW: I have a ryzen 5600x, evga nvidia 1660 ti, and 2 LG panels.
Monitor 1: The first LG panel is a 27GL83A-B in landscape mode, 2560@144hz plugged into the DP -- primary display
Monitor 2: The second LG panel is a 32UD59-B in portrait mode (Left rotation) 3840x2160@60hz

My issue is that Monitor 2 even at boot time only sometimes works (always works in Windows). It will beep as though it is getting a signal but remain black and power down. But other times it loads up okay! Sometimes there's an issue with rotation at SDDM but most of the time it will correct itself (when it works). After it falls asleep it only rarely comes back on okay. (again works fine in Windows)
I have tried doing the alt-F2 -> alt-F1 trick. Rarely it will cause the second monitor to come on, but sometimes I just have to reboot. The only solution I have found that tends to reliably get the monitor back on is to lower the refresh of the panel in display settings to 24hz, then bump it back up to 60hz and it will stay on. I'm not sure if there's a way to automate this though so I don't have to do it every time it wakes up. Once in a while even this trick doesn't work but mostly it does. Very frustrating and no clear way to fix it.

Edit: replaced my 1660ti with an rtx 2070. When plugged into the HDMI port, I have the same issue with the second monitor (now on Nvidia 525 drivers as well, still hasn't fixed it), however, when using both monitors on display port, both monitors seems to wake up just fine (now using Pop_OS). Seems like it's an issue with HDMI. Haven't tried on Wayland w/ HDMI yet to see if somehow wayland compositors don't have the same issue that xorg does.

Last edited by FrostedCookies (2022-12-12 17:05:10)

Ninpo · 2022-03-14 20:03:13

Does everyone having this issue have it with a 4K monitor?

oversize · 2022-03-31 11:55:23

I do have the same issue as well. I always can help myself by Ctrl+alt+F2 to wake the screen up and then get back in X.
I am using Manjaro though with 5.15.28-1-MANJARO on awesome-wm. I do have KDE installed as well and dont have any issues there ... its only when i am in awesome-wm that this happens.

Laptop is a Dell XPS 15 9510 with an nvidia GeForce RTX 3050.
The external monitor is plugged in with a usb-c to DisplayPort cable. (IIyama ProLite XB3270); no 4k

So nothing new from me, but wanted to jump in anyhow.

  inxi -G
  Use of uninitialized value in concatenation (.) or string at /usr/bin/inxi line 13841.
  Graphics:
    Device-1: Intel TigerLake-H GT1 [UHD Graphics] driver: i915 v: kernel
    Device-2: NVIDIA GA107M [GeForce RTX 3050 Mobile] driver: N/A
    Device-3: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo
    Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting
      gpu: i915 s-res: 4480x1440~Hz resolution: 1: 2560x1440 2: 1920x1200
    OpenGL: renderer: Mesa Intel UHD Graphics (TGL GT1) v: 4.6 Mesa 21.3.7

Ninpo · 2022-03-31 12:03:43

oversize wrote:

I do have the same issue as well. I always can help myself by Ctrl+alt+F2 to wake the screen up and then get back in X.
I am using Manjaro though with 5.15.28-1-MANJARO on awesome-wm. I do have KDE installed as well and dont have any issues there ... its only when i am in awesome-wm that this happens.
Laptop is a Dell XPS 15 9510 with an nvidia GeForce RTX 3050.
The external monitor is plugged in with a usb-c to DisplayPort cable. (IIyama ProLite XB3270); no 4k
So nothing new from me, but wanted to jump in anyhow.
  inxi -G
  Use of uninitialized value in concatenation (.) or string at /usr/bin/inxi line 13841.
  Graphics:
    Device-1: Intel TigerLake-H GT1 [UHD Graphics] driver: i915 v: kernel
    Device-2: NVIDIA GA107M [GeForce RTX 3050 Mobile] driver: N/A
    Device-3: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo
    Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting
      gpu: i915 s-res: 4480x1440~Hz resolution: 1: 2560x1440 2: 1920x1200
    OpenGL: renderer: Mesa Intel UHD Graphics (TGL GT1) v: 4.6 Mesa 21.3.7

I'm not familiar with awesome-wm is it based on i3 or use any similar principles? Lots of mentions of i3 from other users in this thread.

I can give going back to full KDE/Plasma a shot when I can summon the will to lose a tiling WM for a bit.

oversize · 2022-03-31 13:13:48

Its only similar in concepts not in code, afaik. I've read somewhere awesome was at some point a fork (?) of dwm, with the idea to have a more human friendly configuration syntax (the lua language).

Since someone in this thread mentioned snd_hda and i have a ridiculous amount of sound cards listed from "aplay -L" i somehow suspect the sound of the monitor to be an issue, but i have no evidence that really suggests that.

MordecaiShalom · 2024-11-08 22:31:07

UPDATE ONE MONTH LATER:
Hello again, decided to give Arch a try as I really wanted to get to the root cause of this issue.

Research:
Found this thread on discuss.kde.org https://discuss.kde.org/t/second-displa … a-x11/4388

From here, I powered off my computer, and powered it back on and both screens were working. Per the discussion, I set one tab in Konsole to monitor `kscreen-console` output. I opened another tab, and ran `xrandr`. The HDMI -> DP monitor switched to a wonky resolution and reported a different (and incorrect) table of resolutions.

I toggled the KVM (simulates turning off the monitor or unplugging it) toggled it back, and the HDMI -> DP monitor was off.

What `kscreen-console` reported was similar to what they report on this thread.

```
Id: 478
Name: "HDMI-0"
Type: "Unknown"
Connected: false
```

From reading the thread they suggested a hardware issue. So I changed adapters, but also changed cables. I swapped the DP cable to the direct DP output and connected that cable to the adapter.

Powered off the computer, powered it back on and now the system is working fine. I'm thinking the DP cable I was using is borderline failing and on re-init, it isn't properly detecting the monitor through the adapter.

PRIOR POST:
It's awesome to run across the thread and hopefully the research I've done can help someone in the future.

HW:
Ryzen 5 2600
32 GB RAm
Nvidia 1660 TI

From my video card I have a display port cable and and HDMI to display port adapter going to a dual DP KVM. From the KVM it goes to 2 Dell 22" 1080p monitors.

Any arch based distro with plasma (and likely window managers using similar backend) when the monitors sleep or I switch the KVM the HDMI output (through the DP adapter which I tried several of those as well thinking that was the problem) will not recover, and it gets stuck running super slow.

Arch + Gnome shell however worked fine.

Fedora distros + Plasma same thing, second monitor wouldn't come on.
Gnome shell worked fine.

Solus Linux plasma also didn't work. The HDMI to DP adapter pulled an awesome truck of being stuck in 1024x768. Didn't even bother trying to sleep switch KVM.

Did try budgie, which I believe is gnome shell 2? That worked with the latest kernel in Solus and the Nvidia loader. Not a fan of budgie, kept moving on.

Kaos (which is an independent arch fork) plasma worked fine, monitors slept fine and KVM worked. Lack of direct support for steam however had me keep looking.

Nixos worked fine with plasma. Got steam working, and since I have personal apps in flatpaks in my user space I don't have to reinstall a lot.

However I noticed severe lag, system ran slow (which I don't understand with the specs I have)

Tried another arch distro, rebornos. Same issue except worse. Plasma wouldn't even boot.

Tried Wayland and X.org has same results. Wouldn't boot into plasma. Installed gnome shell thinking I'd give that a try.

Still can't stand the UX. I've tried using extensions as well to make it for my paradigm, find them super buggy, and still not as customizable as plasma.

Xfce in that distro however worked fine, which means it likely would in other problem distros.

Tried mint with its cinnamon desktop.
Worked fine.

So I tried installing Debian 12.5 with plasma 5.x

It works fine.

I'm still not sure what combination of plasma, Nvidia driver and Linux kernel causes the issue or which of the three is the root cause.

But it appears to have been introduced after the stable software in Debian 12.5

Last edited by MordecaiShalom (2024-12-04 19:44:55)

Arch Linux

#1 2020-10-24 18:04:17

One Monitor Doesn't Wake from Sleep Mode

#2 2020-11-01 22:43:05

Re: One Monitor Doesn't Wake from Sleep Mode

#3 2020-11-02 06:19:55

Re: One Monitor Doesn't Wake from Sleep Mode

#4 2020-11-02 23:53:24

Re: One Monitor Doesn't Wake from Sleep Mode

#5 2020-11-03 15:30:45

Re: One Monitor Doesn't Wake from Sleep Mode

#6 2020-11-26 03:12:40

Re: One Monitor Doesn't Wake from Sleep Mode

#7 2020-11-26 09:18:58

Re: One Monitor Doesn't Wake from Sleep Mode

#8 2020-11-26 14:42:51

Re: One Monitor Doesn't Wake from Sleep Mode

#9 2020-12-04 21:43:54

Re: One Monitor Doesn't Wake from Sleep Mode

#10 2020-12-04 22:14:01

Re: One Monitor Doesn't Wake from Sleep Mode

#11 2020-12-22 03:20:21

Re: One Monitor Doesn't Wake from Sleep Mode

#12 2021-01-16 20:11:25

Re: One Monitor Doesn't Wake from Sleep Mode

#13 2021-02-10 22:52:59

Re: One Monitor Doesn't Wake from Sleep Mode

#14 2021-03-11 10:40:41

Re: One Monitor Doesn't Wake from Sleep Mode

#15 2021-03-19 06:51:49

Re: One Monitor Doesn't Wake from Sleep Mode

#16 2021-04-21 09:15:06

Re: One Monitor Doesn't Wake from Sleep Mode

#17 2022-02-18 01:34:45

Re: One Monitor Doesn't Wake from Sleep Mode

#18 2022-02-18 09:45:50

Re: One Monitor Doesn't Wake from Sleep Mode

#19 2022-02-28 22:21:17

Re: One Monitor Doesn't Wake from Sleep Mode

#20 2022-03-14 19:46:07

Re: One Monitor Doesn't Wake from Sleep Mode

#21 2022-03-14 20:03:13

Re: One Monitor Doesn't Wake from Sleep Mode

#22 2022-03-31 11:55:23

Re: One Monitor Doesn't Wake from Sleep Mode

#23 2022-03-31 12:03:43

Re: One Monitor Doesn't Wake from Sleep Mode

#24 2022-03-31 13:13:48

Re: One Monitor Doesn't Wake from Sleep Mode

#25 2024-11-08 22:31:07

Re: One Monitor Doesn't Wake from Sleep Mode

Board footer