Hi all... Wondering if there's a way to use DPMS to put my monitor to
sleep instead of a screen blanker. I'm using KDE and doesn't appear
that this is an option in there...
Regards,
Joe Tham
Regards,
Joe Tham
Sure. I have the following in ~/.xinitrc :Quote:> Hi all... Wondering if there's a way to use DPMS to put my monitor to
> sleep instead of a screen blanker. I'm using KDE and doesn't appear
> that this is an option in there...
xset s 300 (screensaver)
xset dpms 3000 3300 3600 (time in seconds)
See man page for "xset"
Cheers,
--
Howard Mann
http://www.xmission.com/~howardm
(a LINUX website for newbies)
Regards,
Joe
> Sure. I have the following in ~/.xinitrc :
> xset s 300 (screensaver)
> xset dpms 3000 3300 3600 (time in seconds)
> See man page for "xset"
> Cheers,
> --
> Howard Mann
> http://www.xmission.com/~howardm
> (a LINUX website for newbies)
1. screen blanking/dpms: gets disabled at random times
Hello,
This is a question about a dpms problem under kde2.
I have these settings in my .xinitrc:
xset s 420 (to get screenblanking after 420 seconds)
xset dpms 540 660 780 (to get monitor energy saving modes standby,
suspend and "off" mode after the times specified here)
In kde2's control center I disabled the kde screensaver, but left dpms
settings (the same as for xset) activated, because otherwise kde wins
against my xset settings and disables dpms).
Everything works all right, indeed.
But:
At random times, my xset s 420 and sometimes additionally my xset dpms
settings (see above) get disabled - I can find this when returning to
my
computer after a longer absence, but not always, only rather rarely,
but
why?
When this happens, xset q gives me this:
screensaver timeout: 0 (i.e. xset s 0)
plus (even less frequently):
dpms disabled
What the hell?
I have no xscreensaver running, and I checked that "xlock" doesn't
change my dpms settings. So these potential culprits are not the
answer!
Why am I so interested in my xset settings?
Well, see above, when this scenario happens, not only dpms gets
disabled, but the screensaver timeout is set to "0" (like xset s 0,
instead of 420).
What is so bad about xset s 0?
Well, in my case, a setting of xset s 0 (i.e. no "screensaver - prefer
blanking") is evil, since it makes dpms kind of dangerous (remember
that
dpms, in contrast to the screensaver blanking, doesn't get disabled in
most cases)
So when the monitor enters energy saving modes, this leads to a wildly
flickering and very distorted screen image. Several times now, I came
back and found the monitor in this state, giving me some fear of an
implosion or damage...
To repeat it:
I _need_ screen blanking (which means a positive value after xset s,
like xset s 420) - or else this flickering occurs! (although only
under
kde, which seems to give a setting of xset s 0, unless I override this
via my .xinitrc settings).
Why is xset s 420 changed then? And why only sometimes? (Why is
sometimes dpms completely disabled, when I return?)
I now help myself by running a tiny script which periodically (every
60
seconds) forces a xset s 420!
Someone with a good idea/solution?
Thanks
Peter
(who doesn't think he installed anything special recently, which could
explain this new issue...)
2. Is anyone working on "metadisks"?
3. screen blanking/dpms gets disabled at random times
4. hangs on verifying dmi pool with hard drive
5. vi blanks out, long listing blanks screen
6. xtoolplaces??? Where is it?
7. olvwm- get current screen and blank screen
9. DPMS Monitor PowerSave Blanking
10. Console-Screen-Blanking: black chars on white screen
11. !! help how to turn off DPMS on xdm login screen !!
12. Screen saver that supports DPMS/Energy Star monitors?
13. Enabling Screen "Green" Features (VESA DPMS)