On Tue, Oct 09, 2001, Jan Schubert <[EMAIL PROTECTED]> wrote: > When connecting the camera i get (the camera/cable > works fine using a win98-system): [snip timeouts] > Oct 9 20:01:26 jupiter kernel: hub.c: USB new device connect on bus1/1, > assigned device number 72 > Oct 9 20:01:30 jupiter kernel: usb_control/bulk_msg: timeout > Oct 9 20:01:30 jupiter kernel: usb.c: USB device not accepting new > address=72 (error=-110)
This is usually indicitive of an IRQ routing problem. What kind of system are you using? Can you give me the output of /proc/interrupts? > Oct 9 20:01:31 jupiter kernel: hub.c: port 1, portstatus 100, change 0, > 12 Mb/s > Oct 9 20:01:31 jupiter kernel: hub.c: port 1 of hub 1 not reset yet, > waiting 200ms > Oct 9 20:01:31 jupiter kernel: hub.c: port 1, portstatus 100, change 0, > 12 Mb/s > Oct 9 20:01:31 jupiter kernel: hub.c: port 1 of hub 1 not reset yet, > waiting 200ms > Oct 9 20:01:31 jupiter kernel: hub.c: port 1, portstatus 100, change 0, > 12 Mb/s > Oct 9 20:01:31 jupiter kernel: hub.c: port 1 of hub 1 not reset yet, > waiting 200ms > Oct 9 20:01:31 jupiter kernel: hub.c: port 1 of hub 1 not enabled, > trying reset again... [snip more of the same] > Oct 9 20:01:34 jupiter kernel: hub.c: port 1 of hub 1 not enabled, > trying reset again... > Oct 9 20:01:34 jupiter kernel: hub.c: Cannot enable port 1 of hub 1, > disabling port. > Oct 9 20:01:34 jupiter kernel: hub.c: Maybe the USB cable is bad? This is very odd. I haven't see this. Looks like the roothub got confused. JE _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
