[solved - hardware issue] Monitor blanks; won't wake up

[dedanna1029]

Well see, there was this one little package, uuuuummm,,, something just slightly, um, WELL...
See, I kinda did these updates tonight, and um, there was one small update that well, I really don't know why I didn't think of it before:

Code: Select all

:) ls /var/cache/pacman/pkg | grep init
initscripts-2010.07-2-i686.pkg.tar.xz

Well, see, I'd had similar symptoms before, just never on this scale or anywhere near this bad. Got thinking back when I saw that little baby come up in updates, and kinda thought, "oops"... yep, that's what it was at the time.

We be gonna confirm or deny this overnight tonight, to see if that got it.

Good night, bjoernvold.

[dedanna1029]

I r resumed this morning! YEEEEEEEESSS!

[viking60]

Life is good then

[dedanna1029]

Well, um, not quite yet it seems. Just got in from an appointment - had left it going - had a bit of a time resuming, but not like it was. Just that it's there though... *cringes

[dedanna1029]

Per this thread, this issue is now resolved. I hope they fix the bug in that program. Would be nice.

[dedanna1029]

It is indeed the nvidia driver. It's doing it again. It had resolved, but then on updates 2 days ago (nvidia driver update), started doing this again.
In xset, I have everything turned off, including blanking, and it still blanks and won't resume. What's happening, is when I come back to the computer I try resuming by moving the mouse. It comes back but then goes right back to blanking again. If I hit a key, it does the same thing soon as I do. I have to keep trying and trying until it finally resumes, with anything to do with the keyboard or mouse making it go right back to blank. Fedora 14 it's doing it in this time. I think I'm seeing a regression here.

Code: Select all

$ rpm -qa | grep nvidia
nvidia-xconfig-1.0-7.fc14.i686
kmod-nvidia-2.6.35.13-92.fc14.i686-260.19.36-1.fc14.5.i686
akmod-nvidia-260.19.36-1.fc14.i686
xorg-x11-drv-nvidia-libs-260.19.36-1.fc14.i686
xorg-x11-drv-nvidia-260.19.36-1.fc14.i686
nvidia-settings-1.0-9.fc14.i686

Any clue what to do? It appears I've found the wide wide world of regression.
Resume hook maybe? I'm uninstalling gnome-power-manager right now just in case that helps.

Thanks.

[rolf]

Personally, I think the screensavers are a throwback to CRT's and my LCD doesn't need one, so I prefer to let it burn on. That blanking deal has been a real annoyance, for me, whenever I install a new release. I run KDE and go round and round with power saving and screen management. I like the screen to stay on. When I'm lying on the bed/office chair, watching tv, I like to be able to see if something comes in on my email, or watch a movie w/o the screen blanking.

I don't know if it is related to what is vexing you but I have a little command set to run at every log-in to the KDE desktop, set via the handy little Autostart module in Systemsettings:

xset -dpms

and all is well, even with nvidia.

[dedanna1029]

Yeah, I tried that, rolf. I've got my xset set up as so:

Code: Select all

Screen Saver:
  prefer blanking:  no    allow exposures:  yes
  timeout:  0    cycle:  0
Colors:
  default colormap:  0x20    BlackPixel:  0    WhitePixel:  16777215
Font Path:
  catalogue:/etc/X11/fontpath.d,built-ins
DPMS (Energy Star):
  Standby: 0    Suspend: 0    Off: 0
  DPMS is Disabled

I've been up 3 days with that, and it's still doing it.

Code: Select all

[dedanna@dedanna ~]$ uptime
 21:49:46 up 3 days, 21:49,  3 users,  load average: 0.42, 0.22, 0.46

I've uninstalled gnome-power-manager, but haven't had chance to see if the blanking starts again - I've been using the computer since.

Thanks,,,

And you're right, it's a pain in the ass. Screensavers I don't mind, if the blanking wouldn't take them over and put this thing right to sleep - I like for them to run overnight. But, they're not running again, and the blanking/sleeping is taking precedence.

I may try downgrading nvidia, and see what happens. I don't know. *shrug

Addendum, two things I'm thinking. Try running xset as root, and set it to the above, or a resume hook. The problem with the resume hook with the kernel, is if that's not the problem, then the resume hook would (in theory anyway) make things worse.
Just tried running it as root - it's already set to the above.

[dedanna1029]

Check it out. It's doing the exact same thing in Arch, and it's on a much higher version of the nvidia driver and the kernel both:

Code: Select all

:) pacman -Ss gnome-power-manager
extra/gnome-power-manager 3.0.2-2 [2.91 MB] (gnome) [installed]

Code: Select all

pacman -Ss kernel26
core/kernel26 2.6.39.3-1 [36.07 MB] (base) [installed]
    The Linux Kernel and modules
core/kernel26-docs 2.6.39.3-1 [3.28 MB] [installed]
    Kernel hackers manual - HTML documentation that comes with the Linux kernel.
core/kernel26-headers 2.6.39.3-1 [4.27 MB] [installed]
core/kernel26-docs 2.6.39.3-1 [3.28 MB] [installed]
    Kernel hackers manual - HTML documentation that comes with the Linux kernel.
extra/kernel26-manpages 2.6.39-1 [2.48 MB] [installed]
    Kernel hackers manual - Section 9 manpages that comes with the Linux kernel.

The commonality is that they both have (or had; I've uninstalled it from Fedora) gnome-power-manager installed.

Code: Select all

pacman -Ss gnome-power-manager
extra/gnome-power-manager 3.0.2-2 [2.91 MB] (gnome) [installed]
    Session daemon that makes it easy to manage your laptop or desktop system.

That's what it was last time, I guess we get to find out if that's what it is this time.

[dedanna1029]

I uninstalled gnome-power-manager, and waited a time without using the computer. It did blank, but then that's all that Gnome 3 does is blank; there are no screensavers for it. This time it resumed; however, I think it will need more testing, such as the overnight test to make sure.

I'm going to test it out in Fedora in a bit.

Relevant section in xset is set to as it was above:

Code: Select all

Screen Saver:
  prefer blanking:  no    allow exposures:  yes
  timeout:  0    cycle:  0
Colors:
  default colormap:  0x20    BlackPixel:  0    WhitePixel:  16777215
Font Path:
  /usr/share/fonts/misc/,/usr/share/fonts/TTF/,/usr/share/fonts/Type1/,/usr/share/fonts/100dpi/,/usr/share/fonts/75dpi/,built-ins
DPMS (Energy Star):
  Standby: 600    Suspend: 600    Off: 600
  DPMS is Disabled

[dedanna1029]

Yup, that did it. Went back to Fedora - it did blank, but at least it resumed after being left alone for some 45 minutes, and I didn't even set xset. At this point, I'd probably get screensavers if I did set xset:

Code: Select all

$ xset q
Keyboard Control:
  auto repeat:  on    key click percent:  0    LED mask:  00000002
  XKB indicators:
    00: Caps Lock:   off    01: Num Lock:    on     02: Scroll Lock: off
    03: Compose:     off    04: Kana:        off    05: Sleep:       off
    06: Suspend:     off    07: Mute:        off    08: Misc:        off
    09: Mail:        off    10: Charging:    off    11: Shift Lock:  off
    12: Group 2:     off    13: Mouse Keys:  off
  auto repeat delay:  500    repeat rate:  30
  auto repeating keys:  00ffffffdffffbbf
                        fadfffefffedffff
                        9fffffffffffffff
                        fff7ffffffffffff
  bell percent:  50    bell pitch:  400    bell duration:  100
Pointer Control:
  acceleration:  10/10    threshold:  3
Screen Saver:
  prefer blanking:  yes    allow exposures:  yes
  timeout:  0    cycle:  0
Colors:
  default colormap:  0x20    BlackPixel:  0    WhitePixel:  16777215
Font Path:
  catalogue:/etc/X11/fontpath.d,built-ins
DPMS (Energy Star):
  Standby: 600    Suspend: 600    Off: 600
  DPMS is Enabled
  Monitor is On

That's what it's set to now. I'm going to call it good because it does at least resume without gnome-power-manager (of course, this is liable to change, as it already did).

[dedanna1029]

Yup, that got it. Final solution is to uninstall gnome-power manager, and run xset as so:

Code: Select all

Screen Saver:
  prefer blanking:  no    allow exposures:  yes
  timeout:  0    cycle:  0
Colors:
  default colormap:  0x20    BlackPixel:  0    WhitePixel:  16777215
Font Path:
  catalogue:/etc/X11/fontpath.d,built-ins
DPMS (Energy Star):
  Standby: 600    Suspend: 600    Off: 600
  DPMS is Disabled

That is, unless you're like me and now want to know what's so buggy in gnome-power-manager. I r now haz either screensavers, or nothing, as it should be.

Edit: This morning I woke up, couldn't resume. I'm going to look elsewhere for the issue. I'll find it.