That's right, but it's not entirely right. When no devices are attached (like when you unplugged your drive) the controller is suspended. While suspended it can still detect connections; it just doesn't perform DMA and doesn't drive the USB bus. A connection triggers an interrupt which then resumes the controller. However, even without that interrupt the stat1 value should still indicate the presence of a connection. In your case neither one happened, no status indication and no interrupt.
If you have another USB port available, you could try plugging something into that one. It might make a difference.
Nope. I have 3 ports, that report as 3 different busses. But again, it doesn't make a difference.
I think its usb-uhci, as per lsmod report. Was that the correct way to determine it?
The initialization code probably has changed since 2.4; it may well be the source of your problem. Which driver are you using with 2.4: uhci or usb-uhci?
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
