Home > Device Descriptor > Device Descriptor Read/8 Error 110

Device Descriptor Read/8 Error 110


So short of compiling my own kernel, I'm unable to properly use these drives. Awesome Donkey (awesomedonkey) wrote on 2015-11-09: #37 Yep, happening here too with a MSI Z97 MPOWER Max AC with the latest 4.2 and 4.3 kernels... [ 11.225438] usb 1-3: device descriptor Source: http://ubuntuforums.org/showthread.php?t=1610142 Let me know in the comments below if you need recovery help as well. =D Good luck! 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 http://completeprogrammer.net/device-descriptor/device-descriptor-read-8-error-71.html

Offline #6 2015-06-15 21:46:06 dgalt Member Registered: 2015-04-22 Posts: 46 Re: [Solved] USB issue - device descriptor read/8, error -110 As I suspected, the option for fast boot is there, but While GRUB to LightDM with upstart is 10 seconds (then I have to wait about half a minute for the USB devices to get initialised) $ lsusb Bus 004 Device 002: Share a link to this question via email, Google+, Twitter, or Facebook. I've also checked to ensure the correct (modified) USB options are enabled in the kernel config. https://bbs.archlinux.org/viewtopic.php?id=198460

Device Descriptor Read 64 Error 110

Three riddles, one solution 50-minute connection in Helsinki between Schengen and non-Schengen - enough time? The bootup gave the error only in UsB 5-6. I am hoping someone can help me recover the files on this usb drive, perhaps with the help of these log files. Report a bug This report contains Public information Edit Everyone can see this information.

After this, the keyboard was working right away, but the mouse wasn't working until the screen blinked. –Greg Kramida Dec 3 '15 at 16:09 add a comment| 3 Answers 3 active MSI z97 gaming 7 4.2.0-19-generic I'm going to install 4.2.0-27 now and post any updates if it was resolved. Cutting power to the system and powering on allows the init sequence to complete normally. Device Descriptor Read/64 Error -71 All the errors in my case are on bus 7.

Brad Figg (brad-figg) wrote on 2011-07-14: Unsupported series, setting status to "Won't Fix". #47 This bug was filed against a series that is no longer supported and so is being marked Usb Device Descriptor Read 64 Error 110 It seems that the Xen hypervisor handles USB the way it should be handled, so if you happen to have VT-d or SVM, installing Xen is an easy fix. yeah.. I think beacuse of this error won't work my wireless mouse (logitech M505) and keyboard (logitech K340) fabioamd87 (fabioamd87) wrote on 2011-12-10: #49 I have this error on Kubuntu 11.10 my

How does an exponent work when it's less than one? Device Descriptor Read 64 Error 18 Not sure if it's just a coincidence and this will crop up again, but so far after several reboots I haven't had the described issue occur again. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the Intel ICH8)?

Usb Device Descriptor Read 64 Error 110

Probing ports directly. [ 1.809249] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 1.809255] serio: i8042 AUX port at 0x60,0x64 irq 12 [ 1.809308] mice: PS/2 mouse device common for http://stackoverflow.com/questions/13653692/device-descriptor-read-64-error-110 Both keyboard and camera work. Device Descriptor Read 64 Error 110 Perhaps something was changed regarding the USB enumeration process for this release? Usb 1 1 Device Descriptor Read 64 Error 110 Can my boss open and use my computer when I'm not present?

The system took 2 minutes to boot (as opposed to 10 seconds usually) and the mouse and keyboard didn't respond when the greeter appeared. my review here A friend of mine has an Asus Z97-A and he runs Arch and has exactly the same problem. Its just the login message can not be responded to. Tango Icons Tango Desktop Project. Device Descriptor Read/64 Error 32

Internet 350 Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub $ lsusb -s 1 Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Frederick Chang (frdchang) wrote on 2016-02-17: #54 also have usb issues with 15.10 and asus x99e-ws. In one of them it mentioned something about power. click site Just upgraded to 15.04 today and boot time increased significantly.

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. Device Descriptor Request Failed I have an Asrock Z87 Extreme6/ac and modifying the Intel USB3 behavior causes my system to break in various ways (from no USB devices working, to just USB3 devices, to this 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?

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.

I remember this problem popped up once Gentoo went amd64 stable on a 4.x kernel. and do mention if it's the only thing that works, as I suppose there could be an issue with the state 'warm' hardware comes up in. Adv Reply February 2nd, 2011 #6 SpinUp View Profile View Forum Posts Private Message First Cup of Ubuntu Join Date Feb 2011 Location Canada Beans 7 DistroUbuntu 10.10 Maverick Meerkat Device Descriptor Read Error 110 One is Z97 Fatality.

Sense: Illegal mode for this track [24230.596679] end_request: I/O error, dev sr0, sector 0 [24230.601185] sr 4:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [24230.601195] sr 4:0:0:0: [sr0] Sense Key : Illegal Request [current] I want USB2 ;-) ( my troubble is similar, but with "error -32" : #586435 ) delca85 (delca85) wrote on 2010-06-08: #37 @manatlam Thanks! Maybe that is normal, I can't say. navigate to this website These all requires 10.10 as Eucalyptus 2 can not be installed on top of 10.4.

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, If you remove the power plug, all USB ports turn off, so the issue gets fixed, until the issue reappears at some random time, when the kernel gets loaded again. Reset CMOS (on board, using jumper, not "load defaults" through BIOS, that didn't help). I tend to say clear of new versions for a while to let the bugs get ironed out.

Are there any saltwater rivers on Earth? I'm off to play with some VMs. How can I have low-level 5e necromancer NPCs controlling many, many undead in this converted adventure? Report a bug This report contains Public information Edit Everyone can see this information.

No worries ! Makes the system *really* hard to use. What is fungibility and why does it matters? I hope a more stable 10.4. [24230.537875] sr 4:0:0:0: [sr0] Sense Key : Illegal Request [current] [24230.537893] Info fld=0x0 [24230.537898] sr 4:0:0:0: [sr0] Add.

What motherboard do you have? Fred (eldmannen+launchpad) wrote on 2015-08-11: #27 A search for "asmedia" on the Linux kernel commit log: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?id=refs%2Ftags%2Fv4.2-rc6&qt=grep&q=asmedia Merge tag 'usb-3.18-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b9427910d2f7fae717dc780fd7bde58e6a475c61 Perhaps? Plug Kinesis keyboard back in, additional output from 'dmesg|grep -i usb' 5. 'lsusb' output at this point 6. 'systemd-analyze blame' 7. 'uname -a' Immediately after boot: $ dmesg|grep -i usb [