Home > Device Descriptor > Usb Device Descriptor Read/64 Error 71

Usb Device Descriptor Read/64 Error 71

Contents

Here is some documentation for some of the other values that can be configured: usbcore.autosuspend= [USB] The autosuspend time delay (in seconds) used for newly-detected USB devices (default 2). I have no log, the only message is this one: "usb 2-1 device descriptor read/64 error -71" when I try to shutdown my computer. Restarting didn't help either. They worked fine on Windows though. this content

Jeffrey Lebowski 4 months ago And sorry for all the typos... Share this:EmailMorePrintTwitterFacebookLinkedInGoogleReddit Related This entry was posted in Linux, Tips and tagged Errors on June 26, 2008 by Guy. I'm trying to help someone with the same issue. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

Device Descriptor Read/64 Error 32

All I needed to do was add the following line to /etc/modprobe.d/options: options usbcore use_both_schemes=y (If you are curious as to why this solved the problem, please read this clear explanation.) dato000 over 4 years ago thank you very much!!! Saved me a bunch of time as well. PR 5 months ago Cables...

  1. Would it be possible for you to test the latest upstream kernel?
  2. Kris over 4 years ago Worked for me, thanks! :-D.
  3. I was worried that my keyboard might be dead leegold 10 months ago Tearing huge hunks of hair out of my head.
  4. Note: Previously I tried just unplugging the computer and letting it sit for a while; that didn't work.
  5. Then just reboot and Bob's your Uncle.
  6. awesome!! 2 days looking for a solution.

SAved me some big headaches! Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled current community chat Stack Overflow Meta Stack Overflow your communities Sign up or log in Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Device Not Accepting Address Error 110 Makes sense that it was an over-currenting problem.

It didn't work there too. –Hanna Jul 3 '15 at 12:37 In windows on another computer? Device Not Accepting Address Error 32 joel 9 months ago Merci beaucoup dan 9 months ago Thank You !! Maybe I need to have my computer connected to the charger (via cable) when I turn it on. Journal recovered, inodes number corrected, and after a 2 second wait my drive was read.

I just disconnected the power and re-connected the hub and it was fine. Device Not Responding To Setup Address For those guys, whom the first method (recommended by Paul) did not help, try to use a shorter cable to attach your device. Usually, it's just a matter of rebooting, but today that wasn't working. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Device Not Accepting Address Error 32

I have a similar error on a home-built system, but the error code is "-104", which I cannot seem to find addressed anywhere. ur solution solved the problem. Device Descriptor Read/64 Error 32 nothing. Usb Device Descriptor Error 71 Duplicate of bug #1437492 Remove Convert to a question Link a related branch Link to CVE You are not directly subscribed to this bug's notifications.

García about 3 years ago yes!! news Raspbian starts, bbut the peripherals are not working. I disconnected all other USB devices. –Hanna Jul 3 '15 at 13:14 add a comment| up vote 2 down vote The device descriptor read/64, error -110 means that USB port power Did a bit of research and found this so damn easy solution on the Mint Forum: in the terminal type: echo -1 >/sys/module/usbcore/parameters/autosuspend I was logged in as root - not Device Descriptor Read/all Error 71

Turned it physically off (using the switch in the power supply), and left it off for 3-4 minutes. It's probably still there in your dmesg output or the system logs. I was getting mad. http://crimsonskysoftware.com/device-descriptor/usb-2-1-device-descriptor-read-64-error-71.html When I run lsusb I get this:Bus 002 Device 002: ID 8087:0024 Intel Corp.

will smith about 5 years ago God bless you! Usb Error Codes So thanks. Related Posted by urukrama Filed in General Tags: linux, ubuntu, usb, usbcore 4 Comments » 4 Responses to "USB drive not recognised (error-71)" pollux_master said June 10, 2010 at 12:09 pm

gregorIO almost 2 years ago Works!

Thanks, Justin pytheas22October 23rd, 2008, 03:26 PMI tried this fix for the same error message with a different error number (-110), but it did not seem to have any effect. Necesité + de un minuto pero funcionó ********************** Thank you very much!! + I needed a minute but it works Jeffrey Lebowski 4 months ago As always, French people show great Very old thread, but this is still very applicable. Usb Device Not Accepting Address My 21-year-old adult son hates me Disproving Euler proposition by brute force in C If two topological spaces have the same topological properties, are they homeomorphic?

Then I read this post and turned my computer off, connected my computer to the main power source, unplugged my USB mouse, then turned my computer back on - and then I am a devoted Linux user, Ruby programmer, Open Source software developer, photography hobbyist, and a world traveller. Thanks anyway - good to see that someone is looking through all the unanswered threads. check my blog Plenty of suggestions were offered online (including recompiling the kernel) but most of them did not help me at all.

I had a logitech USB keyboard on a ThinkPad T420 and apart from the lower right USB port all others threw this error. kamran about 2 years ago thanks man... sobol about 4 years ago I encountered this problem connecting the Arduino MEGA 2560 to the ALIX 2d13 SBC. I've tried rebooting at least 15 times, to no avail.

for some resons they are not quite doing what they should. Try this: echo Y | sudo tee /sys/module/usbcore/parameters/old_scheme_first That should work. Sergei Kirjanov over 4 years ago I had similar problem (error message).