> 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 ma
Erik DeBill [[EMAIL PROTECTED]] 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
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
> 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
hello
i made an kernelupdate 2.2.16 to 2.4.2 and i am using RH 7.0
with the 2.2.16 kernel the usb-visor communication works perfekt.
now with the 2.4.2 kernel my usb does want to connect to my handspring-visor
#dmesg
...
usb.c: registered new driver hub
uhci.c: USB UHCI at I/O 0xd400, IRQ 9
uhci
5 matches
Mail list logo
