045e:0745 Microsoft keyboard being detected as a joystick

[pullasuti]

The keyboard/receiver in my case is a 045e:0745 Microsoft Wireless Keyboard 3000, and a quick jstest says the following: "Joystick (Microsoft Microsoft® 2.4GHz Transceiver v6.0) has 37 axes and 57 buttons".

The main problem with this seems to be that in any application that uses a joystick, navigation is impossible because the keyboard joystick device /dev/input/js0 keeps sending nonsense to the application. (usually resulting in the "cursor" ending in left top/bottom corner).

A way to bypass this might be to rmmod joydev, but this will naturally prevent the use of actual joysticks.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-23-generic 3.2.0-23.36
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: suti 2082 F.... pulseaudio
 /dev/snd/controlC0: suti 2082 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xfa100000 irq 49'
   Mixer name : 'Realtek ALC887-VD'
   Components : 'HDA:10ec0887,10438445,00100302'
   Controls : 40
   Simple ctrls : 21
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xfa080000 irq 17'
   Mixer name : 'Nvidia GPU 16 HDMI/DP'
   Components : 'HDA:10de0016,10de0101,00100100'
   Controls : 24
   Simple ctrls : 4
Date: Tue Apr 24 17:53:54 2012
HibernationDevice: RESUME=UUID=16f06351-846d-482a-843a-2c69b1c802d3
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110920.5)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=f09d9467-7136-4930-8df0-12d03739eb5a ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-23-generic N/A
 linux-backports-modules-3.2.0-23-generic N/A
 linux-firmware 1.79
RfKill:

SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: Upgraded to precise on 2012-03-02 (52 days ago)
WifiSyslog:

dmi.bios.date: 02/11/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0401
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H61-M
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev x.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0401:bd02/11/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H61-M:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc4-precise/

[pullasuti (pullasuti)]

Tested the latest kernel, but the same js0 device is still generated for the keyboard. Attached a jstest with the latest kernel.

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[faceless (tiagolapa)]

Same problem here!! make some games unplayable. One less than satisfactory workaround is to rename /dev/input/js0

[Paulo Villi (paulovilli)]

Same behavior on fully updated Linux Mint 18 Cinnamon (based on Ubuntu 16.04) with linux kernel 4.4.0-31.

I see my Microsoft Wireless Keyboard 2000 as "Microsoft Microsoft® 2.4GHz Transceiver v7.0" with Axes:37 Buttons:75 as Device:/dev/input/js0 on jstest-gtk.

On Doom & Destiny it really treats the transceiver as a joystick and registers a constant "directional up" from it, making the game unplayable.