[I've added some more information at the bottom of the message.  The topic
is old enough that I thought I should repost it all.]

**

On Fri, 7 Jan 2000, Christopher P. Gill wrote:

> I've noticed some slightly strange (but not really problematic) behaviour
> with the mice connected to my NetBSD machine (Quadra 800, NetBSD 1.4
> GENERIC kernel).
> 
> In my setup, I've got a KVM switcher box connected to that machine and my
> MacOS machine, so that I can share my keyboard, mouse and monitor between
> the two machines, just by flipping a switch.  The NetBSD machine only has
> an additional 3-button mouse connected for use with X-windows.  It's not
> on the MacOS machine because the driver control panel doesn't work with
> some newer interface elements (like the drop-down menus attached to
> buttons in a window).  The KVM switch is connected to one ADB port on the
> Q800, and the 3-button mouse uses the other port. 
> 
> At boot-up, the KVM box is always switched to the Q800, with both the
> keyboard and mouse plugged in.  It stays switched until the boot
> sequence is complete.  The weirdness is shown below: 
> 
> 
> ==>>
> Dec 24 01:19:51 gateman /netbsd: adb0 at obio0 (direct, II series): 4
> targets
> Dec 24 01:19:51 gateman /netbsd: aed0 at adb0 addr 0: ADB Event device
> Dec 24 01:19:51 gateman /netbsd: kbd0 at adb0 addr 2: extended keyboard
> Dec 24 01:19:51 gateman /netbsd: ms0 at adb0 addr 3: MicroSpeed mouse,
> default parameters
> Dec 24 01:19:52 gateman /netbsd: ms1 at adb0 addr 3: MicroSpeed mouse,
> default parameters
> Dec 24 01:19:52 gateman /netbsd: ms2 at adb0 addr 3: 1-button, 100 dpi
> mouse
> <<==
> 
> It seems to find the 3-button mouse *twice*.  Next time, it seems to find
> the Apple mouse twice:
> 
> ==>>
> Dec 24 02:05:00 gateman /netbsd: adb0 at obio0 (direct, II series): 4
> targets
> Dec 24 02:05:00 gateman /netbsd: aed0 at adb0 addr 0: ADB Event device
> Dec 24 02:05:00 gateman /netbsd: kbd0 at adb0 addr 2: extended keyboard
> Dec 24 02:05:01 gateman /netbsd: ms0 at adb0 addr 3: MicroSpeed mouse,
> default parameters
> Dec 24 02:05:01 gateman /netbsd: ms1 at adb0 addr 3: 1-button, 100 dpi
> mouse
> Dec 24 02:05:01 gateman /netbsd: ms2 at adb0 addr 3: 1-button, 100 dpi
> mouse
> <<==
> 
> and again:
> 
> ==>>
> Dec 28 13:39:12 gateman /netbsd: adb0 at obio0 (direct, II series): 4
> targets
> Dec 28 13:39:12 gateman /netbsd: aed0 at adb0 addr 0: ADB Event device
> Dec 28 13:39:12 gateman /netbsd: kbd0 at adb0 addr 2: extended keyboard
> Dec 28 13:39:12 gateman /netbsd: ms0 at adb0 addr 3: MicroSpeed mouse,
> default parameters
> Dec 28 13:39:12 gateman /netbsd: ms1 at adb0 addr 3: 1-button, 100 dpi
> mouse
> Dec 28 13:39:12 gateman /netbsd: ms2 at adb0 addr 3: 1-button, 100 dpi
> mouse
> <<==
> 
> 
> I had two failures booting into NetBSD around this time, but they might
> have been due to other hardware changes I was making, and the ADB sections
> succeeded each time.  MacOS boots always went fine.  After I'd shut
> everything down, checked all my connections, and powered up, it all went
> smoothly.
> 
> I know that having two mice on the same machine is a little unusual, but
> it's not supposed to be problematic, since trackballs/mice/joysticks and
> other pointing devices usually can co-exist peacefully.  Does anyone know
> why this might be happening? 


On Fri, 7 Jan 2000, David Brownlee wrote:

>       Just curious - does the problem happen without the KVM box?

Well, I've retested this with ADB switching bypassed, i.e. the keyboard
and Apple mouse are directly connected in series to one ADB port, and the
3-button mouse is connected to the other.  (Video was still switched).  I
booted NetBSD twice, and then re-routed the Apple mouse & keyboard through
the KVM switch box and booted up the last time.  All three times, I got
boot messages like the examples below (from the last two boots, since I
had a kernel panic during boot #1, which was necessary after another 
kernel panic): 

==>>

Jan 23 18:45:15 gateman /netbsd: adb0 at obio0 (direct, II series): 4
targets
Jan 23 18:45:15 gateman /netbsd: aed0 at adb0 addr 0: ADB Event device
Jan 23 18:45:15 gateman /netbsd: kbd0 at adb0 addr 2: extended keyboard
Jan 23 18:45:15 gateman /netbsd: ms0 at adb0 addr 3: 1-button, 100 dpi
mouse
Jan 23 18:45:15 gateman /netbsd: ms1 at adb0 addr 3: 1-button, 100 dpi
mouse
Jan 23 18:45:15 gateman /netbsd: ms2 at adb0 addr 3: 1-button, 100 dpi
mouse

[and again...]

Jan 23 19:41:38 gateman /netbsd: adb0 at obio0 (direct, II series): 4
targets
Jan 23 19:41:38 gateman /netbsd: aed0 at adb0 addr 0: ADB Event device
Jan 23 19:41:38 gateman /netbsd: kbd0 at adb0 addr 2: extended keyboard
Jan 23 19:41:38 gateman /netbsd: ms0 at adb0 addr 3: 1-button, 100 dpi
mouse
Jan 23 19:41:38 gateman /netbsd: ms1 at adb0 addr 3: 1-button, 100 dpi
mouse
Jan 23 19:41:38 gateman /netbsd: ms2 at adb0 addr 3: 1-button, 100 dpi
mouse

<<==

NetBSD now reports the Apple mouse thrice, and fails to report the
presence of the Microspeed mouse altogether, although I can use the
Microspeed mouse, all three buttons, with no problem.  Weird, but not a
problem as far as I can tell.

Clues, anyone?


/*======================================================================
"Don't die wondering..."                http://www.cldc.howard.edu/~cpg
                                              email: cpg@scs.howard.edu
chris out-              Christopher P. Gill
  peace.        C.L.D.C. Senior System Operator (Ret.)
======================================================================*/