On Fri, Dec 24, 2004 at 02:54:07PM -0500, Tom Vier wrote:

> The installer image boots and gets to the "enter your terminal type" prompt,
> and then the mouse and kbd are basically dead.

The short answer: use a serial console.

The long answer: the Indigo2, like the Indy, has a PC-style keyboard/mouse
chip.  1.6.2 did not have a real driver for the keyboard/mouse; when using
a glass TTY as a console, it used ARCS.  2.0 has a keyboard/mouse driver, so
the kernel will attach the pskbd/psaux driver when it notices that it's 
running on an Indy or Indigo.

The Indy's framebuffer is a newport.  Most Indigo2 use GR2 as a framebuffer.
Although both have NetBSD drivers, the GR2 wasn't quite stable enough to be
pulled up to 2.0.  (I _will_ finish the GR2 driver.  Someday.)

So, what's happening is that the kernel thinks that it's using ARCS for
console I/O (because you don't have a kernel-supported framebuffer), but the
kernel also attached the pskbd/psaux driver and your keypresses aren't 
associated with console input.

This should be fairly easy to work around -- if console is not newport, the
pskbd/psaux attach should be made to fail.
-- 

-- Chris
	GPG key FEB9DE7F (91AF 4534 4529 4BCC 31A5  938E 023E EEFB FEB9 DE7F)