I get "device not accepting address". If the device works OK at full speed on the same system, after you "rmmod ehci-hcd", this is likely the problem you're seeing. What am I? Found http://paulphilippov.com/articles/how-to-fix-device-not-accepting-address-error Sure enough, inserting a powered USB hub in the equation solved it. this contact form
None, the status of the bug is updated manually. I also have a SuSE 10.3 installation with the 2.6.22 kernel which doesn't have this problem. Edit bug mail Other bug subscribers Subscribe someone else Bug attachments sudo dmesg > /home/gustavo/dmesg.txt (edit) dmesg_dell_inspiron_5100.txt (edit) dmesg.log (edit) dmesg.log (edit) lspci-vvnn.log (edit) uname, version signature, lsusb, dmesg (edit) dmesg.out my device pulls 35mA @ 5volts,.. https://ubuntuforums.org/archive/index.php/t-898939.html
I put a powered usb hub between my USB DVD reader and my computer and that seems to have solved the problem of -71 errors. Thanks. hoang Hi, I really need help here. [email protected] David I had a weard problem with wifi.
My math students consider me a harsh grader. I found an esoteric solution : unplug the pc (in my case a laptop removed from the docking station), press & hold the power button for 20s (provoking a hard shutdown). 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 "device Descriptor Read/64, Error -32" from my dmesg: ====================================== [15571.551295] usb 1-2: new high speed USB device using ehci_hcd and address 3 [15581.914390] usb 1-2: device not accepting address 3, error -110 [15582.026381] usb 1-2: new
I have a toshiba laptop running 8.04 LTS 64 bit edition not only does my wifi not work but the 4 USB ports do not work with my thumb drive or Best wishes! You may see different port and/or error code. http://askubuntu.com/questions/117524/usb-device-not-accepting-address Unfortunately it did not solve my issue, but as soon as I read here the error explanation - about over-current protection - I found root cause for my case.
I spent the whole morning, until found out why. Device Not Accepting Address 7, Error -32 I'll try the patch from David Brownell, and let people know if this is works. I've tried rebooting at least 15 times, to no avail. dobbi View Public Profile Find all posts by dobbi #5 25th December 2014, 11:37 PM flogger Offline Registered User Join Date: Oct 2009 Posts: 16 Re: Keyboard USB:
Fisher's exact test or logistic regression to determine if distributions differ As a first stab How do computers calculate sin values? some people get these error messages, and their hardware doesn't work 2. Device Not Accepting Address Error 110 The problem most usually occurs after I disable the adaptor, then re-enable it again with blueman's tray applet. Device Not Accepting Address Error 32 Was there a prior kernel version where you were not having this particular problem?
How? weblink scsi 2:0:0:0: Direct-Access USB 2.0 Flash Disk 1100 PQ: 0 ANSI: 0 CCS sd 2:0:0:0: [sdc] 4013056 512-byte hardware sectors (2055 MB) sd 2:0:0:0: [sdc] Write Protect is off sd 2:0:0:0: Controller is probably using the wrong IRQ.usb 2-2: device descriptor read/64, error -110Could this be causing all these problems? Now I don't need to manually run the script everytime I start up. Usb Device Descriptor Read/64, Error
hope this helps! - Samsung Series 3, Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz - 6Gb DDR3 ram - 700Gb HDDOn board intel Graphics & Sound Offline #14 2009-01-27 19:18:22 ninjaprawn Member http://quantombone.blogspot.com/ Tomasz Worked beautifully for me -- now my external hard drive works again! unfortunately it doesnt work with my new H/W config. http://completeprogrammer.net/device-not/device-not-accepting-address-6-error-32.html orion log # tail syslog Dec 7 23:15:54 orion kernel: [37197.148268] hub 2-0:1.0: >unable to enumerate USB device on port 6 orion ~ # lsusb -t /: Bus 08.Port 1: Dev
Topology and the 2016 Nobel Prize in Physics How to make the development and use of Steam Engines preferred over that of Combustion Engines? 2048-like array shift Why does the ISS Device Not Accepting Address 2 Error If I plug it into the onboard OHCI controller, it works. The module is compiled into kernel.
The USB ports on my desktop seem to work fine front and back. I have a similar error on a home-built system, but the error code is "-104", which I cannot seem to find addressed anywhere. A soft reboot on didn't appear to fix it, so definitely power off/unplug/power on. "device Descriptor Read/64, Error -71" After longer search, I found in log the ‘unable to enumerate usb' message which appears during each bootup when wifi fails afterwards.
USB1.1 is on the left side of my laptop but im lefthanded so i'm not using it. I believe it is a problem with the BIOS in my case as I cannot mount 2 different USB devices in WinXP (Dual boot, no I never really use XP) and 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 http://completeprogrammer.net/device-not/device-not-accepting-address-23-error.html Story_1982 brother, thank you very much !
Glad it works for you guys, though! But on others I get: ------------------- ct 5 08:19:44 zly-hugo kernel: [ 806.363995] usb 1-1.3: new low-speed USB device number 13 using ehci_hcd Oct 5 08:19:46 zly-hugo kernel: [ 808.504620] usb Changing hardware is not an option and plugging the usb card reader into a different port is only an option for the older manchines. Is my teaching attitude wrong?
Gui Ambros about 1 year ago This has been annoying me for weeks. Tags: xenial amd64 apport-bug kernel-da-key Edit Tag help Cristian Aravena Romero (caravena) wrote on 2016-04-02: #1 AlsaInfo.txt Edit (30.2 KiB, text/plain; charset="utf-8") CRDA.txt Edit (392 bytes, text/plain; charset="utf-8") CurrentDmesg.txt Edit (60.3 None of my devices or systems cause this error. Some USB ports didn't work (as if they didn't exist).
I also have seen this same problem on other computers. once lsusb picks the device up, just run fsck on it; su password fsck /dev/sdcx fsck 1.41.3 (12-Oct-2008) dosfsck 3.0.1, 23 Nov 2008, FAT32, LFN /dev/sdc1: 0 files, 0/60102 clustersas long Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". over 1 year ago Thanks a lot for your quick response. ;-) My problem is that I'm the Hardware-guy, while my ESW-guy is no longer working here.
breta Perfect, thank you very much! Last edited by flogger; 29th December 2014 at 06:18 PM.