Okay, I see a couple of possible issues that could be contributing. (And, hey everybody, let's all just be cool here.)
The first question is, whether the module is set up to be loaded automatically (hotplug...), and if it can in fact be loaded, and if the module that you think you're loading actually is the one that is. Some modules are designed to printk()
a message to the system console-log when they're loaded or unloaded, just for this reason. Try explicitly loading and unloading it by hand.
Then, the USB device signature is used both by hotplug and (should be...)
by the driver to recognize the device that the driver's supposed to be loaded-for and then attached-to.
I always approach debugging tasks like this in more or less the same way: put a debugging symbol with conditional #define
s that cause a bunch
of messages to be spewed out to the system console log, as the module gives a "play by play account" of exactly what it's doing. (This usually is quickly followed by "d'oh!"