i unplugged it and the messages stopped. as a pure, ill-educated guess, it could be that the SET_ADDRESS is being timed out by the stack, then takes effect on the device, and then getting clobbered by the hub What is the most befitting place to drop 'H'itler bomb to score decisive victory in 1945? Using hpet for high-res timesource Calibrating delay using timer specific routine.. 4412.53 BogoMIPS (lpj=2206266) Security Scaffold v1.0.0 initialized SELinux: Initializing. click site
Here some details: Code: dmesg [ 195.275079] usb 2-1: new low-speed USB device number 6 using ohci-pci [ 195.440041] usb 2-1: device descriptor read/64, error -71 [ 195.705145] usb 2-1: device I found this message in dmesg after doing it: hda-intel: IRQ timing workaround is activated for card #0. checking TSC synchronization across 2 CPUs: CPU#0 had -1462333 usecs TSC skew, fixed it up. When I boot them I get a long series of messages: ... [ 2347.768419] hub 1-6:1.0: unable to enumerate USB device on port 6 [ 2347.968178] usb 1-6.6: new full-speed USB
I was about to throw in the towel and assuming that my system takes 4 minutes more to start, when I came to your page. I have no idea where to start. Thanks a lot for pointing me in the right direction! Thank you!
Comment 13 Alan Stern 2007-07-26 09:35:13 UTC Sounds like it could be a wiring problem on the gumstix, or something of that sort. Enabling unmasked SIMD FPU exception support... Ubuntu didn't recognized it at all. Usb Device Descriptor Read 64 Error 32 SAved me some big headaches!
Not working for me! Device Not Accepting Address 7, Error -71 There are one of two ways you should be able to test: 1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to yes!! I'd like to see USB2.0 speeds again...
Thanks in advance. https://bugzilla.kernel.org/show_bug.cgi?id=6078 about 1 year ago Thanks, helped me to safe a lot of time! Device Not Accepting Address Error 110 Mouse works with PS2 converter but not straight into USB. **lsusb output: Bus 004 Device 001: ID 0000:0000 Bus 001 Device 003: ID 03f0:7204 Hewlett-Packard DeskJet 36xx Bus 001 Device 001: Usb Device Not Accepting Address Error 32 I'm happy to provide more details if you need them.
Jeffrey Lebowski 3 months ago And sorry for all the typos... http://completeprogrammer.net/device-not/device-not-accepting-address-2-error.html Chuck Short (zulcss) wrote on 2006-08-19: #4 Please attach the output of dmesg as an attachment. heavymerchant over 1 year ago You Sir, are my saviour. Greetings from Italy! Device Not Accepting Address Error 62
Nobody has tried to duplicate his results or interpolate between the two .configs to see if the problem can be traced to a single item. The device in question, so far as I can tell, is my internal USB card-reader (its activity light is going like gangbusters). I saved the BIOS (never updated) with the dafault settings and I have never modify any parameters in the GRUB. navigate to this website I connected to it although I didn't connect anything to the serial end.
or are they damaged? Device Not Accepting Address Raspberry Pi Offline #7 2007-10-31 08:34:34 zenlord Member From: Belgium Registered: 2006-05-24 Posts: 1,209 Website Re: usb x-x: device not accepting address x, error -62 And another update: Ubuntu 7.10 desktop in livecd Arch Linux HomePackagesForumsWikiBugsAURDownload Index Rules Search Register Login You are not logged in.
lo just switched it over to uhci: Code: [ 225.574244] hub 4-0:1.0: cannot disable port 4 (err = -19) [ 225.574252] hub 4-0:1.0: cannot disable port 4 (err = -19) [ This may take a while, as I've never built a kernel under Ubuntu before :) Comment 15 Phil Lello 2007-10-16 05:06:29 UTC Nope, the David's patch doesn't fix my issue. ACPI: PCI Interrupt Link [LSMB] (IRQs 5 *7 9 10 11 14 15) ACPI: PCI Interrupt Link [LUB2] (IRQs 5 7 9 10 11 14 *15) ACPI: PCI Interrupt Link [LIDE] Rmmod: Error: Module Ehci_hcd Is Builtin. easy!
Do you want to help us debug the posting issues ? < is the place to report it, thanks ! 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 Any idea what's going on? my review here udev loaded cdc_acm as expected, and the phone charged for ~4 seconds and then quit.
Jul 8 14:50:30 greg-laptop usb 2-1: uevent Jul 8 14:50:30 greg-laptop usb 2-1: configuration #1 chosen from 2 choices Jul 8 14:50:30 greg-laptop usb 2-1: adding 2-1:1.0 (config #1, interface 0) I plug some in, and get those "device descriptor read/64, error #" messages, yet, without doing anything to the system and using the same usb cable, I can plug in any When I try to mount them again after such crashing (or just after having them unmounted manually before), they won't work anymore. No amount of fussing with services or modules or rebooting brings it back.
I've tried different cables with the same problem and it happens on any port. Then it becomes detectable again. My workaround has been to add "nomodeset" parameter to kernel boot parameters. Is that the problem?
ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22 23) *0, disabled. Until recently I operated with a single external USB disk in one of the ports, which works fine. Thanks so much! :-) diyhouse over 2 years ago Sorry,.. Thanks.
Updated BIOS. Jacob Buscher 3 months ago Thanks you so much! I have looked around to find a solution and it seems this is a reasonably common problem. Bug watch updates for Red Hat Bugzilla are disabled.