Try recompiling the driver per this thread:
ads-b-flight-tracking-f21/dump1090-not-displaying-data-t19996.html
Thanks for the advise, but it came a bit late. I have already formatted the mivroSD card, and downloaded & burned new image (ARMBIAN Debian GNU/Linux 8 (jessie) 3.4.112-sun8i). Will now run JP’s automated script to install dump1090-mut, data feefers & web portal.
You may still need to recompile the driver. Honestly, this is probably the best approach to use vs. the blacklist.
sudo modprobe -r dvb_usb_rtl2832u
works without restart!
If you restart after this then the result of this command is lost!
Please do this
sudo lsmod | grep rtl
if you see some result then the kernel module is loaded and it should be removed
To persist the changes after reboot edit this file
/etc/modprobe.d/rtl-sdr-blacklist.conf
and add a blacklist line with the kernel module you saw with the lsmod command
The problem is that even blacklisting it doesn’t always work after a reboot. From the Armbian Forum Administrator
Afternoon all,
For c£15, thought I’d have a play with the Orange Pi Pc 1.2; ordered on Alibaba few weeks back - arrived today!
Reading through this thread ahead of purchase, pretty sure I can get PiAware set up to act as a second fA reciever, happy to have a play anyway…
From those of you who’ve done it - is it actually worth the hassle?
I’ve read that they run very hot, the chip’s a b*tch and can be a Pain in the ass…
As I say though, happy to have a play for the few ££…
Will mutability run on it - ultimately, once set up - is it comparable to the RPi 2 for our adsb use?
Ultimately - those of you who’ve done it - would you recommend it / do it again?
I haven’t attempted PiAware, but dump1090-mutability definitely runs on it.
I use the most recent Armbian version as the OS and then use the install scripts from Mr. Prochazka. Fast and simple. Heat has not been an issue for me, and my most recent install is outside on the roof.
On an earlier install I have two dongles running with two different antennas, and two instances of mutability 1.14 on one OPi PC.
The big attraction was low price, good performance, more memory (if I recall correctly), and extra USB ports. Obviously, others may have different experiences.
Still have the rPi and it’s running fine on another antenna
Thanks Yxespotter,
Got the oPi set up and running Armbian Jessie from the link above… upgraded to Armbian 3.4.112-Sun8i , so far so good.
Must say, pleasantly surprised so far!
Couple of things I did note:
-
Running of the HDMI, screen boundary was so far off, I could never actually see the command prompt. Seemed to boot OK, but assume the command prompt was off the bottom of the screen… SSH’d in, and all good.
-
Tried to upgrade the kernal, started ok, then dropped out to command line, saying “Error - unsupported HW”. Slightly odd (its a Orange Pi PC 1.2), but not too fussed.
Just about to start Jo’s adsbreceiver scripts… so far, so good! 
I run all of my devices ‘headless’ so didn’t notice hdmi errors. Having tried a few of the other distros, the recent Armbian Jessie one definitely took the least amount of fiddling to get it to actually work.
Good luck
@cy80rg
Yes, using HDMI & TV screen, the command prompt is outside the screen, and entering user name & password on first boot is real headache. I had to resort to SSH.
Hi guys,
Dont know how much we want to go into the “Orange Pi” issues in this forum, but having a poke around on the Armbian forums, found this regarding the “overscan / cant see login / cant see command prompt” issue.
Basically, the guys at Armbian have (rightly) said they’ve got more important things to work on for the device (fair enough).
SOLUTION for any one else in this is
1: On your TV, switch between “picture modes” in the TV’s menu (cinema, overscan, etc etc). You should find one that will show the full screen.
or
2: Just SSH in like I / others did.
http://forum.armbian.com/index.php/forum/13-allwinner-h3/page-6?prune_day=100&sort_by=Z-A&sort_key=last_post&topicfilter=all is your friend…
Quick report on my experience with the Orange Pi PC 1.2 last night:
-
Installed the Armbian Jessie image from a few posts back in this thread - Believe it’s this one:
http://www.armbian.com/orange-pi-pc/ -
Followed write image / install instructions from here:
armbian.com/documentation/
NB - for initial setup I was running into a TV over the HDMI. Booted fine, but command line / login was off screen due to massively poor overscan. You’ll need to switch “picture modes” on your Tv, or just SSH in on default port 22 with the user creds in that guide in #2.
-
Updated (see link in 2)
-
Set local time (see #2)
All working really well - rather surprised based on some of the reviews online!
TO DO:
Wifi - running fine off cat5 at the moment, but will try wifi dongle.
See here for info (I know some have issues with Wifi dongles, this looks pretty clear …
http://forum.armbian.com/index.php/topic/1032-best-compatible-wifi-dongle-for-orange-pi-pc-v12/
USB Ports - other than a USB wireless keyboard (which I ultimately didnt use / confirm working - I SSH’d in), I’ve not tried plugging any USB devices in yet.
I hear some here have had issues getting all of the USB ports to work.
Guess I’ll have that joy when I come to using the RTL dongle… 
ADSB-Reciever Scripts From a post earlier in this thread, it’s been reported that the scripts for this work “as expected” on this image… Will look at this in the next few days.
Hi All,
Just installed ADSB-Receiver using Jo’s scripts…
All went well, with a couple of queries:
- (UNKNOWN) [127.0.0.1] 30005 (?) : Connection refused
- No graphs showing on “Performance Graphs”
- No data showing on Dump1090 Live Map - doesnt even know location (set in latLong in setup)
- Live Map gives:
“Problem fetching data from dump1090.
AJAX call failed (error: Not Found). Maybe dump1090 is no longer running?
The displayed map data will be out of date.”
Bearing in mind, this Orange Pi is connected to neitherthe RTL_SDR stick, not an antenna, so I wouldnt expect Dump1090 to actually recieve any data, but I would hope:
- Dump1090 would be running, showing reciever location
- Be communicating with the UI, even if not sending any data?
With no “live data” coming from dump1090 - i.e no signals - would the UI believe dump1090’s not running?
Equally, with no data to show, would the graphs in “Performance graphs” have nothing to show, hence no graphs? (All graph locations have the “broken image” place holder icon).
Anyone else have this?
Out of interest, the PlaneFinder client on port 30053 shows its own UI as expected, even down to the location of the receiver…
However, the PF log shows:
2016-06-11 17:51:18.75014 -] Failed TCP connection to all provided addresses for: 127.0.0.1:30005
Which again would suggest a network connection issue?
FWIW, I have my primary station running at the same location, in my attic - with the RTL stick and antenna attached, and feeds running as normal (not touched that today).
Again out of interest, the system graphs (except Core Temp - which shows chart UI, just no data) are all tracking and showing UI as expected…
Think I’ve found the solution to the Core Temp issue (post in Jo’s ADSB-R thread), but in the meantime, my Opi doesnt have a user “pi” - just root and a user “charles”.
Do Jo’s scripts need a specific “pi” user?
EDIT: Core Temp graph now showing data, by changing “1000 to 1” as discussed elsewhere here…
WORK AROUND FOR 5 ISSUES
Orange Pi PC / ARMBIAN 5.10 Debian 8 (jessie) 3.4.112
(1) Changing hostname & adding user:
The default user is root and the default hostname is Orangepi:
root@Orangepi:~#
(a) Changing hostname
In Raspberrypi, the dialogue opened by sudo raspi-config has an option to change host name. This dialogue is not provided in Armbian. To change hostname do following:
Step 1:
~$ sudo nano /etc/hostname
#this will open a file with one entry as follows
Orangepi
#remove Orangepi and type the hostname you want
#Alternatively, you can modify file “hostnames” by following command:
#(replace yourhostname by hostname of your choice)
sudo echo yourhostname > /etc/hostname
Step 2:
~$ sudo nano /etc/hosts
#add your host name shown in red (replace xxxxx by your desired hostname)
127.0.0.1 xxxxxx localhost orangepipc
::1 localhost orangepipc ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
#save file, exit, and reboot
(b) Adding user “pi”:
On 1st boot, it is required to add a user name and password. This name can be anything of your choice. However I prefer to use user name “pi” because /home/pi/ has a widespread use in scripts due to Raspberrypi, and using “pi” makes things simpler.
If you did not add “pi” at 1st boot, and want to add it at later stage:
#login as root
root@Orangepi:~# adduser pi
#after output confirms that user “pi” has been added successfully, grant it sudo privileges
root@Orangepi:~# adduser pi sudo
#after output confirms that user “pi” has been added to group “sudo”, login as user pi and confirm it is in sudo group by following command
opi@Orangepi:~$ groups
#the output will include “sudo” group as shown below
opi sudo
(c) To remove a user:
deluser --remove-home username
#the --remove-home option will delete the user’s home directory as well
(2) DUMP1090 not working (RTL problem in version 3.4.112)
~$ sudo nano /etc/modprobe.d/rtl-sdr-blacklist.conf
#add the line below:
blacklist dvb_usb_rtl2832u
blacklist dvb_usb
#save file, exit and reboot
~ $ sudo reboot
Also do this:
~$ sudo lsmod | grep rtl
If you see some result then the kernel module is loaded and it should be removed.
Add a line for each kernel module you saw with the lsmod command in the rtl-sdr-blacklist.conf file:
~$ sudo nano /etc/modprobe.d/rtl-sdr-blacklist.conf
#Add a line for each kernel module you saw with the lsmod command
#Save & exit the file, and reboot
~ $ sudo reboot
(3) MAC address spoof:
~ $ sudo nano /etc/network/interfaces
#ADD THE LINE SHOWN IN RED BELOW (Change xx:xx:xx:xx:xx:xx to required MAC address)
…
Wired adapter #1
auto eth0
iface eth0 inet dhcp
hwaddress ether xx:xx:xx:xx:xx:xxhwaddress ether # if you want to set MAC manually
pre-up /sbin/ifconfig eth0 mtu 3838 # setting MTU for DHCP, static just$
…
#save the file, exit, and reboot
~ $ sudo reboot
(4) Temperature graph Empty
(thanks to LudgerBoergerding, ieand, and idh for solution)
~$ sudo nano /home/pi/adsb-receiver/build/portal/graphs/make-collectd-graphs.sh
#Go to function temp_graph_metric(), and in its line “CDEF:tfin=traw,1000,/” , changed 1000 to 1
#Save & exit the file, and reboot
~ $ sudo reboot
(5) Only one dvb-t plugged into Orange Pi, but both dump1090 & dump978 installed:
With single dongle, dump978 will grab it, and dump1090 will be left dongle-less. Solve this by:
~$ sudo nano /etc/rc.local
#comment out this line:
#/home/pi/adsb-receiver/build/dump978/dump978-maint.sh &
#save & exit the file, and reboot
~ $ sudo reboot
@abcd567 - good man, looks pretty straight forward…
For the record, re HostName, what would one change this to, and where would I get this from?
(From a bit of research, this is basically to avoid / negate any duplicate hostnames? As this is my only “orangePi” on my network, do I need to do this, “orangepi” is already unique?).
I’ll have another go and report back.
Re Changing Host Name - although the default “orangepi” is unqiue on my network (so no duplicate issues), I did get some odd responces…
(UNKNOWN) [127.0.0.1] 30005 (?) : Connection refused
… that would appear to be related to hostname.
Would this be solved by changing the hostname?
Try
NET_BIND_ADDRESS=“”
in /etc/default/dump1090-mutability
It will allow connection to 127.0.0.1, ::1 and the local IP addres