Piaware install failure

I attempted a clean install of piaware. I installed Bullseye lite, and then followed the instructions on the Flight Aware website, copying the linux commands from their website to terminal and then running them. When it got to sudo apt-get update, there was the following failure:

pi@raspberrypi:~ $ sudo apt-get update
Hit:1 Index of /debian-security bullseye-security InRelease
Hit:2 Index of /debian bullseye InRelease
Hit:3 Index of /debian bullseye-updates InRelease
Hit:4 http://flightaware.com/adsb/piaware/files/packages bullseye InRelease
Hit:5 Index of /debian bullseye InRelease
Reading package lists… Done
N: Skipping acquire of configured file ‘piaware/binary-arm64/Packages’ as repository ‘http://flightaware.com/adsb/piaware/files/packages bullseye InRelease’ doesn’t support architecture ‘arm64’

At this point I don’t know what to do. Can someone give me some help?

Thanks.

Your OS seems to be Bullseye 64-bit (arm64 / aarch64) .
Flightaware has not yet released 64-bit packages of piaware, dump1090-fa, & dump978-fa.

To know positively about your OS, please post output of following commands:

uname -m

lsb_release -sc

cat /etc/os-release

You have obviously installed the 64-bit version of Raspberry OS Bullseye.
Currently the Piaware and Dump1090 package will not work on it.

You should reimage your SD card with the armhf version of Raspberry OS

Not necessary.

The 64-bit pre-built packages, though not available from Flightaware, can still be installed in two ways:

  1. Building from Flightaware source code. This can be done by hand or by using automated script to build the packages.

  2. Installing 64-bit pre-built packages from my ppa (personal package archive) at Github.

Please see this post:

1 Like

FULL 64-BIT HOW-TO

STEP-1: Download and write one of the following 64-bit images to microSD card.

STEP-2: Install 64-bit version of dump1090-fa, piaware, piaware-web, and dump978-fa.

STEP-3: Install feeders of other sites (Flightradar24, Planefinnder, Radarbox24, Adsbexchange, Graphs) on 64-bit OS on RPi 3 / 4 with (1) 64-bit Raspberry Pi OS Bullseye OR (2) 64-bit DietPi Bullseye OR (3) 64-bit Ubuntu 20 server Focal Fossa for RPi

 

Thank you. I was able to follow your instructions and links and got piaware working on the 64 bit lite version. But 1090 is not working correctly. Here is a report of piaware-status:

pi@raspberrypi:~ $ sudo piaware-status
PiAware master process (piaware) is running with pid 738.
PiAware ADS-B client (faup1090) is running with pid 1159.
PiAware ADS-B UAT client (faup978) is running with pid 1148.
PiAware mlat client (fa-mlat-client) is running with pid 765.
Local ADS-B receiver (dump1090-fa) is running with pid 1109.
Local ADS-B UAT receiver (dump978-fa) is running with pid 1127.

dump1090-fa (pid 1109) is listening for ES connections on port 30005.
dump978-fa (pid 1127) is listening for UAT connections on port 30978.
faup1090 is connected to the ADS-B receiver.
faup978 is connected to the ADS-B UAT receiver.
piaware is connected to FlightAware.

dump978 is producing data on localhost:30978.
dump1090 is NOT producing data on localhost:30005.

Your feeder ID is 266afada-84ee-457f-90eb-e8267d9b1a63 (configured at /etc/piaware.conf:7)

Here is the report of rtl_test -t

pi@raspberrypi:~ $ sudo rtl_test -t
Found 2 device(s):
0: Realtek, RTL2832U, SN: 00000978
1: Realtek, RTL2832U, SN: 00001090

Using device 0: Generic RTL2832U
usb_claim_interface error -6
Failed to open rtlsdr device #0.

Can you please give me some help on getting 1090 working?

Thanks again for your help. I sent an e-mail to support@flightaware last night and their answer to my problem was that I had not claimed my feeder. I sent them the install log and they totally missed the real problem, that I had 64 bit Bullseye. You not only provided the correct answer and solution but you answered faster. I can’t say Thanks enough.

If i am not wrong the tool needs exclusive access to the USB stick. That requires that you stop dump1090-fa for the time beeing.

(1) Did you REBOOT the RPI after installing dump1090-fa? The dump1090-fa wont detect the dongle without rebooting the Pi after installing it.
Please REBOOT the RPI, then check again.

(2) Please post output of following command:

sudo systemctl status dump1090-fa    

(3) To test the dongle of dump1090-fa, first stop dump1090-fa (and piaware also as it may try to restart dump1090-fa). After that do the test, and after test restart both:

sudo systemctl stop piaware dump1090-fa

rtl_test -t   

sudo systemctl restart piaware dump1090-fa   

 

pi@raspberrypi:~ $ sudo systemctl status dump1090-fa
● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; vendor preset: >
Active: active (running) since Thu 2022-02-17 13:21:36 CST; 1min 10s ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Main PID: 858 (dump1090-fa)
Tasks: 3 (limit: 8987)
CPU: 11.941s
CGroup: /system.slice/dump1090-fa.service
└─858 /usr/bin/dump1090-fa --quiet --device-type rtlsdr --device-index 00>

Feb 17 13:21:36 raspberrypi dump1090-fa[858]: Found Rafael Micro R820T tuner
Feb 17 13:21:36 raspberrypi dump1090-fa[858]: rtlsdr: tuner gain set to about 58.6 dB >
Feb 17 13:21:36 raspberrypi dump1090-fa[858]: adaptive: using 50% duty cycle
Feb 17 13:21:36 raspberrypi dump1090-fa[858]: adaptive: enabled adaptive gain control >
Feb 17 13:21:36 raspberrypi dump1090-fa[858]: adaptive: enabled dynamic range control,>
Feb 17 13:21:36 raspberrypi dump1090-fa[858]: Allocating 4 zero-copy buffers
Feb 17 13:21:47 raspberrypi dump1090-fa[858]: adaptive: available dynamic range (28.3d>
Feb 17 13:21:47 raspberrypi dump1090-fa[858]: adaptive: changing gain from 58.6dB (ste>
Feb 17 13:21:47 raspberrypi dump1090-fa[858]: rtlsdr: tuner gain set to 49.6 dB (gain >
Feb 17 13:21:57 raspberrypi dump1090-fa[858]: adaptive: available dynamic range (38.2d>

pi@raspberrypi:~ $ rtl_test -t
Found 2 device(s):
0: Realtek, RTL2832U, SN: 00001090
1: Realtek, RTL2832U, SN: 00000978

Using device 0: Generic RTL2832U
Detached kernel driver
Found Rafael Micro R820T tuner
Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6
[R82XX] PLL not locked!
Sampling at 2048000 S/s.
No E4000 tuner found, aborting.
Reattached kernel driver

pi@raspberrypi:~ $ sudo piaware-status
PiAware master process (piaware) is running with pid 958.
PiAware ADS-B client (faup1090) is running with pid 988.
PiAware ADS-B UAT client (faup978) is running with pid 991.
PiAware mlat client (fa-mlat-client) is running with pid 985.
Local ADS-B receiver (dump1090-fa) is running with pid 959.
Local ADS-B UAT receiver (dump978-fa) is running with pid 527.

dump1090-fa (pid 959) is listening for ES connections on port 30005.
dump978-fa (pid 527) is listening for UAT connections on port 30978.
faup1090 is connected to the ADS-B receiver.
faup978 is connected to the ADS-B UAT receiver.
piaware is connected to FlightAware.

dump978 is producing data on localhost:30978.
dump1090 is NOT producing data on localhost:30005.

Your feeder ID is 266afada-84ee-457f-90eb-e8267d9b1a63 (configured at /etc/piaware.conf:7)
pi@raspberrypi:~ $

There are the results

  1. How did you install dump1090-fa, by using script to build it from source code, OR by command sudo apt install dump1090-fa?

  2. What is Model of your RPi?

  3. What is output of following commands?

uname -m

cat /etc/os-release  

I installed it with sudo apt install dump1090-fa

Here is the output

pi@raspberrypi:~ $ uname -m
aarch64
pi@raspberrypi:~ $ cat /etc/os-release
PRETTY_NAME=“Debian GNU/Linux 11 (bullseye)”
NAME=“Debian GNU/Linux”
VERSION_ID=“11”
VERSION=“11 (bullseye)”
VERSION_CODENAME=bullseye
ID=debian
HOME_URL=“https://www.debian.org/”
SUPPORT_URL=“Debian -- User Support”
BUG_REPORT_URL=“https://bugs.debian.org/”
pi@raspberrypi:~ $

It is a raspberrypi 4

Not sure if this is the root cause of your problems.
I think it’s similar to that one:

Gentlemen,

I think I found the problem. The antenna was not connected. It would be a long story but there is a connection in the attic and I had the coax that comes to the raspberrypi connected to the coax that went outside. So I just moved the antenna outside, that is how I found the problem, and now piaware-status reports:

pi@raspberrypi:~ $ sudo piaware-status
PiAware master process (piaware) is running with pid 729.
PiAware ADS-B client (faup1090) is running with pid 797.
PiAware ADS-B UAT client (faup978) is running with pid 800.
PiAware mlat client (fa-mlat-client) is running with pid 794.
Local ADS-B receiver (dump1090-fa) is running with pid 536.
Local ADS-B UAT receiver (dump978-fa) is running with pid 537.

dump1090-fa (pid 536) is listening for ES connections on port 30005.
dump978-fa (pid 537) is listening for UAT connections on port 30978.
faup1090 is connected to the ADS-B receiver.
faup978 is connected to the ADS-B UAT receiver.
piaware is connected to FlightAware.

dump978 is producing data on localhost:30978.
dump1090 is producing data on localhost:30005.

Your feeder ID is 266afada-84ee-457f-90eb-e8267d9b1a63 (configured at /etc/piaware.conf:7)
pi@raspberrypi:~ $

I don’t see any aircraft yet but I will give it a few minutes.

I can’t thank you enough.

2 Likes

I do have one more question. In your instructions you say that when Piaware 7 becomes available for 64 bit, that we need to get rid of your depositary. When I installed Piaware on this card, I did it all from flightaware. Do I need to get rid of their depositary?

no you don’t need to get rid of ther repository.
If you would do so it won’t be able to find future updates from flightaware.

abcd567 pointed this out in order to make sure people download from flightaware and not from his repository on github

Not necessary if you can tolerate the following harmless but annoying notice during updates

N: Skipping acquire of configured file
‘piaware/binary-arm64/Packages’ as repository ‘http://flightaware.com/adsb/piaware/files/packages bullseye InRelease’ doesn’t support architecture ‘arm64’

 

Your comment is NOT APPLICABLE NOW. It will become applicable only AFTER Flightaware makes available 64 bit packages from their repository.

 

I stand corrected sir. No harm intended by my remark.

1 Like

My piaware is working fine now. I have been getting many aircraft on 1090 since I moved the antenna outside.

Many thinks to those who helped. Without the help from this group, it would not be working.

1 Like

Congratulations. :clap: :+1:
Glad to know your 64-bit piaware system is up and running.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.