How can I know which of the /dev/input/eventX (X=0..7) have the Linux input stream?

LinuxEventsInput

Linux Problem Overview


I am trying to capture linux keyboard/mouse input, and I am reading events from like /dev/input/event2. But it seems the input are sometimes directed to /dev/input/event2, sometimes to /dev/input/event3. I wonder if there is a place I can find out which of the stream has the input?

Linux Solutions


Solution 1 - Linux

Just stumbled across this -- rather late in the day.

You can find out the names and other attributes of different devices using:

cat /proc/bus/input/devices

Solution 2 - Linux

Using sudo evtest is very helpful. It will list all your input devices by name and corresponding event number. Then you can enter device event number of your interest and monitor its events.

Solution 3 - Linux

To find out, go to /dev/input/by-id or /dev/input/by-path and do a ls -l to find out which symlink points to which event<*>.

Also, I thought it would be helpful for all those who come across this page to find this helpful [link][1] to some code which captures keyboard events.

[1]: http://www.thelinuxdaily.com/2010/05/grab-raw-keyboard-input-from-event-device-node-devinputevent/ "link"

Solution 4 - Linux

Run this in Terminal, it will work just fine:

cat /proc/bus/input/devices | awk '/keyboard/{for(a=0;a>=0;a++){getline;{if(/kbd/==1){ print 
$NF;exit 0;}}}}'

Source

Solution 5 - Linux

I know it's a little late to reply but I hope this is helpful for friends.

“mice” contains mouse input data, but to find the file related to the keyboards we need to check the files in folder “by-path”, keyboards file names end with “event-kbd”. We need to find the links to the keyboards, and then we can find the keyboards event file. The following commands can do this automatically for us:

kbdEvents=($(ls /dev/input/by-path | grep "event-kbd"))     
for forCounter in "${kbdEvents[@]}"
do
    eventFile=$(readlink --canonicalize "/dev/input/by-path/${forCounter}")     
    # do anything ...
done

This code is part of the code for the break time on my personal website : mazKnez.com

Solution 6 - Linux

Following the others hints and some trial and error as I ain't a bash wizard, this is how I am using to get the inputXX of my bluetooth controller, to use with xboxdrv tool. Any other case that uses the /dev/input/eventXX and that shows up in cat /proc/bus/input/devices will also work.

#!/bin/bash
event="`sudo cat /proc/bus/input/devices | grep -Poz '("STK-7007F1"[\s\S]+?)\Kevent\d+'`"
echo $event #event26, for example

You may use other commands instead of echo. The "STK-7007FI" is how my controller is named when running cat /proc/bus/input/devices. The script will throw a warning regarding a null char or something for some reason beyond my linux commands knowledge, but it works fine even with it.

The -Poz flag in grep is to use multiline regex. The \K is a working alternative for lookbehind. There may be better ways to do it, but that's what I came up with.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionJustin ZhangView Question on Stackoverflow
Solution 1 - LinuxdajamesView Answer on Stackoverflow
Solution 2 - Linuxmadhat1View Answer on Stackoverflow
Solution 3 - LinuxDeveshView Answer on Stackoverflow
Solution 4 - LinuxCyber-SurferView Answer on Stackoverflow
Solution 5 - LinuxmazKnezView Answer on Stackoverflow
Solution 6 - LinuxHenrique BrunoView Answer on Stackoverflow