Many thanks for the answer. Yes my workaround worked. I added the following ExecStartPre statement to my IR daemon service script..
It was also necessary to disable the dtoverlay statement in /boot/config.txt (for Bullseye). I updated the apt-utils package in Bullseye and the problem was sorted.
The problem remains in Bookwork so I will look forward to the updated apt-utils package.
There was another consideration. You can no longer guarantee that the device in /sys/class/rc will be rc0 as vc4-hdmi also uses kernel events. In my case it was rc2.
Use -s flag with the correct device (rc2 in this case)
Code:
ExecStartPre=dtoverlay gpio-ir gpio_pin=25It was also necessary to disable the dtoverlay statement in /boot/config.txt (for Bullseye). I updated the apt-utils package in Bullseye and the problem was sorted.
The problem remains in Bookwork so I will look forward to the updated apt-utils package.
There was another consideration. You can no longer guarantee that the device in /sys/class/rc will be rc0 as vc4-hdmi also uses kernel events. In my case it was rc2.
Code:
$ sudo ir-keytableFound /sys/class/rc/rc1/ with: Name: vc4-hdmi-1 :Found /sys/class/rc/rc2/ with: Name: gpio_ir_recv Driver: gpio_ir_recv Default keymap: rc-rc6-mce Input device: /dev/input/event2 LIRC device: /dev/lirc0 Attached BPF protocols: Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon Enabled kernel protocols: lirc rc-6 bus: 25, vendor/product: 0001:0001, version: 0x0100 Repeat delay = 500 ms, repeat period = 125 msFound /sys/class/rc/rc0/ with: Name: vc4-hdmi-0 :Code:
sudo /usr/bin/ir-keytable -s rc2 -c -w /etc/rc_keymaps/myremote.tomlStatistics: Posted by bobrathbone — Tue Apr 02, 2024 2:42 pm