You may see different port and/or error code. Connected all USB devices back, and everything is now working fine. Nabeel Moidu about 3 years ago Paul, had this same issue and my USB keyboard wouldn't power on. I had the problem on this one. check over here
Trying everything I was about to throw in the towel. Only the front panel USBs work... Solutions? It is driving me bats!!!
This change has been made by an automated script, maintained by the Ubuntu Kernel Team. I've tried both applying the patch to the current wily source (4.2.0-38.45) and also compiling the master-next source for wily. JonW almost 5 years ago Yep. How do I respond to the inevitable curiosity and protect my workplace reputation?
Kernel: 2.6.31-16-generic The printer worked on Ubuntu since january 2008, with issues (often I had to reboot for the document to print, or to boot with the printer switched on). Read more... Even tried uninstalling drivers, but still the same. Device Descriptor Read/64, "error -62" it was clean!
SMP alternatives: switching to UP code
ACPI: Core revision 20060707
CPU0: Intel(R) Xeon(TM) CPU 2.80GHz stepping 09
SMP alternatives: switching to SMP code
Booting processor 1/1 eip 11000
CPU 1 Device Descriptor Read/8 Error 110 But that is what software returns. Update: I flashed my bios to the newest firmware (3003) and with xHCI enabled in the bios my USB3.0 HDD still doesn't work, but all my other devices don't have any even with in-rush surge power up,..
yeah.. Usb Error Codes See: 1) http://stackoverflow.com/questions/13653692/device-descriptor-read-64-error-110 2) http://ubuntuforums.org/showthread.php?t=1610142 share|improve this answer answered Jul 3 '15 at 12:35 Ron 8,55932038 I restarted the system and tested in on Windows. Because it has not enough power also the USB stick cannot provide the device descriptor to the host, as a result it cannot be identified and so on. While the computer was off, I had time to actually think about the technicalities of it all, and realized that because a USB port is powered, that your fix is actually
What are the specific devices triggering these issues for you? In this scenario I assume it's something like the host is sending an initialization command that the target is ignoring or improperly answering during the usb handshake, and the host gives Device Descriptor Read Error 110 will not work on this server.Here's some preliminary diagnostic information. Usb Device Descriptor Read 64 Error 71 Gregster (madd0131) wrote on 2009-11-02: #8 Update- the problem is being caused by my HP LaserJet 1018 printer.
No worries ! check my blog I doubt this is the case for me - there simply aren't enough USB devices (just a keyboard and a mouse using the powered hub built into my monitor). It works fine on 10.10 on a Dell XPS 9100, which I can not see the difference between the 9100 and 9000. Cheers! Device Descriptor Read/64 Error 32
Unplug power to Inateck - pull wall wart plug from wall socket. bturrie (bturrie-yahoo) wrote on 2010-08-27: #40 syslog for usb during boot Edit (3.5 KiB, text/plain) I'm having a similar problem after an update I installed this morning I'm running Kubuntu Lucid like they guy who said his USB ports haven't worked in 18months?? http://crimsonskysoftware.com/device-descriptor/usb-2-1-device-descriptor-read-64-error-71.html Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 002: ID 04eb:e033 Northstar Systems, Inc.
The patch integrates successfully and the kernel compiles fine. 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 Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-Share Alike 4.0 International License. π Guy Rutenberg Keeping track of what I do Menu Skip to Device Not Accepting Address Error 32 I started noticing this problem when I switched to a 4.0 kernel on Gentoo.
Nothing that could drain so much power... –maximilian009 Dec 2 '12 at 17:35 Hmmm, it depends... Anyway. None, the status of the bug is updated manually. have a peek at these guys The bootup gave the error only in UsB 5-6.
Any thoughts on why the issue would have cropped up later on, and not been there from the beginning (i.e. Fred (eldmannen+launchpad) wrote on 2015-08-11: #26 Thank you John5788! Success! 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
I've been tearing my hair out all morning trying to get my USB ports to work and this fixed it! Debian Bug tracker #785494 Linux Kernel Bug Tracker #93681 URL: The information about this bug in Launchpad is automatically pulled daily from the remote bug. But your solution worked! sog (sogrady) wrote on 2010-02-04: #23 If it's of help, my machine will properly mount an USB flash drive, but remains unable to properly handle two separate - and confirmed working
Adv Reply March 26th, 2013 #10 stbcomp View Profile View Forum Posts Private Message First Cup of Ubuntu Join Date Sep 2006 Beans 9 Re: USB 2/3 device descriptor read64, Top eLusive Posts: 28 Joined: 2009/11/15 00:52:05 Re: USB issues: device descriptor read/64, error -110 Quote Postby eLusive » 2011/06/23 00:31:02 Considering this is the first page that comes up, I Fred (eldmannen+launchpad) wrote on 2015-04-08: #5 journal.txt Edit (1.1 MiB, text/plain) journal as requested Martin Pitt (pitti) wrote on 2015-04-11: #6 Thanks. Doesn't seem like it should be necessary though...
No more problems! In one of them it mentioned something about power. 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 Olcay Korkmaz (olci) wrote on 2015-08-15: #29 same issue on msi gaming 7 mainboard z97 booting stuck with bios error code 99 then bios initialization waits for two minutes sometimes asmedia
Another update: Well, most of the ports work.. This's really crazy!!! 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