I am a devoted Linux user, Ruby programmer, Open Source software developer, photography hobbyist, and a world traveller. The attached file contains uname, version signature, lsusb, dmesg. One is a 80GB hard drive usb and the other is a ATI remote wonder. A soft reboot on didn't appear to fix it, so definitely power off/unplug/power on. click site
It's definitely a problem. Another mentioned that upgrading from BIOS revision 1.16 to 1.20 fixed it (but he wasn't sure if he had an AK73 or the Pro or some other variant). After connecting an external 12V power supply to the Arduino, everything works like charm. Check the USB cable and connections. hop over to this website
Hope that helps. Andreas S. share|improve this answer edited Jun 30 '12 at 12:51 Eliah Kagan 56k15162255 answered Feb 24 '12 at 21:20 jedijf 21913 when I issue lsusb to terminal it write to Brilliant; I was tired to search on Ubuntu forums for a special mouse bug, and to try different version to find back the old drivers -all of course without success.
What's an easy way of making my luggage unique, so that it's easy to spot on the luggage carousel? So thought it was a driver problem... Leann Ogasawara notes at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/256767/comments/14 that this is known to upstream and they consider it harmless, it's the report of a real potential error. "device Descriptor Read/64, Error -71" Turns out that shutting down (if you can, my system freezes up and REISUB doesn't work) and then disconnecting Power to the Power Supply for a few minutes fixes the problem.
I encountered a similar problem with error code 110. So it was a hardware issue. greg@greg-laptop ~ $ lspci 00:00.0 Host bridge: Intel Corporation 82845 845 (Brookdale) Chipset Host Bridge (rev 04) 00:01.0 PCI bridge: Intel Corporation 82845 845 (Brookdale) Chipset AGP Bridge (rev 04) 00:1d.0 https://paulphilippov.com/articles/how-to-fix-device-not-accepting-address-error Nicolas lanzen (lanzen) wrote on 2008-08-24: #26 I've just run into this bug.
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 Device Descriptor Read/64 Error 32 I think the Ubuntu kernel devs should dignify us with a better answer than "wait for 9.10" (because it seems the 9.04 alpha also suffers from this same problem). But it wasn't until I had this issue with the hub (that works both with and without power) than I could see that enumaration fails on powered USB devices if they idProduct 0x2110 bcdDevice 1.00 iManufacturer 1 Broadcom Corp iProduct 2 BCM2045B iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 216 bNumInterfaces 4 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0
On the other hand, I did notice that this only happens when my iPod is plugged in on boot. check here Tero Karvinen (karvinen+launchpad) wrote on 2007-12-31: Mobo USB ports work after BIOS update #13 My problem was bypassed by updating BIOS and using USB ports on the motherboard. Usb Device Not Accepting Address Error 71 If I boot into Ubuntu and try to mount the drive, I can't. Usb Device Not Accepting Address Error 32 I'm getting the following in a loop inside dmesg.
It's been sitting there for over a month now waiting for you ... get redirected here 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. I'm currently investigating this solution: askubuntu.com/questions/62315/lost-wireless-mouse-connection-when-laptop-is-on-battery In other words, I'm blacklisting the USB suspend feature for this mouse device. I've just attached the player to a few different ports on my Compaq, with subtly different results in the logs, so I'm attaching them here. Device Not Accepting Address "error -62"
I often have problems with my USB ports - they don't detect my USB mouse. Usb Device Descriptor Read/64 Error -32 Juan J. Today we live at the very South of Canada.
However, in case #2 there is still a problem from an end-user point of view: the error message is logged to syslog once a second. 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 You can try it . "device Descriptor Read/64, Error -62" I powered it down and left it for 15 minutes.
Red Hat Bugzilla #511391 URL: The information about this bug in Launchpad is automatically pulled daily from the remote bug. Richard Ayotte (rich-ayotte) wrote on 2008-12-27: #38 dmesg.log Edit (122.3 KiB, text/plain) Richard Ayotte (rich-ayotte) wrote on 2008-12-27: #39 lspci-vvnn.log Edit (12.5 KiB, text/plain) Mary Gardiner (puzzlement) wrote on 2009-01-04: #40 No more annoying "device not accepting address xx, error -32". my review here It happens with all of them.
ok, good luck for all, and look the FAQ ;) PD: sorry for my english (i'm spanish speaker) Luke Hoersten (lukehoersten) wrote on 2006-08-23: #8 Thanks for the advice. it was clean! Paul Philippov over 1 year ago Jesper, I guess that in order to be reset by the peer the connection has to be initiated by the host first. Nobody has tried to duplicate his results or interpolate between the two .configs to see if the problem can be traced to a single item.
They worked fine on Windows though. But hey, I was desperate, and had nothing to lose. The ubuntu-kernel-team is being unassigned from this bug report. Linux currently assumes the operation actually succeeded, which is rather optimistic.
What can I do? harvest316 (harvest316) wrote on 2008-12-09: #34 FYI: I have a Dell Dimension 5100 with a Samsung USB Memory Card Reader, and I'm on Intrepid 184.108.40.206.13 chrono13 (chrono13) wrote on 2008-12-09: #35 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 I reinstalled Windows on the HP, and now the Sansa connects just fine, so it is definitely a problem with Linux.