| View previous topic :: View next topic |
| Author |
Message |
dave.fraser
n00b
Joined: 07 Jul 2002
Posts: 12
Location: Scotland
|
 Posted: Wed Apr 30, 2003 4:22 pm Post subject: USB flash drive |
 |
|
I have a USB flash drive, which works OK on my laptop with Redhat installed. I have all the necessary kernel modules installed (I think), as well as hotplug, but the device can't be accessed. I've read a couple of other related threads, but I seem to have a different problem.
dmesg says...
| Quote: | uhci.c: cc00: wakeup_hc
uhci.c: root-hub INT complete: port1: 480 port2: 493 data: 4
hub.c: port 1, portstatus 100, change 0, 12 Mb/s
hub.c: port 2, portstatus 101, change 1, 12 Mb/s
hub.c: port 2 connection change
hub.c: port 2, portstatus 101, change 1, 12 Mb/s
hub.c: port 2, portstatus 101, change 0, 12 Mb/s
hub.c: port 2, portstatus 101, change 0, 12 Mb/s
hub.c: port 2, portstatus 101, change 0, 12 Mb/s
hub.c: port 2, portstatus 101, change 0, 12 Mb/s
hub.c: port 2, portstatus 103, change 0, 12 Mb/s
hub.c: new USB device 00:07.2-2, assigned address 2
usb.c: kmalloc IF c87bc280, numif 1
usb.c: skipping descriptor 0x29
usb.c: skipped 1 class/vendor specific endpoint descriptors
usb.c: new device strings: Mfr=1, Product=3, SerialNumber=0
usb.c: USB device number 2 default language ID 0x409
Manufacturer: Prolific Technology Inc.
Product: USB Embedded Hub
hub.c: USB hub found
hub.c: 2 ports detected
hub.c: part of a compound device
hub.c: individual port power switching
hub.c: individual port over-current protection
hub.c: Port indicators are not supported
hub.c: power on to power good time: 100ms
hub.c: hub controller current requirement: 100mA
hub.c: port removable status: FF
hub.c: local power source is lost (inactive)
hub.c: no over-current condition exists
hub.c: enabling power on all ports
usb.c: hub driver claimed interface c87bc280
usb.c: kusbd: /sbin/hotplug add 2
hub.c: port 1, portstatus 101, change 1, 12 Mb/s
hub.c: port 1 connection change
hub.c: port 1, portstatus 101, change 1, 12 Mb/s
hub.c: port 1, portstatus 101, change 0, 12 Mb/s
uhci.c: uhci_result_interrupt/bulk() failed with status 500000
[c7d221e0] link (07d22060) e0 IOC Stalled Babble Length=2 MaxLen=2 DT0 EndPt=1 D
ev=2, PID=69(IN) (buf=077aaf28)
hub.c: nonzero status in irq -75
usb_control/bulk_msg: timeout
hub.c: usb_hub_port_status (2) failed (err = -110)
hub.c: connect-debounce failed, port 1 disabled
usb_control/bulk_msg: timeout
hub.c: cannot disable port 1 of hub 2 (err = -110)
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -6
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -6
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -6
usb_control/bulk_msg: timeout
hub.c: usb_hub_port_status (2) failed (err = -110)
usb_control/bulk_msg: timeout
hub.c: get_hub_status failed
usb_control/bulk_msg: timeout
hub.c: usb_hub_port_status (2) failed (err = -110)
usb_control/bulk_msg: timeout
hub.c: usb_hub_port_status (2) failed (err = -110)
usb_control/bulk_msg: timeout
hub.c: get_hub_status failed
SCSI subsystem driver Revision: 1.00
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
|
As far as I can tell, the embedded hub is being set up OK (it has 2 logical drives inside), but when it comes to the actual storage devices, somethings falling over. One of the logical drives is an encrypted drive, which I don't expect to work (although if anyone has any tips they would be welcome). The main drive, though should work OK.
I'm baffled. Any ideas? |
|
| Back to top |
|
 |
BradN
Advocate
Joined: 19 Apr 2002
Posts: 2391
Location: Wisconsin (USA)
|
| Posted: Wed Apr 30, 2003 8:12 pm Post subject: |
|
|
| You could possibly try some newer/older kernels to see if they help the problem at all. Maybe something from the 2.5 series? |
|
| Back to top |
|
|
dave.fraser
n00b
Joined: 07 Jul 2002
Posts: 12
Location: Scotland
|
| Posted: Wed Apr 30, 2003 9:05 pm Post subject: Seems like a hardware fault |
|
|
OK, I've done some googling (which I should've done before posting...  ) and it seems like this is a fault with the USB controller on my VIA mothertboard, which dies when it receives a babble message (whatever that is). Arse! |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
