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.
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> hter2:~ $ cat /etc/udev/ rules.d/ 99-false- joystick- microsoft. rules =="Microsoft Wired Keyboard 600", ATTRS{phys} =="*/input1" , RUN{program} +="/bin/ rm %p", RUN{program} +="/bin/ rm /dev/input/%k"
idaho@streetfig
SUBSYSTEM=="input", ATTRS{name}
</pre>
This deletes every /dev entry for the second device of the keyboard (input1), including /dev/input/js0 and /dev/input/event3.