You are not logged in.
Hello,
My logictech joystick moves the cursor. For most, this means they have xf86-input-joystick installed (a la)
https://wiki.archlinux.org/index.php/joystick
but I do not have that package installed. Nor do I have any of the files that come with that package. I've played with a number of different input devices over the years that may fool with the cursor (apple trackpad, ati remote, xbox controller), but I'm pretty sure I've uninstalled everything (for example, the joystick package was installed at one time). The same joystick works properly on another arch install (on a different computer). Is there a way I can trace what's going on? Can I find out, for example, which kernel module is sending mouse events to X? I've looked at DMESG and which kernal modules get loaded when I plug it in, but I can't seem to detect any differences between the computer that works and the one that doesn't.
I'm trying to play Kerbal space program, and the joystick does send the appropriate signals, but in addition it moves the cursor.
thanks
Last edited by benslice (2014-08-08 17:14:26)
Offline
What Desktop Environment / Window Manager are you using?
Are you using Compiz?
Edit: Oh, Welcome to Arch Linux ![]()
Last edited by ewaller (2014-08-08 04:45:40)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
I've been using arch for years now, but I'm new to the forums, thanks for the reply!
On my laptop (which works) I'm running gdm/gnome-shell, and on my desktop (with the problem), I'm running slim/fluxbox.
When I switch the desktop to slim/gnome-shell however, I see the same broken behavior.
Oh, and BTW, the joystick is a Logitech Extremem 3d Pro.
Offline
Check /var/log/Xorg.0.log maybe.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
Check /var/log/Xorg.0.log maybe.
That log might be in ~/.local/share/org if you are running a rootless Xorg.
But do look at that log and see if it is processing the event node for the joystick as a mouse. If it is, we can fix that ![]()
If you like, post the log here, but be sure to use code tags. It is pretty big. Even better, use pastebin.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Yes, here is the output of the X log when I plug the joystick in. On the other (working) machine, there is NO output to the log when I plug it in.
Are evdev and XINPUT doing different things here, or are they tied together?
Also, the "Applying InputClass "trackball"" seems strange to me. It may be hitting an xorg.conf file I'm using for my trackball (second insert below), but I'm using a very specific identifier for the trackball so I would think it that it shouldn't match the joystick.
Xorg log
[ 1104.561] (II) config/udev: Adding input device Logitech Logitech Extreme 3D (/dev/input/event17)
[ 1104.561] (**) Logitech Logitech Extreme 3D: Applying InputClass "trackball"
[ 1104.561] (II) Using input driver 'evdev' for 'Logitech Logitech Extreme 3D'
[ 1104.561] (**) Logitech Logitech Extreme 3D: always reports core events
[ 1104.561] (**) evdev: Logitech Logitech Extreme 3D: Device: "/dev/input/event17"
[ 1104.562] (--) evdev: Logitech Logitech Extreme 3D: Vendor 0x46d Product 0xc215
[ 1104.562] (--) evdev: Logitech Logitech Extreme 3D: Found absolute axes
[ 1104.562] (--) evdev: Logitech Logitech Extreme 3D: Found x and y absolute axes
[ 1104.562] (II) evdev: Logitech Logitech Extreme 3D: Forcing relative x/y axes to exist.
[ 1104.562] (II) evdev: Logitech Logitech Extreme 3D: Configuring as mouse
[ 1104.562] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:12.2/usb1/1-5/1-5.1/1-5.1:1.0/0003:046D:C215.0006/input/input21/event17"
[ 1104.562] (II) XINPUT: Adding extended input device "Logitech Logitech Extreme 3D" (type: MOUSE, id 10)
[ 1104.562] (II) evdev: Logitech Logitech Extreme 3D: initialized for absolute axes.
[ 1104.562] (**) Logitech Logitech Extreme 3D: (accel) keeping acceleration scheme 1
[ 1104.562] (**) Logitech Logitech Extreme 3D: (accel) acceleration profile 0
[ 1104.562] (**) Logitech Logitech Extreme 3D: (accel) acceleration factor: 2.000
[ 1104.562] (**) Logitech Logitech Extreme 3D: (accel) acceleration threshold: 4
[ 1104.562] (II) config/udev: Adding input device Logitech Logitech Extreme 3D (/dev/input/js0)
[ 1104.562] (**) Logitech Logitech Extreme 3D: Applying InputClass "trackball"
[ 1104.562] (II) Using input driver 'evdev' for 'Logitech Logitech Extreme 3D'
[ 1104.562] (**) Logitech Logitech Extreme 3D: always reports core events
[ 1104.562] (**) evdev: Logitech Logitech Extreme 3D: Device: "/dev/input/js0"
[ 1104.562] (EE) evdev: Logitech Logitech Extreme 3D: Unable to query fd: Invalid argument
[ 1104.611] (EE) PreInit returned 2 for "Logitech Logitech Extreme 3D"
[ 1104.611] (II) UnloadModule: "evdev"xorg.conf
Section "InputClass"
Option "MatchDevicePath" "/dev/input/by-id/usb-Kensington_USB_PS2_Expert_Mouse-event-mouse"
Identifier "trackball"
Driver "evdev"
Option "Buttons" "10"
Option "EmulateWheel" "on"
Option "EmulateWheelButton" "8"
Option "ZAxisMapping" "4 5"
EndSectionOffline
Ok, I think I've actually fixed it. I was under the impression that specifying an exact MatchDevicePath would mean my trackball config would apply only to my trackball. But it seems that the rules you specify are "sufficient" but not "necessary". So, while my trackball does match that rule, so might a bunch of other junk. (like my joystick) This is very useful, but it seems silly that you can't supply exact matching rules for a single custom device. I'd be interested in how to do that if anybody knows. Maybe you have to do that deeper down in udev or evdev.
I fixed the problem by adding a joystick catchall as a final rule and set the Ignore option so that Xorg doesn't touch it (or rather it un-touches it after loading the wrong rule). I modeled the section on the catchalls in /etc/X11/xorg.conf.d/10-evdev
My trackball rule is in /etc/X11/xorg.conf.d/40-kensington.conf
So I put the following in /etc/X11/xorg.conf/50-joystick.conf
Section "InputClass"
Identifier "evdev joystick catchall"
MatchIsJoystick "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
Option "Ignore" "on"
EndSectionThanks for the help!
Last edited by benslice (2014-08-08 17:11:43)
Offline