You are not logged in.
Hi All,
I love the package after having played with DSL and GRML. Hats off to the group.
I've booted off the LiveCD and found that the screen never blanks or jo into screen saving mode. I installed the "xset" package "xorg-xset-1.0.4.tazpkg" to try to understand this and this is what I found/did:
The command was invoked as follows:
sleep 3; xset dpms force standby
The other related commands also do not work:
sleep 3; xset dpms force standby
sleep 3; xset dpms force standby
I also try an experiment to redefine the intervals and to poll the state of DPMS using "xset -q" in a seperate window, as follows:
Window 1 xterm:
xset dpms 10 11 12
Window 2 xterm script (for monitoring):
while true
do
echo ""
sleep 2
xset -q
done
The above scripts shows that "xset" does indeed go through the various standby, suspend and off states at roughly 10 seconds(standby), 20 seconds(suspend) and 30 second points(off) BUT the monitor STAYS ON with a stable image
I'm not sure if this is a hardware/motherboard issue with my Asus P5G41T-M motherboard (G41 integrate graphics aka x4500).
Here is the the listing for "lspci":
00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller (rev 03)
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
Offline
Vesa driver on stable (2.6.30.6-slitaz) DPMS+intel graphics broken.
If you install xorg-xf86-video-intel and it's depends DPMS works.
Use tazx which requires an internet connection.
Vesa driver on cooking (2.6.37-slitaz) DPMS+intel graphics works.
Offline
Thanks 'mojo' for the info. Today I looked at my other system running Ubuntu 8.10
and took a look at the the differences in the dependency list for "xset" via "ldd xset":
For Slitaz using Vesa:
tux@slitaz:~# ldd --list /usr/bin/xset
linux-gate.so.1 => (0xffffe000)
libXmuu.so.1 => /usr/lib/libXmuu.so.1 (0xb8030000)
libX11.so.6 => /usr/lib/libX11.so.6 (0xb7ef2000)
libXext.so.6 => /usr/lib/libXext.so.6 (0xb7ee1000)
libXp.so.6 => /usr/lib/libXp.so.6 (0xb7ed8000)
libXau.so.6 => /usr/lib/libXau.so.6 (0xb7ed4000)
libc.so.6 => /lib/libc.so.6 (0xb7d6e000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb7d68000)
libdl.so.2 => /lib/libdl.so.2 (0xb7d64000)
/lib/ld-linux.so.2 => /lib/ld-2.10.1.so (0xb8035000)
and for the Ubuntu system (2.6.27-7):
peak@PeAK:/$ ldd /usr/bin/xset
linux-gate.so.1 => (0xb7f79000)
libXmuu.so.1 => /usr/lib/libXmuu.so.1 (0xb7f3f000)
libXext.so.6 => /usr/lib/libXext.so.6 (0xb7f30000)
libX11.so.6 => /usr/lib/libX11.so.6 (0xb7e40000)
libXxf86misc.so.1 => /usr/lib/libXxf86misc.so.1 (0xb7e3d000)
libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0xb7cdf000)
libXau.so.6 => /usr/lib/libXau.so.6 (0xb7cdc000)
libxcb-xlib.so.0 => /usr/lib/libxcb-xlib.so.0 (0xb7cd9000)
libxcb.so.1 => /usr/lib/libxcb.so.1 (0xb7cc0000)
libdl.so.2 => /lib/tls/i686/cmov/libdl.so.2 (0xb7cbb000)
/lib/ld-linux.so.2 (0xb7f5f000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb7cb6000)
I've indented the libs/lines that are different and they are in libraries
libXxf86misc.so.1 and libxcb-xlib.so.0
Hopefully this helps sort out the brokenish...
Offline
The vesa 2.3.0 driver fix's intel graphics DPMS and improves X autoconfiguration:
http://dl.dropbox.com/u/5197027/slitaz/xorg-xf86-video-vesa-2.3.0_2.6.30.6.tazpkg
Offline
Thanks,
Just tried the updated vesa driver in your link and things are "blanking" good!!!
Offline
I've just rolled the changes by remastering the rootfs.gz file (via writeiso) and
now have blanking working off the boot. I thought backported 2-3.0 vesa fix would
get backported into the STABLE 3.0 release but when I recharged the package list, yesterday, it had
not changed and still contained the Vesa 2-0 module with the broken DPMS.
Mojo, I understand the concept of taking a snapshot but how do you reconcile
someone bumping up against the same dpms problems with an older release short of using the
the "newish" cooking release ?
Using the JWM/Windows analogy, why not have an upgraded recharge list called 3.1 containing
only the updated packages that have been fixed...sort of like a "service pack?
Some might call it legacy support.
Offline
[ Generated in 0.017 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]