Anyone having radio detection issue on RPI4 / docker with recent releases ? #1883
Unanswered
mulder999
asked this question in
🇩🇪 Fragen&Antworten
Replies: 2 comments 2 replies
-
I have the same setup: RPI-RF-MOD on GPIO I can confirm that it is not working for me on the newest bullseye release (Kernel 5.15) as well. Same errors. After a reinstall with buster (Kernel 5.10) it works as expected. |
Beta Was this translation helpful? Give feedback.
0 replies
-
@heilerich I finally managed to sort it. I forced reinstall of pivccu version 3.65.6-73 and had to mess around with
instead of
|
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I am using raspberry pi 4 with RPI-RF-MOD connected on GPIO.
The setup has been fine up to raspmatic 3.61.7.20220226 on docker 20.10.14 on Linux aarch64 5.10.92-v7+
Then I started experiencing unreliable radio with raspmatic 3.63.8.20220330, so I had to revert to 3.61.7 to regain stable radio.
Yesterday I went with a system upgrade and now radio is no longer detected at all on docker 20.10.17 on Linux aarch64 5.15.32-v8+, no matter the raspmatic image.
In fact it ressembles some driver issue:
dmesg at boot:
[ 3.725544] eq3_char_loop: loading out-of-tree module taints kernel.
Without much surprise radio detection fails at docker image start:
Trying to isolate the problem one step at a time, but would love to see if anyone managed to run it with latest on everything on pi4.
PS: Still have a rpi3 with RPI-RF-MOD running on some older release/kernel and I confirmed both setups are indeed similar.
Beta Was this translation helpful? Give feedback.
All reactions