rpi-ir-remote icon indicating copy to clipboard operation
rpi-ir-remote copied to clipboard

irsend not working

Open endyb66 opened this issue 5 years ago • 9 comments

I've done everything step by step, like in this guide. Before the update to kernel 4.19.x, everything worked fine with irsend. Now i upgraded my rpi to kernel 4.19.x and did everything like in this guide, but still no luck. There is no error, neither in the console when using irsend, nor in the syslog. So it should work i think. Don't know where to look further for issues.

endyb66 avatar May 30 '19 19:05 endyb66

Oh no! Hopefully we can resolve it. I'll update the guide if we find any additional information.

Since you don't see any errors, can you check whether the LED is lighting up? A phone camera can see the LED flash.

I'd like to see the output of the sanity check commands. Could you reply with the output of these commands?

dmesg | grep "lirc\|gpio-ir" lsmod | grep gpio_ir ll /dev/lirc0 ps aux | grep lirc

Also, please include the output of uname -a.

And I want to confirm: you did make the dtoverlay change and substitute your pin number(s) for the example values?

mtraver avatar May 30 '19 20:05 mtraver

I think there is some sort of issues, i can't see the LED lighting up with a camera...Here are the Outputs of the commands

# dmesg | grep "lirc\|gpio-ir"
[   10.218604] rc rc0: GPIO IR Bit Banging Transmitter as /devices/platform/gpio-ir-transmitter@16/rc/rc0
[   10.218994] rc rc0: lirc_dev: driver gpio-ir-tx registered at minor = 0, no receiver, raw IR transmitter
[   10.309623] rc rc1: lirc_dev: driver gpio_ir_recv registered at minor = 1, raw IR receiver, no transmitter
[   30.118165] input: lircd-uinput as /devices/virtual/input/input2
# lsmod | grep gpio_ir
gpio_ir_recv            3095  0
gpio_ir_tx              3569  0
# ls -l /dev/lirc0
crw-rw---- 1 root video 252, 0 May 30 21:02 /dev/lirc0
# ps aux | grep lir
root       225  0.0  0.4   4260  2056 ?        Ss   May30   0:00 /usr/sbin/lircmd --nodaemon
root       233  0.0  0.4   4188  2136 ?        Ss   May30   0:00 /usr/bin/irexec /etc/lirc/irexec.lircrc
root       391  0.0  0.7   7292  3400 ?        Ss   May30   0:18 /usr/sbin/lircd --nodaemon
root       393  0.0  0.5   4264  2384 ?        Ss   May30   0:00 /usr/sbin/lircd-uinput
root     10881  0.0  0.4   4360  1956 pts/0    S+   07:58   0:00 grep lir
# uname -a
Linux raspi 4.19.46+ #1230 Tue May 28 16:00:00 BST 2019 armv6l GNU/Linux

Inside my /boot/config.txt i have changed

dtoverlay=lirc-rpi,gpio_in_pin=27,gpio_out_pin=22

to

dtoverlay=gpio-ir,gpio_pin=27
dtoverlay=gpio-ir-tx,gpio_pin=22

Edit// For testing i downgraded the kernel to 4.14 and everything is working again. So don't know where the issue could be. I also removed / purged lirc on kernel 4.19 and reinstalled it again, and copied my remote config over. But without luck.

endyb66 avatar May 31 '19 06:05 endyb66

The logs seem fine. I noticed that I was on an earlier kernel than you (4.19.42-v7+ #1219) so I upgraded to 4.19.46-v7+ #1230. For me it still works though, so I'm not sure. If you figure it out please post back here!

mtraver avatar Jun 02 '19 23:06 mtraver

Could it be an issue, when upgrading directly to the newest kernel? I mean the weird Thing is, that after downgrading to kernel 4.14.x it worked again like before. So somewhere has to be a problem.

endyb66 avatar Jun 03 '19 15:06 endyb66

I suppose it could be, but all I can say is that using rpi-update to upgrade and roll back hasn't caused issues for me.

Well, we know that on 4.14 it works well with lirc-rpi. Newer firmware and newer kernel introduce lots of differences and for me only the dtoverlay change to gpio-ir was needed, but for your setup it seems like that's insufficient.

While doing my initial debugging on 4.19 I found this: https://www.raspberrypi.org/forums/viewtopic.php?t=235256. The original post only talks about differences in recording, but some replies talk about broken transmit being resolved. You might try the patch and see if it helps.

mtraver avatar Jun 03 '19 16:06 mtraver

Ok, could it be because i did a apt-get dist-upgrade first, instead of using rpi-update?

endyb66 avatar Jun 03 '19 18:06 endyb66

I don't know. You can try both approaches, and also try the patch from the forum post I linked to.

mtraver avatar Jun 04 '19 16:06 mtraver

Were you able to diagnose the problem?

mtraver avatar Jun 14 '19 21:06 mtraver

Currently no, i haven't time yet, because the device has to run without Interrupts. So i currently i stay on the older kernel.

endyb66 avatar Jun 24 '19 15:06 endyb66