Re: k 2.4.2; usb; handspring-visor

[Bob McElrath <rsmcelrath@students.wisc.edu>]

[-- Attachment #1: Type: text/plain, Size: 1654 bytes --]

Erik DeBill [edebill@swbell.net] wrote:
> On Wed, Apr 11, 2001 at 08:52:30AM -0500, John Madden wrote:
> > > Apr  8 23:33:09 horus kernel: hub.c: USB new device connect on bus1/1,
> > > assigned device number 5
> > > Apr  8 23:33:12 horus kernel: usb_control/bulk_msg: timeout
> > > Apr  8 23:33:12 horus kernel: usb.c: USB device not accepting new
> > > address=5 (error=-110)
> > 
> > Funny, I've been getting the same messages (on 2.4.0 and now 2.4.3) for a 
> > while now, and I thought the problem was with my Visor.  (...I haven't 
> > been able to sync for months...)
> 
> Have you tried using the normal UHCI driver, instead of the UHCI
> Alternate Driver (JE)?  I know the "alternate" one is default from
> Linus, but it's incompatible with the usb-visor driver.  The
> maintainer said he'd patch the docs to clear up the confusion, but it
> hasn't shown up in the mainstream kernels yet.

I've also been seeing these messages (for a very, very long time), with
both the uhci and usb-uhci drivers, with many different devices (not
just visor).  Usually the only way to fix it is to have the usb stuff
compiled as modules, remove it all, and the re-insmod it all.  Then it
works again for a little while...

There really needs to be only one driver.  It's just confusing.

> In my case, trying to use the visor would actually lock up the
> machine, requiring a cold boot.  Switched to the other UHCI driver
> and it works fine.

Never had to reboot though...on either x86 or alpha with UHCI...

Cheers,
-- Bob

Bob McElrath (rsmcelrath@students.wisc.edu) 
Univ. of Wisconsin at Madison, Department of Physics

[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]