I keep my Raspberry Pi up to date with latest software (sudo apt-get update; sudo apt-get upgrade). I seem to have accidentally installed a kernel module that conflicts with dump1090, causing it to fail silently and thus not feed data to piaware.
Solution was to prevent the Linux kernel from loading the conflicting module. I did this by creating a file called /etc/modprobe.d/dvb_usb_rtl28xxu.conf containing this line:
Symptom was that dump1090 failed silently from the init script. Starting it manually showed an error message that explained the conflict with the kernel module (which had the device open). A look on the Debian forums recommended using a ‘fake start script’ to prevent the kernel from loading the conflicting module.
I might be wrong, but does blacklisting the relevant modules fix this?
/etc/modprobe.d/rtl-sdr-blacklist.conf
# This system has librtlsdr0 installed in order to
# use digital video broadcast receivers as generic
# software defined radios.
blacklist dvb_usb_rtl28xxu
blacklist e4000
blacklist rtl2832
Hmmm. Mine appears to be a hardware issue. Thing gets really hot then hangs with CPU kernel panic. Swapped PS and no better. Thanks for the heads up though, just in case we do run into this.
I’m running this same kernal on two RPi2 ADS-B feeders without any of the issues you describe. Both were built from scratch with the latest Debian/Wheezy starting point, dump1090-mutability, PiAware, etc…
…Tom
One difference is that I’m running plain dump1090 (not the ‘mutability’ version). Another could be that I somehow installed a kernel module that you don’t have.
You can list installed modules with ‘lsmod’. When I don’t blacklist I have ‘dvb_usb_rtl28xxu’ loaded. Do you?