On Wed, 20 Jun 2001, Greg KH wrote: > On Wed, Jun 20, 2001 at 02:07:18PM -0400, [EMAIL PROTECTED] wrote: > > > > I did notice that if I move the device to a different USB port I have > > to modprobe hid again before it will work (er, show up in the listed > > devices under usbview) -- is that normal? > > No that isn't. Who is unloading the hid driver? If you plug a new > device in, usbview should detect that. What kernel version are you > using? 2.4.5 -- no patches or anything added. That might have been a fluke or a problem with usbview refreshing, as I just tested it again and it showed up properly. > > Is there any way I can force the hid driver to bind itself to the device? > > What does the kernel debug log show when you plug the device in, and the > hid driver is loaded? Jun 20 17:14:58 forsaken kernel: usb.c: USB device 4 (vend/prod 0x6666/0x667) is not claimed by any active driver. The only variable is the device number (based upon where I plug the thing in). This is after using modprobe and after configuring usbmgr for the specific vendor device (not that I'd expect that to make any difference). I'm a bit confused here. If the devices identifies itself as a HID device and hid.o still doesn't know to bind to it, what does determine what hid will bind with? _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: http://lists.sourceforge.net/lists/listinfo/linux-usb-users
