Hi

I am having trouble getting a piece of hardware to succesfully connect. I get the following if I type dmesg after connecting and disconnecting the device 4 times:

usb 3-2: new high speed USB device using ehci_hcd and address 2
usb 3-2: device not accepting address 2, error -71
usb 3-2: new high speed USB device using ehci_hcd and address 3
usb 3-2: unable to read config index 0 descriptor/all
usb 3-2: can't read configurations, error -71
usb 3-2: new high speed USB device using ehci_hcd and address 4
usb 3-2: device not accepting address 4, error -71
usb 3-2: new high speed USB device using ehci_hcd and address 5
usb 3-2: can't set config #1, error -71
usb 3-2: new high speed USB device using ehci_hcd and address 6
usb 3-2: usbfs: USBDEVFS_CONTROL failed cmd lt-test_usrp_st rqt 64 rq 160 len 13 ret -71 usb 3-2: usbfs: USBDEVFS_CONTROL failed cmd usrper rqt 64 rq 160 len 2 ret -71
usb 3-2: USB disconnect, address 6
usb 3-2: new high speed USB device using ehci_hcd and address 7
usb 3-2: device not accepting address 7, error -71
usb 3-2: new high speed USB device using ehci_hcd and address 8
usb 3-2: device not accepting address 8, error -71
usb 3-2: new high speed USB device using ehci_hcd and address 9
usb 3-2: can't set config #1, error -71
usb 3-2: new high speed USB device using ehci_hcd and address 10
usb 3-2: device descriptor read/8, error -71
usb 3-2: device descriptor read/8, error -71
usb 3-2: new high speed USB device using ehci_hcd and address 11
usb 3-2: usbfs: USBDEVFS_CONTROL failed cmd usrper rqt 64 rq 160 len 4 ret -71
usb 3-2: usbfs: USBDEVFS_CONTROL failed cmd usrper rqt 64 rq 1 len 0 ret -71
usb 3-2: usbfs: USBDEVFS_CONTROL failed cmd usrper rqt 64 rq 1 len 0 ret -71
usb 3-2: usbfs: USBDEVFS_CONTROL failed cmd usrper rqt 64 rq 160 len 14 ret -71 usb 3-2: usbfs: USBDEVFS_CONTROL failed cmd usrper rqt 64 rq 160 len 6 ret -71
usb 3-2: USB disconnect, address 11

I am certain that the device works because I tested it on another machine. It worked fine a while back, but now I get these problems. Searching for a solution online proved unsuccessful. The closest I got was someone explaining how the order of connecting certain devices on the same hub might cause one device to stop connecting. This is the only thing I can think of that may have happened, seeing as I didn't make any system changes between the time when the device worked, and when it stopped working. If this is the problem, how can it be fixed?

I am using a Chronos USB2.0 PCI Host Card, and a debian machine with the standard 2.6.15 kernel from a package. My last attempt to connect also failed. The output of tail -f val/log/messages was:

Apr 4 12:48:21 sar6 kernel: usb 3-2: new high speed USB device using ehci_hcd and address 40 Apr 4 12:48:22 sar6 kernel: usb 3-2: new high speed USB device using ehci_hcd and address 41 Apr 4 12:48:23 sar6 kernel: usb 3-2: new high speed USB device using ehci_hcd and address 42 Apr 4 12:48:23 sar6 kernel: usb 3-2: new high speed USB device using ehci_hcd and address 43

Any help would be greatly appreciated.

Regards

Lance


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to