DPMS Standby not working with NVS 810 using driver 375.26 via mini-DP to DVI

Graphics / Linux Linux
1

I recently switched from an AMD Radeon HD 7870 Eyefinity 6(6 x mini-DP) using the proprietary catalyst driver to an Nvidia NVS 810 (8 x mini-DP) using the proprietary nvidia driver. Since the switch, when I try to put my monitors in stand-by they go to black but the LED backlight stays on with the monitor status lights indicating an active connection(they go amber when in stand-by). The nouveau driver appears to work just fine, however afterwards I switched to the nvidia driver which has caused the nouveau driver to become blacklisted.

I have uploaded my nvidia-bug-report.log.gz here:

[url]https://drive.google.com/open?id=0ByJffg-2C-nkMFkydWVXY1o0cDg[/url]

This is on Fedora 25 with all updates applied at time of posting.

It looks like many other users are having issues based on searching through the various forum posts here, but since they are using cards with multiple output types the blame seems to get placed on random culprits.

Since I came from the 7870 card which had DPMS working with the same exact mini-DP to DVI adapters and monitors with the only change being the graphics card and drivers signs would point to the driver being the issue. This is especially evident when the nouveau driver handles DPMS just fine.

I really hope a resolution is found for this issue. Going from AMD to Nvidia, running 6 1080p monitors off the same GPU(technically 2 in 1) on linux I can say has been an eye opener, the performance is day and night; much smoother, much better performance. The “SLI Mosaic” option works great with the NVS 810. In short, kickass card for monitor arrays on Linux.

The only issue I’ve found is this DPMS problem so I would love to see it fixed. Any assistance would be appreciated, more logs/output can be given as needed.

2

I’m having a similar issue, if not the same. Previously, it was working fine, but since 375 or so, the monitor won’t take the signal. I’m using Debian and an GF119 [NVS 310] (rev a1); I’m also patching DisplayPort through a KVM; but it’s previously worked fine, and works fine when i’m switched to the Dell/Windows laptop.
Even Ctrl+Alt+F7/F1 switch to console and back does nothing under 375; previous versions that could get the monitor started back up.

These kinds of issues are why I quit buying nvidia years ago. Good hardware, but poor support.

3

I am also more or less in a similar situation . i have NVS 810 with 8 x Mini-DP connected to 8 Monitors ( where 5 x Mini-DP to DP and 3 x Mini-DP to DVI )

Monitors Max Resolutions --all at 60Hz :

1920 x 1200 ( 2 x Dell U2412Mb 24 inch monitors )
1920 x 1080 ( 2 x Dell G2410t 24 inch monitors )
1920 x 1080 ( 1 x Dell P2412Hb 24 inch monitor )
1920 x 1080 ( 3 x HP E221 22 inch monitors )

When i connect the card to windows server 2012 R2 with 375.26 , all 8 monitors are detected and are not blank

When i move them to the UBUNTU 16.04.1 system with 375.26 , all 8 monitors are active but only 4 are live and the other 4 are blank even though they are active. The Blank monitors are on GPU# 1 ( 3 x Mini-DP to DVI and 1 x mini-DP to DP )

On UBUNTU 16.04.1 (Linux) when i run the command: nvidia-xconfig --query-gpu-info i get

Number of GPUs: 2

GPU #0:
Name : NVS 810
UUID : GPU-a60fdc1e-8949-5b40-cbe4-2499f729f6ba
PCI BusID : PCI:10:0:0

Number of Display Devices: 4

Display Device 0 (TV-4):
EDID Name : DELL U2412M
Minimum HorizSync : 30.000 kHz
Maximum HorizSync : 83.000 kHz
Minimum VertRefresh : 50 Hz
Maximum VertRefresh : 61 Hz
Maximum PixelClock : 170.000 MHz
Maximum Width : 1920 pixels
Maximum Height : 1200 pixels
Preferred Width : 1920 pixels
Preferred Height : 1200 pixels
Preferred VertRefresh : 60 Hz
Physical Width : 520 mm
Physical Height : 320 mm

Display Device 1 (TV-5):
EDID Name : DELL U2412M
Minimum HorizSync : 30.000 kHz
Maximum HorizSync : 83.000 kHz
Minimum VertRefresh : 50 Hz
Maximum VertRefresh : 61 Hz
Maximum PixelClock : 170.000 MHz
Maximum Width : 1920 pixels
Maximum Height : 1200 pixels
Preferred Width : 1920 pixels
Preferred Height : 1200 pixels
Preferred VertRefresh : 60 Hz
Physical Width : 520 mm
Physical Height : 320 mm

Display Device 2 (TV-6):
EDID Name : HP E221
Minimum HorizSync : 24.000 kHz
Maximum HorizSync : 94.000 kHz
Minimum VertRefresh : 50 Hz
Maximum VertRefresh : 76 Hz
Maximum PixelClock : 170.000 MHz
Maximum Width : 1920 pixels
Maximum Height : 1080 pixels
Preferred Width : 1920 pixels
Preferred Height : 1080 pixels
Preferred VertRefresh : 60 Hz
Physical Width : 500 mm
Physical Height : 290 mm

Display Device 3 (TV-7):
EDID Name : HP E221
Minimum HorizSync : 24.000 kHz
Maximum HorizSync : 94.000 kHz
Minimum VertRefresh : 50 Hz
Maximum VertRefresh : 76 Hz
Maximum PixelClock : 170.000 MHz
Maximum Width : 1920 pixels
Maximum Height : 1080 pixels
Preferred Width : 1920 pixels
Preferred Height : 1080 pixels
Preferred VertRefresh : 60 Hz
Physical Width : 500 mm
Physical Height : 290 mm

GPU #1:
Name : NVS 810
UUID : GPU-c6868dfd-a173-3b97-dc75-0e11d179f311
PCI BusID : PCI:12:0:0

Number of Display Devices: 4

Display Device 0 (TV-0):
EDID Name : DELL G2410
Minimum HorizSync : 30.000 kHz
Maximum HorizSync : 83.000 kHz
Minimum VertRefresh : 56 Hz
Maximum VertRefresh : 76 Hz
Maximum PixelClock : 170.000 MHz
Maximum Width : 1920 pixels
Maximum Height : 1080 pixels
Preferred Width : 1920 pixels
Preferred Height : 1080 pixels
Preferred VertRefresh : 60 Hz
Physical Width : 530 mm
Physical Height : 300 mm

Display Device 1 (TV-1):
EDID Name : DELL G2410
Minimum HorizSync : 30.000 kHz
Maximum HorizSync : 83.000 kHz
Minimum VertRefresh : 56 Hz
Maximum VertRefresh : 76 Hz
Maximum PixelClock : 170.000 MHz
Maximum Width : 1920 pixels
Maximum Height : 1080 pixels
Preferred Width : 1920 pixels
Preferred Height : 1080 pixels
Preferred VertRefresh : 60 Hz
Physical Width : 530 mm
Physical Height : 300 mm

Display Device 2 (TV-2):
EDID Name : DELL P2412H
Minimum HorizSync : 30.000 kHz
Maximum HorizSync : 83.000 kHz
Minimum VertRefresh : 56 Hz
Maximum VertRefresh : 76 Hz
Maximum PixelClock : 170.000 MHz
Maximum Width : 1920 pixels
Maximum Height : 1080 pixels
Preferred Width : 1920 pixels
Preferred Height : 1080 pixels
Preferred VertRefresh : 60 Hz
Physical Width : 530 mm
Physical Height : 300 mm

Display Device 3 (TV-7):
EDID Name : HP E221
Minimum HorizSync : 24.000 kHz
Maximum HorizSync : 94.000 kHz
Minimum VertRefresh : 50 Hz
Maximum VertRefresh : 76 Hz
Maximum PixelClock : 170.000 MHz
Maximum Width : 1920 pixels
Maximum Height : 1080 pixels
Preferred Width : 1920 pixels
Preferred Height : 1080 pixels
Preferred VertRefresh : 60 Hz
Physical Width : 500 mm
Physical Height : 290 mm

I have tried Generating the /etc/X11/Xorg.conf file with several variations

nvidia-xconfig --enable-all-gpus

nvidia-xconfig --enable-all-gpus --seperate-x-screens

Even with all that i can’t not get the 4 other monitors to display anything they are blank even though they are being detected and lit up except they are blank but i can move the mouse cursor over the monitor screen and see it moving across the other 4 blank monitors .

Below is the /etc/X11/xorg.conf file i am using when i run the command nvidia-xconfig --enable-all-gpus --seperate-x-screens . Please help

nvidia-xconfig: X configuration file generated by nvidia-xconfig

nvidia-xconfig: version 375.26 (buildmeister@swio-display-x86-rhel47-01) Thu Dec 8 19:07:46 PST 2016

Section “ServerLayout”
Identifier “Layout0”
Screen 0 “Screen0”
Screen 1 “Screen1” RightOf “Screen0”
Screen 2 “Screen2” Above “Screen1”
Screen 3 “Screen3” Above “Screen2”
Screen 4 “Screen4” RightOf “Screen2”
Screen 5 “Screen5” RightOf “Screen4”
Screen 6 “Screen6” Above “Screen5”
Screen 7 “Screen7” Above “Screen6”
InputDevice “Keyboard0” “CoreKeyboard”
InputDevice “Mouse0” “CorePointer”
EndSection

Section “Files”
EndSection

Section “InputDevice”

# generated from default
Identifier     "Mouse0"
Driver         "mouse"
Option         "Protocol" "auto"
Option         "Device" "/dev/psaux"
Option         "Emulate3Buttons" "no"
Option         "ZAxisMapping" "4 5"

EndSection

Section “InputDevice”

# generated from default
Identifier     "Keyboard0"
Driver         "kbd"

EndSection

Section “Monitor”
Identifier “Monitor0”
VendorName “Unknown”
ModelName “Unknown”
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option “DPMS”
EndSection

Section “Monitor”
Identifier “Monitor1”
VendorName “Unknown”
ModelName “Unknown”
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option “DPMS”
EndSection

Section “Monitor”
Identifier “Monitor2”
VendorName “Unknown”
ModelName “Unknown”
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option “DPMS”
EndSection

Section “Monitor”
Identifier “Monitor3”
VendorName “Unknown”
ModelName “Unknown”
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option “DPMS”
EndSection

Section “Monitor”
Identifier “Monitor4”
VendorName “Unknown”
ModelName “Unknown”
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option “DPMS”
EndSection

Section “Monitor”
Identifier “Monitor5”
VendorName “Unknown”
ModelName “Unknown”
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option “DPMS”
EndSection

Section “Monitor”
Identifier “Monitor6”
VendorName “Unknown”
ModelName “Unknown”
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option “DPMS”
EndSection

Section “Monitor”
Identifier “Monitor6”
VendorName “Unknown”
ModelName “Unknown”
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option “DPMS”
EndSection

Section “Device”
Identifier “Device0”
Driver “nvidia”
VendorName “NVIDIA Corporation”
BoardName “NVS 810”
BusID “PCI:10:0:0”
Screen 0
EndSection

Section “Device”
Identifier “Device1”
Driver “nvidia”
VendorName “NVIDIA Corporation”
BoardName “NVS 810”
BusID “PCI:10:0:0”
Screen 1
EndSection

Section “Device”
Identifier “Device2”
Driver “nvidia”
VendorName “NVIDIA Corporation”
BoardName “NVS 810”
BusID “PCI:10:0:0”
Screen 2
EndSection

Section “Device”
Identifier “Device3”
Driver “nvidia”
VendorName “NVIDIA Corporation”
BoardName “NVS 810”
BusID “PCI:10:0:0”
Screen 3
EndSection

Section “Device”
Identifier “Device4”
Driver “nvidia”
VendorName “NVIDIA Corporation”
BoardName “NVS 810”
BusID “PCI:12:0:0”
Screen 4
EndSection

Section “Device”
Identifier “Device5”
Driver “nvidia”
VendorName “NVIDIA Corporation”
BoardName “NVS 810”
BusID “PCI:12:0:0”
Screen 5
EndSection

Section “Device”
Identifier “Device6”
Driver “nvidia”
VendorName “NVIDIA Corporation”
BoardName “NVS 810”
BusID “PCI:12:0:0”
Screen 6
EndSection

Section “Device”
Identifier “Device7”
Driver “nvidia”
VendorName “NVIDIA Corporation”
BoardName “NVS 810”
BusID “PCI:12:0:0”
Screen 7
EndSection

Section “Screen”
Identifier “Screen0”
Device “Device0”
Monitor “Monitor0”
DefaultDepth 24
SubSection “Display”
Depth 24
EndSubSection
EndSection

Section “Screen”
Identifier “Screen1”
Device “Device1”
Monitor “Monitor1”
DefaultDepth 24
SubSection “Display”
Depth 24
EndSubSection
EndSection

Section “Screen”
Identifier “Screen2”
Device “Device2”
Monitor “Monitor2”
DefaultDepth 24
SubSection “Display”
Depth 24
EndSubSection
EndSection

Section “Screen”
Identifier “Screen3”
Device “Device3”
Monitor “Monitor3”
DefaultDepth 24
SubSection “Display”
Depth 24
EndSubSection
EndSection

Section “Screen”
Identifier “Screen4”
Device “Device4”
Monitor “Monitor4”
DefaultDepth 24
SubSection “Display”
Depth 24
EndSubSection
EndSection

Section “Screen”
Identifier “Screen5”
Device “Device5”
Monitor “Monitor5”
DefaultDepth 24
SubSection “Display”
Depth 24
EndSubSection
EndSection

Section “Screen”
Identifier “Screen6”
Device “Device6”
Monitor “Monitor6”
DefaultDepth 24
SubSection “Display”
Depth 24
EndSubSection
EndSection

Section “Screen”
Identifier “Screen7”
Device “Device7”
Monitor “Monitor7”
DefaultDepth 24
SubSection “Display”
Depth 24
EndSubSection
EndSection

What am i missing in trying to configure this monitors or make them all work with Nvidia NVS 810 ? Any help please . Have spent a few hours on this trying to make it work

4

It appears to be exacerbated by Hibernate (pm-hibernate) as well. I rebooted, and the display worked fine for a while – although DPMS did not trigger a monitor standby/shutdown.

Since resuscitating from hibernation, however, the monitor will not turn on.

FWIW:

$ dpkg-query -l nvidia* | grep 'ii'
ii  nvidia-alternative              375.26-1     amd64        allows the selection of NVIDIA as GLX provider
ii  nvidia-driver-libs:amd64        375.26-1     amd64        NVIDIA metapackage (OpenGL/GLX/EGL/GLES libraries)
ii  nvidia-driver-libs:i386         375.26-1     i386         NVIDIA metapackage (OpenGL/GLX/EGL/GLES libraries)
ii  nvidia-driver-libs-i386:i386    375.26-1     i386         NVIDIA metapackage (OpenGL/GLX/EGL/GLES 32-bit libraries)
ii  nvidia-egl-common               375.26-1     amd64        NVIDIA binary EGL driver - common files
ii  nvidia-egl-icd:amd64            375.26-1     amd64        NVIDIA EGL installable client driver (ICD)
ii  nvidia-egl-icd:i386             375.26-1     i386         NVIDIA EGL installable client driver (ICD)
ii  nvidia-installer-cleanup        20151021+4   amd64        cleanup after driver installation with the nvidia-installer
ii  nvidia-kernel-common            20151021+4   amd64        NVIDIA binary kernel module support files
ii  nvidia-kernel-dkms              375.26-1     amd64        NVIDIA binary kernel module DKMS source
ii  nvidia-kernel-support           375.26-1     amd64        NVIDIA binary kernel module support files
ii  nvidia-legacy-check             375.26-1     amd64        check for NVIDIA GPUs requiring a legacy driver
ii  nvidia-libopencl1:amd64         375.26-1     amd64        NVIDIA OpenCL ICD Loader library
ii  nvidia-modprobe                 367.44-1     amd64        utility to load NVIDIA kernel modules and create device nodes
ii  nvidia-settings                 361.45.11-1  amd64        tool for configuring the NVIDIA graphics driver
ii  nvidia-support                  20151021+4   amd64        NVIDIA binary graphics driver support files
ii  nvidia-vdpau-driver:amd64       375.26-1     amd64        Video Decode and Presentation API for Unix - NVIDIA driver
ii  nvidia-vulkan-common            375.26-1     amd64        NVIDIA Vulkan driver - common files
ii  nvidia-vulkan-icd:amd64         375.26-1     amd64        NVIDIA Vulkan installable client driver (ICD)
ii  nvidia-vulkan-icd:i386          375.26-1     i386         NVIDIA Vulkan installable client driver (ICD)
5

This sounds a lot similar to the descriptions other users were giving on earlier driver releases, though I haven’t seen many responses to those threads stating that the problem was fixed. Some eyes on the issue would be nice.

6

Update: After buying a DP-to-HDMI converter, the card/monitor work fine, through Hibernation, etc. It’s clearly related to the DP support in the driver, and potentially a regression in 375.

Can nvidia look for the regression and release an update?

7

Haven’t tested DP to HDMI but like I said mini-DP to DVI active adapters for me have the issue. Nor have I tried hibernation, though I should probably give that a check just to see.

I opened a case with Nvidia and with a bit of back and forth they stated they’re going to look into it.

We’ll see what happens.

8

Some clues, perhaps?

Display Power Management Signaling - ArchWiki
[url]https://wiki.archlinux.org/index.php/Display_Power_Management_Signaling[/url]

–

How to Choose a DisplayPort Cable, and Not Get a Bad One! - DisplayPort
[url]http://www.displayport.org/cables/how-to-choose-a-displayport-cable-and-not-get-a-bad-one/[/url]

Related:

Notice regarding incompatibility of certain 3rd party DisplayPort video cables
[url]http://www.necdisplay.com/documents/Miscellaneous/DisplayPort_Notice.pdf[/url]

Updated 04/27/2011
Active vs Passive DP-> DVI adaptors | NVIDIA
[url]Error | NVIDIA

Find Answers | NVIDIA
[url]http://nvidia.custhelp.com/app/answers/list[/url]

9

Good thoughts but in the majority of these cases the nouveau driver works so it’s definitely a driver issue. On my setup using an AMD card with the proprietary catalyst drivers had DPMS working just fine so the system should be fully capable of handling it.

10

can NVIDIA --please please please fix this issue with NVS 810 . it is a shame to NVIDIA. The issue affects all Linux Distros as far as i know.

11

I can verify that as of driver 375.26 this issue still exists. Running xset dpms force off causes the monitors to go black but the LED backlight remains on and they are clearly not suspending as expected.

12

Same as before with version 375.39. xset dpms force off causes the monitors to go black but the LED backlight remains on and the monitors are not suspending as expected.

13

Hi survient, We are tracking this issue under : 1858977 : NVS 810 + minDP-DVI

Is this issue reproduce with any other monitors ?
Is any earlier old driver version worked for you?
What desktop env you are running like - gnome, kde, xfce or else?
What is make/model of the dongle you are using?
Is it DV-I or DV-D display cable?

14

I’ve tried other monitors with the same result, and I’ve tried several versions of the driver including the one that first supported the NVS 810, they all result in the same issue.

Based on feedback I’ve seen in other forum threads this clearly appears to be a wider issue with the driver even outside of the NVS 810.

Definitely looks to be a regression issue, as there were spans of time in posts made several years back that complained about the issue as well, then a period of silence, and now another surge in activity.

15

Hi survient,
Is this issue reproduce with any other monitors ?
Is any earlier old driver version worked for you?
What desktop env you are running like - gnome, kde, xfce or else?
What is make/model of the dongle you are using?
Is it DV-I or DV-D display cable?

16

Is this issue reproduce with any other monitors ? Yes
Is any earlier old driver version worked for you? No
What desktop env you are running like - gnome, kde, xfce or else? I’m running xfce but I’ve tried gnome and kde to no avail
What is make/model of the dongle you are using? HIS HMDPSDVIEYE HIS Active Mini DisplayPort to Single Link-DVI Eyefinity Adapter < Cables & Adapters < Gaming Accessories < Products | HIS Graphic Cards
Is it DV-I or DV-D display cable? DVI-I cable

17

Is this issue reproduce with any other monitors ? Yes
Thanks for this info. What are all models of monitors you tested and observe this issue?
Also issue reproduce with ideal desktop, When I mean no applications running/open ? Or Do We have to run any application on desktop?

18

What are all models of monitors you tested and observe this issue? I work in an office so while I have tested several I’m only familiar with the model information of my primary monitors, which are Acer V213HL. If I can get the models of any others I’ll let you know; so far every monitor I’ve tested with has the DPMS issue.

Also issue reproduce with ideal desktop, When I mean no applications running/open ? This happens regardless of what I have running on the desktop.

Or Do We have to run any application on desktop? The desktop can have nothing running on it and the issue still persists.

19

I’m seeing related issues, especially resuming from hibernation, but also just with DPMS. However, I’m having the problem when trying to use the DisplayPort output of:

01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [NVS 310] (rev a1)

Screens won’t resume AT ALL from hibernation. I had to switch to DVI to get them to work at all.

For monitors, I’m using:
VendorName “ViewSonic”
ModelName “VG2239 Series”
and
VendorName “ViewSonic”
ModelName “VX2260WM”

I’m currently using:
ii xserver-xorg-video-nvidia 375.39-1 amd64 NVIDIA binary Xorg driver

But it started a while ago, so previous drivers are suspect.

As survient indicated, it’s probably a regression issue. I think further up the thread he pointed to the likely timeframe as well.

20

I am completely disappointed with NVS 810. Nvidia brags about producing great expensive cards and they can’t even fix a Driver issue with their own NVS 810 Driver that affects all Linux Distros. It does not matter what the Linux distros or monitors. If you have multi-monitors ( 4 to 8 ) you will have issues no matter the connector

Mini-DP to DP or Mini-DP to DVI

Please i beg you do not buy this card – NVS 810 for any Linux Distros or Signage. It is completely useless unless NVIDIA can have their act together and fix the issue. Driver’s version 375.26 or 375.39 don’t fix the issue.

Please spend your US$ 990 somewhere NOT at NVIDIA buying NVS 810 – it will not work for what they are advertising .

Let’s use our wallet to force NVIDIA to fix the issue. Its actually pathetic and unacceptable for more than 4 months and no permanent fix. Just useless suggestions that are not helpful from NVIDIA technical team.

NVIDIA , FIX THE DAMN DRIVER , PLEASE, PLEASE