Re: USB mouse woes

Doug White wrote:
> 1. With the mouse connected collect the output of usbdevs -v. That should
> show how the mouse is connected.

Relevant part is:

Controller /dev/usb3:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000),
VIA(0x0000), rev 1.00
 port 1 powered
 port 2 addr 2: low speed, power 50 mA, config 1, product
0x006a(0x006a), vendor 0x045e(0x045e), rev 0.17

I also dug up another mouse (a micro innovations wireless unit):

Controller /dev/usb3:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000),
VIA(0x0000), rev 1.00
 port 1 powered
 port 2 addr 2: low speed, power 100 mA, config 1, Wireless RF
Mouse(0x0101), Cellink Co., LTD.(0x1733), rev 0.01

with similar results.

Then tried a different USB port (even though it works perfectly fine
with both Windows and Ubuntu).

Again, detected fine:

ums0: Cellink Co., LTD. Wireless RF Mouse, rev 1.10/0.01, addr 2, iclass 3/1
ums0: 3 buttons and Z dir.

but nothing happens with moused.

> 2. From the trace it looks like the mouse is USB2 since ehci keeps popping
> up. Try removing ehci from your kernel.

All of the above was with ehci removed.

> STALLED is an error in USB terms.  Exactly why the device is stalling,
> though, is unclear.

Given that it now appears to be stalling with two different mice, from
two different vendors, it would appear to be something at fault with the
handling of the USB chipset.  Again, for reference:

usb0: <VIA 83C572 USB controller> on uhci0
usb0: USB revision 1.0
usbd_get_string: getting lang failed, using 0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered

This is on an MSI K8T Neo-FSR mainboard with a Socket 754 Athlon 64
running -CURRENT as of today (6/28/2005).

Both mice work fine when connected via a USB->PS/2 converter.

-aDe