Subject: Re: wskbd not attached to wsdisplay
To: None <port-i386@netbsd.org>
From: Greg A. Woods <woods@weird.com>
List: port-i386
Date: 10/06/2000 18:00:42
[ On Friday, October 6, 2000 at 21:48:39 (+0200), Manuel Bouyer wrote: ]
> Subject: Re: wskbd not attached to wsdisplay
>
> I had to uncomment:
> #keyboard       auto
> in wsconf.conf

Which causes "/usr/sbin/wsconscfg -k" to be run....

Can that not be always permitted (i.e. have the default wscons.conf
ship with that line uncommented)?

I also find it extremely annoying that I can't leave "screen 0"
uncommented in /etc/wscons.conf either.  If there's hardware brain
damage that means the driver doesn't allow the already attached console
screen to be reconfigured then at least there should be a way to find
out what the current configuration is from within wsconscfg and then
silently succeed without doing anything if the new specification is the
same, or else just print a warning if it is different.

Currently when you boot a system with default configs and a serial
console you see the login prompt on the screen but even if you run
"wsconscfg -k" you're on the wrong screen and you have to switch to the
first active virtual console before things work.  Switching back to 

Someone familiar with wscons innards should boot a system on a serial
console and see just how weird and brain damaged things are with the
default configs!  It really shouldn't matter where the system console is
redirected -- the wscons hardware configuration should always be the
same if it's enabled at all.

-- 
							Greg A. Woods

+1 416 218-0098      VE3TCP      <gwoods@acm.org>      <robohack!woods>
Planix, Inc. <woods@planix.com>; Secrets of the Weird <woods@weird.com>