Home > Device Descriptor > Usb Device Descriptor Read 64 Error

Usb Device Descriptor Read 64 Error


Alexandre (ab-linuxfr) wrote on 2011-05-17: #45 It looks like my previous comment is related to bug #773524 Jeremy Foshee (jeremyfoshee) on 2011-05-23 tags: removed: regression-potential whochismo (whochismo) wrote on 2011-07-01: #46 Coben over 2 years ago Thanks so much!!! Noticed there was a green glowing LED on the Inateck wall wart; waited for that to go dark. Sergei Kirjanov over 4 years ago I had similar problem (error message). this content

With a camera I tried the modprobe thing, but it did solve the problem Adv Reply July 4th, 2008 #5 toni_uk View Profile View Forum Posts Private Message 5 Cups The situaton did not improve with Karmic (errors where more random). Perhaps something was changed regarding the USB enumeration process for this release? In my case, is caused by a USB webcam.

Device Descriptor Read/64 Error 32

Would it be possible for you to test the latest upstream kernel? inktvis75 2016-05-19 08:21:52 UTC #3 It can be an hardware issue, but it's also possible that it's hardware related.I see a lot of USB related problems starting with the 4.1 kernel It seems that also adding the "acpi=force irqpoll" boot option (as described here: http://www.ubuntugeek.com/how-to-fix-usb-stops-working-problem-in-ubuntu.html ) improves things a bit: it just revived my usb2 connectivity and seems to keep it working Not the printer does not work at all.

  • This fixed it for me: shutdown -h now (turn off the computer) Unplug USB device from computer.
  • Thanks!
  • Linux USB FAQ lists some of the reasons why you are seeing this issue.
  • Worked liked a charm.

I experienced it on Fedora 12, Archlinux, Debian Lenny and Ubuntu. Gregster (madd0131) wrote on 2009-10-31: #7 I forgot to mention; this happened after upgrading to Karmic. kapetr about 3 years ago I have interesting experience: I have long (5m) USB extension cable. Device Not Accepting Address Error 32 So, to all fellow smarty pants out there that think you know better: save yourself some headache and give it a try.

I don't know why the drive runs out of power sometimes. Adv Reply July 5th, 2008 #6 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 I want USB2 ;-) ( my troubble is similar, but with "error -32" : #586435 ) delca85 (delca85) wrote on 2010-06-08: #37 @manatlam Thanks! Does anyone have any clue as to how I can solve this issue?

I was getting mad. Device Descriptor Error -71 Turned it physically off (using the switch in the power supply), and left it off for 3-4 minutes. Unplug all USB devices from PC, turn power off, and wait a minute or two. Disproving Euler proposition by brute force in C How do really talented people in academia think about people who are less capable than them?

Usb Device Descriptor Read 64 Error 110

What's wrong? passed by 8 months ago Thank you for this, to me i changed the USB to front panel and everything worked i guess it was drawing too much power from the Device Descriptor Read/64 Error 32 What I can tell already is the following:When running dmesg | tail -20 after plugging in the USB drive I get the following errors:usb 3-3: new full-speed USB device number 8 Usb "device Descriptor Read/64, Error -71" share|improve this answer answered Feb 20 '13 at 5:13 maximilian009 3711314 add a comment| up vote 0 down vote Main voltage is not high enough in my home.

It looks like some kernel upgrade (-14 -15 -16, I don't know) changed something in USB. news I unplugged and replugged the mouse and keyboard, and they still didn't work. Aaron Thomas (athomas-lbl) wrote on 2012-10-18: #50 This issue still exists for me in ubuntu precise which is an LTS release. My USB was detected straight away. Device Descriptor Read/64, "error -62"

In hindsight, it's pretty obvious now that the power button doesn't cut the power to the USB hub, so if you tripped the over-current protection, you need a full power off Anthony J Lucas (anthonyjlucas) wrote on 2009-11-28: #13 I can confirm this is also happening on the latest mainline kernel 2.6.32-rc8. Then, a simple idea striked me: e2fsck. http://crimsonskysoftware.com/device-descriptor/usb-2-1-device-descriptor-read-64-error-71.html For some reason, the same drives still work on Macs.

If this issue still exists in a supported series, please file a new bug. Device Descriptor Read/8 Error 110 Matt Zimmerman (mdz) on 2010-02-25 tags: added: regression-potential sog (sogrady) wrote on 2010-03-02: #26 The latest Lucid updates (3/2/2010) have eliminated this issue for me. It may sounds strange, but in my case I found a series of connect/disconnect events into dmesg and syslog as well.

Had this problem with a short 24" cable.

Noticed there was a green glowing LED on the Inateck wall wart; waited for that to go dark. Could it be usb controller related (i.e. Jorge Gustavo (jgr) wrote on 2009-12-08: #15 I can report the same error on Karmic, with 2.6.31-16-generic-pae and the CD/DVD no longer works under Ubuntu. Usb Error Codes Sense: Illegal mode for this track [24230.537911] end_request: I/O error, dev sr0, sector 0 [24230.537919] __ratelimit: 29 callbacks suppressed [24230.537925] Buffer I/O error on device sr0, logical block 0 [24230.537936] Buffer

Is it dangerous to use default router admin passwords if only trusted users are allowed on the network? I'm running 2.6.32-21-generic in an amd64 environment Manoj Iyer (manjo) wrote on 2010-05-03: #33 Looks similar to Bug #54273, in that bug rmmod ehci_hcd seems to fix the issues or at As you see, it takes a long time and gnome desktop interface is not accessible. check my blog What are the alternatives of compound interest for a Muslim?

lezard fsnlenneth over 1 year ago I'm having this problem too trying to boot the latest clonezilla live on a usb stick on a z97 deluxe board. Anyway. I'm trying to help someone with the same issue. Changed in linux (Ubuntu Lucid): status: Confirmed → Won't Fix See full activity log To post a comment you must log in.

I plug some in, and get those "device descriptor read/64, error #" messages, yet, without doing anything to the system and using the same usb cable, I can plug in any Thanks in advance. Did you disconnect the power supply or just hit restart? –Ron Jul 3 '15 at 12:41 In Windows On another PC. As of today, however, both with Karmic and - post-upgrade - Lucid, I am now experiencing the same condition: [ 16.048101] usb 1-1: device descriptor read/64, error -110 [ 31.264117] usb

If you need to reset your password, click here. Registration is quick, simple and absolutely free. I almost want to throw the HDD. There may be also other reasons.

I don't want to try them myself I can't break my computer right now, and it's hard to test USB stuff in a virtual machine. Re: device descriptor read/64, error -71 - USB problem I have the same problem. Five years later this post is still helping people! On my brand new PC also running Ubuntu 8.04 it is not detected.