Now I believe that this is a separate problem to my
last... and this may even be a longstanding problem that not very many
people will see.

	For most of my NetBSD time, I have had only the cgtwo0 device
configured (and NOT the bwtwo0) because of a bug.  PK has since fixed
this bug, and I can configure both cgtwo0 and bwtwo0 and have
everything boot and work just fine.

	However, in this configuration, when I drop into the DB>
prompt, it does not reset the console to black and white --- it leaves
the colour planes on rendering the text usually unreadable.  Also
affected is the plain old console prompt --- after X has run at least
once, the console prompt will be in some strange random (usually an
ugly pink) colour, and it won't come out of it.

	So... something is not reacting entirely properly.  I can't
guarentee it, but it seems to me that this all happened recnetly when
I compiled both drivers into the kernel... all in an effort to move
closer to working with a generic kernel.

	Is that all?  Well... it would be cool if X would detect this
hackery.  Currently, X seems to ignore /dev/fb, and detect that it can
use /dev/bwtwo0.  I have to start X with -dev /dev/fb to make it
use the cgtwo0.

	Maybe someone has a newer version of X? ... or is there some
stuff we can fix here.

Dave.

-- 
============================================================================
|David Gilbert, PCI, Richmond Hill, Ontario.  | Two things can only be     |
|Mail:      dgilbert@jaywon.pci.on.ca         |  equal if and only if they |
|http://www.pci.on.ca/~dgilbert               |   are precisely opposite.  |
=========================================================GLO================