- #CANNOT GET RIGH CLICK BUTTON TO WORK LOGITECH TRACKMAN FX INSTALL#
- #CANNOT GET RIGH CLICK BUTTON TO WORK LOGITECH TRACKMAN FX DRIVER#
- #CANNOT GET RIGH CLICK BUTTON TO WORK LOGITECH TRACKMAN FX CODE#
Click the red button twice (without movign the ball at the same time or in between) to activate horizontal-only scrolling.Click red button once after scrolling to go back to normal mode. Rolling the wheel up/down will now send vertical scroll events to whatever app you are using. Click the red button once (without moving the ball at the same time or pressing any buttons) to activate vertical-only scrolling.
#CANNOT GET RIGH CLICK BUTTON TO WORK LOGITECH TRACKMAN FX INSTALL#
Please note that you will need to run this on every boot to install the driver, which will also make sure it is always compiledĪgainst the kernel you are running even if it has been updated.
So especially horizontal scrolling might not be optimal. It will finally try to tweak the device settings for more optimal scrolling, but this seem to have broken lately, It will then (re)load the marblefx module, and on success dump the associated messages from dmesg.
#CANNOT GET RIGH CLICK BUTTON TO WORK LOGITECH TRACKMAN FX DRIVER#
It will also reload the usbhid driver right now if the kernel commandline change is not yet active so you can try the driver right away without booting,īut this might cause some connected keyboards/mice to re-initialize and I guess that's not optimal, so that's why it will patch the kernel commandline as well. It will try to patch your kernel commandline with a paramter to make the regular usbhid driver which normally would be activated for thisĪdapter to ignore this adapter (otherwise we cannot activate our driver for it). Make sure you have what is needed to compile kernel modules (packages like linux-headers) and optionally the xinput binary from e.g. Then I just made some logic to send scroll events instead of mouse movement events when scrolling mode has been activated. Identify whether the fourth (red) button has been pressed. I have made a few changes to detect a funny pattern of PS/2 messages sent by at least this Holtek-based adapter I have, and was able to after all the driver is newer than the mouse :)
#CANNOT GET RIGH CLICK BUTTON TO WORK LOGITECH TRACKMAN FX CODE#
The code is based on the ancient drivers/hid/usbhid/usbmouse.c because it was easy to hack for my purposes. It currently also doesn't attempt to recognize the mouse in any way so if you connect a regular mouse with this driver loaded it might not work or not work well. At the moment I'm a bit sceptic whether this will work with all adapters. If it works, open an issue and I will add it. My adapter looks very much like this one, but can't say if it has the same chip inside:ĭoes not currently work with native PS/2 and will not activate for adapters with other chips than the mentioned.įeel free to patch the usb ids at the top of the source file if you want to try with yours. To work in Linux when connecting the mouse via an active PS/2 -> USB adapter which uses chip by Holtek, USB id 04d9:1400. So this is my hacky driver to get fourth button aka the red button of a "Logitech TrackMan Marble FX" trackball mouse