| View previous topic :: View next topic |
| Author |
Message |
mortar
Tux's lil' helper
Joined: 03 Feb 2005
Posts: 131
|
 Posted: Mon Apr 03, 2006 12:14 am Post subject: Is this destructive? "device descriptor read/64, error |
 |
|
Basically everytime I plugged in any USB devices into my laptop, I would continually receive this error, rendering the device plugged in, unusable.
| Code: | | "device descriptor read/64, error -71" |
If it was a USB Storage device for instance, the laptop would detect the device, assign it an SDXy and basically drop the connection, leaving many USB disconnect messages similar to this one below and then continue to repeat the whole process again, errors, disconnections and all..
| Code: |
usb 1-7.4: new full speed USB device using ehci_hcd and address 28
usb 1-7.4: USB disconnect, address 28
|
I was sure that it wasn't good for the devices that were plugged in, and having installed my laptop months ago as a Brand New Gentoo N00b, I thought i'd have another shot at it and try again..
I've got it to the point now, where i've compiled all of the usb devices as modules, load all the modules and everything seems to work fine.
When I plug in a USB Device, I only receive "device descriptor read/64, error -71" twice. Once as soon as you plug it in, and soon after it assigns an SDXy device.
Is there any chance that this could be damaging the drive if I leave it like this? I've searched the forums high and low but can't find a solution to fix the error... I did find this page though, and followed it's instructions, but it still renders the same problem. |
|
| Back to top |
|
 |
fangorn
Veteran
Joined: 31 Jul 2004
Posts: 1886
|
| Posted: Mon Apr 03, 2006 1:05 pm Post subject: |
|
|
This just tells you, that the USB_core cannot identify the device plugged in.
AFAIK this can be caused because the driver is asking for an identification too fast. There is a kernel parameter (got mentioned here somewhere) which I cant remember at the moment and never had to use.
It could also be an inconsistency of the chipset driver and the actual hardware on your board.
Did I read this correct? you load every kernel module for usb explicitely?
What I did is compile usb_core into the kernel, everything else usb_* as modules and let udev handle the loading of the modules. Works like a charm.
_________________
Video Encoding scripts collection | Project page |
|
| Back to top |
|
|
mortar
Tux's lil' helper
Joined: 03 Feb 2005
Posts: 131
|
| Posted: Mon Apr 03, 2006 10:02 pm Post subject: |
|
|
Yeh I tried to load usbcore/ ehci/ohci/uhci etc straight from the kernel but when I was having problems, I compiled them all as modules to test the inconsistencies. I might try that but I wasn't aware that udev does that? As soon as you plug in the device? Does it work straight from a fresh install or do you have to configure something?
So in your opinion I can still use storage devices fine on this laptop? |
|
| Back to top |
|
|
fangorn
Veteran
Joined: 31 Jul 2004
Posts: 1886
|
| Posted: Tue Apr 04, 2006 5:54 am Post subject: |
|
|
With a recent udev it works in most cases for mouse and usb_storage. Havent had any other devices, but tried HDD, CF, SD, DVD-RW and such devices without problems.
Depends on the Chipset though. Sometimes you have to experiment with driver modules. EHCI_HCD is for USB2.0 devices OHCI_HCD and UHCI_HCD are for USB1.1 devices, where AFAIK UHCI_HCD is only the last hope (the kernel claims for borked chips IIRC  ) because the detection does not work correctly, but that didnt happen to me for half a year.
_________________
Video Encoding scripts collection | Project page |
|
| 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
