On Thu, 20 Nov 2003, Rogério Brito wrote: > I am using kernel 2.6.0-test9, just as a reminder. > > I did the following steps and for most of those steps, I put the > accompanying dmesg on my site <http://www.ime.usp.br/~rbrito/usb/>: > > 1 - booted without any device plugged; > 2 - did "modprobe -k uhci-hcd debug=2"; > 3 - loaded both the sd_mod and usb-storage modules; > 4 - checked what I had in /proc/driver/uhci and did the "echo 4 > ..." > for each of the controllers that were there; > 5 - plugged the drive (this didn't recognize it as a block device); > 6 - unplugged and replugged the drive (also didn't work). > > > OTOH, I compiled a 2.6.0-test9 kernel for my old notebook (a Compaq > Armada V300) and for this notebook, the drive works. The appropriate > dmesgs are also included at <http://www.ime.usp.br/~rbrito/usb/>.
Looking at your dmesg ouput, the important parts are at the end. For your desktop system it said: hub 1-1:1.0: enabling power on all ports hub 1-1:1.0: transfer --> -75 usb 1-1: control timeout on ep0in For your notebook, it said: hub 1-1:1.0: enabling power on all ports hub 1-1:1.0: port 1, status 101, change 1, 12 Mb/s hub 1-1:1.0: debounce: port 1: delay 100ms stable 4 status 0x101 hub 1-1:1.0: new USB device on port 1, assigned address 3 hub 1-1:1.0: transfer --> -75 and went on from there. The -75 error code means that the internal hub isn't behaving correctly. It's sending back replies that are longer than they are supposed to be. But even apart from that, there's still something else wrong. The fact that the problems began right after the power was turned on to the internal hub's ports is suspicious. It suggests that the power level could be a problem. Maybe your desktop computer isn't supplying enough power over its USB connection and your notebook is; that would explain everything. If you have an external hub that uses an external power supply -- one that you have to plug in to a wall socket -- that would make a good test. Attach the external hub to your desktop computer and then attach the drive to the hub. Since the hub gets power from the wall socket, it ought to provide sufficient current for the drive to operate. Another helpful thing you could do is to post the contents of /proc/bus/usb/devices on your notebook while the drive is plugged in and working. That would indicate if the drive is bus-powered and how much electricity it needs. Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
