Klaus Zipfel

Judging on the code changes, this looks straight forward so far.

This might get resolved, once #14 is implemented.

When /sys/module/leetmouse/parameters/ does not exist, then the kernel module is not loaded. Try uninstalling and reinstalling the module.

It all sounds pretty weird, that you need to manually load the module. In principle, that is the job of udev. Can you please check your udev logs? It looks...

Try also unplug/replug your mouse. What is shown in dmesg and udevadm monitor output then? Can you post an of your mouse as mentioned in this debug readme https://github.com/systemofapwne/leetmouse/blob/master/debug/Readme.org? Also:...

Ok, the issue clearly is that your trackball identifies itself as a "keyboard" instead of as a mouse, so the udev rule ignores it. There is basically one thing that...

Can you please replace the contents of /usr/lib/udev/rules.d/99-leetmouse.rules with the following content ``` ACTION=="remove", GOTO="leetmouse_end" SUBSYSTEMS=="usb|input|hid", ATTRS{bInterfaceClass}=="03", ATTRS{bInterfaceSubClass}=="01", ATTRS{bInterfaceProtocol}=="02", RUN+="leetmouse_bind leetmouse $kernel" #Quirk for PloopyCo devices using QMK Firmware (https://github.com/systemofapwne/leetmouse/issues/20#issuecomment-1237448456)...

So even ``modprobe leetmouse`` + ``echo -n "1-2:1.1" > /sys/bus/usb/drivers/leetmouse/bind`` did not work anymore?

Have you made sure, that you execute both commands as root?

Does /sys/bus/usb/drivers/leetmouse/bind even exist? (I guess so. It should after modprobing) Which shell are you using? Did you also try bash?