Subject: Re: Console/X-server problems on SS5
To: John D. Baker <email@example.com>
From: Michael <firstname.lastname@example.org>
Date: 09/28/2005 17:46:44
Content-Type: text/plain; charset=US-ASCII
> What I'd read in the archives appeared to discuss both issues (cgsix
> improvements and wscons support) at the same time. Separate devices,
> of course, but this is where they come together, so to speak.
> And the default config files, naturally, don't enable wscons support.
> They don't even have the requisite items present but commented out, so
> unless I knew what to add, I wouldn't be able to enable it anyway.=20
> Not that I'm presently interested in wscons support, but just trying
> to figure out why X11/keyboard/etc. is misbehaving and fix it--and the
> wscons support stuff was the most recent work in that region I'd read
Hmm, the last commits in this area were about making it work with wskbd
and ignoring idle events.
> Looks pretty ordinary to me.
Indeed. Had to be sure ;)
> The "kbd: returning ENOTTY" at the
> end was probably appended to the dmesg when I started X11 manually.
This is the keyboard driver complaining that someone called an ioctl it
doesn't know about. Remains to be seen what the Xserver tried to do and
why it choked.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (NetBSD)
-----END PGP SIGNATURE-----