Thanks to all who responded to my original question:
> On a few occasions recently, the monitor attached to our
> Sparc 1000 becomes locked up in the screenblank state. So
> today I remotely killed the screenblank routine and that
> took the screen out of blank but it appears there is no
> communication now between the 1000 and the monitor even
> though the 1000 is humming along just fine.
>
> Is there any way to get these 2 guys talking together again
> short of a reboot? I thought I could find a driver process
> for the monitor and give it a kill -1 but I can't.
I received the following 4 replies. I've only had one lockup
since I posted and, after trying Stephen Hauskins suggestion
(sunlist@mendel.ucsc.edu) I was able to CTRL C the monitor
back to life after issuing the kbd_mode -a command.
More testing is required.
***************************************************
From: sunlist@mendel.ucsc.edu
If you have openwindows installed, try using the command:
/usr/openwin/bin/kbd_mode -a
This should revive the monitor.
***************************************************
From: jmarble@zambezi.cambric.com (Jeff Marble)
Sun has said that this is a bug with screenblank and the a conflict with the
date command. For us it was on several machines, but for only several hours.
Our only way to get the monitor back was to reboot.
***************************************************
From: "Brian T. Wightman" <wightman@sol.acs.uwosh.edu>
Sorry if this is late. You may have hit a ^S. This happens to us
quite frequently in our "open" labs. Try a ^Q to see if that restarts
the screen.
***************************************************
From: root@treveris.Uni-Trier.DE (Smooth Operator)
we do have very similar problems. The usual way to recover is simply
sending a kill -HUP to init.
If this doesn't work your propably will have to reboot.
***************************************************
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:27 CDT