cvs commit: src/sys/dev/usb ums.c

[Doug Barton]

Julian Elischer wrote:
> 
>> Apparently the recent changes to mouse stuff have broken my Dell docking
>> station. I get this on boot:
>>
>> Starting ums0 moused:moused: unable to open /dev/ums0: No such file or
>> directory
>>
>> .
>> Starting ums1 moused:usb3: *** WARNING: opening low/full speed device,
>> this
>> does not work yet.
>>
>> moused: unable to open /dev/ums1: Input/output error
>>
>> Plugging the same mouse directly into the machine works fine.
>>
> 
> which mose do yuo use?
> ums1 or ums0?

It used to be ums0 only. I only have one USB mouse plugged in at any one
time (although depending on location it can be different mice).
Interestingly, when I unplugged it from the docking station and plugged it
into the laptop, I got this:

ums1: at uhub5 port 1 (addr 3) disconnected
ums1: detached
ums0: Logitech Trackball, rev 1.10/2.20, addr 2, iclass 3/1
ums0: 3 buttons and Z dir.

The last two entries are pretty normal, but apparently it was seen as ums1
on boot anyway.

> looks like the inteface is ehci?

Oh bugger. I was messing with my kernel config file yesterday adding wlan
stuff, and consolidating a few old config files I had laying around, and
"somehow" this must have gotten uncommented. Sorry about the noise, this
docking station has never worked with ehci enabled. I will try nuking that
and building a new kernel.

Actually that reminds me ... if anyone is interested in working on USB2/ehci
stuff, I have an interesting collection of USB 1 and 2 devices, including a
USB 2 device that works, and a couple that don't (including this docking
station). I'd be happy to test some patches and/or give more detail if
someone is interested.

> what does usbdevs say?

For completeness sake:

addr 1: UHCI root hub, Intel
 addr 2: BC02 Bluetooth USB Adapter, Dell
addr 1: UHCI root hub, Intel
 addr 2: Trackball, Logitech
addr 1: UHCI root hub, Intel
addr 1: EHCI root hub, Intel
 addr 2: Port Replicator, Dell

I'll go try a non-ehci kernel just to be sure, but I'm 99% sure that will
solve the problem. Once again, sorry for the noise/time wasting.

Doug

-- 

	If you're never wrong, you're not trying hard enough