Primary monitor doesn't wake up out of power save mode

[Nick Davis]

Binary package hint: nvidia-glx-185

I have a dual-head configuration in Ubuntu 9.10. My video card is an nvidia quadro NVS 295, I have two displays: a 24" Dell 2408WFP, and a 19" NEC LCD1880SX (the 24" Dell is the primary one). Whenever my machine goes into power save, and I move the mouse to wake it, the NEC monitor comes alive, but the Dell doesn't. I have to turn the power off on the Dell monitor, and turn it back on, in order to get the display to activate again. I'm using driver version 185.18.36.

Following is my xorg.conf file:

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 1.0 (buildd@crested) Sun Feb 1 20:25:37 UTC 2009

Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "Screen0" 0 0
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "Module"
    Load "dbe"
    Load "extmod"
    Load "type1"
    Load "freetype"
    Load "glx"
EndSection

Section "ServerFlags"
    Option "Xinerama" "0"
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"
    # HorizSync source: edid, VertRefresh source: edid
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "NEC LCD1880SX"
    HorizSync 31.0 - 82.0
    VertRefresh 50.0 - 85.0
    Option "DPMS"
EndSection

Section "Device"
    Identifier "Device0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "Quadro NVS 295"
EndSection

Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    Option "TwinView" "1"
    Option "TwinViewXineramaInfoOrder" "DFP-2"
    Option "metamodes" "DFP-1: nvidia-auto-select +1920+0, DFP-2: nvidia-auto-select +0+0"
    SubSection "Display"
        Depth 24
    EndSubSection
EndSection

[Nick Davis (argoneus)]

By the way, this bug wasn't present in 9.04.

[Mike Javorski (mike-javorski)]

I can report this as well, though in my configuration it is a laptop with a Quadro FX770M chip. The laptop display will resume from a power save, the attached external display (via DisplayPort) does not. After power cycling the external display, visibility is restored, but it's extremely aggravating to have to repeatedly power-cycle that external display.

I saw a note in one of the later nvidia drivers that they resolved a power-save problem with DisplayPort attached devices, though I don't know if this is related.

[Nick Davis (argoneus)]

If Nvidia has indeed fixed the issue, then the solution for Ubuntu 9.10 should just require the appropriate package maintainer to add the latest Nvidia driver package to the repository.

Mike, do you have a link to the Nvidia changelog describing the fix?

[Mike Javorski (mike-javorski)]

After some digging on the nvidia site, it appears that it was an earlier version of version 185 that contained the fix. There is several mentions of the issue on the nvidia forums as well. I am going to try running the 190 drivers on my machine, though I don't know when exactly I will be able to get them set up.

[Nick Davis (argoneus)]

In the nvidia release notes for driver version 190.53 (http://www.nvidia.com/object/linux_display_amd64_190.53.html), there's mention in the release notes of a DisplayPort bugfix:

    - Fixed a problem that caused resolution limitations or corruption on certain DisplayPort devices such as the Apple 24" Cinema display or some DisplayPort to VGA adapters.

This could be related to the power management issue.

[Mike Javorski (mike-javorski)]

I have been testing 195.30 from https://launchpad.net/~nvidia-vdpau/+archive/ppa and so far this has resolved the issues for me. External display now resumes from power save cleanly. I did not try 190.53 though.

[Nick Davis (argoneus)]

This has been fixed as of Ubuntu 10.04.

[Nick Davis (argoneus)]

Can someone close this as fixed?