How to debug the input from an input - tool (/ dev/input/event *)
I have a IR receiver that is making use of the imon - vehicle driver and also I would love to get it collaborating with the kernel. Now half of the keys on the remote (image) functions, yet a very important think like the numerical keys does not!
The unusual think is that the kernel keymap component (rc - imon - pad) appears to be proper yet it appears that it is not actually made use of given that excatly the very same keys are functioning without that component.
It appears that the rc - imon - pad component constantly obtains filled when I load imon, and afterwards I believe that the keycodes are cached so it does not make a distinction if I unload rc - imon - pad
Now I am shed, if I do
cat /dev/input/event5 or
ir-keytable -t there is information whatever key I push, so the vehicle driver signs up the switches yet it simply appears that they are converted to the incorrect keycodes.
My bits is an ubuntu supply kernel from Natty (Linux xbmc 2.6.37 - 11 - common # 25 - Ubuntu SMP Tue Dec 21 23: 42 :56 UTC 2010 x86_64 GNU/Linux)
I have the very same remote and also I have it sending out proper keycodes to my 2.6.38 - gentoo - r3 kernel. I did not compile keycodes as a component, due to the fact that they possibly have not had time to make it feasible to select specific keymaps yet. It is all or absolutely nothing and also I do not such as a billions pointless components littering me. Rather I'm allowing v4l - utils manage it with udev.
Number of points I found out :
- Check result of ir - keytable - r, it needs to detail all the keycodes applicable to your remote.
- Load the keytable by hand : ir - keytable - c - w bleh/keymaps/imon _ pad, after which ir - keytable - r need to offer you the table back
- You could in fact have a damaged receiver, you state absolutely nothing concerning background. I bear in mind seeing at the very least one message on lirc-list where individual claimed sending out the instance back and also obtaining a new one addressed his concerns.
Allow us recognize just how it went.
You might find valuable
xinput list and also
xinput test <device>.
As an example,
$ xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Sleep Button id=8 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=9 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)]
and also I can check my key-board (
xinput test 10) or touchpad (
xinput test 11, or perhaps
xinput test "SynPS/2 Synaptics TouchPad" ) for all sort of input occasions, and also they get rather published to gaming console, and also parameters get removed and also published also.
This will not address your trouble, yet at the very least will certainly aid a little bit by decoding the mess which as an example
cat /dev/input/event1 generates.