On Mon, 6 Sep 2004, Robert Urban wrote: > should I copy the list, and you two when replying in the future?
Yes please. > > Just three? The EHCI controller reports there are three more > > busses in addition to EHCI ... you showed one UHCI, I'd expect > > there would be two more. (Each UHCI bus having two ports, > > and the EHCI one having six. I'm guessing this is an Intel > > controller; it doesn't look like VIA since the size of the periodic > > schedule is fixed at 1024 entries, it's not tunable.) Note that the complete logs showed 3 UHCI controllers in addition to the EHCI controller. I edited the other ones out because they weren't relevant to the problem at hand. > > > Coincidentally, > > > or not, the bus on which the drive works is the one whose jacks > > > are directly soldered to the MB, that is, the ones right next to > > > the serial, parallel, mouse, KB, ethernet, etc connectors at the > > > back. The other (2) USB busses are connected to jacks via cables > > > that plug in to the MB. > > > > Are you sure those are connected properly, rather than maybe > > being reversed? The motherboard connectors I've seen were easy > > to hook up backwards, or even just offset by a row of pins or two. > > And some of those cables didn't seem to handle high speed signals > > all that well, either. > > > > Since you're seeing catastrophic errors very early, a wiring > > problem like that could explain everything... Bear in mind that under 2.6.7 the EHCI driver failed even before any devices had been connected, whereas with 2.6.5 it worked for the directly-soldered connection. Alan Stern ------------------------------------------------------- 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
