> By the way, Andras, was the device plugged directly into your computer's > USB port or did you use an intermediate hub?
It was plugged into a USB 2.0 hub, but behaviour is exactly the same when it's plugged in directly (well, maybe there is less stuff in the logs, I haven't tried). Let me know if you want me to try that as well. > ENODEV from a port reset? Sounds like a problem with the root hub driver > or the controller itself. Or else the device crashed _really_ hard. Don't think it crashed -- it is self-powered, and if I reboot the computer, it works again although it hasn't been powered down at any time. Andras =========================================================================== Major Andras e-mail: [EMAIL PROTECTED] www: http://andras.webhop.org/ =========================================================================== ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel