DP1.2 connected monitor cannot be turned on again with DPMS
Hello, I have the problem that every time when I lock my desktop environment and the monitor is turned off it is not activated again by moving the mouse or pressing any key. Only by switching tty (ctrl+alt+f7) the monitor is turned on again. The problem can easily be reproduced on my pc by connecting from another device per ssh with the following commands: [code]export DISPLAY=:1 xset dpms force off[/code] using afterwards [code]xset dpms force on[/code] has no effect. I tried the following driver version: 340.96, 361.42 (both official repository), 358.16, 364.19 (from graphics-drivers ppa) The problem is not occurring when using nouveau and not on Windows 10. The problem only occurs if the monitor is connect per displayport. (I need displayport for getting 4k@60hz) I could reproduce the problem on the live version of ubuntu (only installed the nvidia driver 361). Moreover I m using ubuntu gnome and could reproduce the problem with gdm3 and lightdm. A probably different issue that occurs after the monitor is restored by using switching tty (ctrl+alt+f7) is that the desktop looks “corrupted”: color of the background on gnome and icons, buttons in unity are messed up (I attach two screen shots of this). My settings: - ubuntu 16.04, - geforce 670 gtx - Samsung U28E590D Thanks for reading!
Hello,

I have the problem that every time when I lock my desktop environment and the monitor is turned off it is not activated again by moving the mouse or pressing any key. Only by switching tty (ctrl+alt+f7) the monitor is turned on again.

The problem can easily be reproduced on my pc by connecting from another device per ssh with the following commands:

export DISPLAY=:1
xset dpms force off



using afterwards

xset dpms force on



has no effect.

I tried the following driver version: 340.96, 361.42 (both official repository), 358.16, 364.19 (from graphics-drivers ppa)

The problem is not occurring when using nouveau and not on Windows 10.

The problem only occurs if the monitor is connect per displayport. (I need displayport for getting 4k@60hz)

I could reproduce the problem on the live version of ubuntu (only installed the nvidia driver 361).
Moreover I m using ubuntu gnome and could reproduce the problem with gdm3 and lightdm.

A probably different issue that occurs after the monitor is restored by using switching tty (ctrl+alt+f7) is that the desktop looks “corrupted”: color of the background on gnome and icons, buttons in unity are messed up (I attach two screen shots of this).


My settings:
- ubuntu 16.04,
- geforce 670 gtx
- Samsung U28E590D

Thanks for reading!

#1
Posted 04/26/2016 05:43 PM   
Hello, I have a nVidia ASUS STRIX GTX970 graphics connected to my DELL U3415W (21:9 ultrawide) via mDP. Having similar issues to the above poster. Running Arch Linux x86_64 with proprietary nVidia drivers 364.19-3 from the official repository. When my monitor goes to sleep, if it is within a short duration it will wake-up immediately. However, if it is off for about 15 minutes, it will not turn back on my moving mouse, pressing keys. Only by switching to a tty like the above user. I've attached the bug report, but I believe there is nothing in it that indicates there is a problem.
Hello,

I have a nVidia ASUS STRIX GTX970 graphics connected to my DELL U3415W (21:9 ultrawide) via mDP. Having similar issues to the above poster. Running Arch Linux x86_64 with proprietary nVidia drivers 364.19-3 from the official repository.

When my monitor goes to sleep, if it is within a short duration it will wake-up immediately. However, if it is off for about 15 minutes, it will not turn back on my moving mouse, pressing keys. Only by switching to a tty like the above user.

I've attached the bug report, but I believe there is nothing in it that indicates there is a problem.

#2
Posted 05/21/2016 09:04 AM   
https://onedrive.live.com/redir?resid=8C16C0F9FE654EC4!533&authkey=!AIIfwRhpaUX1GSE&ithint=file%2cgz - bug report, for some reason site won't upload. Keep seeing this on website: Attachments [SCANNING... PLEASE WAIT] nvidia-bug-report.log.gz
https://onedrive.live.com/redir?resid=8C16C0F9FE654EC4!533&authkey=!AIIfwRhpaUX1GSE&ithint=file%2cgz


- bug report, for some reason site won't upload. Keep seeing this on website:

Attachments

[SCANNING... PLEASE WAIT] nvidia-bug-report.log.gz

#3
Posted 05/21/2016 08:27 PM   
Hi All, Please test with latest 364.19 and 367.18 and share results.
Hi All, Please test with latest 364.19 and 367.18 and share results.

Thanks,
Sandip.

#4
Posted 05/22/2016 07:44 AM   
Update: I installed the latest beta driver, 367.18, and still have the issue. I did some investigating and screen blanking works i.e. black screen after inactivity and moving mouse to wake up the screen. The main issue is that when the monitor is turned off and then turned back on, the GFX card will not detect the monitor. In order to resolve the problem, I need to press CTRL+ALT+F6, switching to TTY6, and then KILL THE XORG SERVER. After this happens, my system detects XOrg isn't working and restarts the display - at which point the monitor starts working again. I'll investigate the issue further and post my bug reports, when I get more time. I think the problem lies somewhere with XOrg and nVidia drivers. Thank you for reading.
Update:

I installed the latest beta driver, 367.18, and still have the issue. I did some investigating and screen blanking works i.e. black screen after inactivity and moving mouse to wake up the screen.

The main issue is that when the monitor is turned off and then turned back on, the GFX card will not detect the monitor.

In order to resolve the problem, I need to press CTRL+ALT+F6, switching to TTY6, and then KILL THE XORG SERVER. After this happens, my system detects XOrg isn't working and restarts the display - at which point the monitor starts working again.

I'll investigate the issue further and post my bug reports, when I get more time.

I think the problem lies somewhere with XOrg and nVidia drivers.

Thank you for reading.

#5
Posted 05/22/2016 06:22 PM   
We are tracking this issue under 200202601
We are tracking this issue under 200202601

Thanks,
Sandip.

#6
Posted 05/23/2016 05:40 AM   
Hello, i also tested 367.18 and the problem is still present. However the corrupted desktop after restoring the monitor with ctrl-alt-f7 seems to be gone. Thanks
Hello,
i also tested 367.18 and the problem is still present. However the corrupted desktop after restoring the monitor with ctrl-alt-f7 seems to be gone.

Thanks

#7
Posted 05/29/2016 10:04 AM   
Looks this issue is very specific to Samsung U28E590D and DELL U3415W which are not available with us. We are not able to repro this issue with other displays like HP spectre 32 - HSTND-5001-A , Dell UP2414Qt , Acer XB281HK , Asus PQ32 and Dell UP321Qt .
Looks this issue is very specific to Samsung U28E590D and DELL U3415W which are not available with us. We are not able to repro this issue with other displays like HP spectre 32 - HSTND-5001-A , Dell UP2414Qt , Acer XB281HK , Asus PQ32 and Dell UP321Qt .

Thanks,
Sandip.

#8
Posted 06/28/2016 03:01 AM   
The ASUS PB278Q also has this issue if you have the ability to test with this monitor.
The ASUS PB278Q also has this issue if you have the ability to test with this monitor.

#9
Posted 06/28/2016 06:36 PM   
Still occurs with 367.27. What could i provide to identify this problem? Would an ssh access help? I could switch my hdd and do a fresh ubuntu 16.04 install.
Still occurs with 367.27. What could i provide to identify this problem? Would an ssh access help? I could switch my hdd and do a fresh ubuntu 16.04 install.

#10
Posted 06/30/2016 07:56 AM   
in the meantime while waiting for a response... i also tested debian jessie with 340.96 where the issue is also reproducible! However when using the legacy driver 304.131 the issue did not occur but 4k resolution is not possible with this driver so not a real solution. Moreover i noticed that sometimes in ubuntu 16.04 the monitor-wakeup works once but fails at the second time.
in the meantime while waiting for a response... i also tested debian jessie with 340.96 where the issue is also reproducible! However when using the legacy driver 304.131 the issue did not occur but 4k resolution is not possible with this driver so not a real solution.

Moreover i noticed that sometimes in ubuntu 16.04 the monitor-wakeup works once but fails at the second time.

#11
Posted 07/14/2016 09:08 AM   
Attempted test with Monitor ASUS PB278Q + Geforce GTX 670 + vBIOS 80.04.19.00.21 + Driver 340.96 + 364.19 (from graphics-drivers ppa) + Ubuntu 16.04 ) --> No Repro. Resolution set to 4k@60hz and DP Stream from monitor settings set to :- DP 1.2 Performed command " xset dpms force off " then waited for 10 mins, 15 mins, 30 mins and moved mouse, observed no black screen able to resume the display. After keeping system in dpms off overnight still not able to repro in black display . Is this repro steps straight forward ? Don't know why we are not hitting this issue? We have testing on fresh OS and Unity desktop. Is there any specific repro sequence to trigger this issue?
Attempted test with Monitor ASUS PB278Q + Geforce GTX 670 + vBIOS 80.04.19.00.21 + Driver 340.96 + 364.19 (from graphics-drivers ppa) + Ubuntu 16.04 ) --> No Repro.
Resolution set to 4k@60hz and DP Stream from monitor settings set to :- DP 1.2
Performed command " xset dpms force off " then waited for 10 mins, 15 mins, 30 mins and moved mouse, observed no black screen able to resume the display.

After keeping system in dpms off overnight still not able to repro in black display .

Is this repro steps straight forward ? Don't know why we are not hitting this issue? We have testing on fresh OS and Unity desktop. Is there any specific repro sequence to trigger this issue?

Thanks,
Sandip.

#12
Posted 07/18/2016 01:02 PM   
Hello, Try testing with those monitors but with a GTX 1080. Try and do anything DPMS related when they are connected via DisplayPort.
Hello,

Try testing with those monitors but with a GTX 1080. Try and do anything DPMS related when they are connected via DisplayPort.

#13
Posted 07/19/2016 03:19 AM   
Hello, i also tested 367.35 and its still present. To reproduce the problem i perform the following steps: - install a fresh system ( i tested normal ubuntu 16.04, ubuntu gnome 16.04 or debian jessie 8.5) or use the ubuntu live media version with persistence - i update all packages but this can be omitted - install the nvidia-driver (4k@60Hz by default) - at this point dpms is working since the system still uses nouveau - i perform a reboot so that the nvidia driver is active - i type: xset dpms force off -> screen becomes black and after 2-3s the monitor goes in standby by moving the mouse or pressing a key the monitor turns on again. - i repeat this: xset dpms force off -> screen becomes black and after 2-3s the monitor goes in standby now the monitor isn't turned on again (doesn't matter if i wait here or not!) until pressing ctrl+alt+f7 I can still provide ssh access and moreover a skype video session with my laptop so that you could see the monitor. Would a video where i start from a live session until the problem occurs help you to further understand the problem? (i mean a real video showing the monitor not a screen recored)
Hello,
i also tested 367.35 and its still present.

To reproduce the problem i perform the following steps:
- install a fresh system ( i tested normal ubuntu 16.04, ubuntu gnome 16.04 or debian jessie 8.5)
or use the ubuntu live media version with persistence
- i update all packages but this can be omitted
- install the nvidia-driver (4k@60Hz by default)
- at this point dpms is working since the system still uses nouveau
- i perform a reboot so that the nvidia driver is active
- i type: xset dpms force off -> screen becomes black and after 2-3s the monitor goes in standby
by moving the mouse or pressing a key the monitor turns on again.
- i repeat this: xset dpms force off -> screen becomes black and after 2-3s the monitor goes in standby
now the monitor isn't turned on again (doesn't matter if i wait here or not!) until pressing ctrl+alt+f7


I can still provide ssh access and moreover a skype video session with my laptop so that you could see the monitor.
Would a video where i start from a live session until the problem occurs help you to further understand the problem? (i mean a real video showing the monitor not a screen recored)

#14
Posted 07/19/2016 10:40 AM   
checked with new fresh install ubuntu 16.04 + GTX 1080 + HP Spectre 32 ( 4k@60 Hz ) attempted 30 time xset dpms force off, still not able to repro, will check for similar monitor ASUS PB278Q Also Tested with ASUS PB278Q , EFI mode ubuntu 16.04 , same config not able to repro.
checked with new fresh install ubuntu 16.04 + GTX 1080 + HP Spectre 32 ( 4k@60 Hz )
attempted 30 time xset dpms force off, still not able to repro, will check for similar monitor ASUS PB278Q
Also Tested with ASUS PB278Q , EFI mode ubuntu 16.04 , same config not able to repro.

Thanks,
Sandip.

#15
Posted 08/09/2016 03:31 AM   
Scroll To Top

Add Reply