Mythtv on Ubuntu 20.04 (edit: mostly ir-keytable/lirc issue)

For discussion of topics specific to MythTV on linux
nexzzt
Junior
Posts: 18
Joined: Wed Jun 18, 2014 3:58 am
Australia

Re: Mythtv on Ubuntu 20.04 (edit: mostly ir-keytable/lirc issue)

Post by nexzzt »

Ah OK, looks good to me. Moving on...
Lester_Burnham
Junior
Posts: 15
Joined: Sat Jun 14, 2014 7:50 am
Australia

Re: Mythtv on Ubuntu 20.04 (edit: mostly ir-keytable/lirc issue)

Post by Lester_Burnham »

wesnewell wrote:
Fri May 29, 2020 4:39 am
Did a fresh install of 20.04LTS and no luck with ir-keytable. While all the remote buttons work using ir-keytable -t, only a few work in apps. All 4 arrow keys and the Return key are the only ones that worked in app or CL iirc. Not sure why it doesn't work. More info here.
https://answers.launchpad.net/ubuntu/+question/690977

But no response yet. In the meantime, I've just switched to using mini wireless KB's.
Hi,

In 20.04 with ir-keytable I didn’t have to set a config file. (rc_maps.cfg) I remember years ago I needed a config as you have done, but not this time.
With mine I just had to copy the remote file from “sudo cp /lib/udev/rc_keymaps/rc6_mce.toml /etc/rc_keymaps/“ then modify the button presses to suit what key I wanted to see output. Need to reload config and restart the frontend to test from memory.
Maybe it’s something as simple as your old config is tripping it up.

Lester
wesnewell
Senior
Posts: 731
Joined: Mon Jun 23, 2014 6:54 pm
Location: Wylie TX, USA
United States of America

Re: Mythtv on Ubuntu 20.04 (edit: mostly ir-keytable/lirc issue)

Post by wesnewell »

Could be. Problem is my remote uses my own codes that I uploaded to the remote. I've added an entry for it in /lib/udev/rc_keymaps/
wes@mythfe0:~$ ls /lib/udev/rc_keymaps/my*
/lib/udev/rc_keymaps/myremotes.toml
But I'm not sure it's in the right format yet. Been busy with something else and will get back to this later.
BE/FE-Asrock AB350 Pro Ryzen 3 3200G, 6 atsc tuners. FE's-GF8200's Athlon II, Ryzen 3 2200G. Mythtv user since 2005.
Lester_Burnham
Junior
Posts: 15
Joined: Sat Jun 14, 2014 7:50 am
Australia

Re: Mythtv on Ubuntu 20.04 (edit: mostly ir-keytable/lirc issue)

Post by Lester_Burnham »

No worries.
What ever is in /etc/rc_keymaps/ is loaded by default, otherwise if you only have your remote config in /lib/udev/rc_keymaps/ you will need to tell it what to load. Which is what your config used to do.

You could try just copying your config to /etc/rc_keymaps/ and reload ir-keytable to see what happens.

My rc6_mce.toml has the likes of these codes in there. The scan code is very different to yours.
0x800f0408 = "KEY_8" #WAS KEY_NUMERIC_8
0x800f0409 = "KEY_9" #WAS KEY_NUMERIC_9
0x800f040a = "KEY_DELETE"
0x800f040b = "KEY_ENTER"
0x800f040c = "KEY_SLEEP"
0x800f040d = "KEY_M" #WAS KEY MEDIA

Good luck when you get around to it.
Lester
wesnewell
Senior
Posts: 731
Joined: Mon Jun 23, 2014 6:54 pm
Location: Wylie TX, USA
United States of America

Re: Mythtv on Ubuntu 20.04 (edit: mostly ir-keytable/lirc issue)

Post by wesnewell »

OK, finally took some time to look into this more and got it working in all apps and CL. Had to redo my rc-map file because the one from 18.04 wouldn't load properly and renamed it to *.toml. Once I did that, I had to manually load it. I also copied it to lib/udev/rc_keymaps dir and usr/lib/udev/rc_keymaps. I don't know if that's needed but... To get it to load automatically on boot, I had to make it the top entry in /etc/rc_maps.cfg.
Here's portions of that;

# Table to automatically load the rc maps for the bundled IR's provided with the
# devices supported by the linux kernel
mceusb * /etc/rc_keymaps/myremotes.toml

#driver table file
* rc-adstech-dvb-t-pci adstech_dvb_t_pci.toml

And here's the top of my map file.Note the equal signs and quotes. Also had to remove trailing comments from original.

[[protocols]]
name = "myremotes"
protocol = "nec"
variant = "nec"
[protocols.scancodes]
0x0f = "KEY_F12"
0x2b = "KEY_L"
0x29 = "KEY_T"
0x26 = "KEY_B"
0x21 = "KEY_COMMA"

Hope this gives you enough to get yours working.
BE/FE-Asrock AB350 Pro Ryzen 3 3200G, 6 atsc tuners. FE's-GF8200's Athlon II, Ryzen 3 2200G. Mythtv user since 2005.
Lester_Burnham
Junior
Posts: 15
Joined: Sat Jun 14, 2014 7:50 am
Australia

Re: Mythtv on Ubuntu 20.04 (edit: mostly ir-keytable/lirc issue)

Post by Lester_Burnham »

Hi,

I see some smart cookie on the mailing list figured out the new lirc remote and blasting setup. I was interested in the remote part and it works well. I just needed to tweak the mythtv lircrc to match some remote buttons for an mceusb. Need to look at irexec Now to launch apps.

https://www.mythtv.org/wiki/FTDI_USB_IR ... using_LIRC

I’m fine with what I have now, but it’s good to have options.
Lester
nouglywires
Junior
Posts: 20
Joined: Sun Nov 23, 2014 7:17 pm
United States of America

Re: Mythtv on Ubuntu 20.04 (edit: mostly ir-keytable/lirc issue)

Post by nouglywires »

Thanks for this thread, and thanks especially to wesnewell who got me pointed in the right direction. Here are the details of what i did to get my remote control working again with MythTV after upgrading from 18.04 to 20.04.1:
wesnewell wrote:
Wed Jun 03, 2020 7:38 pm
Had to redo my rc-map file because the one from 18.04 wouldn't load properly and renamed it to *.toml.
KEY_RETURN (the numpad Enter key) is no longer supported; I had to make that KEY_ENTER.

You must add sections for protocols and protocols.scancodes. Here's the new preamble in my /etc/rc_keymaps/rc6_mce.toml. The Debian manual page for ir-keytable lists some known protocols and variants:

Code: Select all

[[protocols]]
name = "myremotes"
protocol = "rc-6"
variant  = "rc-6-mce"
[protocols.scancodes]  
Previously, this simple format was supported:

Code: Select all

0x800f0412 KEY_PAGEUP
Now you must code

Code: Select all

0x800f0412 = "KEY_PAGEUP"
I ran "sudo ir-keytable -c -p rc-6 --write=/etc/rc_keymaps/rc6_mce.toml --sysdev=rc0" and ! my remote control worked again. (I determined the sysdev from the output of ir-keytable (no arguments - it "Found /sys/class/rc/rc0/ with: ..."). "-p" sets the protocol to rc-6, -c clears existing entries (you may not want to do this).

I have only one copy of the file - /etc/rc_keymaps/rc6_mce.toml - and the first line of /etc/rc_maps.cfg points to it:

Code: Select all

mceusb * /etc/rc_keymaps/rc6_mce.toml
I also had to ensure that this runs on every restart, so I saved the command into a script - /usr/local/bin/ir-keytable-setup.sh (root:root, 755) :

Code: Select all

#!/bin/bash
sudo ir-keytable -c -p rc-6 --write=/etc/rc_keymaps/rc6_mce.toml --sysdev=rc0
and made it a service - this goes in /etc/systemd/system/ir-keytable-setup.service (root:root, 644)

Code: Select all

[Unit]
Description=Set IR Keytable for Myth TV
After=network.service

[Service]
Type=oneshot
ExecStart=/usr/local/bin/ir-keytable-setup.sh

[Install]
WantedBy=default.target
To verify that the service works, execute sudo service ir-keytable-setup start and check the results with ir-keytable -r

Now do sudo systemctl enable ir-keytable-setup and reboot.


I hope someone finds this helpful.
User avatar
heyted
Senior
Posts: 301
Joined: Sun Jun 08, 2014 2:14 am
Location: South Florida
Contact:
United States of America

Re: Mythtv on Ubuntu 20.04 (edit: mostly ir-keytable/lirc issue)

Post by heyted »

My experience:

On my Ubuntu 20.04 Asus box with an Inteset IR receiver, setup was very easy. I just replaced the contents of /lib/udev/rc_keymaps/rc6_mce with my previous 18.04 info, edited the info to match the new toml format, added the top protocols info, and rebooted. That worked.

On my Xubuntu 20.04 Zotac box with an Inteset IR receiver, setup was not as easy. I tried placing the edited toml file in /etc/rc_keymaps/, rebooted, but that did not work. I tried editing /etc/rc_maps.cfg and rebooted, but that did not work. I used an /etc/systemd/system service file similar to that used by nouglywires. That worked.

Code: Select all

[Unit]
Description=Load rc_keymap file
After=rc-local.service systemd-user-sessions.service

[Service]
Type=oneshot
ExecStart=bash -c "ir-keytable -c -w /etc/rc_keymaps/bdrm_remote.toml"

[Install]
WantedBy=multi-user.target
Ted | My blog
instantlinux
Newcomer
Posts: 1
Joined: Fri Dec 18, 2020 3:23 am
Location: San Francisco
Contact:
United States of America

Re: Mythtv on Ubuntu 20.04 (edit: mostly ir-keytable/lirc issue)

Post by instantlinux »

After quite a bit of digging, I found this pair of bug reports in the upstream Ubuntu repository (for package v4l-utils):

- https://bugs.launchpad.net/ubuntu/+sour ... ug/1903966
- https://bugs.launchpad.net/ubuntu/+sour ... ug/1906986

The udev rule that used to work in 18.04 has to be updated. Ubuntu 20.04.1 LTS currently has v4l-utils version 1.18.0-1. If you type this:

dpkg -s v4l-utils

and see a version less than 1.20.0-2 (released 1-Dec-2020), you can workaround the issue by manually adding the file /lib/udev/rules.d/70-infrared.rules with this content:

Code: Select all

# Automatically load the proper keymaps after the Remote Controller device
# creation.  The keycode tables rules should be at /etc/rc_maps.cfg

ACTION=="add", SUBSYSTEM=="input", SUBSYSTEMS=="rc", KERNEL=="event*", ENV{.rc_sysdev}="$id", RUN+="/usr/bin/ir-keytable -a /etc/rc_maps.cfg -s $env{.rc_sysdev}"
If you have a custom keymap file, you need to put it in .toml format thus:

Code: Select all

[[protocols]]
name = "myremotes"
protocol = "rc6"
variant  = "rc6_mce"

[protocols.scancodes]  
0x800f0400 = "KEY_0"
0x800f0401 = "KEY_1"
 ...
The older formats that don't have a protocols header don't work anymore. My old keymap file had a third field on each scancode line; I had to drop the third field (keycode) and simplify to just specify scancode = "name". Because I installed MythTV a dozen years ago, the keycode names in my database are undoubtedly different from those found in a fresh install. If this is the case for you, and you have a keymap that works under 18.04, keep the names that were working for you.

Look in the directory /lib/udev/rc_keymaps for the name of the file matches your remote. Using that same file name, put your customized version into the (empty directory from the distro) /etc/rc_keymaps. It must have the suffix .toml. The udev startup rule, as corrected above, will look for your remote there in /etc before looking in /lib/udev/rc_keymaps.

By adopting this solution, the other workarounds proposed earlier in this thread (adding a /etc/rc.local or systemd unit file, plus some other suggestions I tried) aren't needed. Edit: After writing the above and verifying it on my first frontend, I found it didn't work on a second frontend. I wound up adding this file as /etc/rc.local - to run the exact same command as the one defined in udev:

Code: Select all

#!/bin/bash
/usr/bin/ir-keytable -a /etc/rc_maps.cfg 2>&1 | /usr/bin/logger -t ir-keytable-fudge
The frontends are running kernel 5.4.0-58.

None of this is well-documented anywhere, and I cannot fathom why the upstream repos ever bother to change code related to antiquated IR technology -- but I've had to overhaul this every couple years since the 2000s. Hope this explanation helps. I'm open to suggestions on how to improve upon this analysis and solution.
Last edited by Steve Goodey on Fri Dec 18, 2020 8:12 am, edited 3 times in total.
Reason: url amended as new user.
- rich braun
wesnewell
Senior
Posts: 731
Joined: Mon Jun 23, 2014 6:54 pm
Location: Wylie TX, USA
United States of America

Re: Mythtv on Ubuntu 20.04 (edit: mostly ir-keytable/lirc issue)

Post by wesnewell »

Don't know if it's mentioned here, but newer kernels have broken ir-keytable.
https://bugs.launchpad.net/ubuntu/+sour ... ug/1901089
https://bugzilla.kernel.org/show_bug.cgi?id=210755
BE/FE-Asrock AB350 Pro Ryzen 3 3200G, 6 atsc tuners. FE's-GF8200's Athlon II, Ryzen 3 2200G. Mythtv user since 2005.
User avatar
AnalogBill
Junior
Posts: 29
Joined: Fri Feb 10, 2017 2:11 am
United States of America

Re: Mythtv on Ubuntu 20.04 (edit: mostly ir-keytable/lirc issue)

Post by AnalogBill »

Thought I made all required changes, but "sudo ir-keytable -r" still shows the old format.
"sudo ir-keytable -t" doesn't recognize ANY key presses, though Myth FE responds to the arrow keys (only).
Hoping someone spots what I'm not seeing:

Code: Select all

sudo ir-keytable
Found /sys/class/rc/rc0/ with:
	Name: ITE8708 CIR transceiver
	Driver: ite-cir
	Default keymap: rc-rc6-mce
	Input device: /dev/input/event3
	LIRC device: /dev/lirc0
	Attached BPF protocols: Operation not supported
	Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon rc-mm 
	Enabled kernel protocols: lirc rc-6 
	bus: 25, vendor/product: 1283:0000, version: 0x0000
	Repeat delay = 500 ms, repeat period = 125 ms
sudo ir-keytable -c -p rc-6 --write=/etc/rc_keymaps/rc6_mce.toml --sysdev=rc0 gets me:

Code: Select all

Read rc6_mce table
Old keytable cleared
Wrote 64 keycode(s) to driver
Protocols changed to rc-6 
But no results

Code: Select all

$ sudo ir-keytable -r
scancode 0x800f0400 = KEY_NUMERIC_0 (0x200)
scancode 0x800f0401 = KEY_NUMERIC_1 (0x201)
scancode 0x800f0402 = KEY_NUMERIC_2 (0x202)
scancode 0x800f0403 = KEY_NUMERIC_3 (0x203)
I was expecting to see

Code: Select all

 cat rc6_mce.toml
[[protocols]]
name = "rc6_mce"
protocol = "rc6"
variant = "rc6_mce"
[protocols.scancodes]
0x800f0400 = "KEY_NUMERIC_0"
0x800f0401 = "KEY_NUMERIC_1"
...
0x800f040d = "KEY_MEDIA"
0x800f040e = "KEY_MUTE"
0x800f040f = "KEY_INFO"
0x800f0410 = "KEY_VOLUMEUP"
...
Ideas? Thanks!
User avatar
heyted
Senior
Posts: 301
Joined: Sun Jun 08, 2014 2:14 am
Location: South Florida
Contact:
United States of America

Re: Mythtv on Ubuntu 20.04 (edit: mostly ir-keytable/lirc issue)

Post by heyted »

Code: Select all

sudo ir-keytable -c -w /etc/rc_keymaps/rc6_mce.toml
Without rebooting,

Code: Select all

sudo ir-keytable -t
shows no output when an arrow button is pressed?
Ted | My blog
User avatar
AnalogBill
Junior
Posts: 29
Joined: Fri Feb 10, 2017 2:11 am
United States of America

Re: Mythtv on Ubuntu 20.04 (edit: mostly ir-keytable/lirc issue)

Post by AnalogBill »

that was true. Seems resolved. Getting keypress response after a cold startup. Need to change the mapping now.
dmsauer
Newcomer
Posts: 3
Joined: Sun Feb 18, 2024 5:28 am
United States of America

Re: Mythtv on Ubuntu 20.04 (edit: mostly ir-keytable/lirc issue)

Post by dmsauer »

Not Solved!!!! What is wrong with this? Why does it not "just work" like Ubuntu claims?

/etc/rc_keymaps/rc6_mce.toml has cotents:
# Generated with gen_keytables . pl from drivers/media/rc/keymaps/rc-rc6-mce.c
[[protocols]]
name = "rc6_mce"
protocol = "rc6"
variant = "rc6_mce"
[protocols.scancodes]
0x800f0400 = "KEY_NUMERIC_0"
0x800f0401 = "KEY_NUMERIC_1"
0x800f0402 = "KEY_NUMERIC_2"
0x800f0403 = "KEY_NUMERIC_3"
0x800f0404 = "KEY_NUMERIC_4"
0x800f0405 = "KEY_NUMERIC_5"
0x800f0406 = "KEY_NUMERIC_6"
0x800f0407 = "KEY_NUMERIC_7"
0x800f0408 = "KEY_NUMERIC_8"
0x800f0409 = "KEY_NUMERIC_9"
0x800f040a = "KEY_DELETE"
0x800f040b = "KEY_ENTER"
0x800f040c = "KEY_SLEEP"
0x800f040d = "KEY_MEDIA"
0x800f040e = "KEY_MUTE"
0x800f040f = "KEY_INFO"
0x800f0410 = "KEY_VOLUMEUP"
0x800f0411 = "KEY_VOLUMEDOWN"
0x800f0412 = "KEY_CHANNELUP"
0x800f0413 = "KEY_CHANNELDOWN"
0x800f0414 = "KEY_FASTFORWARD"
0x800f0415 = "KEY_REWIND"
0x800f0416 = "KEY_PLAY"
0x800f0417 = "KEY_RECORD"
0x800f0418 = "KEY_PAUSE"
0x800f0419 = "KEY_STOP"
0x800f041a = "KEY_NEXT"
0x800f041b = "KEY_PREVIOUS"
0x800f041c = "KEY_NUMERIC_POUND"
0x800f041d = "KEY_NUMERIC_STAR"
0x800f041e = "KEY_UP"
0x800f041f = "KEY_DOWN"
0x800f0420 = "KEY_LEFT"
0x800f0421 = "KEY_RIGHT"
0x800f0422 = "KEY_OK"
0x800f0423 = "KEY_EXIT"
0x800f0424 = "KEY_DVD"
0x800f0425 = "KEY_TUNER"
0x800f0426 = "KEY_EPG"
0x800f0427 = "KEY_ZOOM"
0x800f0432 = "KEY_MODE"
0x800f0433 = "KEY_PRESENTATION"
0x800f0434 = "KEY_EJECTCD"
0x800f043a = "KEY_BRIGHTNESSUP"
0x800f0446 = "KEY_TV"
0x800f0447 = "KEY_AUDIO"
0x800f0448 = "KEY_PVR"
0x800f0449 = "KEY_CAMERA"
0x800f044a = "KEY_VIDEO"
0x800f044c = "KEY_LANGUAGE"
0x800f044d = "KEY_TITLE"
0x800f044e = "KEY_PRINT"
0x800f0450 = "KEY_RADIO"
0x800f045a = "KEY_SUBTITLE"
0x800f045b = "KEY_RED"
0x800f045c = "KEY_GREEN"
0x800f045d = "KEY_YELLOW"
0x800f045e = "KEY_BLUE"
0x800f0465 = "KEY_POWER2"
0x800f0469 = "KEY_MESSENGER"
0x800f046e = "KEY_PLAYPAUSE"
0x800f046f = "KEY_PLAYER"
0x800f0480 = "KEY_BRIGHTNESSDOWN"
0x800f0481 = "KEY_PLAYPAUSE"
....
loading the config file:
mythtv@tivofront:/etc/rc_keymaps$ sudo ir-keytable -c -w rc6_mce.toml
Read rc6_mce table
Old keytable cleared
Wrote 64 keycode(s) to driver
Protocols changed to rc-6

then running a test:
mythtv@tivofront:/etc/rc_keymaps$ sudo ir-keytable -t
Testing events. Please, press CTRL-C to abort.
299.153492: lirc protocol(rc6_mce): scancode = 0x800f0422 toggle=1
299.153520: event type EV_MSC(0x04): scancode = 0x800f0422
299.153520: event type EV_KEY(0x01) key_down: KEY_OK(0x0160)
299.153520: event type EV_SYN(0x00).
299.288173: event type EV_KEY(0x01) key_up: KEY_OK(0x0160)
299.288173: event type EV_SYN(0x00).

Why does the test return a code of 0x0160 for the KEY_OK when it is clearly defined as 0x800f0422 = "KEY_OK" in the config file? The config file has no such hex code above FF. This seems to be the problem, but I can't figure out how ir-keytable gets some other config file to assign button presses to. Does anyone know where else it might be getting this info?

/etc/rc_maps.cfg:
#
# Keymaps table
#
# This table creates an association between a keycode file and a kernel
# driver. It can be used to automatically override a keycode definition.
#
# Although not yet tested, it is mented to be added at udev.
#
# To use, you just need to run:
# ./ir-keytable -a
#
# Or, if the remote is not the first device:
# ./ir-keytable -a -s rc1 # for RC at rc1
#

# Format:
# driver - name of the driver provided via uevent - use * for any driver
# table - RC keymap table, provided via uevent - use * for any table
# file - file name. If directory is not specified, it will default to
# /etc/rc_keymaps.
# For example:
# driver table file
# cx8800 * ./keycodes/rc5_hauppauge_new.toml
# * rc-avermedia-m135a-rm-jx ./keycodes/kworld_315u.toml
# saa7134 rc-avermedia-m135a-rm-jx ./keycodes/keycodes/nec_terratec_cinergy_xs.toml
# em28xx * ./keycodes/kworld_315u.toml
# * * ./keycodes/rc5_hauppauge_new.toml

# Table to automatically load the rc maps for the bundled IR's provided with the
# devices supported by the linux kernel

#driver table file
* rc-adstech-dvb-t-pci adstech_dvb_t_pci.toml
* rc-alink-dtu-m alink_dtu_m.toml
* rc-anysee anysee.toml
* rc-apac-viewcomp apac_viewcomp.toml
* rc-astrometa-t2hybrid astrometa_t2hybrid.toml
* rc-asus-pc39 asus_pc39.toml
* rc-asus-ps3-100 asus_ps3_100.toml
* rc-ati-tv-wonder-hd-600 ati_tv_wonder_hd_600.toml
* rc-ati-x10 ati_x10.toml
* rc-avermedia-a16d avermedia_a16d.toml
* rc-avermedia-cardbus avermedia_cardbus.toml
* rc-avermedia-dvbt avermedia_dvbt.toml
* rc-avermedia-m135a avermedia_m135a.toml
* rc-avermedia-m733a-rm-k6 avermedia_m733a_rm_k6.toml
* rc-avermedia-rm-ks avermedia_rm_ks.toml
* rc-avermedia avermedia.toml
* rc-avertv-303 avertv_303.toml
* rc-azurewave-ad-tu700 azurewave_ad_tu700.toml
* rc-beelink-gs1 beelink_gs1.toml
* rc-behold-columbus behold_columbus.toml
* rc-behold behold.toml
* rc-budget-ci-old budget_ci_old.toml
* rc-cec cec.toml
* rc-cinergy-1400 cinergy_1400.toml
* rc-cinergy cinergy.toml
* rc-ct-90405 ct_90405.toml
* rc-d680-dmb d680_dmb.toml
* rc-delock-61959 delock_61959.toml
* rc-dib0700-nec dib0700_nec.toml
* rc-dib0700-rc5 dib0700_rc5.toml
* rc-digitalnow-tinytwin digitalnow_tinytwin.toml
* rc-digittrade digittrade.toml
* rc-dm1105-nec dm1105_nec.toml
* rc-dntv-live-dvb-t dntv_live_dvb_t.toml
* rc-dntv-live-dvbt-pro dntv_live_dvbt_pro.toml
* rc-dtt200u dtt200u.toml
* rc-dvbsky dvbsky.toml
* rc-dvico-mce dvico_mce.toml
* rc-dvico-portable dvico_portable.toml
* rc-em-terratec em_terratec.toml
* rc-encore-enltv-fm53 encore_enltv_fm53.toml
* rc-encore-enltv encore_enltv.toml
* rc-encore-enltv2 encore_enltv2.toml
* rc-evga-indtube evga_indtube.toml
* rc-eztv eztv.toml
* rc-flydvb flydvb.toml
* rc-flyvideo flyvideo.toml
* rc-fusionhdtv-mce fusionhdtv_mce.toml
* rc-gadmei-rm008z gadmei_rm008z.toml
* rc-geekbox geekbox.toml
* rc-genius-tvgo-a11mce genius_tvgo_a11mce.toml
* rc-gotview7135 gotview7135.toml
* rc-hauppauge hauppauge.toml
* rc-hisi-poplar hisi_poplar.toml
* rc-hisi-tv-demo hisi_tv_demo.toml
* rc-imon-mce imon_mce.toml
* rc-imon-pad imon_pad.toml
* rc-imon-rsc imon_rsc.toml
* rc-iodata-bctv7e iodata_bctv7e.toml
* rc-it913x-v1 it913x_v1.toml
* rc-it913x-v2 it913x_v2.toml
* rc-kaiomy kaiomy.toml
* rc-khadas khadas.toml
* rc-khamsin khamsin.toml
* rc-kworld-315u kworld_315u.toml
* rc-kworld-pc150u kworld_pc150u.toml
* rc-kworld-plus-tv-analog kworld_plus_tv_analog.toml
* rc-leadtek-y04g0051 leadtek_y04g0051.toml
* rc-lme2510 lme2510.toml
* rc-manli manli.toml
* rc-mecool-kii-pro mecool_kii_pro.toml
* rc-mecool-kiii-pro mecool_kiii_pro.toml
* rc-medion-x10-digitainer medion_x10_digitainer.toml
* rc-medion-x10-or2x medion_x10_or2x.toml
* rc-medion-x10 medion_x10.toml
* rc-minix-neo minix_neo.toml
* rc-msi-digivox-ii msi_digivox_ii.toml
* rc-msi-digivox-iii msi_digivox_iii.toml
* rc-msi-tvanywhere-plus msi_tvanywhere_plus.toml
* rc-msi-tvanywhere msi_tvanywhere.toml
* rc-nebula nebula.toml
* rc-nec-terratec-cinergy-xs nec_terratec_cinergy_xs.toml
* rc-norwood norwood.toml
* rc-npgtech npgtech.toml
* rc-odroid odroid.toml
* rc-pctv-sedna pctv_sedna.toml
* rc-pine64 pine64.toml
* rc-pinnacle-color pinnacle_color.toml
* rc-pinnacle-grey pinnacle_grey.toml
* rc-pinnacle-pctv-hd pinnacle_pctv_hd.toml
* rc-pixelview-002t pixelview_002t.toml
* rc-pixelview-mk12 pixelview_mk12.toml
* rc-pixelview-new pixelview_new.toml
* rc-pixelview pixelview.toml
* rc-powercolor-real-angel powercolor_real_angel.toml
* rc-proteus-2309 proteus_2309.toml
* rc-purpletv purpletv.toml
* rc-pv951 pv951.toml
* rc-rc6-mce rc6_mce.toml
* rc-real-audio-220-32-keys real_audio_220_32_keys.toml
* rc-reddo reddo.toml
* rc-snapstream-firefly snapstream_firefly.toml
* rc-streamzap streamzap.toml
* rc-su3000 su3000.toml
* rc-tanix-tx3mini tanix_tx3mini.toml
* rc-tanix-tx5max tanix_tx5max.toml
* rc-tbs-nec tbs_nec.toml
* rc-technisat-ts35 technisat_ts35.toml
* rc-technisat-usb2 technisat_usb2.toml
* rc-terratec-cinergy-c-pci terratec_cinergy_c_pci.toml
* rc-terratec-cinergy-s2-hd terratec_cinergy_s2_hd.toml
* rc-terratec-cinergy-xs terratec_cinergy_xs.toml
* rc-terratec-slim-2 terratec_slim_2.toml
* rc-terratec-slim terratec_slim.toml
* rc-tevii-nec tevii_nec.toml
* rc-tivo tivo.toml
* rc-total-media-in-hand-02 total_media_in_hand_02.toml
* rc-total-media-in-hand total_media_in_hand.toml
* rc-trekstor trekstor.toml
* rc-tt-1500 tt_1500.toml
* rc-twinhan-dtv-cab-ci twinhan_dtv_cab_ci.toml
* rc-twinhan1027 twinhan_vp1027_dvbs.toml
* rc-vega-s9x vega_s9x.toml
* rc-videomate-k100 videomate_k100.toml
* rc-videomate-s350 videomate_s350.toml
* rc-videomate-tv-pvr videomate_tv_pvr.toml
* rc-videostrong-kii-pro kii_pro.toml
* rc-wetek-hub wetek_hub.toml
* rc-wetek-play2 wetek_play2.toml
* rc-winfast-usbii-deluxe winfast_usbii_deluxe.toml
* rc-winfast winfast.toml
* rc-x96max x96max.toml
* rc-xbox-dvd xbox_dvd.toml
* rc-zx-irdec zx_irdec.toml
# * * af9005.toml # found in af9005-remote.c
# * * az6027.toml # found in az6027.c
# * * cinergyt2.toml # found in cinergyT2-core.c
# * * dibusb.toml # found in dibusb-common.c
# * * digitv.toml # found in digitv.c
# * * megasky.toml # found in m920x.c
# * * tvwalkertwin.toml # found in m920x.c
# * * pinnacle310e.toml # found in m920x.c
# * * haupp.toml # found in nova-t-usb2.c
# * * opera1.toml # found in opera1.c
# * * vp702x.toml # found in vp702x.c

How do we make ir-keytable respond only to the mapping we want mythtv to get? Everything else seems to work, but why is this so difficult? Clean install on 22.04. LIRC & LIRCD are not installed.

mythtv@tivofront:/etc$ sudo ir-keytable
Found /sys/class/rc/rc0/ with:
Name: Media Center Ed. eHome Infrared Remote Transceiver (1784:0011)
Driver: mceusb
Default keymap: rc-rc6-mce
Input device: /dev/input/event7
LIRC device: /dev/lirc0
Attached BPF protocols: Operation not supported
Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon rc-mm
Enabled kernel protocols: lirc rc-6
bus: 3, vendor/product: 1784:0011, version: 0x0100
Repeat delay = 500 ms, repeat period = 125 ms
nouglywires
Junior
Posts: 20
Joined: Sun Nov 23, 2014 7:17 pm
United States of America

Re: Mythtv on Ubuntu 20.04 (edit: mostly ir-keytable/lirc issue)

Post by nouglywires »

As I wrote above, I added a line at the top of /etc/rc_maps.cfg, to point to the toml table:

Code: Select all

mceusb * /etc/rc_keymaps/rc6_mce.toml
Also, as I wrote above, I had to create a service to ensure that ir-keytable is run on every system startup.

Maybe that will help you.
Post Reply