> Not at this time. Am I correct to assume that this is the > disk in question, connected to Linux 2.4 at full speed? <snip>
Yes. > Matched with an ALI EHCI controller, which 2.6 boots like this: <snip><snip> Yes. > > Nobody has yet reported problems with ALI's EHCI silicon, so > I wouldn't expect that to be an issue. > > But I don't know about the ALI usb-to-ide adapters; this one > is for some reason rejecting the SET_ADDRESS request. <more snipping> > The only thing that comes to mind is that maybe the disk is > violating the USB protocol by expecting Linux to fetch its > device descriptor before setting the address. I've yet to > actually hear of hardware that fails that way ... but poorly > tested hardware might end up with failures like that if it > were only tested against MS-Windows. You could experiment to > see if that's the case, just add an extra fetch before the > (only) call to usb_set_address() in usbcore. I've just screwed the eproms in an attempt to see if upgrading the 2-year old bios on my motherboard (ECS K7S5A) would make any difference. :( I've ordered a new MB (ECS KT600) which will arrive on Wednesday. Double :( > You've said that "devices" -- plural -- aren't recognized. > What other high speed devices are acting this way for you? > Is it the identical failure (EPROTO)? Sorry, I should have been more clear. I only have the one high-speed device. Initially other 1.0 and 1.1 devices were not recognized, but this changed after upgrading to the 2.6 kernel. Chris ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
