-
Notifications
You must be signed in to change notification settings - Fork 26
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
RTLs are "blanked" on container start #39
Comments
My best guess would be the kernel modules are either not unloaded or the UDEV rules aren't installed properly. https://sdr-enthusiasts.gitbook.io/ads-b/setting-up-rtl-sdrs/blacklist-kernel-modules to blacklist the modules and sudo -E "$(which bash)" -c "curl -sL -o /etc/udev/rules.d/rtl-sdr.rules https://raw.githubusercontent.com/wiedehopf/adsb-scripts/master/osmocom-rtl-sdr.rules" to install the UDEV rules. Restart the pi after those steps have been done. |
Unfortunately, I had run the standard install script that includes this - but I ran the steps again just to confirm. It still seems to blank out each after docker starts. Complete step:
After the reboot, log back in SSH:
Physically unplug both USB sticks and plug them back in:
|
do you have this in your docker-compose.yml, section for ultra feeder:
|
This has been solved in the Discord - apparently the stock Bookworm Raspbian OS has a broken USB kernel driver. Heads up for those doing a fresh install - As soon as I flipped to a different OS (DietPi as recommended by the mods), I had no issues at all. |
I'm having trouble pinpointing what's going on here, but the basics are:
I have two RTL usb sticks for 1090 and 978 plugged into a Raspberry Pi 4 - when the pi boots, both RTL (which were serialized) display just fine. As soon as I start either ultrafeeder or dump978, the respective RTL then blanks out - which causes both docker images to say they cannot find an RTL that has the supplied serialnumber.
For instance, I can stop the docker service and see RTLs:
However, as soon as I restart the docker service:
I thought this might be a power thing, but I've tried both USB-C from an adequate power source, the POE+ hat, and even the RTLs on a powered USB hub that's connected to the pi - all have the same issue.
Any ideas as to what's going on?
The text was updated successfully, but these errors were encountered: