Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lirc_rpi got replaced by gpio-ir and gpio-ir-tx, how do I upgrade? #2993

elmicha opened this issue May 29, 2019 · 6 comments

lirc_rpi got replaced by gpio-ir and gpio-ir-tx, how do I upgrade? #2993

elmicha opened this issue May 29, 2019 · 6 comments


Copy link

@elmicha elmicha commented May 29, 2019

I found that lirc-rpi has been replaced by gpio-ir and gpio-ir-tx, and I found that I have to use "dtoverlay=gpio-ir-tx,gpio_pin=17" in /boot/config.txt to get the transmitter working like before. But I can't figure out how the receiver is supposed to work now.

I tried various values for the gpio_pull and rc-map-name options, but none worked.

Describe the bug
I rebooted. All IR transmission and receiving broke. I googled and found how to replace the transmission capability with gpio-ir-tx and it worked. I googled again for the receiving part and nothing worked.

To reproduce
Upgrade from a kernel before 4.19 to 4.19.x when you were happily using LIRC to send and receive IR codes.

Expected behaviour
Everything works like before, maybe after a bit of googling and replacing some module names and options.

Actual behaviour
Both transmitting and receiving broke without warning. No useful documentation to be found anywhere.

pi@rpi ~ $ raspinfo
raspinfo: command not found
pi@rpi ~ $ apt search raspinfo
Sortierung... Fertig
Volltextsuche... Fertig

Copy link

@pelwell pelwell commented May 29, 2019

That's a good question. I've had no reason to use IR remotes with a Pi except for testing, and although I did some work with the LIRC driver once I've not played with the replacement - gpio-ir.

I managed to find this LibreElec IR guide which may help:

I also think that if you read that and come back with more questions then @HiassofT may be able to give you a few pointers.

Copy link

@HiassofT HiassofT commented May 29, 2019

both gpio-ir and gpio-ir-tx will provide a /dev/lircX device so if you like you can use lircd as before - but you'll need to add udev rules to create symlinks for the receive/transmit device nodes if you enable both at the same time as the /dev/lircX numbers aren't guaranteed to be fixed (0 could be receive and 1 transmit, or the other way round). You'll also need to run 2 lircd instances (one for receive, one for transmit/blast).

For receiving I'd recommend to drop lircd and switch to in-kernel decoding / ir-keytable configuration. The majority of consumer remotes are supported and you only need to use lircd for a few non-standard remotes.

You can also use ir-ctl to transmit/blast IR codes instead of using lircd/irsend

Search the RPi forums for more details, I posted some info there

Copy link
Contributor Author

@elmicha elmicha commented May 30, 2019

Thank you! I want to keep using lircd, because I already configured a few remotes with it.
For anyone who wants to keep using lircd for a transmitter and a receiver, here's what I did.

In /boot/config.txt remove the lirc-rpi line and add gpio-ir for the receiver and gpio-ir-tx or pwm-ir-tx for the transmitter:

# dtoverlay=lirc-rpi
# dtoverlay=gpio-ir-tx,gpio_pin=18

I exchanged the gpio_pin numbers (and the wires of the transmitter and receiver), because pwm-ir-tx doesn't work with gpio pin 17. See /boot/overlays/README for the details.

Remove the lirc_rpi module from /etc/modules.

Add these rules in /etc/udev/rules.d/71-lirc.rules to get stable /dev/lirc-rx and /dev/lirc-tx device names:

ACTION=="add", SUBSYSTEM=="lirc", DRIVERS=="gpio_ir_recv", SYMLINK+="lirc-rx"
ACTION=="add", SUBSYSTEM=="lirc", DRIVERS=="gpio-ir-tx", SYMLINK+="lirc-tx"
ACTION=="add", SUBSYSTEM=="lirc", DRIVERS=="pwm-ir-tx", SYMLINK+="lirc-tx"

Change the device and listening address in /etc/lirc/lirc_options.conf:

device          = /dev/lirc-rx
listen          =

Copy lirc_options.conf to lirc_tx_options.conf and edit these lines:

device          = /dev/lirc-tx
output          = /var/run/lirc/lircd-tx
pidfile         = /var/run/lirc/
listen          =
connect         =

Create /etc/systemd/system/lircd-tx.service (from the output of systemctl cat lircd) and edit it to be:

Description=Second lircd, the transmitter
Wants=lircd-setup.service lircd-setup.service lircd.service

ExecStart=/usr/sbin/lircd --nodaemon --options-file /etc/lirc/lirc_tx_options.conf
; User=lirc
; Group=lirc

; Hardening opts, see systemd.exec(5). Doesn't add much unless
; not running as root.
; # Required for dropping privileges in --effective-user.
; CapabilityBoundingSet=CAP_SETEUID
; MemoryDenyWriteExecute=true
; NoNewPrivileges=true
; PrivateTmp=true
; ProtectHome=true
; ProtectSystem=full


Create /etc/systemd/system/lircd-tx.socket (from the output of systemctl cat lircd.socket) and edit it:



Start lircd-tx:

sudo systemctl daemon-reload
sudo systemctl start lircd-tx
sudo systemctl enable lircd-tx

Create /usr/local/bin/irsend and make it executable:

 #! /bin/sh
 exec /usr/bin/irsend --device=/var/run/lirc/lircd-tx "$@"

@elmicha elmicha closed this May 30, 2019
Copy link

@majki09 majki09 commented May 30, 2019

Hello. I'm also here with the same problem for receiving IR signal. After a week of banging my head against the wall I've noticed that:

  • no IR signal is comming to RPi - I've checked the RAW signal with ir-ctl -d /dev/lirc0 -r
  • my IR receiver (3-pinned AT138B connected to GPIO18) is "not enabled" - which means no 3.3V power and no pull-up (my receiver requires pull-up to work).

So I'd rather look for the reason here and it doesn't make sense to go further with any configuration.

@elmicha, I suppose the problem is still there, can you please try the same with ir-ctl -d /dev/lirc0 -r ? This will check IR signal is indeed comming to your RPi, it's like mode2 in lircd...
Also, you need to make sure that the gpio-ir overlay has been loaded with
sudo vcdbg log msg

For now I need to revert back my kernel to previous stable (4.14.y) with lircd working and I'm waiting for stable solution in new kernel release. You can downgrade your kernel using following command:
sudo rpi-update c30ae2bb624f7fd60fcbedff950cc4361c8d2aec

Copy link

@carloselectro carloselectro commented Aug 10, 2019

Thank you for this Elmicha!
I can finally make the IR receiving working in Buster and my raspberry 4.
Were you able to record new remotes with this command:?
irrecord -d /dev/lirc-rx

Copy link

@josla972 josla972 commented Jan 12, 2020

This forum thread summarizes everything very well:

Had to patch and rebuild the 4.19 kernel to get my AC control working again because of the #define LIRCBUF_SIZE limitation. Sounds like this is going to be fixed in future kernel versions but that is probably going to take a long while. Not really happy about this surprise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants