Home > Device Descriptor > Device Descriptor Read 64 Error 110 Fedora

Device Descriptor Read 64 Error 110 Fedora


I eventually traced it to a faulty USB cable Stephen 12 months ago @Isabelle AA, thanks so much for your post! Brian Hames almost 3 years ago I have a multi-card reader with addition USB ports & alternate power and it was driving me nuts - it worked before and didn't now. I've tried rebooting at least 15 times, to no avail. joel 8 months ago Merci beaucoup dan 8 months ago Thank You !! http://completeprogrammer.net/device-descriptor/device-descriptor-read-64-error-71-fedora.html

On some devices connected on it, no problem. After reading your post, I noted that the notebook had been running on for many days now. After safely removing an ext4 USB3.0 pen drive when a text file inside it was open, the drive would not mount anymore. Sense: Illegal mode for this track [24230.601223] end_request: I/O error, dev sr0, sector 0 Olivier Mengué (dolmen) wrote on 2009-12-12: #16 Download full text (8.3 KiB) I also have an HP

Usb Device Descriptor Read 64 Error 110

And, maybe, removing VirtualBox didn't get rid of everything it added/changed on my system? This's really crazy!!! yes!! I'm glad it works now.

Kris over 4 years ago Worked for me, thanks! :-D. What am I? Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-Share Alike 4.0 International License. π Usb Device Descriptor Read 64 Error 71 Nabeel Moidu about 3 years ago Paul, had this same issue and my USB keyboard wouldn't power on.

Changed in linux (Ubuntu Lucid): status: Confirmed → Won't Fix See full activity log To post a comment you must log in. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Lucas C. (lucasoptura) wrote on 2009-11-23: #12 Download full text (5.4 KiB) This problem began with an upgrade to kernel 2.6.31-14-generic. Merci!!!

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Comment 2 Bug Zapper 2010-06-28 08:59:25 EDT Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Linux Usb Error Codes Changed in linux (Ubuntu): status: Confirmed → Won't Fix Marek Rodkiewicz (marek-rodkiewicz) wrote on 2011-09-20: #48 I get this error in ubuntu and also kubuntu 11.04. Wireless PID:101b] on usb-0000:00:1d.2-1: Rolf Leggewie (r0lf) wrote on 2015-06-17: #54 lucid has seen the end of its life and is no longer receiving any updates. What I find the most strange is that I get those error messages even without any USB devices plugged in!

Usb 1 1 Device Descriptor Read 64 Error 110

Waiting for 1 threads to finish - F22 installation in VirtualBox [closed] Fedora doesn't want to recognize a android phone! https://bbs.archlinux.org/viewtopic.php?id=149384 wenjing over 3 years ago I almost had a headache due to error code 110 this morning. Usb Device Descriptor Read 64 Error 110 Edit bug mail Other bug subscribers Subscribe someone else Bug attachments syslog for usb during boot (edit) Add attachment • Take the tour • Read the guide © 2004-2016 CanonicalLtd. Usb Device Descriptor Read Error 110 Not only was I able to format with LVM as I was with the 9100 but after the reinstall there are no errant messages about the usb ports but the keyboard

Here is what is in dmesg [ 1.762268] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.762281] ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18 get redirected here And the boot process... But on others I get: ------------------- ct 5 08:19:44 zly-hugo kernel: [ 806.363995] usb 1-1.3: new low-speed USB device number 13 using ehci_hcd Oct 5 08:19:46 zly-hugo kernel: [ 808.504620] usb Cheers! Device Descriptor Read/64 Error 32

Question Tools Follow 1 follower subscribe to rss feed Stats Asked: 2015-06-28 22:18:22 +0000 Seen: 256 times Last updated: Jun 30 '15 Related questions /bin/sh g++ comand not found Fedora 22 Five years later this post is still helping people! FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc. http://completeprogrammer.net/device-descriptor/device-descriptor-read-8-error-71.html I've had to repeat this trick several times in the intervening months, and it has worked every time.

Gui Ambros about 1 year ago This has been annoying me for weeks. Device Descriptor Read/64, "error -62" Something else that is different, not to conflate this problem with another is both of those machines (from Dell) came with Win 7 installed, both have Raid 1 configured. If it to helps to solve the problem I can attach the dmesg-Output.

Register All Albums FAQ Today's Posts Search Hardware & Laptops Help with your hardware, including laptop issues Google™ Search FedoraForum Search Red Hat Bugzilla Search
Search Forums Show Threads

Cycling power on the printer brings it right back online ( with instant lsusb's). Saffron and coloration - is there a way to know why it gave the wrong color? So at this time the issue appears to be affecting my SD card reader. Device Not Accepting Address Error 62 Is it possible that VirtualBox created virtual USB ports and they're the ports that are causing this error?

I would suggest anyone else experiencing similar problems try unplugging all USB devices and rebooting- try booting with one device plugged in at a time (or watch kernel log while you Adv Reply October 31st, 2010 #2 IcarusR View Profile View Forum Posts Private Message Fresh Brewed Ubuntu Join Date Oct 2006 Location Milton Keynes, UK Beans 1,141 DistroUbuntu 10.04 Lucid more hot questions question feed about us tour help blog chat data legal privacy policy work here advertising info mobile contact us feedback Technology Life / Arts Culture / Recreation Science my review here I had to turn off the power at the PS like someone in the comments suggested.

Find all posts by Firewing1 #5 2nd December 2008, 05:51 PM SendDerek Offline Registered User Join Date: Nov 2007 Posts: 198 I thought that was a little odd None, the status of the bug is updated manually. over 1 year ago Thanks a lot for your quick response. ;-) My problem is that I'm the Hardware-guy, while my ESW-guy is no longer working here. So thought it was a driver problem...

Power cycling the printer works to resolve (sometimes) smallreactor (ecmporter) wrote on 2010-03-06: #28 I don't have the problem anymore. I read the answers in links you mentioned. Today I went to use my USB Thumb Drive in Fedora 10 and found that it wasn't showing up anywhere. Unfortunately it did not solve my issue, but as soon as I read here the error explanation - about over-current protection - I found root cause for my case.

For some reason, the same drives still work on Macs. Will a small engine oil overfill damage the engine or turbo? more hot questions question feed about us tour help blog chat data legal privacy policy work here advertising info mobile contact us feedback Technology Life / Arts Culture / Recreation Science more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed

usb 4-4: device descriptor read/8, error -62 it's not clear for me DO you disconnect the psu suddenly and wait for 5 minutes? I disconnected the machine, not shutdown -P and reconnected the power cord. In fact all the peripherals were sharing the same power source, and in some situations the board was cutting the power to the camera, in order to suply it the more Still working with the *other* OS.

manatlan (manatlan) wrote on 2010-05-27: #36 @Adam B Butler > Would love a fix, naturally -- but in the meantime, is there a practical > (quick) way to perform the "modprobe Rolder about 1 month ago Thank you. Read more... Louis, Mo.