laptop monitor does not turn on after inactivity when using nvidia-glx-new

Bug #190526 reported by Jayhawk
16
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.24 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: nvidia-glx-new

If the laptop is not being used for several minutes, the laptop monitor will power off. When I come back and move the mouse or press a key, the monitor will light up, but the screen does not return unless you switch terminals and come back (via control-alt-F6 and control-alt-F7 a few times). If using the 'nv' mode in xorg.conf, the monitor works fine.

My laptop is an HP dv6000 (dv6338se) using an AMD Turion chip with an Nvidia GeForce 6150 Go video card. I am currently running Hardy 2.6.24-7-generic. My uname -a reports:
Linux allen-fieldhouse 2.6.24-7-generic #1 SMP Thu Feb 7 00:56:31 UTC 2008 x86_64 GNU/Linux
The nvidia-glx-new version is: 169.09+2.6.24.7-7.17

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Does it work with the latest version, 169.12?

Changed in linux-restricted-modules-2.6.24:
status: New → Incomplete
Revision history for this message
Michael DePaulo (mikedep333) wrote :

I am experiencing this on my HP TX1000z (customized) laptop using the Geforce 61050 go also.

This problems also occurs whenever I switch over to the console or when it is shutting down.

Here are some other people noticing this problem.
http://ubuntuforums.org/showpost.php?p=4514822&postcount=697
http://ubuntuforums.org/showpost.php?p=4617732&postcount=773

Revision history for this message
Michael DePaulo (mikedep333) wrote :

Correction, for me it seems like there is corruption rather than the screen being turned off.

Revision history for this message
waspbr (notaduck) wrote :

I am also having the same problem with the HP tx1000z notebook series. When the computer turns off the monitor when it goes idle for too long or the lid is closed, the screen gets weird and you can see lines it something like a bad fil from the eartly 1900.

When shutting down there's a similar problem the progress bar does not show, instead the screen starts fading resembling white-noise static which you would get from a TV, but weirder.

 a fix for this would be nice

Revision history for this message
Michael DePaulo (mikedep333) wrote :

Timo, this is occuring with the latest Nvidia driver, 169.12 (at least for me and presumably waspbr.)

Revision history for this message
Alex Tercete (alextercete) wrote :

I'm having the exact same problem in a Compaq Presario v6000 (Nvidia GeForce 6150 Go also) running an updated Hardy Beta.

I'm also having problem with the restart/shutdown splash screen which I can't see (nor hear the sound). Maybe this problems are related?

Revision history for this message
armin_somorjai (somorjaiarmin-gmail) wrote :

Same problem here with an MSI M670X laptop with Nvidia Geforce Go 6100, Hardy Beta. Hope someone finds that thing.

Revision history for this message
Spike (spikenick) wrote :

I am experiencing this same bug on my Compaq Presario V6000 very similair to models above. The only way to get the desktop back is to do the ctrl+F6 then ctrl+F7 trick. This is quite a bug and most people can't even figure it out that use my laptop. Did a fresh install to the Release Canidate today to see if that fixed it and NO Joy.... :(

Revision history for this message
Michael DePaulo (mikedep333) wrote :

On Hardy x86, this bug is present with the following drivers directly from NVIDIA:
169.07
169.12
173.08
It is not present with:
100.14.19 (the same driver as in gutsy.)

Revision history for this message
armin_somorjai (somorjaiarmin-gmail) wrote :

Now I just need to get that driver 100.14.19 to make myself happy. :D Where can I find that? It is a good solution before they clear that bug.

Revision history for this message
Michael DePaulo (mikedep333) wrote :

armin_somorjai:

First of all, if you are new to Linux, I would probably suggest just installing nvidia-glx. Its features are not all that much less. The manual installation process of the 100.14.19 requires moderate linux experience.

Regardless, here is the other driver:
http://www.nvidia.com/object/linux_display_ia32_100.14.19.html
I also had to modify Section "Device" in xorg.conf to disable the hardware cursor. Without disabling it, the mouse cursor was missing. If you can get the hardware cursor working (as it is necessary for compiz) please let me know.
------
Section "Device"
...
Driver "nvidia"
...
Option "HWCursor" "off"

Revision history for this message
Spike (spikenick) wrote :

Anyword on a real fix to this bug.... kinda a big thing if you are anyone with an nvidia card that makes real use of ubuntu...

Revision history for this message
Alex Tercete (alextercete) wrote :

This bug is the reason I haven't fully migrated from Feisty to Hardy. I'm testing Hardy on a partition and I'll try a clean install from the Final version. I would really appreciate if any of the developers could give us some feedback on what's going on.

Revision history for this message
Jayhawk (the-ayuthias) wrote :

The issue still occurs with the current kernel 2.6.24-16-generic and it is like how Michael DePaulo said. The 100.14.19 driver is the last driver that worked. The issue is not on the Ubuntu developer's side because the same problem occurs in other Linux distros (I am also using Arch and Gentoo). I have been trying to see if I can get a copy of the 2.6.25 kernel to see if 100.14.19 will work on it. I tried 2.6.25-rc6 and I was unable to get the Nvidia driver to work.

Revision history for this message
Jayhawk (the-ayuthias) wrote :

The bug fixes are fixed for me in 173.14.05. I downloaded the driver from the Nvidia site. It fixes the console issues and the black screen on inactivity.

Revision history for this message
Jayson Rowe (jayson.rowe) wrote :

Since it's been a very long time since any additional info was added to this bug, I'm just checking to see if this is still an issue, and find out what additional work should be done on this bug.

Revision history for this message
Gláuber Gonçalves (glaubergoncalves) wrote :

Since I've upgraded to 8.10, this bug is no longer an issue for me.

Revision history for this message
Jayson Rowe (jayson.rowe) wrote :

Closing since reporter states it's no longer an issue in 8.10.

Changed in linux-restricted-modules-2.6.24:
status: Incomplete → Invalid
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.