I’m trying to do a clean install of dump1090-fa/piaware on a ubuntu server as per the instructions on the FlightAware site.
When I do: apt-get install dump1090-fa_
I get: Unable to locate package dump1090-fa
Has the package been moved ?
You are trying to install dump1090-fa on which hardware/architecture, armv7 (RPi) or x86/amd64 (PC)?
The package install only works on arm systems.
Here are the instruction page to add the repository for the piaware+dump1090 package:
The actual commands to add the download the repository location and add it to your system.
wget http://flightaware.com/adsb/piaware/files/packages/pool/piaware/p/piaware-support/piaware-repository_3.5.3_all.deb
sudo dpkg -i piaware-repository_3.5.3_all.deb
This will not work on x86 systems. You will need to download the files from GitHub and compile the software. There are some scripts floating around the forums but these are not maintained by FlightAware.
@OldDxer:
The Flightaware package from apt repository is for RPi (arm7).
For PC (i386/x86/amd64), you need to build package from source.
J Prochazka has written script for doing this automatically.
Using this script, I have installed dump1090-mutability and Piaware data feeder on my PC running Ubuntu 16.04, but option to install dump1090-fa is also available in this script.
.
.
sudo apt-get update
sudo apt-get install git
git clone https://github.com/jprochazka/adsb-receiver.git
cd ~/adsb-receiver
chmod +x install.sh
./install.sh
.
For details and instructions, please see this thread:
@OldDxer:
The current version of J Prochazka’s script successfully installs dump1090-fa on Ubuntu 16.04 x86/amd64. However the script installs older version 3.5.1 of dump1090-fa. However it installs latest version 3.5.3 of Piaware data feeder add-on.
The reason is the script clones Github’s master branch of dump1090, which is version 3.5.1. The version 3.5.3 is available in dev branch.
I therefore used manual method to build and install dump1090-fa from dev branch. The step-by-step method is given below the screenshot.
.
.
cd ~
sudo apt-get update
sudo apt-get install git
#install dependencies for bladeRF
sudo apt-get install cmake doxygen libtecla-dev help2man pandoc
sudo mkdir build
cd build
sudo git clone https://github.com/Nuand/bladeRF.git
cd bladeRF
sudo dpkg-buildpackage -b
cd ../
sudo dpkg --install libbladerf1_*.deb
sudo dpkg --install libbladerf-dev_*.deb
sudo dpkg --install libbladerf-udev_*.deb
.
#install dependencies for dump1090-fa
sudo apt-get install librtlsdr-dev debhelper dh-systemd libncurses5-dev lighttpd
#clone dump1090
sudo git clone https://github.com/flightaware/dump1090.git
#set git repository to dev branch
cd dump1090
sudo git fetch --all
sudo git reset --hard origin/dev
#build installation package
sudo dpkg-buildpackage -b
#install dump1090
cd ../
sudo dpkg --install dump1090-fa_*_amd64.deb
sudo /etc/init.d/lighttpd force-reload
sudo reboot
.
sudo nano /etc/default/dump1090-fa
#scroll down to following line
DECODER_OPTIONS="--max-range 360"
#add your latitude and longitude as shown below.
#replace xx.xxxx and yy.yyyy by your actual latitude and longitude
DECODER_OPTIONS="--lat xx.xxxx --lon yy.yyyy --max-range 360"
#save file (Ctrl+o) close file (Ctrl+x)
#restart dump1090-fa
sudo systemctl restart dump1090-fa
Reload your browser. If Station Marker and Site Circles do not show, clear browser cache (Ctrl+Shift+Delete) and then hard reload the browser (Ctrl+F5).
That is all. Enjoy…
Making the best attempt at getting dump1090-fa to build using these instructions but ran into the following when trying to build bladeRF:
– Configured to build bladeRF-cli version: 1.5.1-git-8b420eb
CMake Error at host/utilities/bladeRF-fsk/c/CMakeLists.txt:261 (target_compile_definitions):
Unknown CMake command “target_compile_definitions”.
Comments?
J
This is strange. Just now I repeated the blade RF built procedure (Ubuntu 16.04 x64 on PC with intel CPU) exactly as given in my last post, and it completed successfully.
POSIBILITY-A:
Seems in your case one or more of the dependencies did not install properly. Please repeat the following command and watch the output. If all dependencies were installed, it will show that. If any was missed out, it will try to install it .
sudo apt-get install cmake doxygen libtecla-dev help2man pandoc
After above command, try again to build bladeRF.
POSSIBILITY-B:
If all above fails, then another possibility is that some file got corrupted while cloning bladeRF from Github. Delete the cloned folder bladeRF, and clone again, and then try to build:
cd build
#Delete folder bladeRF which was cloned from Github
sudo rm -rf bladeRF
#Clone fresh copy of bladeRF from Github
sudo git clone https://github.com/Nuand/bladeRF.git
#Now build the bladeRF packages
cd bladeRF
sudo dpkg-buildpackage -b
Method successfully tested on Debian Jessie adm64 too.
Congratulations!
A little remark: sudo is not required for git and dpkg-buildpackage.
Regards
Trouble on Ubuntu 16.04 LTS:
/usr/bin/ld: cpu_features/src/string_view.o: relocation R_X86_64_32 against `.rodata.str1.1’ can not be used when making a shared object; recompile with -fPIC
cpu_features/src/string_view.o: error adding symbols: Feil verdi
collect2: error: ld returned 1 exit status
Makefile:190: recipe for target ‘dump1090’ failed
make[2]: *** [dump1090] Error 1
make[2]: Leaving directory ‘/home/rune/build/dump1090’
dh_auto_build: make -j1 RTLSDR=yes BLADERF=yes HACKRF=yes LIMESDR=yes DUMP1090_VERSION=5.1~dev returned exit code 2
debian/rules:48: recipe for target ‘override_dh_auto_build’ failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory ‘/home/rune/build/dump1090’
debian/rules:57: recipe for target ‘build’ failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
please create a github issue with complete details (including the exact steps you took to build). The thread you replied to is 3 years old and is unlikely to help you.
not sure how and where, but trying other platforms to see if I can make it work. If you have other links to help than this thread, would appreciate it.
Too old a distro.
If you can, the best option is to replace it with latest Ubuntu 20.04 LTS
The link below is tested for latest versions (amd64):
Ubuntu 20.04, Debian 10.8 and Kali Linux 2021.1
The method of above link may or may not work with Ubuntu 16.04 i386.
You are more likely to get help if you make a new post with details rather than replying to a 3-year-old post that describes different problems.