Hi Alan,
I build a 2.6.5 kernel with debugging turned on. The external drive
(Maxtor OneTouch) worked properly.
On
http://www.unix-wissen.de/usb/
you will find links to the boot-messages and the USB kernel
debugging messages under 2.6.5, along with the old stuff under
2.6.7, when it did not work properly.
I neglected to mention that when I was testing on 2.6.7, the "dd"
test command could take 30 seconds or longer after receiving
a "kill -9" to actually exit. I suppose that could have been caused
by the slowdown of writing all that debug info...
I would be grateful if you could have a look at the logs. As usual,
please let me know if there's any additional information I can
provide.
cheers,
Robert Urban
Alan Stern wrote:
> On Wed, 25 Aug 2004, Robert Urban wrote:
> > Alan Stern wrote:
> > > In short, everything is working as it should, except for your EHCI
> > > controller. You may need to get a replacement for it.
> >
> > Do you mean the driver or the hardware?
>
> Could be either one. Although if the hardware still works under 2.6.5
> (when was the last time you tried it?) then clearly some software is at
> fault. It might not the the EHCI driver itself though; it could be some
> other part of the system. It could even be related somehow to the BIOS.
>
> > It seems to me significant that the external disk (OneTouch) was
> > working fine under 2.6.5, however, only when connected to the set of
> > two directly-soldered USB connectors on the MB. Connecting the disk
> > to any other set of USB connectors led to a complaint about a high
> > speed device being on a low-speed connection.
>
> That would be expected if the other connectors weren't attached to a
> high-speed controller. Or if the controller they are attached to weren't
> working.
>
> > When a 2.6.7 or 2.6.8
> > kernel is booted, however, all USB connections behave similarly:
> > I get the complaint about a high-speed device on a low-speed connection.
> >
> > Clearly something changed between 2.6.5 and 2.6.7.
>
> My advice is to try running 2.6.5 again, with USB debugging configured on.
> Keep the system log and look especially for messages involving ehci, both
> during initial bootup and when plugging in the drive. Try plugging it
> into all the USB ports you've got and verify which ones will run at high
> speed. Then do the same thing under 2.6.8 and compare the results. If
> you find that a controller dies under one kernel but not the other, that
> gives a place to start digging. If a controller dies under both kernels
> then probably the hardware has gone bad.
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
