Home > Device Descriptor > Usb Device Descriptor Read 64 Error 62

Usb Device Descriptor Read 64 Error 62

Contents

Search this Thread 09-06-2010, 02:11 AM #1 DebianUser Member Registered: Apr 2010 Posts: 88 Rep: USB device descriptor read/64, error -62 I'm running Debian on a Linksys NSLU2 (slug) User contributions on this site are licensed under the Creative Commons Attribution Share Alike 4.0 International License. Maybe the USB cable is bad? [ 5921.021000] hub 3-0:1.0: Cannot enable port 2. Topics: Active | Unanswered Index ┬╗Kernel & Hardware ┬╗usb x-x: device not accepting address x, error -62 Pages: 1 #1 2007-10-21 14:09:34 Oblong_Cheese Member Registered: 2007-01-25 Posts: 41 usb x-x: device check over here

PJ Brunet over 3 years ago That fixed it for me. Almufadado (almufadado) said on 2010-12-03: #15 This affect this motherboard too GA-TRC410MN-RH This comes with a packard bell imedia ???? (not even the right model is given to the consumer !!!) Join Date May 2010 Location uk Beans 9,374 DistroXubuntu 14.04 Trusty Tahr Re: unable to enumerate USB device (ft232r) Hi Originally Posted by hundred1906 I have tried on a different computer Switched to a better quality 60" cable which works.

Device Descriptor Read/64 Error 32

i had this issue from live distros on it!! From DMESG I get the following: Code: [ 6323.428040] usb 6-3: new full speed USB device number 21 using ohci_hcd [ 6323.612042] usb 6-3: device descriptor read/64, error -62 [ 6323.900045] I google around but could not find it.

  • Did you try to connect any other device to the port while watching dmesg?
  • Not sure if it just needed to be disconnected/reconnected, i.e., the same original port would have worked.
  • Usually, it's just a matter of rebooting, but today that wasn't working.
  • length is less important than quality because various issues come into play: impedance, capacitance, shielding, susceptibility to crosstalk (often solved by twisting matched pairs), etc.
  • Cheers!
  • Code: [email protected]:~/my_documents/router/dlink_dir_615$ sudo modprobe ftdi_sio [sudo] password for matthew: [email protected]:~/my_documents/router/dlink_dir_615$ lsmod | grep ftdi_sio ftdi_sio 40715 0 usbserial 47077 1 ftdi_sio [email protected]:~/my_documents/router/dlink_dir_615$ It seem you need this driver loaded.

Code: sudo modprobe ftdi_sio Assuming this is the correct driver then it has to be loaded before anything will happen. inxi is installable from most distro repositories. Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Official Flavours Support General Help [SOLVED] unable to enumerate USB device Device Descriptor Error Thanks so much! :-) diyhouse over 2 years ago Sorry,..

Just to prove it's not a hardware problem, you have tried it on a different platform (Windows or MAC) ? Device Descriptor Read 64 Error 71 That is what is happening i think but I would need more time to look at the code to be totally sure though. JonW almost 5 years ago Yep. Arch Linux HomePackagesForumsWikiBugsAURDownload Index Rules Search Register Login You are not logged in.

Jesper K. Device Not Accepting Address Error -62 Thanks! kernel: [ 2999.524782] usb 1-1: device descriptor read/64, error -62 Dec 3 22:14:16 ???? Join Date Mar 2008 Location UK Beans 133 DistroUbuntu 14.04 Trusty Tahr Re: unable to enumerate USB device (ft232r) Thanks for that advice.

Device Descriptor Read 64 Error 71

I see it like your USB port sent the initial request but did not receive an answer. my device pulls 35mA @ 5volts,.. Device Descriptor Read/64 Error 32 For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. Usb "device Descriptor Read/64, Error -71" UNIX is a registered trademark of The Open Group.

It may sounds strange, but in my case I found a series of connect/disconnect events into dmesg and syslog as well. check my blog I didn't think my card reader could have spontaneously stopped working (and it's only a couple months old, besides) but I decided to try an experiment. It's a usb to serial driver. That by disconnecting then reconnecting it, I might have forced the system to re-recognize it? Device Descriptor Read/64 Error 110

But what I took from that is that the driver is already in the kernel and that the ft232r does not require the latest driver. I have swapped cables and ports to no effect. once lsusb picks the device up, just run fsck on it; su password fsck /dev/sdcx fsck 1.41.3 (12-Oct-2008) dosfsck 3.0.1, 23 Nov 2008, FAT32, LFN /dev/sdc1: 0 files, 0/60102 clustersas long http://crimsonskysoftware.com/device-descriptor/usb-2-1-device-descriptor-read-64-error-71.html Die Liebe höret nimmer auf Why was Susan treated so unkindly?

After safely removing an ext4 USB3.0 pen drive when a text file inside it was open, the drive would not mount anymore. Device Not Accepting Address Error 32 My wife Eugenia and I originate from a place in Russian Siberia. Adv Reply March 14th, 2012 #8 matt_symes View Profile View Forum Posts Private Message Visit Homepage I'm back baby.

Had this problem with a short 24" cable.

Merci!!! USB 2.0 Controller Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR-

I have not tried the IRQPOLL recommendation for a couple of reasons, firstly my /boot/grub/menu.lst is empty, plus there are reported problems with IRQPOLL on 11.10 so am hesitant to go Device e017 IDE interface ATI Technologies Inc IXP SB400 IDE Controller (rev 80) (prog-if 82 [Master PriP]) Subsystem: Packard Bell B.V. Controller is probably using the wrong IRQ.usb 2-2: device descriptor read/64, error -110Could this be causing all these problems? have a peek at these guys scillystuff about 3 years ago Great, just what I was after.

It will only accept windows 7 or Ubuntu ... Plug everything back and boot into Linux. If you believe everything you read, you better not read. ~ Japanese Proverb If you don't read the newspaper, you're uninformed. What I think you were advising me is that ftdi_sio is present in the kernel Precise install (not sure precisely what that is) but is not enabled and that Modprobe...(etc) loads/enables

I'm currently investigating this solution: askubuntu.com/questions/62315/lost-wireless-mouse-connection-when-laptop-is-on-battery In other words, I'm blacklisting the USB suspend feature for this mouse device. My mouse would still randomly disconnect and never reconnect again. If you run dynamic, try to boot into something like minimal environment (kernel+initramfs that offers shell prompt instantly) with fully statically compiled kernel and try your devices. up vote 5 down vote favorite With kernels up to 3.19, all of my USB devices work perfectly.

If you read the newspaper, you're mis-informed. - Mark Twain Thinking about becoming an Ubuntu Member?