At the suggestion of eric_j in #avr on freenode, I added a pair of caps, a 47 uf electrolytic and a 0.1 uf across the power near the avr. wenjing over 3 years ago I almost had a headache due to error code 110 this morning. I also have a SuSE 10.3 installation with the 2.6.22 kernel which doesn't have this problem. Search this Thread 09-06-2010, 02:11 AM #1 DebianUser Member Registered: Apr 2010 Posts: 88 Rep: USB device descriptor read/64, error -62 I'm running Debian on a Linksys NSLU2 (slug) navigate here
Personal site | Understanding Wireless Chipsets | Troubleshooting ndiswrapper | The VAR Guy Adv Reply September 3rd, 2008 #7 toni_uk View Profile View Forum Posts Private Message 5 Cups of Jesper K. If you use ubuntu, you can run the liquorix kernel, at least if it's current ubuntu, not LTS, same for debian, non stable releases. Linux have a problem with my 4-Port > HUB. additional hints
https://lkml.org/lkml/2015/6/26/511 that's the changes in USB for 4.2-rc1. As an Android developer, I have a stack of devices here. I encountered a similar problem with error code 110.
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: I am currently unable to use an external harddrive for the same -71 error. How can I reduce my code when I used \addplot [black, mark = *] coordinates many times? Device Descriptor Read 64 Error 18 I had my phone plugged into my laptop (charging) while listening to the radio on my phone, while the laptop was on.
Finally, from Googling the error message I found an old post that mentioned the hardware. Device Descriptor Read Error 110 and I do not know what!! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Official Flavours Support Hardware [ubuntu] [SOLVED] device descriptor read/64, error -71 https://ubuntuforums.org/showthread.php?t=797789 The mythtv backend is also running zfsonlinux for bulk storage.
Therefore, to disable autosuspend you either: - recompile kernel without CONFIG_USB_SUSPEND - configure /etc/modprobe.d/ with a file containing "options usbcore autosuspend=-1" or set to 0 depending on your kernel If your https://paulphilippov.com/articles/how-to-fix-device-not-accepting-address-error Then just reboot and Bob's your Uncle. Device Descriptor Read All Error 71 mcrandello (mcrandello+launchpad) said on 2009-11-19: #11 Same/similar problem with Karmic 9.10 - Kernel, motherboard and USB hub details follow: ~$ uname -a Linux farkstar 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 Device Descriptor Read 64 Error Comment 10 Alan Stern 2007-09-06 07:07:49 UTC I can't answer your questions without more information.
BTW, the same effect can be achieved by disabling the onboard USB2.0 controller in the BIOS. check over here kernel: [ 3000.549032] usb 1-1: new full speed USB device using ohci_hcd and address 12 Dec 3 22:14:17 ???? Maybe the USB cable is bad? [ 864.200333] hub 1-1:1.0: cannot disable port 4 (err = -62) [ 864.203344] hub 1-1:1.0: cannot reset port 4 (err = -62) [ 864.206345] hub Offline #9 2007-11-10 14:36:05 Mazaev Member Registered: 2004-05-25 Posts: 29 Website Re: usb x-x: device not accepting address x, error -62 Having the same issue with a Seagate FreeAgent here. Usb1 1 Device Descriptor Read 64 Error
Adv Reply July 4th, 2008 #3 pytheas22 View Profile View Forum Posts Private Message Visit Homepage Staff Emeritus Join Date Aug 2007 Location Paris Beans 5,538 DistroUbuntu 11.04 Natty Narwhal Why would it care about the programmer? What causes the error is another story. http://applecountry.net/device-descriptor/device-descriptor-read-8-error-61.php My USB devices > disconnects/reconnects in every 5 minutes.
kernel: [ 2999.804037] usb 1-1: new full speed USB device using ohci_hcd and address 11 Dec 3 22:14:16 ???? Device Descriptor Read 8 Error 110 Maybe the USB cable is bad? [ 59.332000] ehci_hcd 0000:00:13.2: port 4 reset error -110 [ 59.332000] hub 3-0:1.0: hub_port_status failed (err = -32) [ 59.540000] ehci_hcd 0000:00:13.2: port 4 reset Offline #5 2007-10-30 13:13:48 zenlord Member From: Belgium Registered: 2006-05-24 Posts: 1,209 Website Re: usb x-x: device not accepting address x, error -62 Same here.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-Share Alike 4.0 International License. π current community chat Unix & Linux Unix & Linux Meta your Page 1 of 2 12 Last Jump to page: Results 1 to 10 of 15 Thread: [SOLVED] device descriptor read/64, error -71 - USB problem Thread Tools Show Printable Version Subscribe Thanks so much! :-) diyhouse over 2 years ago Sorry,.. Device Descriptor Read 64 Error 145 As I tell people when they ask this type of question, a new linux kernel has several possible outcomes: something that didn't work before works now everything stayed the same on
After that, it never turned on anymore. –fdierre Apr 6 at 19:37 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Main Menu LQ Calendar LQ Rules LQ Sitemap Site FAQ View New Posts View Latest Posts Zero Reply Threads LQ Wiki Most Wanted Jeremy's Blog Report LQ Bug Syndicate Latest Just a short follow-up: Who is the "peer" at this point - the Host controller itself, the hub(s) underway or the Device recently attached) Thanks. http://applecountry.net/device-descriptor/device-descriptor-read-64-error-usb.php my question is whether i need always -r ehci_hcd?
Awesome Donkey 11 months ago Unfortunately this didn't work for me... [ 11.225438] usb 1-3: device descriptor read/all, error -110 [ 11.337524] usb 1-3: new high-speed USB device number 3 using What is the total output of 'dmesg | tail' after you plug in the device? What is the definition of soliton? USB has an over-current protection, which gets triggered when power consumption from the port is too high.
I need specific information about changes/bugs/regression in 4.0 and later kernels...and hopefully a pointer to a patch or at least a workaround. After safely removing an ext4 USB3.0 pen drive when a text file inside it was open, the drive would not mount anymore. Turned it back on, checked dmesg and... Anyway.