045e:00b0 Microsoft keyboard and 045e:0745 nano transceiver recognised as joystick - interferes with some games

[themusicalduck]

Microsoft Digital Media Pro keyboard interferes with certain games. Ubuntu seems to see the keyboard as a joystick control. Package Joystick Calibrator 1.5.6 confirms by listing Microsoft Digital Media Pro Keyboard as a joystick device on /dev/input/js0

Behaviour includes taking over control of any joystick enabled games and continuously pushing control to the left or causing a menu selection to continuously move down or up. Affected games that I know of so far include Tux racer, Alex the Alligator, Track mania Nations forever (wine) and Final Fantasy 8 (wine).

A workaround is to run Joystick Calibrator, click on Calibrate and save settings. This seems to 'calibrate' the keyboard properly and stops it from interfering with games.

Ubuntu version is 9.04. Wine is version 1.1.24.

[AndreK (andre-k)]

Problem still exists in Ubuntu 9.10
Please fix.

[AndreK (andre-k)]

BTW: not all games can handle multiple joysticks , and any "real" joystick ends up as /dev/input/js1 because the keyboard is js0 - so it stops some programs from working properly...

[themusicalduck (themusicalduck)]

This problem still exists in Lucid Lynx. However, Joystick Calibrator doesn't exist in the repos any more, so you need to install package "joystick" and run

jscal -c /dev/input/js0

to fix it.

[Fabio Marconi (fabiomarconi)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Is this bug reproducible with the latest Lucid packages ?
Tanks in advance.

[themusicalduck (themusicalduck)]

Yeah, problem still exists on a fully updated 10.04 system. Just tested it on Alex the Alligator, and the cursor on the menu still moves down continuously.

/dev/input/js0 still exists too and I have no other joystick plugged in.

[Fabio Marconi (fabiomarconi)]

Thanks for the reply.
can you please run in a terminal

lsusb

copy the output, paste into a file and attach here

lspci

copy the output, paste into a file and attach here

we need also you attach these files:

/var/log/syslog
/var/log/dmesg
/var/log/kern.log

:)Fabio

[themusicalduck (themusicalduck)]

Attached the files.

[Fabio Marconi (fabiomarconi)]

Asrequested file are attached i mark as Confirmed.
:)Fabio

[Lee Jones (lag)]

I'm happy to take a look at this for you.

Can you please attach the results of "lshw" and "lsmod" whilst the keyboard is plugged in please?

[Lee Jones (lag)]

And "/var/log/udev" as well please.

[themusicalduck (themusicalduck)]

Attached the files.

For some reason the lshw file won't open in gedit, but it does work with cat, nano and leafpad so hopefully it is readable.

Thanks for taking time to look at the bug :)

[Lee Jones (lag)]

Here's your problem:

UDEV [1286579018.442576] add /devices/pci0000:00/0000:00:02.0/usb2/2-9/2-9:1.1/input/input5/js0 (input)
UDEV_LOG=3
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:02.0/usb2/2-9/2-9:1.1/input/input5/js0
SUBSYSTEM=input
DEVNAME=/dev/input/js0
SEQNUM=1647
ID_INPUT=1
ID_INPUT_KEY=1
ID_INPUT_KEYBOARD=1
ID_VENDOR=Microsoft
ID_VENDOR_ENC=Microsoft
ID_VENDOR_ID=045e
ID_MODEL=Microsoft®_Digital_Media_Pro_Keyboard
ID_MODEL_ENC=Microsoft®\x20Digital\x20Media\x20Pro\x20Keyboard
ID_MODEL_ID=00b0
ID_REVISION=0143
ID_SERIAL=Microsoft_Microsoft®_Digital_Media_Pro_Keyboard
ID_TYPE=hid
ID_BUS=usb
ID_USB_INTERFACES=:030101:030000:
ID_USB_INTERFACE_NUM=01
ID_USB_DRIVER=usbhid
ID_PATH=pci-0000:00:02.0-usb-0:9:1.1
MAJOR=13
MINOR=0
DEVLINKS=/dev/char/13:0 /dev/input/by-id/usb-Microsoft_Microsoft®_Digital_Media_Pro_Keyboard-kbd /dev/input/by-path/pci-0000:00:02.0-usb-0:9:1.1-kbd

Leave it with me and I'll try to address it early next week. :)

[Lee Jones (lag)]

Here is a snip from Documentation/devices.txt

13 char Input core
    0 = /dev/input/js0 First joystick
    1 = /dev/input/js1 Second joystick
      ...
   32 = /dev/input/mouse0 First mouse
   33 = /dev/input/mouse1 Second mouse
      ...
   63 = /dev/input/mice Unified mouse
   64 = /dev/input/event0 First event queue
   65 = /dev/input/event1 Second event queue

For some reason the Microsoft Digital Media Pro Keyboard driver is requesting to be handled at a joystick. I don't know much about the area, but I will have a dig around in the code soon enough.

[Lee Jones (lag)]

Can you send me the output of this command please?

udevadm info --export-db

[themusicalduck (themusicalduck)]

Attached the output.

[Lee Jones (lag)]

I've built you a kernel. It won't fix the errors, but it will give me some clues as to what's going on. The kernel can be found here:

http://people.canonical.com/~ljones/lp390959-keyboard-joystick-lucid/

Once the kernel has been loaded and you have rebooted, if you could issue the following command then unplug and re-plug your keyboard, it should provide me with even more information.

echo 1 | sudo tee -a /sys/module/hid/parameters/debug

Once complete can you upload /var/log/kern.log please?

Thanks.

[themusicalduck (themusicalduck)]

Sorry for the delay getting back to you on this.

I've attached the log. For some reason the .deb file you provided for the headers wouldn't install, either the i386 or all version, so I couldn't get GDM to run as I couldn't recompile the drivers module for my graphics card. I did everything you asked from recovery mode though, so I hope it still provides the same thing.

I'm running Maverick now, so if it needs to be run on Lucid then I could do it again on a live CD session. In which case GDM would hopefully start properly.

[belegdol (belegdol-linux-kernel-bugs)]

The said mouse is being recongnised as a joystick, interfering with input in games [1] and arcade emulators [2].
The following appears in /var/log/messages when you plug the transceiver in:

Feb 11 23:40:08 snowball kernel: [37176.263281] usb 4-2: new full speed USB device using uhci_hcd and address 4
Feb 11 23:40:08 snowball kernel: [37176.423066] usb 4-2: New USB device found, idVendor=045e, idProduct=0745
Feb 11 23:40:08 snowball kernel: [37176.423070] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 11 23:40:08 snowball kernel: [37176.423074] usb 4-2: Product: Microsoft® Nano Transceiver v2.0
Feb 11 23:40:08 snowball kernel: [37176.423077] usb 4-2: Manufacturer: Microsoft
Feb 11 23:40:08 snowball kernel: [37176.434375] input: Microsoft Microsoft® Nano Transceiver v2.0 as /devices/pci0000:00/0000:00:1d.2/usb4/4-2/4-2:1.0/input/input13
Feb 11 23:40:08 snowball kernel: [37176.435724] generic-usb 0003:045E:0745.0007: input,hidraw0: USB HID v1.11 Keyboard [Microsoft Microsoft® Nano Transceiver v2.0] on usb-0000:00:1d.2-2/input0
Feb 11 23:40:08 snowball kernel: [37176.442886] input: Microsoft Microsoft® Nano Transceiver v2.0 as /devices/pci0000:00/0000:00:1d.2/usb4/4-2/4-2:1.1/input/input14
Feb 11 23:40:08 snowball kernel: [37176.443441] generic-usb 0003:045E:0745.0008: input,hidraw1: USB HID v1.11 Mouse [Microsoft Microsoft® Nano Transceiver v2.0] on usb-0000:00:1d.2-2/input1
Feb 11 23:40:08 snowball kernel: [37176.468551] input: Microsoft Microsoft® Nano Transceiver v2.0 as /devices/pci0000:00/0000:00:1d.2/usb4/4-2/4-2:1.2/input/input15
Feb 11 23:40:08 snowball kernel: [37176.472126] generic-usb 0003:045E:0745.0009: input,hiddev96,hidraw2: USB HID v1.11 Device [Microsoft Microsoft® Nano Transceiver v2.0] on usb-0000:00:1d.2-2/input2

Please let me know what other info is needed to help resolving this issue.

[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/581862
[2] http://forums.bannister.org/ubbthreads.php?ubb=showflat&Number=67390

[netbox253 (netbox253-linux-kernel-bugs)]

Same behavior on gentoo (using kernel 2.6.37.6) with Microsoft Wireless Optical Desktop keyboard and mouse combo, seems to be an old bug, see [1].

[1] http://forums.gentoo.org/viewtopic-t-362032.html

[Ryan Armstrong (software+ubuntu)]

I am having the same issue with the Logitech Access Keyboard 600 on Xubuntu 11.10.

[Leonardo Torok (leotorok)]

I'm having the same problem in Ubuntu 11.10. The keyboard works perfectly, but is also recognized as a joystick. It generates problems with several games.

[Ryan Armstrong (software+ubuntu)]

I actually found out that my problem was caused by btnx creating a fake joystick, and not by the keyboard itself. I've stopped using btnx and "solved" the problem accordingly.

[Juliano Ravasi (jravasi)]

I have the same problem with a Microsoft Wired Keyboard 600. It gets detected as a keyboard, mouse and joystick, and creates a /dev/input/js0, causing problems with several games.

Is there a way to blacklist the creation of the dev js0 file for this particular device?

[Jero (jbuencuerpo)]

I solve it following the instructions here http://ryort.wordpress.com/2011/12/04/udev-and-the-microsoft-digital-media-keyboard-3000-wha/

In my case was a microsoft mouse+keyboard 3000 v2.0, at a terminal type:

dsmesg

And search for something like this .

[ 19.205623] generic-usb 0003:045E:0745.0001: input,hidraw0: USB HID v1.11 Keyboard [Microsoft Microsoft® 2.4GHz Transceiver v6.0] on usb-0000:00:1a.0-2/input0

In /etc/udev/rules.d/ folder create an empty file named microsoft-digital-media-keyboard.rules

The add this lines, changing the idVendor and idProduct you see on dsmesg , in my case 045e and 0745

SUBSYSTEM=="input", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="0745", RUN+="/lib/udev/keymap input/event%n /lib/udev/keymaps/microsoft-digital-media-keyboard-3000"
SUBSYSTEM=="input", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="0745", KERNEL=="js0", NAME="not-really-js%n"

at the folder /lib/udev/keymaps/ create another empty file, if you want to remap function keys in future you should edit this file at your purpose as is shown on the blog.

I hope it helps you,
Saludos!

[Jero (jbuencuerpo)]

Sorry I forgot to say you have to name the second empty file as microsoft-digital-media-keyboard-3000

[penalvch (penalvch)]

themusicalduck, thank you for reporting this bug and helping make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 390959

[themusicalduck (themusicalduck)]

Hi Christopher,

I don't have Ubuntu installed anymore but I did have a daily image of 12.04 from a few weeks ago installed on my pendrive. I booted it up and ran your command off there, logged into launchapad and did the authorisation bit, but then got this message:

You are not the reporter or subscriber of this problem report, or the report is a duplicate or already closed.

Please create a new report using "apport-bug".

[penalvch (penalvch)]

themusicalduck, please report a new bug report via the Terminal:
ubuntu-bug linux

Then subscribe me to it and we can take it from there.

[pullasuti (pullasuti)]

I have a Microsoft Wireless Keyboard 3000, and the same nonsense is going on. Running the latest version of 12.04.

[penalvch (penalvch)]

pullasuti, please execute the following via the Terminal and feel free to subscribe me to it:
ubuntu-bug linux

Thanks!

[themusicalduck (themusicalduck)]

Christopher -

Very sorry, your request completely slipped my mind until I got the notification from pullasuti's comment.

I've made a new report here - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987622

If pullasuti makes a report too then they might both be useful at least. Or you can just continue working with him since he probably has a permanent and more up to date installation and won't be relying on using a live-usb.

[pullasuti (pullasuti)]

I posted a report too, if not for anything else, at least for some extra info.

It can be found here : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987877

And yup, I'm running an installation that is in daily use, so if there is something to check I'll do what I can.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Juliano Ravasi (jravasi)]

Still a problem in Precise and kernel 3.2.0-25.

[Juliano Ravasi (jravasi)]

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: juliano 4956 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0000000 irq 22'
   Mixer name : 'Realtek ALC889'
   Components : 'HDA:10ec0889,80860022,00100004'
   Controls : 42
   Simple ctrls : 24
DistroRelease: Ubuntu 12.10
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=4f433bf6-748e-432d-b93f-de4d0e693b91
InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-25-generic root=/dev/mapper/Nagisa1-Root ro rootdelay=5
ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-25-generic N/A
 linux-backports-modules-3.2.0-25-generic N/A
 linux-firmware 1.79
RfKill:

SourcePackage: linux
Tags: quantal quantal
Uname: Linux 3.2.0-25-generic x86_64
UpgradeStatus: Upgraded to quantal on 2012-06-24 (0 days ago)
UserAsoundrc:
 #pcm.!default plug:hw:0
 #ctl.!default hw:0
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare vboxusers
dmi.bios.date: 08/30/2010
dmi.bios.vendor: Intel Corp.
dmi.bios.version: SOX5810J.86A.5456.2010.0830.0013
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DX58SO
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE29331-703
dmi.chassis.type: 2
dmi.modalias: dmi:bvnIntelCorp.:bvrSOX5810J.86A.5456.2010.0830.0013:bd08/30/2010:svn:pn:pvr:rvnIntelCorporation:rnDX58SO:rvrAAE29331-703:cvn:ct2:cvr:

[Juliano Ravasi (jravasi)]

apport information

[timo.jyrinki (timo.jyrinki-linux-kernel-bugs)]

Collected some similar downstream bugs to be duplicates of the following bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/390959

[alan (alan-linux-kernel-bugs)]

Closing as obsolete, if this is still seen on modern kernels please update

[netbox253 (netbox253-linux-kernel-bugs)]

Still a problem here on 3.10 series. Please reopen.

[alan (alan-linux-kernel-bugs)]

Thanks

[Foul (foulweb)]

Still present in Kubuntu 14.14 :\

[Foul (foulweb)]

14.04 sorry..

[Sérgio Pace (svpace)]

I am having the same issue with Microsoft Wireless Mobile Mouse 1000 (Product Id: 0745) and Microsoft Wireless Keyboard 800 (Product Id: 07b2) on Xubuntu 14.04. Each dongle creates 3 devices: a keyboard, a mouse and a generic HID device that is recognized as a joystick.

[Josef Schlehofer (pepe-schlehofer)]

Same issue with other keyboard - Aula Adjudication

Kernel: 3.15.0-031500-generic
Ubuntu: 14.04 64bit

lsusb & lspci
http://pastebin.com/N7jSVH41

dmesg
http://pastebin.com/bR5AgnR4

kern:
https://friendpaste.com/2MCgzw3g18ATOWyLGBBBvy

[pepe (pepe-linux-kernel-bugs)]

Problem still exists with latest kernel (3.15)

[penalvch (penalvch)]

Josef Schlehofer, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[dor.askayo (dor.askayo-linux-kernel-bugs)]

Still happens in 3.16.1.

[Alexander (jufofu)]

Same for Microsoft 2.4GHz Transceiver v9.0 from MS Sculpt Ergonomic Desktop 045e:07a5
$ udevadm info /dev/input/js0 http://pastebin.com/JKJuPWQq
$ udevadm info --attribute-walk /dev/input/js0 http://pastebin.com/0drxcrS5

Looks like a workaround is here: https://forum.manjaro.org/index.php?PHPSESSID=edmjqlp8356fi33uc12ag0hfj0&topic=15275.msg144519#msg144519

[penalvch (penalvch)]

Alexander, thank you for your comment. Could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Martin Spacek (mspacek)]

I seem to be having the same problem with a Microsoft Sculpt Mobile Mouse I just bought.

http://www.microsoft.com/hardware/en-ca/p/sculpt-mobile-mouse

This is in Xubuntu 14.04 amd64 on a Thinkpad W510. In the xfce "Mouse and Touchpad" settings I get two entries for "Microsoft Microsoft (R) Nano Transceiver v1.0".

Some more details:

$ udevadm info /dev/input/js0

https://gist.github.com/mspacek/c805f36a7129a30a0bcf

$ udevadm info --attribute-walk /dev/input/js0

https://gist.github.com/mspacek/96673b195fa0b16f9e20

$ uname -a
Linux Escher 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

[thomas.langkamp (thomas.langkamp-linux-kernel-bugs)]

confirmed with 3.16.4 and A4tech X7 mouse (openSUSE Factory x64)

workaround:
sudo rm /dev/input/js0

But this has to be done after every reboot.

A google for "linux recognize mouse as joystick" for example gives you many results of many people experiencing this, some even with keyboards as joysticks on all Distros.
I found that this bug exists at least since 2010:

http://forums.fedoraforum.org/archive/index.php/t-240201.html

"Hello,
I have the mouse X7, model XL-750F from A4tech. This mouse was running with Fedora 10 without any problems.
Now I have installed Fedora 12 and my mouse pointer always moves to one side or corner of the screen.
My second Logitech mouse is working fine. But it is a little bit old.
So, if anyone can help my with my A4tech mouse ... "

[jufofu (jufofu-linux-kernel-bugs)]

Workaround for MS Sculpt Ergonomic Desktop: https://forum.manjaro.org/index.php?PHPSESSID=edmjqlp8356fi33uc12ag0hfj0&topic=15275

[thomas.langkamp (thomas.langkamp-linux-kernel-bugs)]

updated today to 3.17.1 - still there
workaround is nice, but not a solution for the average user...

what logs etc do you need to fix this?

[Jarkko Korpi (jarkko-korpi-t)]

https://bugs.winehq.org/show_bug.cgi?id=35954

[ghallberg (ghallberg-linux-kernel-bugs)]

And this is still an issue in 3.18.2

[dor.askayo (dor.askayo-linux-kernel-bugs)]

No change in 3.19.3. Would love for it to get some more attention.

[Alexander (alexanderemmanuelpacheco)]

this bug is still present, affecting Microsoft brand wireless mice and keyboards. in 2015, six years after the first bug report.

come on guys.

[alexanderemmanuelpacheco (alexanderemmanuelpacheco-linux-kernel-bugs)]

Chiming in to note this also effects Microsoft Mouse 4000 (Model 1383) as well as many other Microsoft-brand wireless devices. Relevant: https://bugzilla.kernel.org/show_bug.cgi?id=37982 and a Ubuntu bug report dating back to 2009 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/390959

This is pretty huge for anyone with a Microsoft mouse, as it renders many games unplayable. Workarounds exist but involving udev rules but they are device specific and have mixed results.

[dor.askayo (dor.askayo-linux-kernel-bugs)]

Still happens in 4.0.1. It's getting absurd at this point.

[idaho06 (cesar-idaho)]

I have a Microsoft Wired Keyboard 600.
Used the command:
$ udevadm info -q path -a -n input/js0

to get the precise parameters for the udev rules file.

And this is my workaround:

<pre>
idaho@streetfighter2:~$ cat /etc/udev/rules.d/99-false-joystick-microsoft.rules
SUBSYSTEM=="input", ATTRS{name}=="Microsoft Wired Keyboard 600", ATTRS{phys}=="*/input1", RUN{program}+="/bin/rm %p", RUN{program}+="/bin/rm /dev/input/%k"
</pre>

This deletes every /dev entry for the second device of the keyboard (input1), including /dev/input/js0 and /dev/input/event3.

[Denilson Sá (denilsonsa)]

As a workaround, I tried collecting several Vendor/Product IDs that trigger this bug, and created a udev rule for disabling the joystick device for them. I'm sharing this udev rule file at: https://gist.github.com/denilsonsa/978f1d842cf5430f57f6

[denilsonsa (denilsonsa-linux-kernel-bugs)]

As a workaround, I tried collecting several Vendor/Product IDs that trigger this bug, and created a udev rule for disabling the joystick device for them. I'm sharing this udev rule file at: https://gist.github.com/denilsonsa/978f1d842cf5430f57f6

[dmitry.torokhov (dmitry.torokhov-linux-kernel-bugs)]

What is the /proc/bus/input/devices for that mouse please?

[denilsonsa (denilsonsa-linux-kernel-bugs)]

Created attachment 177051
/proc/bus/input/devices

I have a "Microsoft Wireless Desktop 800", which is a tiny wireless receiver for both mouse and keyboard. It gets detected as a joystick with several axes (besides the normal mouse and keyboard).

I also have a "Wacom Graphire 4" tablet, that also gets detected as a joystick.

Right now I'm using Ubuntu 15.04 with Linux kernel 3.19.0, but this bug exists for several years.

Relevant lsusb lines:

Bus 001 Device 004: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
Bus 001 Device 003: ID 056a:0016 Wacom Co., Ltd Graphire 4 6x8

I also remember that the following project also got (incorrectly) detected as a joystick:
https://bitbucket.org/denilsonsa/atmega8-magnetometer-usb-mouse
https://github.com/denilsonsa/atmega8-magnetometer-usb-mouse
However, I can't provide more info on it because I don't have the hardware anymore and it happened 4 years ago. If you really really want, I can hack that project again on a breadboard, but it might take a while.

Still, if you need more info regarding the Microsoft wireless keyboard/mouse, or regarding the Wacom tablet, just ask and I can provide right away.

[chibiriak (chibiriak-linux-kernel-bugs)]

Ubuntu 15.04 bug exist with A4Tech X7 mouse:
dmesg:
[ 684.641672] usb 1-2.1: new full-speed USB device number 6 using ehci-pci
[ 684.914756] usb 1-2.1: New USB device found, idVendor=09da, idProduct=8090
[ 684.914761] usb 1-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 684.914764] usb 1-2.1: Product: USB Full Speed
[ 684.914765] usb 1-2.1: Manufacturer: A4Tech
[ 684.916844] input: A4Tech USB Full Speed as /devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2.1/1-2.1:1.0/0003:09DA:8090.0006/input/input18
[ 684.917106] hid-generic 0003:09DA:8090.0006: input,hidraw1: USB HID v1.11 Mouse [A4Tech USB Full Speed] on usb-0000:00:12.2-2.1/input0
[ 684.919709] input: A4Tech USB Full Speed as /devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2.1/1-2.1:1.1/0003:09DA:8090.0007/input/input19
[ 685.025280] hid-generic 0003:09DA:8090.0007: input,hiddev0,hidraw2: USB HID v1.11 Keyboard [A4Tech USB Full Speed] on usb-0000:00:12.2-2.1/input1

lsusb:
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 058f:6364 Alcor Micro Corp. AU6477 Card Reader Controller
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 07d1:3a10 D-Link System DWA-126 802.11n Wireless Adapter [Atheros AR9271]
Bus 001 Device 005: ID 062a:0201 Creative Labs Defender Office Keyboard (K7310) S Zodiak KM-9010
Bus 001 Device 006: ID 09da:8090 A4 Tech Co., Ltd X-718BK Oscar Optical Gaming Mouse <---------------- This is my mouse
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

[chibiriak (chibiriak-linux-kernel-bugs)]

(In reply to Denilson Figueiredo de Sá from comment #15)
> As a workaround, I tried collecting several Vendor/Product IDs that trigger
> this bug, and created a udev rule for disabling the joystick device for
> them. I'm sharing this udev rule file at:
> https://gist.github.com/denilsonsa/978f1d842cf5430f57f6

Thanx!
There is A4Tech X7 mouse with that bug:
---------------------------------------LSUSB--------------
Bus 001 Device 006: ID 09da:8090 A4 Tech Co., Ltd X-718BK Oscar Optical Gaming Mouse
---------------------------------------DMESG-------------
new full-speed USB device number 6 using ehci-pci
[ 684.914756] usb 1-2.1: New USB device found, idVendor=09da, idProduct=8090
[ 684.914761] usb 1-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 684.914764] usb 1-2.1: Product: USB Full Speed
[ 684.914765] usb 1-2.1: Manufacturer: A4Tech
[ 684.916844] input: A4Tech USB Full Speed as /devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2.1/1-2.1:1.0/0003:09DA:8090.0006/input/input18
[ 684.917106] hid-generic 0003:09DA:8090.0006: input,hidraw1: USB HID v1.11 Mouse [A4Tech USB Full Speed] on usb-0000:00:12.2-2.1/input0
[ 684.919709] input: A4Tech USB Full Speed as /devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2.1/1-2.1:1.1/0003:09DA:8090.0007/input/input19
[ 685.025280] hid-generic 0003:09DA:8090.0007: input,hiddev0,hidraw2: USB HID v1.11 Keyboard [A4Tech USB Full Speed] on usb-0000:00:12.2-2.1/input1

[ghallberg (ghallberg-linux-kernel-bugs)]

Is there anything one can do to get some attention to this bug? Even with disabling access to the /dev nodes, the mere presence of these bad "joysticks" causes havoc with other gamepads (at least the XBOX360 wireless ones).

[alexhultman (alexhultman-linux-kernel-bugs)]

The Cooler Master Mizar mouse is facing the same issues. Here is a link to the Valve bug report:

https://github.com/ValveSoftware/steam-for-linux/issues/3943

This is still an issue in Linux 4.2.3.

[killertofu (killertofu-linux-kernel-bugs)]

For those inclined to work on kernel code, the following is a good starting point to understanding why current devices are detected as joysticks:

 * [1] drivers/input/joydev.c:joydev_ids[]
 * [2] drivers/input/joydev.c:joydev_match()
 * [3] drivers/input/joydev.c:joydev_dev_is_absolute_mouse()

Looking at these three, it appears a joystick device will be created for input devices which have any of the following events...

 * ABS_X
 * ABS_WHEEL
 * ABS_THROTTLE
 * BTN_JOYSTICK
 * BTN_GAMEPAD
 * BTN_TRIGGER_HAPPY

... *unless* one of the following is also present (or the device appears to be a an "absolute mouse")

 * BTN_TOUCH
 * BTN_DIGI (aka BTN_TOOL_PEN)

(You can use a tool like "evemu-record" to determine the events that are sent from specific /dev/input/event* devices)

Possible solutions would be to improve the the filtering by adding additional checks that filter out the problem devices without preventing legitimate joysticks from appearing; altering the input/HID drivers that add these events if some events are added incorrectly; or adding a blacklist table to joydev.c that prevents the driver from matching devices with specific IDs.

[1]: http://lxr.free-electrons.com/source/drivers/input/joydev.c#L942
[2]: http://lxr.free-electrons.com/source/drivers/input/joydev.c#L798
[3]: http://lxr.free-electrons.com/source/drivers/input/joydev.c#L740

[Paulo Villi (paulovilli)]

Bug happens 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 Steam version of Doom & Destiny it really treats the transceiver as a joystick and registers a constant "directional up" from it, making the game unplayable.

On Steam version of The Banner Saga it works as keyboard but at the same time when I try using volume up and volume down it detects these as a gamepad input and starts the built-in gamepad setup in mid-game.

[denilsonsa (denilsonsa-linux-kernel-bugs)]

Is this bug a duplicate of bug 37982?
Is it fixed by this commit?
https://web.git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git/commit/?id=1989dada7ce07848196991c9ebf25ff9c5f14d4e

See also: https://github.com/denilsonsa/udev-joystick-blacklist/issues/20

(Personally, I cannot test, I don't have that piece of hardware anymore.)

[netbox253 (netbox253-linux-kernel-bugs)]

(In reply to Denilson Figueiredo de Sá from comment #23)
> Is this bug a duplicate of bug 37982?
> Is it fixed by this commit?
> https://web.git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git/commit/
> ?id=1989dada7ce07848196991c9ebf25ff9c5f14d4e

Hi,

I had completely forgotten this bug. I still have MS Wireless Keyboard+Mouse, so I can test.

Today, I'm using the gentoo distribution kernel : gentoo-kernel-bin-6.1.129

With this kernel, the problem is gone. You can see output of /proc/bus/input/devices :
> $ grep -A 4 'Microsoft Wireless' /proc/bus/input/devices
> N: Name="Microsoft Microsoft Wireless Optical Desktop® 2.10"
> P: Phys=usb-0000:00:1a.0-1.6/input0
> S:
> Sysfs=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/0003:045E:009D.0002/input/input5
> U: Uniq=
> H: Handlers=kbd leds event2
> --
> N: Name="Microsoft Microsoft Wireless Optical Desktop® 2.10"
> P: Phys=usb-0000:00:1a.0-1.6/input1
> S:
> Sysfs=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.1/0003:045E:009D.0003/input/input6
> U: Uniq=
> H: Handlers=kbd mouse0 event3

To make test for this bug, I rebuilt the exact same kernel with this patch reversed.
When rebooting on it, the problem reappeared :
> $ grep -A 4 'Microsoft Wireless' /proc/bus/input/devices
> N: Name="Microsoft Microsoft Wireless Optical Desktop® 2.10"
> P: Phys=usb-0000:00:1a.0-1.6/input0
> S:
> Sysfs=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/0003:045E:009D.0002/input/input5
> U: Uniq=
> H: Handlers=kbd leds event2
> --
> N: Name="Microsoft Microsoft Wireless Optical Desktop® 2.10"
> P: Phys=usb-0000:00:1a.0-1.6/input1
> S:
> Sysfs=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.1/0003:045E:009D.0003/input/input6
> U: Uniq=
> H: Handlers=kbd mouse0 event3 js0

So, I can say that this patch fixed the problem for me.

[belegdol (belegdol-linux-kernel-bugs)]

I no longer have the device so I cannot test this anymore.