Bugzilla – Bug 141157
Two Identical USB Devices Using Different Drivers
Last modified: 2006-04-24 22:14:58 UTC
I have two identical RedOctane USB Dance Pads. Both used to work perfectly using the usbhid module\driver. Now one pad is using the xpad driver as opposed to the usbhid module. How do I change this? By using the xpad driver the dance pad no longer functions correctly. The second pad still works perfect. I didn't change anything on my system. I tried recompiling my kernel and removed the xpad module, but one of the dance pads still won't work. How do I force a device to use the usbhid driver? I'm running SuSE 10.0 64 bit. Is there a file which tells the USB device what to modprobe? I've tested on both 32 and 64 bit SuSE 10.0. Thanks in advance. I have a screenshot attached to this message board posting of my problem here (note: shots were taken with one pad at a time which is why both are /dev/js0): http://forums.suselinuxsupport.de/index.php?showtopic=28794 It seems a lot like this problem of two usb drivers fighting for control: https://bugzilla.novell.com/show_bug.cgi?id=105964 The solution there was to remove both modules, and then load back the one you want to use. I tried this: rmmod xpad usbhid modprobe usbhid Which didn't help. The only difference is that the pad changed it's status active status to "no". Any advice? I'm going crazy. Thanks in advance.
Here Dmesg results from plugging in both pads: usb 1-2: new full speed USB device using uhci_hcd and address 5 hub 1-2:1.0: USB hub found hub 1-2:1.0: 3 ports detected usb 1-2.1: new full speed USB device using uhci_hcd and address 6 input: USB HID v1.01 Joystick [RedOctane RedOctane USB Pad] on usb-0000:00:1d.0-2.1 usb 2-2: new full speed USB device using uhci_hcd and address 3 hub 2-2:1.0: USB hub found hub 2-2:1.0: 3 ports detected usb 2-2.1: new full speed USB device using uhci_hcd and address 4 input: X-Box pad on usb-0000:00:1d.1-2.1<6>usbcore: registered new driver xpad drivers/usb/input/xpad.c: X-Box pad driver:v0.0.5 As you can see the one pad is using the X-Box driver, even though both pads are identical.
attach the hwinfo output.
closing due to lack of info.