On Sun, 2 Jan 2000, Chris Tribo wrote:

>     I finally got a hold of a VS-XXX-BB for my 5000/25 (thanks Bob!),
> however, I can't seem to get things to work right. The keyboard works fine
> regardless if the mouse is installed at the prom. Doing a cnfg 3 shows both
> the keyboard and mouse with the proper model numbers and ROM revisions.
> Rolling the mouse around in the prom gives me [/``, etc. As soon as I boot,
> I can't get the keyboard to work in single user or in X when the mouse is
> installed. If I start the system without the mouse, keyboard works fine in
> both single user and X. Now for the weird part: when I have the mouse
> connected, I can't type anything, but the system still listens to
> cntrl-alt-Return and cntrl-alt-backspace, and moving the mouse around gives
> me the [/`, chars in both X and single user.
>     I've been running under 1.4.1, 1.4P and I'm currently at the December
> 1.4P snapshot. Is this a known problem with the Puck mouse, Serial.Bus
> support, or has it been fixed in the 1.4.2 Alpha snapshot?

  I've had my 5000/25 (and maybe the 5000/50) do this once in a while, but
I've only seen NetBSD have problems.

  What appears to be happening is that the PROM seems to swap the
ACCESS.bus addresses of the keyboard and mouse on occasion.  The PROM
routines know what the address of each device is, but NetBSD assumes they
are at the same address all the time.  I think the proper fix would be to
have NetBSD interrogate the ACCESS.bus devices to determine what's
actually connected, but that requires a much more sophisticated driver
that can send packets to the bus (and be able to read packets without
losing data).  I've been testing a work-around that attempts to detect
a packet from the wrong device type, and swap the handler entries.  It
still has some problems though.

--
Michael L. Hitch			mhitch@montana.edu
Computer Consultant
Information Technology Center
Montana State University	Bozeman, MT	USA