Klaus Zipfel

What does ``sudo /usr/lib/udev/leetmouse_bind "1-2:1.1"`` ``sudo /usr/lib/udev/leetmouse_bind "leetmouse" "1-2:1.1"`` print out? That is exactly what the UDev rules would call. It checks, if the driver is present and if not,...

Error from my side. The command should have been this (fixed in original post): ``sudo /usr/lib/udev/leetmouse_bind "leetmouse" "1-2:1.1"``

I really don't get the "No such device" error :/

I have another suspicion about the USB address being not ok. Does 1-2:1.0 work? And what is the output of ``lsusb -t``?

If this does not work, I might give this a try with real hardware in about 2 weeks: I just ordered a $12 ATMega32u4 Development board, similar to the one...

According to your ``lsusb -t``output, 1-2:1.1 seems to be the right device, since it is bound to usbhid already. My guess of 1-2:1.0 was a dead end. It also seems...

I agree. Only the UDEv rules were related to QMK. The "no such device" is related to something else though.

Can you, one more time, send me a fresh ``lsusb -t`` right after you booted up your system? And how does ``ls -l /sys/bus/usb/devices/1-2:1.1/driver`` and ``ls -l /sys/bus/usb/drivers/usbhid/`` look like?...

This at least confirms my suspicion, that the both subdevices of the mouse (1-2:1.0 and 1-2:1.1) are both handled via usbhid. Generally, there is nothing that speaks against binding these...

Thank you. I will take a look at it. Sounds reasonable to me TBH. IIRC, the code has been taken from the original repo, that tried to mimic quake-like acceleration....