I believe that I'm suffering from this problem
$ uname -a
SunOS sunray3 5.11 snv_36 i86pc i386 i86pc
$
<http://www.beehive.org.nz/newsletters/2006/bnl-2006-06.pdf>
<http://www.beehive.org.nz/newsletters/2006/bnl-2006-06.pdf>$ xset -q
Keyboard Control:
auto repeat: on key click percent: 0 LED mask: 00000001
auto repeating keys: fff8fffffffffefd
fe1fc8fbff050000
8001000000000000
0000000000000000
bell percent: 50 bell pitch: 400 bell duration: 100
Pointer Control:
acceleration: 2/1 threshold: 4
Screen Saver:
prefer blanking: no allow exposures: yes
timeout: 0 cycle: 0
Colors:
default colormap: 0x22 BlackPixel: 0 WhitePixel: 16777215
Font Path:
/home/simon/.gnome2/share/cursor-fonts,/usr/openwin/lib/X11/fonts/Type1/,/usr/openwin/lib/X11/fonts/Type1/sun/,/usr/openwin/lib/X11/fonts/F3bitmaps/,/usr/openwin/lib/X11/fonts/Speedo/,/usr/openwin/lib/X11/fonts/misc/,/usr/openwin/lib/X11/fonts/75dpi/,/usr/openwin/lib/X11/fonts/100dpi/,/usr/openwin/lib/X11/fonts/TrueType,/home/simon/.gnome2/share/fonts
Bug Mode: compatibility mode is disabled
DPMS (Energy Star):
Display is not capable of DPMS
$
This is on a Sunray1 client connected to a Viewsonic VG710s (Standard
LCD screen that is about 2 years old). The monitor is (I'm 99% sure)
DPMS capable.
I've not made any major changes to what is otherwise a basic install
(Solaris11 + SRSS + some blastwave packages)
Regards
Simon
<http://www.beehive.org.nz/newsletters/2006/bnl-2006-06.pdf>
Bob Doolittle wrote:
Tom Shaw wrote:
In Solaris at least you need to use xset instead of xscreensaver:
/usr/openwin/bin/xset s on s blank s 300
(blank after 300 seconds - this may not be the exact syntax but it
should get you started)
If you want to turn this on for every user, put it in a script in
/etc/dt/config/Xsession.d/
This should *not* be required, and if this fixes
the issue, there's a bug either in xscreensaver or
SRSS.
We've heard scattered reports on this, but so far
haven't identified the common
circumstances/environment. Many people are using
xscreensaver with S10 and SRSS 3.1 with latest
patches and monitors are power-saving just fine.
Others have issues as you describe, with similar
monitors.
Screen savers, such as xscreensaver, are supposed
to set the X server parameters for blanking
directly. So it would seem that in some
circumstances either those parameters are not
being set properly, or the X server or SRSS is not
handling them properly, or the administrator isn't
configuring xscreensaver properly (no offense
folks, but admins make mistakes too :-).
If you're certain that xscreensaver is configured
properly, and you're certain that you're seeing
this problem (screen is blanking, but monitor is
not ever going into power-save mode), can you run
"xset q" and send the output to this list?
-Bob
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
