We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I use a Thinkpad compact 2 Bluetooth keyboard.
I added a udev rule:
#ThinkPad TrackPoint Keyboard I & II USB SUBSYSTEM=="hid", \ DRIVER=="lenovo", \ ATTRS{idVendor}=="17ef", ATTRS{idProduct}=="6047|60ee", \ ATTR{fn_lock}="0" #ThinkPad TrackPoint Keyboard I & II Bluetooth SUBSYSTEM=="input", \ ATTRS{id/vendor}=="17ef", ATTRS{id/product}=="6048|60e1", \ TEST=="/sys/$devpath/device/fn_lock", \ RUN+="/bin/sh -c 'echo 0 > \"/sys/$devpath/device/fn_lock\"'"
in a file called /etc/udev/rules.d/99-thinkpad-trackpoint-disable-fn-lock.rules
/etc/udev/rules.d/99-thinkpad-trackpoint-disable-fn-lock.rules
I also did
sudo su udevadm control --reload-rules && udevadm trigger
but I still get the error:
./tp-compact-keyboard --fn-lock-enable No keyboard found!
the keyboard is working super fine, just the FN Lock is not working
uname -r 6.5.0-15-generic
I'm on Ubuntu 22.04 LTS version
The text was updated successfully, but these errors were encountered:
Mine too not working since like a month as it's always on and cannot be turned off, what gives? Did you figure out a solution?
Sorry, something went wrong.
unfortunately not. I was not able to get it running at all yet.
did you got it running ?
No branches or pull requests
I use a Thinkpad compact 2 Bluetooth keyboard.
I added a udev rule:
in a file called
/etc/udev/rules.d/99-thinkpad-trackpoint-disable-fn-lock.rules
I also did
sudo su udevadm control --reload-rules && udevadm trigger
but I still get the error:
the keyboard is working super fine, just the FN Lock is not working
I'm on Ubuntu 22.04 LTS version
The text was updated successfully, but these errors were encountered: