Installer Steam
connexion
|
langue
简体中文 (chinois simplifié)
繁體中文 (chinois traditionnel)
日本語 (japonais)
한국어 (coréen)
ไทย (thaï)
Български (bulgare)
Čeština (tchèque)
Dansk (danois)
Deutsch (allemand)
English (anglais)
Español - España (espagnol castillan)
Español - Latinoamérica (espagnol d'Amérique latine)
Ελληνικά (grec)
Italiano (italien)
Bahasa Indonesia (indonésien)
Magyar (hongrois)
Nederlands (néerlandais)
Norsk (norvégien)
Polski (polonais)
Português (portugais du Portugal)
Português - Brasil (portugais du Brésil)
Română (roumain)
Русский (russe)
Suomi (finnois)
Svenska (suédois)
Türkçe (turc)
Tiếng Việt (vietnamien)
Українська (ukrainien)
Signaler un problème de traduction
Linux xinput detect my mouse wrong.
if I run:
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ A4TECH USB Device id=11 [slave pointer (2)]
⎜ ↳ A4TECH USB Device id=10 [slave pointer (2)]
I can disable it with:
NOW, I can use keyboard for moving in the game.
I added this line in /etc/X11/Xsession.d/40x11-common_xsessionrc
- change applied on startup
When I use your code line to disable the mouse, can't use fire... well, can't use mouse.
There is a way to disable only the advance options of the a4tech mouse?
Thanks
In my case, Device ID 10 was the "evil" device. Device ID 11 was the mouse itself.
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ A4TECH USB Device id=9 [slave pointer (2)]
⎜ ↳ A4TECH USB Device id=10 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Power Button id=7 [slave keyboard (3)]
↳ Logitech Logitech Speaker id=8 [slave keyboard (3)]
↳ Logitech USB Keyboard id=11 [slave keyboard (3)]
↳ Logitech USB Keyboard id=12 [slave keyboard (3)]
I tried with 10 and 9 with same result
worked for me. but needs to be done after every reboot
/etc/udev/rules.d/65-joystick.rules
It runs a script /usr/bin/_remove_js0
cause manualy evoking /usr/bin/_remove_js0 works.
I have the same problem but with different device maker
use the command to list all devices configured:
then find the one with "js0" string in my case was:
you will notice a string called "event#" which in my case is "event17" this string locate where the device is being processed
my output was:
with this you have all the information that you need, just create a udev rule whatever name you want preceded by number+dash+rulename.rules in "/etc/udev/rules.d/" with this command:
my config is:
SUBSYSTEM=="input", ATTRS{name}=="*ELECOM*", ATTRS{phys}=="*/input2", RUN+="/usr/bin/rm /dev/input/js0"
named as 52-elecom.rules
I hope this help you, and sorry for my english I'm brazilian.
https://wiki.archlinux.org/index.php/Udev#Writing_udev_rules