Device Not Accepting Address Error 71
Contents |
- USB problem toni_ukMay 17th, 2008, 08:58 PMI have a problem with my USB connections. for some resons they are not
Device Not Accepting Address Error 32
quite doing what they should. I have a new camera and on device descriptor read/64 error 32 my old laptop (running Ubuntu 8.04) it is deteted immediately on the old USB 1.0. On my device not accepting address error 110 brand new PC also running Ubuntu 8.04 it is not detected. dmesg is showing the following: [ 563.332000] end_request: I/O error, dev sdb, sector 60796 [ 563.332000] printk:
Usb Device Descriptor Read/64, Error
24 messages suppressed. [ 563.332000] Buffer I/O error on device sdb1, logical block 60745 [ 717.556000] usb 2-4: new high speed USB device using ehci_hcd and address 12 [ 717.668000] usb 2-4: device descriptor read/64, error -71 [ 717.884000] usb 2-4: device descriptor read/64, error -71 [ 718.100000] usb 2-4: new high speed USB device using ehci_hcd and
Usb Error Codes Linux
address 13 [ 718.212000] usb 2-4: device descriptor read/64, error -71 [ 718.428000] usb 2-4: device descriptor read/64, error -71 [ 718.644000] usb 2-4: new high speed USB device using ehci_hcd and address 14 [ 719.052000] usb 2-4: device not accepting address 14, error -71 [ 719.164000] usb 2-4: new high speed USB device using ehci_hcd and address 15 [ 719.572000] usb 2-4: device not accepting address 15, error -71 [ 801.752000] usb 2-4: new high speed USB device using ehci_hcd and address 16 [ 801.864000] usb 2-4: device descriptor read/64, error -71 [ 802.080000] usb 2-4: device descriptor read/64, error -71 [ 802.296000] usb 2-4: new high speed USB device using ehci_hcd and address 17 [ 802.408000] usb 2-4: device descriptor read/64, error -71 [ 802.624000] usb 2-4: device descriptor read/64, error -71 [ 802.840000] usb 2-4: new high speed USB device using ehci_hcd and address 18 [ 803.248000] usb 2-4: device not accepting address 18, error -71 [ 803.360000] usb 2-4: new high speed USB device using ehc
irritated by the way Ubuntu Hardy interacts with the disk. Half of the time when I connected the hard disk to my computer, I would get the following error messages: [ 4159.607574] usb 1-1: new device descriptor read/64 error 71 full speed USB device using uhci_hcd and address 4 [ 2079.875502] usb 1-1: device
Device Not Responding To Setup Address
descriptor read/64, error -71 [ 2080.099379] usb 1-1: device descriptor read/64, error -71 [ 2080.319263] usb 1-1: new full speed USB device using device not responding to set up address uhci_hcd and address 5 [ 2080.443858] usb 1-1: device descriptor read/64, error -71 [ 4161.322029] usb 1-1: device descriptor read/64, error -71 [ 4161.537896] usb 1-1: new full speed USB device using uhci_hcd and address 6 https://ubuntuforums.org/archive/index.php/t-797789.html [ 4161.945615] usb 1-1: device not accepting address 6, error -71 [ 4162.057577] usb 1-1: new full speed USB device using uhci_hcd and address 7 [ 4162.465330] usb 1-1: device not accepting address 7, error -71 Other than this error message, the device was totally unrecognised. The USB port worked fine, and there were no problems with the hard disk, which I could use without any problems on other computers. Ubuntu's behaviour was very https://urukrama.wordpress.com/2009/01/27/usb-drive-not-recognised-error-71/ unpredictable: I could detect no pattern why it sometimes recognised the disk, and why at other times it would ignore it. An internet search indicated this is not an uncommon problem, and usbcore, which is compiled as a module in Hardy's kernel, seems to be the culprit. Plenty of suggestions were offered online (including recompiling the kernel) but most of them did not help me at all. Finally, I found something on an old mailing list that solved the problem. All I needed to do was add the following line to /etc/modprobe.d/options: options usbcore use_both_schemes=y (If you are curious as to why this solved the problem, please read this clear explanation.) After a reboot, my external USB drive is now recognised without any difficulties every time I plug it in. Related Posted by urukrama Filed in General Tags: linux, ubuntu, usb, usbcore 4 Comments » 4 Responses to "USB drive not recognised (error-71)" pollux_master said June 10, 2010 at 12:09 pm Thx a lot! Solved my problem to connect my W395! Reply Matthew McEachen said June 30, 2010 at 6:26 am Excellent! I had a Western Digital external hard drive that was giving me grief with Ubuntu 10.04. I had to create a new /etc/modprobe.d/options file, but with your config line, everything is happy. Thanks for the post! Reply Matthew
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 answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring http://askubuntu.com/questions/317485/device-not-accepting-address-36-error-71-after-installing-kernel-3-10rc6 developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask https://bugzilla.kernel.org/show_bug.cgi?id=6078 Ubuntu is a question and answer site for Ubuntu users and developers. 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 top device not accepting address 36, error -71 after installing kernel 3.10rc6 up vote 0 down vote favorite I'm using Ubuntu 13.04 device not Gnome edition. I have a problem with my Arduino Duemilanove Board. Previously I was using kernel 3.9.2-030902-generic. After I installed kernel 3.10rc6 and I started my arduino IDE, I didn't see the serial port /dev/ttyusb0 as before. That's important as that's what I use for uploading my code onto the board. Now all I see is /dev/ttyS0. I tried plugging my board in all the usb port but none of them helped in uploading via /dev/ttyS0. I don't know it's actually device not accepting because of kernel 3.10 but previously everything was working fine. Here are links for lsusb and dmesg command output, taken after plugging the board. I did finally remove kernel 3.10 and made 3.9.2 default, but dmesg remains the same and shows some errors in the last lines. I've tried searching Google for solutions, but haven't had any luck. usb kernel tty arduino share|improve this question edited Jul 11 '13 at 8:26 asked Jul 7 '13 at 17:52 meteors 7932718 did you have to post all of dmesg? next time try: #dmesg -c Then plug in the arduino. then run #dmesg –j0h Jul 15 '13 at 0:56 I mean i would love to help, but there is soooo much usb stuff in your linked dmesg file. –j0h Jul 15 '13 at 0:57 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote I know that the answer is too late, but late answer is better than none I had the same problem, and i found the answer on the following link (http://stackoverflow.com/questions/9544557/debian-device-descriptor-read-64-error-71) The problem is mostly due to a hardware issue. that's the linux error code documentation, too: -EPROTO (*, **) a) bitstuff error b) no response packet received within the prescribed bus turn-around time c) unknown USB error share|improve this answer answered May 11 '14 at 9:33 user212807 36116 Thanks I don't have the faulty device currently but only solution I had t
First Last Prev Next This bug is not in your last search results. Bug6078 - USB "device not accepting address XX, error -71" problem Summary: USB "device not accepting address XX, error -71" problem Status: REJECTED INSUFFICIENT_DATA Product: Drivers Classification: Unclassified Component: USB Hardware: i386 Linux Importance: P2 normal Assigned To: Greg Kroah-Hartman URL: Keywords: Depends on: Blocks: USB 5836 Show dependency tree /graph Reported: 2006-02-15 12:15 UTC by Greg Kroah-Hartman Modified: 2007-10-30 23:42 UTC (History) CC List: 12 users (show) amth andrew_perrin boyi.liao charlysnews dbrownell dmitry.torokhov kay luigi.carlotto north phil.lello stern w0901 See Also: Kernel Version: 2.6.16-rc3 Tree: Mainline Regression: --- Attachments Increase the reset recovery delay time (421 bytes, patch) 2006-02-15 14:29 UTC, Alan Stern Details | Diff experimental 2.6.17-rc3 SET_ADDRESS patch (1.58 KB, patch) 2006-05-03 15:41 UTC, David Brownell Details | Diff View All Add an attachment (proposed patch, testcase, etc.) Description Greg Kroah-Hartman 2006-02-15 12:15:14 UTC Comment 1 Greg Kroah-Hartman 2006-02-15 13:36:38 UTC Ok, I've added everyone who has reported this kind of problem with the usb stack to this bug. If you don't want to be on it, please feel free to remove yourself. The problem is that the error: device not accepting address XX, error -71 is happening for some device in your system, on the latest kernel version. But unfortunatly, it's not easily reproducable for anyone in the Linux USB developer group. None of my devices or systems cause this error. So, any help in trying to debug this would be greatly appreciated. I know Alan has a suggested patch that might help people out, if he could attach it and people could try it out, that would be very helpful. Also, if people use git, could you try to use 'git bisect' to determine exactly what change caused this to happen? I think it was working fine for 2.6.13 or maybe 2.6.14, but 2.6.15 and later has the problem reported for it. Comment 2 Greg Kroah-Hartman 2006-02-15 13:37:35 UTC This is also reported in Novell's bugzilla at: https://bugzilla.novell.com/show_bug.cgi?id=145079 Comment 3 Alan Stern 2006-02-15 14:29:42 UTC Created attachment 7360 [details] Increase the reset recovery delay time Here's the patch Greg mentioned. It helped one user with an iPod; I'm sure it won't help everybody. In that case the problem was in the iPod, but the general problem appears to lie in the host controll