-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
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
A lenovo usb keyboard with a new HID_NAME #31
Comments
Addition: seems only tp-compact-usb-keyboard.c works. |
Okay, makes sense that only tp-compact-usb-keyboard works, given it's the same with the Lenovo USB keyboard I have. You could copy the top of the script into a new script that wraps around What hidraw device are you sending commands to, hidraw2 or hidraw3 (assuming you haven't unplugged anything since the above dmesg)? I'm guessing (well, more hoping) that it's the latter device, hidraw3, that works. Do all the special Fn-Key functions work properly if you use Does the keyboard have a pointing device of some kind too? It's hard to find out any information on it, best I can do is guess that it's the keyboard pictured here: http://www.newegg.com/Product/Product.aspx?Item=N82E16883108568 |
Yeah I already done that part for udev to call tp-compact-usb-keyboard. Either hidraw2 or hidraw3 works if I unplugged then plugged it back. It works even only one single hidraw device was given to tp-compact-usb-keyboard. This keyboard have no pointing device. It was the keyboard shipped with Lenovo server and PC sold in China. Here is some photo: Here is the result of xev | grep --line-buffered -A6 KeyRelease after running tp-compact-usb-keyboard /dev/hidraw3:
|
Hi, I found out this utility even works with lenovo USB keyboard LXH-JME2209U. My Fn lock is successfully unlocked! Nice work!
However, its HID_NAME was "Lenovo Lenovo USB Keyboard". Maybe you could handle it too in the script.
dmesg:
lsusb -v:
The text was updated successfully, but these errors were encountered: