I decided to try the x86_64 version of CentOS 5 on my new desktop since it has an Athlon 64 X2 CPU. The one really perplexing oddity is that the monitor no longer goes to power save mode (standby) if the system is idle long enough (e.g., overnight).
The "power management" option is set to put the display to sleep after thirty minutes. The display gets blanked but it never goes to standby. The weird thing is that the display behaved as expected when I still had the 32 bit version of CentOS installed so the hardware supports powering down the monitor.
I don't see anything incriminating in dmesg, /var/log/messages or /var/log/Xorg.0.log. I'll switch the system to boot to runlevel 3 so I can see if X is spewing something to the first alternate console that isn't getting written to the log file. Anyone have other any suggestions as to diagnosing of fixing the problem?
Thanks, Dave
David G. Miller wrote:
I don't see anything incriminating in dmesg, /var/log/messages or /var/log/Xorg.0.log. I'll switch the system to boot to runlevel 3 so I can see if X is spewing something to the first alternate console that isn't getting written to the log file. Anyone have other any suggestions as to diagnosing of fixing the problem?
Are there any DPMS options set in your xorg.conf ? What is your video card/monitor and what driver are you using in X ?
Another thing to check is see if DPMS is enabled as an extension by your setup:
xdpyinfo |grep DPMS
should return "DPMS"
I have to explicitly set my monitor power saving to off on my laptop otherwise the screen has a high likelyhood of not coming back on after turning off. Toshiba says it's a known behavioral issue with multi core laptops. Happened under XP as well. Yay for screen burn in.
nate
nate wrote:
David G. Miller wrote:
I don't see anything incriminating in dmesg, /var/log/messages or /var/log/Xorg.0.log. I'll switch the system to boot to runlevel 3 so I can see if X is spewing something to the first alternate console that isn't getting written to the log file. Anyone have other any suggestions as to diagnosing of fixing the problem?
Are there any DPMS options set in your xorg.conf ? What is your video card/monitor and what driver are you using in X ?
Another thing to check is see if DPMS is enabled as an extension by your setup:
xdpyinfo |grep DPMS
should return "DPMS"
And, see what "xset q" has to say about whether DPMS is currently enabled or not. I've noticed that mplayer disables DPMS on entry, but neglects to re-enable it on termination.
On Feb 1, 2008 6:54 PM, Robert Nichols rnicholsNOSPAM@comcast.net wrote:
And, see what "xset q" has to say about whether DPMS is currently enabled or not. I've noticed that mplayer disables DPMS on entry, but neglects to re-enable it on termination.
Interesting - I have the opposite problem. When I run mplayer, my screensaver acts as normal (goes on after my 20 minute interval), which is really annoying. I have to turn the screensvaer off, and then remember to turn it back on after mplayer is done. Xine seems to work better in this regard, but it won't play everything....
mhr
MHR wrote:
On Feb 1, 2008 6:54 PM, Robert Nichols rnicholsNOSPAM@comcast.net wrote:
And, see what "xset q" has to say about whether DPMS is currently enabled or not. I've noticed that mplayer disables DPMS on entry, but neglects to re-enable it on termination.
Interesting - I have the opposite problem. When I run mplayer, my screensaver acts as normal (goes on after my 20 minute interval), which is really annoying. I have to turn the screensvaer off, and then remember to turn it back on after mplayer is done. Xine seems to work better in this regard, but it won't play everything....
I find it's actually gmplayer that disables DPMS, and does that regardless of the config setting for stopxscreensaver. The non-gui mplayer does not affect the DPMS setting.
-
David G. Miller -
MHR -
nate -
Robert Nichols