-
-
Notifications
You must be signed in to change notification settings - Fork 49
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
Which raw device #1
Comments
Hmm, good question, I didn't notice that. I've just used the first one I find. Do you have multiple logitech usb receivers plugged in? |
Nope, just one. It creates three hidraw devices. From dmesg: [ 4.023771] generic-usb 0003:046D:C52B.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:1d.0-1.6.4/input0 So, presumably the first one (hidraw0) is for keyboard, the second one (hidraw1) for mice, and the third one for other. |
I think it doesn't matter, just try them all until you get the "Switch your device on to pair it." message. |
I had one entry for each physical unifying receiver and one each for both my keyboard and mouse (4). When I pulled the unifying receiver the mouse had been paired with both of those entries disappeared. cat'ting proc gave me just the one unifying receiver and keyboard entries (2) at that point. I expect other peoples' mileage might vary though. Worked like a charm the first time for me. |
You can use
In this case, |
A single unifying receiver can create multiple raw hid devices:
grep '^HID_NAME=Logitech USB Receiver' /sys/class/hidraw/hidraw*/device/uevent
/sys/class/hidraw/hidraw0/device/uevent:HID_NAME=Logitech USB Receiver
/sys/class/hidraw/hidraw1/device/uevent:HID_NAME=Logitech USB Receiver
/sys/class/hidraw/hidraw2/device/uevent:HID_NAME=Logitech USB Receiver
The documentation should state whether the command needs to be run against each of these or not.
The text was updated successfully, but these errors were encountered: