Thanks to several of you for helpful replies. I haven't pursued all your suggestions yet, and I'll respond individually soon.
But maybe I am getting closer: When I run lsusb from a text console rather than in a terminal in X, I get a message that was presumably being eaten by X somehow (going to var/log/messages maybe): usbdevfs: process 16410 (lsusb) did not claim interface 0 before use So: I added a call to usb_claim_interface in the test program testlibusb.c, and it returns -16, which usb_strerror converts to: "Could not claim interface 0: device or resource busy" Is this happening because the interface "belongs" to a module or program already running here? Can I force it to belong to me, at least long enough to check it out? (I am running these things as root, by the way.) Ben ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
