Problem: Trouble getting lircd to work as expected, also is something else handling IR input?
|
5th Jun, 2020, 10:42 PM
(This post was last modified: 5th Jun, 2020 10:53 PM by Nachteule.)
Post: #17
|
|||
|
|||
RE: Trouble getting lircd to work as expected, also is something else handling IR
Something is wrong, kernel sends 0 as keycode, that is definitely an invalid code
Code: 2020-06-04 19:25:24.207 T:2983550240 DEBUG: Keyboard: scancode: 0x00, sym: 0x0000, unicode: 0x0000, modifier: 0x0 So, either the the ir protocol is wrong or the used keytable or the rc sends garbage, no idea since you're always so sparing with information, I can only guess So, please install evtest package and run it: Terminal root@kmxbilr2 /lib/udev/rc_keymaps # sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0: HID 05a4:9881 /dev/input/event1: HID 05a4:9881 Mouse /dev/input/event2: HID 05a4:9881 Consumer Control /dev/input/event3: HID 05a4:9881 System Control /dev/input/event4: Logitech USB Receiver /dev/input/event5: Logitech USB Receiver Consumer Control /dev/input/event6: Logitech USB Receiver System Control /dev/input/event7: Dell USB Keyboard /dev/input/event8: gpio_ir_recv Select the device event number [0-8]: 2 Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x5a4 product 0x9881 version 0x110 Input device name: "HID 05a4:9881 Consumer Control" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 113 (KEY_MUTE) Event code 114 (KEY_VOLUMEDOWN) Event code 115 (KEY_VOLUMEUP) Event code 128 (KEY_STOP) Event code 140 (KEY_CALC) Event code 144 (KEY_FILE) Event code 155 (KEY_MAIL) Event code 156 (KEY_BOOKMARKS) Event code 158 (KEY_BACK) Event code 159 (KEY_FORWARD) Event code 163 (KEY_NEXTSONG) Event code 164 (KEY_PLAYPAUSE) Event code 165 (KEY_PREVIOUSSONG) Event code 166 (KEY_STOPCD) Event code 171 (KEY_CONFIG) Event code 172 (KEY_HOMEPAGE) Event code 173 (KEY_REFRESH) Event code 209 (KEY_BASSBOOST) Event code 217 (KEY_SEARCH) Event code 240 (KEY_UNKNOWN) Event type 4 (EV_MSC) Event code 4 (MSC_SCAN) Properties: Testing ... (interrupt to exit) Event: time 1591360694.706580, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00cd Event: time 1591360694.706580, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 1 Event: time 1591360694.706580, -------------- SYN_REPORT ------------ Event: time 1591360694.706630, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 0 Event: time 1591360694.706630, -------------- SYN_REPORT ------------ Event: time 1591360014.383399, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7004f Event: time 1591360014.383399, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 1 Event: time 1591360014.383399, -------------- SYN_REPORT ------------ Event: time 1591360014.511393, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7004f Event: time 1591360014.511393, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 0 root@kmxbilr2 /lib/udev/rc_keymaps # this is what Kodi gets: Code: Jun 5 14:44:54 kmxbilr2 2020-06-05 14:44:54.707 T:7438 DEBUG <general>: Keyboard: scancode: 0x6a, sym: 0x0113, unicode: 0x0000, modifier: 0x0 So, you can see that (EV_KEY), code 164 is the relevant information, Kodi gets scancode: 0x6a for this button (0x6a == 106) and look if every button sends an individual scan code (MSC_SCAN) and an individual key code (EV_KEY) |
|||
« Next Oldest | Next Newest »
|