Tiny Core Base > TCB Q&A Forum

Xvesa: Default Display Blanking Timeout

<< < (2/3) > >>

Tahoe:
Yeah maybe, I'm thinking lose the 915. Xorg's worked OK on other distros I've tried but not a few boots ago, she wouldn't go. Since eyeballing related items in appbrowser, I'd say it's time for another shot. In the event she doesn't load, what are my outs? Slip a working xorg.conf in there (I know my refresh rates)?

Then again, about that 600 value? It exist somewhere I could adjust?

Juanito:
I've not managed to get the couple of intel graphics chipsets to which I've had access to work confless with xorg, but they do work with a suitable xorg.conf culled from google.

As for the 600 screensaver setting - I don't know, but maybe the xset linux man page might turn something up?

Edit:
--- Quote ---The default values are built into X, and need not appear anywhere else. That's why, if you grepped for timeouts, you may not have found them.

They can also be set via xset. You can set the blank timeout with:
xset s blank
xset s 300
will tell X to use screen blanking after the system has been idle for 300 seconds (five minutes).

xset dpms 0 360 420
disables DPMS standby and sets the DPMS suspend time to 360 seconds and the off time to 420 seconds. In theory, this combined with the previous xset commands would first blank the screen at five minutes; then at six minutes, the display would go to suspend, turning off another minute later. In practice, this won't work for most people, as we'll see later. (DPMS through xorg seems only to toggle the screen-blanked state -- so if the screen was already blanked, it will actually turn back on! -- rather than going to a power saving state.)

But the timeouts can also be specified in the X configuration file: /etc/X11/xorg.conf. In the "Monitor" section, you need a line like:
        Option          "DPMS"
Then, in the "ServerLayout" section (for Xorg 7.2 and later, make a separate ServerFlags section instead), include lines like this:
        Option          "BlankTime"     "4"
        Option          "StandbyTime"   "0"
        Option          "SuspendTime"   "0"
        Option          "OffTime"       "5"
Caution: note the numbers are all small. xorg.conf needs times specified in minutes, not seconds as with xset.

If you're seeing a timeout that isn't one of the defaults, but isn't specified in xorg.conf -- as with the two-minute timeout which set me on this quest in the first place -- you may have to hunt around for a place that's calling xset dpms with a different set of timeouts. In my case, it turned out that Ubuntu Breezy sets the dpms timeouts in /etc/acpi/power.sh, which gets called at boot time. So anything you set in xorg.conf may well get overridden.

Hint: when debugging timeouts, try setting them to unusual numbers like 765 or 666 instead of 300 or 600. That makes it easier to be sure whether you're seeing your own numbers or something coming from a system setting somewhere else.
--- End quote ---

Tahoe:
So Confless is (partially) responsible for auto-configuring users hardware? In the meantime I'll try and follow along here http://forum.tinycorelinux.net/index.php?topic=4091.0, it's recent.

Juanito:
did you see the edit to the post above?

Tahoe:
Oh sure, thanks Juanito. Think I'll dig around a little and see what turns up.

Navigation

[0] Message Index

[#] Next page

[*] Previous page