Device Not Accepting Address 42 Error
Contents |
Canada. flickr Links BitBucket Blogger eBay Drive2 Etsy Facebook Flattr Flickr GitHub Google+ Kroogi Last.fm LinkedIn ohloh Postcrossing Tumblr Twitter YouTube Paul Philippov home is where ~/ is Instead of a resumé Contacts How to fix "device not accepting address" error ← → If device not accepting address error 71 Linux suddenly happen to fail to recognize a USB drive, check dmesg for errors. Once you see
Device Not Accepting Address Error 32
a bunch of errors like usb 1-5: device descriptor read/64, error -32 usb 1-5: new high speed USB device using ehci_hcd and address 21 usb
Device Not Accepting Address Error 110
1-5: device not accepting address 21, error -32 most probably it’s a result of hardware failure rather than a driver or kernel bug. USB has an over-current protection, which gets triggered when power consumption from the port is too high. Unplug all
Device Not Accepting Address Error 62
USB devices from PC, turn power off, and wait a minute or two. Plug everything back and boot into Linux. I spent the whole morning, until found out why. I hope that this message will save someone a few hours, and nerves. PS: Actual errors may vary. You may see different port and/or error code. 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 device not accepting address 2 error 71 problem is the same. Published on October 21, 2010 (almost 6 years ago) Article tags: linux, usb Comments // 77 Click here to leave a comment ThiasJ over 5 years ago Thank you SO much!!! I thought I had to buy a new HDD! will smith about 5 years ago God bless you! I was tearing my hair out trying to fix an error -62 problem that was disabling any usb device I plugged in after I had removed a usb sound card. Unplugging the computer and leaving it unplugged for a couple of minutes fixed it, thank you! No one else seems to have discovered this, I've been reading other posts talking about unloading modules, and many other more complicated troubleshooting methods and fixes when I found your page. Many, many thanks to you! JonW almost 5 years ago Yep. Saved me a bunch of time as well. Thanks a bunch for posting this. dardino over 4 years ago some one knows how to fix the problem without rebooting? Sergei Kirjanov over 4 years ago I had similar problem (error message). USB devices (webcam and /dev/sdX) somehow conflicted. How? May be not just ¨Plug everything back¨, but play with minimal sets of devices. Kris over 4 years ago Worked for me, thanks! :-D. A soft reboot on didn't appear to fix it, so definitely power off/unplug/power on. Yusuke over 4 years ago How can this be fixed, i mean, plug and play, like it's supposed to be? Coz works fine
Importance Assigned to Milestone linux (Fedora) Edit Confirmed Unknown redhat-bugs #511391 You need to log in to change this bug's status. Bug watch updates for Red Hat Bugzilla are disabled. Affecting: linux usb device not accepting address error 32 (Fedora) Filed here by: eyrieowl When: 2009-11-02 Target Distribution Baltix BOSS Juju Charms Collection usb device descriptor read/64 error 32 Elbuntu Fedora Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package "device descriptor read/64, error -71" (Find…) Project (Find…) Status Importance Confirmed Unknown Assigned to unknown Remote Watch None, the status of the bug is updated manually. None, the status of the bug is updated manually. Red Hat Bugzilla #511391 https://paulphilippov.com/articles/how-to-fix-device-not-accepting-address-error URL: The information about this bug in Launchpad is automatically pulled daily from the remote bug. This information hasn't been pulled yet. Comment on this change (optional) Email me about changes to this bug report linux (Ubuntu) Edit Won't Fix Medium KAPIL DUBEY Edit You need to log in to change this bug's status. Affecting: linux (Ubuntu) Filed here by: atdt911 When: 2008-04-08 Assigned: 2015-07-20 Completed: https://bugs.launchpad.net/bugs/54273 2011-07-19 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Won't Fix Medium Assigned to Me KAPIL DUBEY (kapil08dubey-w) Comment on this change (optional) Email me about changes to this bug report linux-source-2.6.15 (Ubuntu) Edit Won't Fix Medium Unassigned Edit You need to log in to change this bug's status. Affecting: linux-source-2.6.15 (Ubuntu) Filed here by: Luke Hoersten When: 2006-07-27 Completed: 2009-07-11 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Won't Fix Medium Assigned to Nobody Me Comment on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description Binary package hint: linux-image-2.6.15-26-k7 I have a USB devices: mouse, camera, ipod and printer plugged in. The only device that works is the printer. Everything used to work in 2.6.15-25-k7. Mouse works with PS2 converter but not straight into USB. **lsusb output: Bus 004 Device 001: ID 0000:0000 Bus 001 Device 003:
VLC How to show black screen on remote computer using TeamViewer How to share wireless from Android device using Bluetooth tethering How to fix NVIDIA driver failure on https://codeyarns.com/2014/05/06/the-strange-case-of-the-usb-error-device-not-accepting-address/ Ubuntu How to fix internet access on Windows hosted network How to delete all lines of file in Vim How to add library directory to ldconfig cache How to change size of http://marc.info/?l=linux-usb-users&m=119595847032341 Matplotlib plot How to access SMB share on Android using ES File Explorer How to set TERM to xterm-256color Archives Archives Select Month October 2016 (3) September 2016 (14) August 2016 (11) July device not 2016 (6) June 2016 (16) May 2016 (15) April 2016 (2) March 2016 (28) February 2016 (31) January 2016 (21) December 2015 (16) November 2015 (15) October 2015 (40) September 2015 (41) August 2015 (21) July 2015 (24) June 2015 (20) May 2015 (24) April 2015 (28) March 2015 (46) February 2015 (40) January 2015 (74) December 2014 (12) November 2014 (26) October 2014 (27) device not accepting September 2014 (36) August 2014 (35) July 2014 (44) June 2014 (40) May 2014 (72) April 2014 (26) March 2014 (17) February 2014 (30) January 2014 (29) December 2013 (30) November 2013 (9) October 2013 (35) September 2013 (27) August 2013 (19) July 2013 (26) June 2013 (61) May 2013 (23) April 2013 (1) March 2013 (46) February 2013 (31) January 2013 (58) December 2012 (32) November 2012 (21) October 2012 (29) September 2012 (5) August 2012 (21) July 2012 (8) June 2012 (24) May 2012 (29) April 2012 (23) March 2012 (21) February 2012 (15) January 2012 (12) December 2011 (5) November 2011 (2) October 2011 (7) September 2011 (7) August 2011 (17) July 2011 (17) June 2011 (21) May 2011 (19) April 2011 (15) March 2011 (18) February 2011 (17) January 2011 (12) December 2010 (20) November 2010 (29) October 2010 (12) September 2010 (13) August 2010 (20) July 2010 (21) June 2010 (4) May 2010 (13) April 2010 (27) March 2010 (22) February 2010 (22) January 2010 (42) December 2009 (11) November 2009 (7) October 2009 (24) September 2009 (10) July 2007 (1) November 2006 (1) October 2006 (1) August
e521 ! site [Download message RAW] All, I've run into a bit of trouble in trying to get my Treo 650 to register with the usb driver. So... the process is as follows. I load the `visor` module [which also loads `usbserial`]. I try a hotsync operation. A new device should appear as /dev/ttyUSB1 or /dev/ttyUSB0 aliased to /dev/pilot. No devices appear. The syslog and dmesg report the following: Nov 24 20:42:34 e521 kernel: usb 1-5: new full speed USB device using ohci_hcd and address 23 Nov 24 20:42:35 e521 kernel: usb 1-5: device descriptor read/64, error -110 Nov 24 20:42:35 e521 kernel: usb 1-5: device descriptor read/64, error -110 Nov 24 20:42:35 e521 kernel: usb 1-5: new full speed USB device using ohci_hcd and address 24 Nov 24 20:42:35 e521 kernel: usb 1-5: device descriptor read/64, error -110 Nov 24 20:42:35 e521 kernel: usb 1-5: device descriptor read/64, error -110 Nov 24 20:42:36 e521 kernel: usb 1-5: new full speed USB device using ohci_hcd and address 25 Nov 24 20:42:36 e521 kernel: usb 1-5: device not accepting address 25, error -110 Nov 24 20:42:36 e521 kernel: usb 1-5: new full speed USB device using ohci_hcd and address 26 Nov 24 20:42:37 e521 kernel: usb 1-5: device not accepting address 26, error -110 I've tried all the notes listed on the linux-usb.org FAQ page. None seem to work. Anyone have any other suggestions?? I'm running opensuse 10.1 x86_64 2.6.16.13-4-smp on a dell e521 open source desktop. thanks john ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users [prev in list] [next in list] [prev in thread] [next in thread] Configure | About | News | Addalist | SponsoredbyKoreLogic