This may well be a problem in either sane or libusb, and even if its a usb-kernel bug, it is unlikely to be related to the SET_ADDRESS problem. Turned it physically off (using the switch in the power supply), and left it off for 3-4 minutes. I've tried rebooting at least 15 times, to no avail. On looking in /var/log/syslog, I found error lines of this form: usb 3-7: device not accepting address 2, error -62 usb 3-7: new full-speed USB device number 3 using xhci_hcd usb More about the author
scillystuff about 3 years ago Great, just what I was after. Thus the usb-core driver and any high-level USB drivers can all be left loaded while this is being done. Then it's just simply: # echo 0000:00:1d.0 > unbind to turn it off. A valuable command for new users is: tail -f /var/log/syslog (or /var/log/messages if older distro) Issue the above command in a terminal and then plug in a usb device. https://ubuntuforums.org/showthread.php?t=898939
Thank you!!! I recently upgraded my H/W (p35+ich9) and it became worse - i can now get the device working only if is connected before boot, and even then it sometimes fails with The error was still there. will smith about 5 years ago God bless you!
ur solution solved the problem. Ashwin Nanjappa over 2 years ago I was tearing my hair out on this error. something else is going on here,.. Device Descriptor Read/64 Error 32 So, to all fellow smarty pants out there that think you know better: save yourself some headache and give it a try.
Can we sort these into other bugs and attempt to triage them, rather than having a giant metabug? On some devices connected on it, no problem. Maybe I need to have my computer connected to the charger (via cable) when I turn it on. This was a problem under 11.04 and I am now running the 12.04 beta and its still happening.
I haven't tried unloading the EHCI component. "device Descriptor Read/64, Error -71" If it is not installed, from the terminal you can issue the command: sudo aptitude install cheese The cheese application will then be available for your usage. I also have seen this same problem on other computers. If I un-mount the drive and try to re-mount it, I get the error again.
My mouse would still randomly disconnect and never reconnect again. his comment is here I was having problem with a mp3 player and with your line its fixed now, really awesome!! Usb Device Not Accepting Address Error 71 What could have gone wrong in 2 days on this notebook where nothing had been touched or tampered with? Usb Device Not Accepting Address Error 32 Report a bug This report contains Public information Edit Everyone can see this information.
This patch makes a more pessimistic assumption. my review here Cheers! Bus 001 Device 001: ID 0000:0000 0:10.51 phil@Ubuntu:~/kernel$ /usr/bin/time --format="%E" lsusb Bus 002 Device 001: ID 0000:0000 Bus 001 Device 002: ID 046d:08f6 Logitech, Inc. Luke Hoersten (lukehoersten) wrote on 2006-08-19: #3 Now none of my USB devices work, not even my printer. Device Not Accepting Address Error 62
Ex.: usb 3-1: device descriptor read/64, error -62 or usb 4-2: device descriptor read/64, error -71 or usb 2-3: device descriptor read/64, error -101 but the root of the problem is Carlos C Soto almost 4 years ago Thanks! However, I do use "noapic" as a boot option. http://completeprogrammer.net/device-not/device-not-accepting-address-25-error.html Not the answer you're looking for?
Connected all USB devices back, and everything is now working fine. Usb Device Descriptor Read/64 Error -32 also get this message shortly after each bootup. Thanks Dean On 20/08/06, ChuckShort
I had a logitech USB keyboard on a ThinkPad T420 and apart from the lower right USB port all others threw this error.
The log messages for me look like this: usb 6-1: new low-speed USB device number 116 using uhci_hcd usb 6-1: device not accepting address 116, error -71 hub 6-0:1.0: unable to At that point the usb-hub still worked for my mice, (but not my external HD, because that required more power). Juan J. "device Descriptor Read/64, Error -62" A soft reboot on didn't appear to fix it, so definitely power off/unplug/power on.
Note You need to log in before you can comment on or make changes to this bug. Michel Andre over 1 year ago Bonjour Merci beaucoup car, suite migration Ubuntu 15.4 , j'avais ces messages d'erreurs et un démarrage très difficile. Thanks so much! :-) diyhouse over 2 years ago Sorry,.. navigate to this website But I used the Ubuntu 10.04.
Hope that helps. Any suggestions, please? Shev77 about 3 years ago Thank you very much! This machine is a Serverworks Dual P3 box and is running the Fedora 2.6.15-1.1833_FC4smp kernel; the USB disk is for backup purposes.
Page 1 of 2 12 Last Jump to page: Results 1 to 10 of 14 Thread: [SOLVED] USB: device not accepting address, new high speed USB device using ehci_hcd. Gustavo Azambuja (gazambuja) wrote on 2006-08-23: #7 ok, ok, I'm stupid, after write the comment, i search more info and find this: http://www.linux-usb.org/FAQ.html#ts6 Q: Why doesn't USB work at all? Before the changes I get: [ 85.867469] ohci_hcd 0000:00:0b.0: wakeup [ 86.251175] usb 2-1: new full speed USB device using ohci_hcd and address 2 [ 86.435057] usb 2-1: device descriptor read/64, twsh 5 months ago Thank you very much, I thought my hardware was becoming faulty.
Errors that i received: [486806.248034] usb 3-1: new low speed USB device using uhci_hcd and address 101 [486806.660012] usb 3-1: device not accepting address 101, error -71 I mention that I You saved me. It seems like there ought to be a kernel parameter to avoid some USB buses but I can't find one. (Based on the answer by titaniumtux but trying to avoid unbinding For those guys, whom the first method (recommended by Paul) did not help, try to use a shorter cable to attach your device.