|
From: Kustaa N. <Kus...@pl...> - 2009-10-13 06:09:16
|
> We can't help you without more information that this. You should > provide the revised source code and the dmesg log (with usbcore's > usbfs_snoop parameter enabled). We may also need to see a usbmon > trace. > > Alan Stern > Alan, thanks for the offer to help further, I will try to come up later today with those things you requested. >From a quick googling it seems that enabling usbf_snoop should be trivial in Ubunty Hardy but usbmon seems like a bit more involved. A few thoughts however. I doubt that usbmon will tell us much, because to me it seems the my code fails before anything happens at usb packet level. An other thought. This page seems to provide instructions on setting up usbmon: http://tjworld.net/wiki/Linux/Ubuntu/USBmonitoring does that look it makes sense? It looks a bit involved but not too bad because I'm an Ubunty Hardy and I'm ready to walk the mile. However, this seems to involve significant changes to the system, including installation of USB device file system (not that I'm up to speed to understand what that is) and this sounds like something that may alter my system so that the problem disappears. Speaking of which, just a hunch, but could be this be the problem: according to the above link Ubuntu hardy does not have USB device file system, does libusb (0.1) depend on that? Ok, anyway I did a clean Ubuntu install first thing this morning, verified that I get permission error without the modifiaction to the default udev rule for usb devices and that after modification I get no such directory/file error on claim interface. Interestingly, for some reason, even after clean install it does no appear as if usbhid grabbed the device anymore, as it did before. Perplexing, need to double check again by reinstalling once we figure out the no such directory. Thanks again, Kusti |