Subject: Re: Three X server problems on NetBSD/shark 4.0
To: Ignatios Souvatzis <firstname.lastname@example.org>
From: Michael Lorenz <email@example.com>
Date: 12/29/2007 10:53:54
-----BEGIN PGP SIGNED MESSAGE-----
On Dec 29, 2007, at 07:02, Ignatios Souvatzis wrote:
> On Fri, Dec 28, 2007 at 01:11:35PM -0500, Michael Lorenz wrote:
>> Switching in and out of X never worked right, shouldn't be enabled at
> Just for the record - it worked fine in 3.0 with the 1.6 XF86_SVGA.
Yeah, it works with a vga(4) console, it may or may not work with
framebuffer consoles - some drivers can't really program video modes
and some XFree86 driver can't be arsed to clean up after themselves
so some combinations work while others don't. Igsfb with wsfb should
work though since wsfb doesn't do any video mode programming either.
All it takes is a #define somewhere in XFree86's bowels, can't
remember where exactly though.
>> And 16bit mode won't work either unless you have patches rotting
>> in my source tree for a while now.
>> Besides that - weird things may happen if X doesn't start on virtual
>> console 0.
> Oh. that is, I should disable getty on ttyE0?
No, just make sure it's started from ttyE0. The problem is that X's
BSD support code doesn't know which console it's started on and
always opens /dev/ttyE0 to read keyboard and mouse events ( with the
keyboard driver at least, kbd uses /dev/wskbd* and /dev/wsmouse* )
and, more importantly, to mmap() the framebuffer. It will switch
ttyE0 into framebuffer mode ( essentially shutup console output ) but
if you're on a different virtual console it doesn't get shut up and
you may not get input events. Yes, that's a bug in X but apparently
it's not annoying enough for anyone to fix it, I at least always had
bigger fish to fry in the past year, and I don't use xdm either, just
startx from ttyE0 always worked for me :/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
-----END PGP SIGNATURE-----