On Thu, 15 Feb 1996 15:46:19 +1030 
 Ian.Dall@dsto.defence.gov.au wrote:

 > Screenblank is weird. When run under X is seems to work OK.  Without X
 > once blanked, it does not wake up on keyboard input. In fact keyboard
 > input doesn't seem to work until it has been woken up. I wake it up
 > from another machine by
 > 
 >   rsh harold echo \> /dev/console

I've noticed that screenblank doesn't work 100% right ... One of these 
I'll look at why.  However, it does work ok if I don't run X ... on my 
3/50, 3/60, 4/260, and SS2.  The problem I've seen is that the 
framebuffer gets blanked during my xlock screensaver, making it hard to 
see the neat eye candy I find so much amusement in :-)  I.e. I don't see 
the problem you're referring to.  Try hitting <return>.

This is probably a bug in the console/keyboard/mouse drivers ... I 
ktrace'd the SunOS screenblank(1) to figure out how it worked (re. 
checking for keyboard, mouse activity) and wrote my version one afternoon 
because I was tired of setting up the sunos compat stuff just to run 
screenblank(1) :-)  I sort of assumed that it would work similarly ... I 
either goofed something up, or the keyboard/mouse drivers don't report 
activity in the same fashion that SunOS did.  I never really paid 
attention to whether or not SunOS's screenblank(1) exhibited the same 
behavior under NetBSD as the native one.

--------------------------------------------------------------------------
Jason R. Thorpe                                       thorpej@nas.nasa.gov
NASA Ames Research Center                               Home: 408.866.1912
NAS: M/S 258-6                                          Work: 415.604.0935
Moffett Field, CA 94035                                Pager: 415.428.6939