DPMS not working on GTX980 with DisplayPort connection

Hi,

I have two displays attached to the GTX980 card: Samsung SA850 is connected via DisplayPort and a Sony TV through HDMI. The problem is with Samsung, it doesn’t turn off in power saving mode. After the idle timeout the screen goes black but the backlight remains on and never turns off. I also tried the ‘sleep 1; xset dpms force off’ command from the console, but result is the same.

I have a dual-boot Windows 7 on the same machine, and on Windows the monitor turns off as expected, so the hardware seems to be fine. I also tried connecting the monitor via DVI-I and it seems to work as well. So the problem is with DisplayPort connection. Is there a way to fix it?

Thanks.

Kubuntu 14.10 x86_64, Xorg 1.16, nvidia driver 346.16

nvidia-bug-report.log.gz (94.5 KB)

Is any other drivers version help you to resolve this issue? Please share EDID of your display. Not sure internally we have exact same Samsung SMS27A850 display to test.

Is any other drivers version help you to resolve this issue?

I shall try 343.22 later. Is there any version I should try in particular?

Please share EDID of your display.

I tried to save EDID in nvidia-settings but it crashed (crashes every time, whether you save to text or binary file). It did save something but I’m not sure the file is complete. I’ll attach it anyway.

samsung_edid.bin.gz (157 Bytes)

Also test with 340.58 . Off the screensaver too and check if this helps
https://wiki.archlinux.org/index.php/Display_Power_Management_Signaling

The 343.22 driver behaves the same, the problem persists. 340.58 doesn’t seem to support Maxwell, so I didn’t install it.

The screen saver and screen lock are disabled in my case, and ‘xset dpms force off’ doesn’t turn off the display, as I mentioned. I tried adding ‘Option “DPMS” “True”’ in my xorg.conf.d but that didn’t help as well (and ‘xset q’ says “DPMS is Enabled” regardless of this option). Disabling screen blanking (‘xset s off’) doesn’t help either.

Generally when this sort of thing happens, it’s because the monitor doesn’t respond properly to the DP power management commands. If you use the xrandr command-line tool’s --off command, does the backlight turn off?

Yes, ‘xrandr --output DP-4 --off’ does disable the monitor properly, although I cannot enable it afterwards with activity or from command line. It seems, the command removes the display from X server layout because afterwards I can see that in the multi-monitor configuration in nvidia-settings the displays lost their positions relative to each other.

I don’t think the problem is in the display because, as I mentioned, it works in Windows and with DVI.

It probably is in the display, actually, since most other displays work. In Windows, the operating system does the equivalent of an xrandr --off right after it triggers DPMS, which explains how the monitor manufacturer may have missed that it doesn’t respond to DP DPMS commands correctly.

Is there a way to confirm that the problem is indeed in the display? Any additional logs?

I’m not an expert in DPMS and DisplayPort protocol, so I don’t quite understand the difference between ‘xrandr --output DP-4 --off’ and ‘xset dpms force off’ on the hardware side. But if there are displays which, as you say, don’t fully support DPMS commands, can you provide an option for the driver to behave similarly to how it works on Windows? Or just always behave that way?

I have the same issue with GTX 970 using driver 346.16 on Ubuntu 14.10.
I have 4 monitors setup 3 on DP and one on HDMI. The issue is that the monitors will not go to sleep unless I force screen lock. “xset dpms force off” shuts only one monitor. This monitor cannot be awaken with mouse movement. I would like to add that My monitors are FHD, QHD, 4k and QHD. When the computer wake-up it is in confused overlapping configuration.

It might help if you could attach the output of nvidia-bug-report.sh.

nvidia-bug-report.sh: https://drive.google.com/file/d/0ByeY7uHIPmjMZGFiWDEwd3J6ajQ/view?usp=sharing

I you notice there are strage mode lines in Xorg.0.log file

[ 67731.976] (II) NVIDIA(0): Setting mode "DP-0: nvidia-auto-select @2560x1440 +1920+0 {ViewPortIn=2560x1440, ViewPortOut=2560x1440+0+0}, HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, DP-4: nvidia-auto-select @2560x1440 +8320+0 {ViewPortIn=2560x1440, ViewPortOut=2560x1440+0+0}"
[ 67732.340] (II) NVIDIA(0): Setting mode "DP-0: nvidia-auto-select @2560x1440 +1920+0 {ViewPortIn=2560x1440, ViewPortOut=2560x1440+0+0}, HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, DP-4: nvidia-auto-select @2560x1440 +8320+0 {ViewPortIn=2560x1440, ViewPortOut=2560x1440+0+0}"
[ 67732.647] (II) NVIDIA(0): Setting mode "DP-0: nvidia-auto-select @2560x1440 +1920+0 {ViewPortIn=2560x1440, ViewPortOut=2560x1440+0+0}, DP-2: nvidia-auto-select @3840x2160 +4480+0 {ViewPortIn=3840x2160, ViewPortOut=3840x2160+0+0}, HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, DP-4: nvidia-auto-select @2560x1440 +8320+0 {ViewPortIn=2560x1440, ViewPortOut=2560x1440+0+0}"

These are not the ones that are specified in xorg.conf

Option         "metamodes" "HDMI-0: nvidia-auto-select +0+0, DP-0: nvidia-auto-select +1920+0, DP-2: nvidia-auto-select +4480+0, DP-4: nvidia-auto-select +8320+0"

I have the same problem

Just notice that it’s because I switched off the dpms feature of my monitor

That seems possible. But given that xrandr can turn off the display, there must be a good way to hook up xrandr to do the work in linux. On the other hand, I wonder if there is a way to convince the display to cooperate.

I have two systems, both running Fedora 19, both show that DPMS is enabled (via ‘xset q’):

  1. one has a G98 Quadro NVS 295 with one Acer K272HUL and one ASUS (2560x1440), driver version 331.67
  2. one has a gtx660 with two Acer K272HUL (2560x1440), driver version 346.47

The first turns off the displays just fine.

The second cannot turn off the display. ‘xset dpms force off’ just blanks the screens, but the backlight remains on. That’s what happens when the screen saver turns off the display. I have tried it with and without a locker and the displays never turn off. I have spent a bunch of time with this system trying to convince it to turn off with dpms, but no luck. xrandr works, but that’s an incomplete description. One of the comments was whether the display itself had dmps enabled, but I don’t see a way to do that with the ACERs.

Any suggestions?

I am having this issue just recently with my 980 Ti and DisplayPort monitor. It actually worked correctly prior to the big update (version 355). It works just fine in Windows with the latest drivers as well.

I’m seeing the same thing with a GTX 670 ever since updating to the 355.06-r1 drivers.
Gentoo, Dell U3014 monitor connected via DP.

My Xorg.0.log file is now filled with:

[296349.058] (–) NVIDIA(GPU-0): DFP-3: disconnected
[296349.058] (–) NVIDIA(GPU-0): DFP-3: Internal TMDS
[296349.058] (–) NVIDIA(GPU-0): DFP-3: 330.0 MHz maximum pixel clock
[296349.058] (–) NVIDIA(GPU-0):
[296349.058] (–) NVIDIA(GPU-0): DELL U3014 (DFP-4): connected
[296349.058] (–) NVIDIA(GPU-0): DELL U3014 (DFP-4): Internal DisplayPort
[296349.058] (–) NVIDIA(GPU-0): DELL U3014 (DFP-4): 960.0 MHz maximum pixel clock
[296349.058] (–) NVIDIA(GPU-0):
[296528.803] (–) NVIDIA(GPU-0): CRT-0: disconnected
[296528.803] (–) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[296528.803] (–) NVIDIA(GPU-0):
[296528.806] (–) NVIDIA(GPU-0): DFP-0: disconnected
[296528.806] (–) NVIDIA(GPU-0): DFP-0: Internal TMDS
[296528.806] (–) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[296528.806] (–) NVIDIA(GPU-0):
[296528.806] (–) NVIDIA(GPU-0): DFP-1: disconnected
[296528.806] (–) NVIDIA(GPU-0): DFP-1: Internal TMDS
[296528.806] (–) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[296528.806] (–) NVIDIA(GPU-0):
[296528.806] (–) NVIDIA(GPU-0): DFP-2: disconnected
[296528.806] (–) NVIDIA(GPU-0): DFP-2: Internal TMDS
[296528.806] (–) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[296528.806] (–) NVIDIA(GPU-0):
[296528.806] (–) NVIDIA(GPU-0): DFP-3: disconnected
[296528.806] (–) NVIDIA(GPU-0): DFP-3: Internal TMDS
[296528.806] (–) NVIDIA(GPU-0): DFP-3: 330.0 MHz maximum pixel clock
[296528.806] (–) NVIDIA(GPU-0):
[296528.807] (–) NVIDIA(GPU-0): DELL U3014 (DFP-4): connected
[296528.807] (–) NVIDIA(GPU-0): DELL U3014 (DFP-4): Internal DisplayPort
[296528.807] (–) NVIDIA(GPU-0): DELL U3014 (DFP-4): 960.0 MHz maximum pixel clock
[296528.807] (–) NVIDIA(GPU-0):

Repeated several dozen times.
The previous driver did not cause entries like this–it only has one set of these entries at initialization.

Reverting to 352.30 driver fixed the problem–so something in the newer driver broke.

Testable simply via:

xset dpms force off

When working, the display blanks and a few seconds later goes into energy saving mode turning off the backlight. With the broken driver, the screen blanks, but the backlight stays on indefinitely.

i have the same issue! GTX 970 with 355.06 driver on Ubuntu 14.04.3 kernel 3.19 and a displayport 1.2 monitor

please fix it!

thanks

Same behaviour with a GTX660Ti and a Dell U2711 (2560x1440) in DisplayPort.

Setup is:

  • Linux (Fedora 22) with kernel 4.1.6-201.fc22.x86_64
  • nvidia drivers (355.11-1) from negativo17 repo (http://negativo17.org/repos/nvidia/fedora-$releasever/$basearch/)
  • GTX660Ti
  • Dell U2711 on DP

With nouveau drivers, blanking screen switch off backlight. Seems to be since 355.xx drivers.

More information:
lspci:

01:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 660 Ti] (rev a1)

lsmod | grep nvidia:

nvidia  8667136  118
drm      331776  6 nvidia

dnf list installed | grep kernel (simplified, v. 4.1.6-201.fc22 everywhere):

kernel.x86_64
kernel-core.x86_64
kernel-devel.x86_64
kernel-headers.x86_64
kernel-modules.x86_64
kernel-modules-extra.x86_64

dnf list installed | grep nvidia (simplified, v. 355.11-1.fc22 everywhere):

akmod-nvidia.x86_64
kmod-nvidia.x86_64
nvidia-driver.x86_64
nvidia-driver-NVML.x86_64
nvidia-driver-libs.x86_64
nvidia-libXNVCtrl.x86_64
nvidia-settings.x86_64

I hope that it helps!

Thanks

which driver version can i use till new drivers will be come with the fix for the problem?