Skip to content
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

Open
arth1 opened this issue Jun 6, 2012 · 5 comments
Open

Which raw device #1

arth1 opened this issue Jun 6, 2012 · 5 comments

Comments

@arth1
Copy link

arth1 commented Jun 6, 2012

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.

@treeder
Copy link
Owner

treeder commented Jun 6, 2012

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?

@arth1
Copy link
Author

arth1 commented Jun 6, 2012

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
[ 4.025906] generic-usb 0003:046D:C52B.0002: input,hiddev96,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:1d.0-1.6.4/input1
[ 4.028485] generic-usb 0003:046D:C52B.0003: hiddev97,hidraw2: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:1d.0-1.6.4/input2

So, presumably the first one (hidraw0) is for keyboard, the second one (hidraw1) for mice, and the third one for other.

@ghost
Copy link

ghost commented Jul 9, 2012

I think it doesn't matter, just try them all until you get the "Switch your device on to pair it." message.

@nam20485
Copy link

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.

@Lekensteyn
Copy link

You can use ls -ld /sys/class/hidraw/hidraw*/device/driver to discover the device you need. Trimmed example:

$ ls -ld /sys/class/hidraw/hidraw*/device/driver
/sys/class/hidraw/hidraw0/device/driver -> ../../../../../../../../bus/hid/drivers/logitech-djreceiver
/sys/class/hidraw/hidraw1/device/driver -> ../../../../../../../../../bus/hid/drivers/logitech-djdevice

In this case, hidraw0 is the device that you are looking for. This is used in the ltunify tool.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants