Hardware | LIRC does not work with current RPi 4.19 kernel #3481
Comments
|
Hi, many thanks for your report. Basically this could be an answer on your question. But I never did this by my own. So don't know if this will work. |
|
dietpi doesn't have |
|
yes, you would need to install it as described an the link |
|
missed that part it doesn't work |
|
hmm probably something to ask on the raspberry board as DietPi is not providing any own kernel. Maybe guys at raspberry knows whats going on. As I see it updated to 64Bit ( available kernel modules should be visible at |
|
|
|
@AlexanderShniperson |
|
@MichaIng today i also try to setup LIRC by instrunction from |
|
and also try to patch LIRC with that instruction from |
|
@MichaIng do you have any success story with LIRC? |
|
i run |
|
so looks like i got working config and placed setup at the repo |
|
@AlexanderShniperson
Sadly I personally never used LIRC/IR on the Raspberry Pi. I would have expected that enabling the related dtoverlay and installing the lirc package should basically do the job, sad that it isn't hat easy. On RPi we have this "JustBoom IR remote" option in dietpi-config > Display Options, for MPD remote control. I never tested it or worked on it (was done by prior devs), but what we do is:
Even that it is a special use case, probably it helps. The other way round probably our remote control implementation is outdated or does not work OOTB for the same reason. |
|
i've inspected output of and see that by default is enabled |
|
@AlexanderShniperson
That is btw expected on RPi. BPF is a new kernel packet filter (firewall) that has not been enabled on recent RPi kernels yet. They just enabled nftables not too long ago.
Looks right to me, although I have no deeper knowledge about those protocols and especially how to configure the adapters to use a certain protocol.
Interesting that it's And another think I just found:
|
|
i start thinking that send and receive signal on the same Raspberry is impossible in case of usage Raspberry Zero that have 1 core, i will check with two devices, one send signal and second receive. |
|
Hooray, its works, connected to socket opened at RPi that receive IR data and got message, updated configs at my repo |
|
Hi, I'm glad you got something working! Can you please resume your step-by-step installation so that I, and others, can follow? I can't even get lircd to run, it always fails. |
|
@GlennFR hi, i summarized all my work in repo |
|
Hi Alexander, thanks for your reply. I'm having trouble because
I'm using ArchLinux on my RPi - and the install of lirc doesn't
seem to be complete. I'm more used to debian type linux, so I'm
struggling under Arch. I'll re-read your post tomorrow with a
fresher brain!
On 27/04/2020 15:49, Alexander
Shniperson wrote:
@GlennFR
hi, i summarized all my work in repo
just install lirc apt-get install lirc and then
read steps at my readme file, also as would be needed install
patched lirc, it's also there
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "#3481 (comment)",
"url": "#3481 (comment)",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
|
|
if you need help i've recommend you to open issue at my Repo, because it's not related to this thread. |
MichaIng
added
Workaround available 🆗
MichaIng
changed the title
|
maybe is there a way to get source of |
|
@AlexanderShniperson
However I think the packages you have with patch included are fine already, the upstream source is still the same anyway. |
|
oh, a lot of work needs to be done to compile |
|
@AlexanderShniperson |
|
@AlexanderShniperson And here is as well a solution going back to the "deprecated" kernel module: https://gist.github.com/prasanthj/c15a5298eb682bde34961c322c95378b |
No i don't but will try. The code in my repository is the union of several articles and solutions, also in my repo i was linked last link as a base solution |
|
@MichaIng experiment end without luck, success update to kernel 5.4 doesn't give positive effect with original
so now all works as expected! |
|
Doesn't work the "new" dtoverlay There seem to be other IR issues with RPi4, failing irrecord: https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=235256&start=50#p1686574 |
|
|
Ah okay makes sense somehow, although I'm confused now whether |
|
@MichaIng do you have any idea why? |
|
by googling i found similar problem where folks talk about wrong kernel mailboxing
now |
|
Meanwhile lirc v0.10.1-6.2 has been merged into Buster, so probably the issue is fixed with current kernel and APT packages: https://packages.debian.org/buster/lirc |
|
I mark this as closed. Feel free to reopen if issue persists. |
Creating a bug report/issue
Required Information
10.2Linux DietPi 4.19.93-v7+ #1290 SMP Fri Jan 10 16:39:50 GMT 2020 armv7l GNU/LinuxRPi 3 Model A+ (armv7l)Additional Information (if applicable)
Steps to reproduce
LIRCpackageirsendExpected behaviour
lircdreceive signal and broadcast to clientsActual behaviour
nothing received, also in logs
Cannot configure the rc device for /dev/lirc0Extra details
setup was done by this instruction without luck: https://github.com/mtraver/rpi-ir-remote
Used IR-receiver TSOP31238 and IR-led TSAL6200
Possible solution: downgrade kernel to 4.14 because many users told that LIRC work fine with that kernel version
How to downgrade kernel to 4.14 ?
The text was updated successfully, but these errors were encountered: