-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Here is what solved for me #31
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi!
I also had this ghost joystick problem... Usb device 045e:0750. Then I started to search for a solution.
First I was looking for what is causing troubles...
My usb keyboard have 2 interfaces: First one is a normal keyboard and second one is used only for multimedia keys. I think others keyboards like internet keyboards works the same way.
The problem is: The second interface is a complete joystick + keyboard interface. So it is detected as a joystick sending 0 to both X and Y absolute axes (ghost joystick).
But if I disable completely second interface... Then multimedia keys will stop working. It is a bad idea.
Tried this:
What I did then?
I want both /dev/input/eventXX from keyboard working, but I don't want joydev to atach to second /dev/input/eventXX and create /dev/input/js0.
So I just remove /dev/input/js0 after creation.
I updated your eudev rules to this one:
KERNEL=="js[0-9]*", SUBSYSTEM=="input", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="0750", RUN+="/bin/rm $env{DEVNAME}"
This way I still have both keyboard interfaces working and just don't have joystick.
I think the others devices from the list can be updated like this also.
The text was updated successfully, but these errors were encountered: