[comp.windows.x] screen blanking

jc@raven.bu.edu (James Cameron) (03/08/91)

Runnning:  SunOS 4.1.1
	   XDM(1)
	   Sun 4/xxx
	   Diskless client NISing off of console
	   SparcStations 1+ partly NISing (running 4.0.3)

We just recently upgrade the console to 4.1.1.  Now, every so often
the screen simply blanks.  It will not return with any amount of
mouse and key combinations (except the reboot keys *8-) ).  If I rlogin
into it from elsewhere, and create a console message (ie, su the console,
etc..) it will clear.  But, only on the console messages..ie, starting
up a window remotely on the machine does nothing.  

Console messages are sent to xterm when I am logged in....

According to screenblank(1) (which I assume is the culprit) the console
messages *would* be the only thing to wake it up...But, as I have typed
this message, the screen has blanked 3 times on me.  It seems very random
as I can be logged in for hours and not have it happen to me, and then
have it happen several times in a 1/2 hour.  It is set up with the default
options in /etc/rc.local:

if [ -f /usr/bin/screenblank ]; then
        /usr/bin/screenblank & echo -n ' screenblank '
fi


If anyone has had similar problems, please do tell.  This ONLY happens
on the console.

Thanks!

JC


--
James Cameron  -  jc@raven.bu.edu

Signal Processing and Interpretation Lab, ECS Engineering Dept.
	Boston University, Boston MA
	Work: 617 353-2879
Information Technology
	Boston University, Boston MA
	work: 617 353-2780 ext. 338

		"But to risk we must, because the greatest hazard in life
	is to risk nothing.  For the man or woman who risks nothing, has
	nothing, does nothing, is nothing."

	(A quote from the eulogy for the late Christa McAuliffe.)

gildea@expo.lcs.mit.EDU (Stephen Gildea) (03/09/91)

    Runnning:  SunOS 4.1.1
	       XDM(1)
	       Sun 4/xxx
	       Diskless client NISing off of console
	       SparcStations 1+ partly NISing (running 4.0.3)

    We just recently upgrade the console to 4.1.1.  Now, every so often
    the screen simply blanks.  It will not return with any amount of
    mouse and key combinations (except the reboot keys *8-) ).

If you are running xdm, you probably don't need to be running
screenblank at all.  Let the X server (which will always be running)
handle screen saving.  You may have to pass the server a -s flag in
xdm's Xservers file.

 < Stephen
   MIT X Consortium

smartin@Canada.lsil.com (Stephen Martin) (03/11/91)

In article <JC.91Mar7224541@raven.bu.edu> jc@raven.bu.edu (James Cameron) writes:

   We just recently upgrade the console to 4.1.1.  Now, every so often
   the screen simply blanks.  It will not return with any amount of
   mouse and key combinations (except the reboot keys *8-) ).  If I rlogin
   into it from elsewhere, and create a console message (ie, su the console,
   etc..) it will clear.  But, only on the console messages..ie, starting
   up a window remotely on the machine does nothing.  

I had the same problem on a couple of occasions.  Both times were after a
power failure which caused the date on the system to get set back a couple
of months.  Setting the proper date fixed the problem.  I think screenblank
is comparing the current time against the of a file (/dev/kb ??) to check
for input. What ever it is checking against, the time does not get set back
when input occures therefore screenblank will see a huge (probably negative)
period of time between the current system time and the time of the last
input.
--
Stephen Martin               -------    LSI Logic Corporation of Canada, Inc.
Phone: (416) 620-7400     LSI|LOGIC|    Suite 1110, 401 The West Mall,        
Fax:   (416) 620-5005        |     |    Etobicoke, Ontario, Canada.
Email: smartin@lsican.uucp   -------    M9C 5J5
 or    smartin@Canada.lsil.com