[nvidia C51] Second monitor (DVI) doesn't wake up after power save mode

Bug #296032 reported by Christopher Peplin
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-180 (Ubuntu)
Expired
Low
Unassigned

Bug Description

I just upgraded my media center to Intrepid via a clean install, and there's a strange problem with powering down the displays.

Hardware:
Foxconn 6150BK8MC-KRSHN2 Socket 939 Motherboard (onboard video, one VGA and one DVI)
Samsung LNT3253HX 32" LCD HDTV

I'm using the nvidia-glx-177 restricted drivers, and have my screens setup with the attached xorg.conf (generated by nvidia-settings).

The HDTV is plugged into the DVI port and set up as the second display (within a single X server). There is a smaller LCD plugged into the VGA port and set up as the primary display.

After 5 minutes of inactivity, both screens go into powersave mode as expected. When I press a key or wiggle the mouse to wake it up, the small LCD (primary screen) wakes up, but the HDTV stays dark and continues to say "No signal."

If I restart X with control-alt-backspace, the HDTV immediately wakes up and works fine until the system turns it off.

I'm not sure if this is an issue with the nvidia driver or with the X server itself, so I'm not able to assign this to a specific package. I was unable to find a similar bug reported elsewhere.

For what it's worth, I have a similar setup on another computer (same driver, similar xorg), but with a PCI-E video card and two DVI monitors and that does not exhibit this problem.

lspci:
VGA compatible controller [0300]: nVidia Corporation C51 [Quadro NVS 210S/GeForce 6150LE] [10de:0245] (rev a2)

Tags: intrepid
Revision history for this message
Christopher Peplin (chris.peplin) wrote :
Revision history for this message
Christopher Peplin (chris.peplin) wrote :

In observing this further, I'm pretty confident the problem has to do with power save mode. In the GNOME Power Management dialog, I set it to never turn off the displays. Now, they both go black after 6 minutes due to the go-to-black screensaver, and both wake up from black properly. Of course, this isn't great as both monitors are using full power.

affects: ubuntu → gnome-power-manager (Ubuntu)
Revision history for this message
Scott Howard (showard314) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Karmic Koala. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/. Thanks again and we appreciate your help.

Changed in gnome-power-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
Christopher Peplin (chris.peplin) wrote :

The same problem occurs in the Karmic Koala Alpha 2 Live CD.

Using the Live CD, I booted into the desktop environment and install the nvidia-glx-180 drivers for my video card. I restarted the X server and used nvidia-settings to enabled the second display with TwinView. Next, I set the monitors to go into power-save mode after 1 minute.

Both monitors entered power save mode as expected, but when I moved the mouse to wake it up only the small LCD came active (the primary TwinView screen).

I'm going to now try this:
a. without twinview
b. without the nvidia drivers

to see if I can pinpoint what's causing this issue.

Revision history for this message
Christopher Peplin (chris.peplin) wrote :

Test a, live CD with nvidia drivers set up for dual X servers, not TwinView: Same issue, TV doesn't return from power save mode

Test b, pure live CD with default drivers: Both displays go to sleep and wake up as expected. No bug.

This somewhat narrows it down to being an issue with the nvidia drivers post version 177, when the problem first showed up.

affects: gnome-power-manager (Ubuntu) → nvidia-graphics-drivers-180 (Ubuntu)
Revision history for this message
Scott Howard (showard314) wrote :

Thank you for the detective work. Please attach your X server log file (/var/log/Xorg.0.log) to the bug report as individual uncompressed file attachments using the "Attachment:" box below after recreating the bug you described here. Also, can you post the output of "lspci -vvnn"? Thanks in advance.

Revision history for this message
Christopher Peplin (chris.peplin) wrote :
Revision history for this message
Christopher Peplin (chris.peplin) wrote :
Revision history for this message
Christopher Peplin (chris.peplin) wrote :

Here's a more interesting lspci output, run as root.

Revision history for this message
Scott Howard (showard314) wrote :

Great - could you also attach the file: "~/.xsession-errors" after the second monitor fails to wake up?

That would be helpful as well.
Thanks

summary: - Second monitor (DVI) doesn't wake up after power save mode
+ [C51] Second monitor (DVI) doesn't wake up after power save mode
description: updated
summary: - [C51] Second monitor (DVI) doesn't wake up after power save mode
+ Second monitor (DVI) doesn't wake up after power save mode
summary: - Second monitor (DVI) doesn't wake up after power save mode
+ [C51] Second monitor (DVI) doesn't wake up after power save mode
summary: - [C51] Second monitor (DVI) doesn't wake up after power save mode
+ [nvidia C51] Second monitor (DVI) doesn't wake up after power save mode
Revision history for this message
Christopher Peplin (chris.peplin) wrote :

Attached is the contents of .xsession-error for a clean session startup, switch to power save mode, and the failed wakeup. The file doesn't change when I attempt to wake up the monitor.

Revision history for this message
Christopher Peplin (chris.peplin) wrote :

Following the "Xlib: extension "XFree86-Misc" missing on display ":0.0"." error I added the "extmod" module to my xorg.conf, like so:

Section "Module"
    Load "extmod"
    Load "glx" // this was already here
EndSection

But this had no effect after restarting my X server. The output of "xdpyinfo | grep -i misc" before and after was just:

peplin@line:~$ xdpyinfo | grep -i misc
    XC-MISC

Revision history for this message
Scott Howard (showard314) wrote :

Thanks - I'm marking as confirmed.

Changed in nvidia-graphics-drivers-180 (Ubuntu):
importance: Undecided → Low
status: Incomplete → Confirmed
Bryce Harrington (bryce)
tags: added: intrepid
Revision history for this message
bugbot (bugbot) wrote :

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: Confirmed → New
status: New → Incomplete
Revision history for this message
bugbot (bugbot) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.