Opened 5 weeks ago
Last modified 5 weeks ago
#15022 new bug
USB 'Joystick' controller no longer works
| Reported by: | Pete | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | Drivers/Input/USB-HID | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Has a Patch: | no | Platform: | All |
Description
Pre-PM, I sometimes used a Microsoft "Strategic Commander" (actually to control some functions of MusicWeaver). I wanted to use it once again in my current PM system, but it no longer works. I went back to the pre-PM partition, and it still functions fine there.
Strangely, I dug out another old USB controller -- a Thrustmaster "Top Gun" -- and it does work in my current system! (BTW, the behaviour is not dependent on MusicWeaver. The 'Stickit' test program shows the same.)
The pre-PM system in which everything works is hrev44674. My usual partition is hrev50180. The latest system I've managed to install is hrev51670, and behaviour there is exactly the same as my usual one.
For comparison, here are extracts from syslog in 44674 and 51670, when plugging in and removing both devices:
Pre-PM:
Thrustmaster: KERN: usb hub 56: port 0: new device connected KERN: usb_audio:01.51.770:init_driver::ver.0.0.4 KERN: usb hub 56: KERN: port 0: device removed KERN: usb_audio:02.06.801:init_driver::ver.0.0.4 Microsoft: KERN: usb hub 56: KERN: port 0: new device connected KERN: usb_audio:03.15.795:init_driver::ver.0.0.4 KERN: usb hub 56: KERN: port 0: device removed KERN: usb_audio:03.32.829:init_driver::ver.0.0.4
PM:
ThrustMaster: KERN: usb hub 56: port 0: new device connected KERN: usb_serial: probing device: 0x0000/0x0000 KERN: usb_serial: probing device: 0x8087/0x0024 KERN: usb_serial: probing device: 0x0c45/0x6457 KERN: usb_serial: probing device: 0x046d/0xc52b KERN: usb_serial: probing device: 0x0a12/0x0001 KERN: usb_serial: probing device: 0x0000/0x0000 KERN: usb_serial: probing device: 0x8087/0x0024 KERN: usb_serial: probing device: 0x044f/0xb102 KERN: usb_serial: probing device: 0x0bda/0x0138 KERN: usb hub 56: KERN: port 0: device removed KERN: usb_serial: probing device: 0x0000/0x0000 KERN: usb_serial: probing device: 0x8087/0x0024 KERN: usb_serial: probing device: 0x0c45/0x6457 KERN: usb_serial: probing device: 0x046d/0xc52b KERN: usb_serial: probing device: 0x0a12/0x0001 KERN: usb_serial: probing device: 0x0000/0x0000 KERN: usb_serial: probing device: 0x8087/0x0024 KERN: usb_serial: probing device: 0x0bda/0x0138 Microsoft: KERN: usb hub 56: KERN: port 0: new device connected KERN: usb_hid: no handlers for hid device KERN: usb_serial: probing device: 0x0000/0x0000 KERN: usb_serial: probing device: 0x8087/0x0024 KERN: usb_serial: probing device: 0x0c45/0x6457 KERN: usb_serial: probing device: 0x046d/0xc52b KERN: usb_serial: probing device: 0x0a12/0x0001 KERN: usb_serial: probing device: 0x0000/0x0000 KERN: usb_serial: probing device: 0x8087/0x0024 KERN: usb_serial: probing device: 0x045e/0x0033 KERN: usb_serial: probing device: 0x0bda/0x0138 KERN: usb hub 56: KERN: port 0: device removed KERN: usb_serial: probing device: 0x0000/0x0000 KERN: usb_serial: probing device: 0x8087/0x0024 KERN: usb_serial: probing device: 0x0c45/0x6457 KERN: usb_serial: probing device: 0x046d/0xc52b KERN: usb_serial: probing device: 0x0a12/0x0001 KERN: usb_serial: probing device: 0x0000/0x0000 KERN: usb_serial: probing device: 0x8087/0x0024 KERN: usb_serial: probing device: 0x0bda/0x0138
(I've removed some intervening messages that are not relevant.)
listusb always shows the same thing. Here are the relevant entries:
044f:b102 /dev/bus/usb/1/0/0 "ThrustMaster, Inc." "Top Gun Fox 2 Pro " ver. 0100 045e:0033 /dev/bus/usb/1/0/1 "Microsoft Corp." "Sidewinder Strategic Commander" ver. 0051
Change History (2)
comment:1 Changed 5 weeks ago by
comment:2 Changed 5 weeks ago by
Good thought, thanks. But no, it has no effect. I even tried removing usb_serial temporarily from the pre-PM system, just in case it was affecting things somehow. Worked just as before.
Does blacklisting the "usb_serial" driver help at all?