[OUTDATED] Piaware ver 6 with Adaptive Gain Control - Install it on x86_64 Machines with Ubuntu 20, Debian 10 &11, and on RPi 2, 3, 4 with Raspbian Buster (32-bit and 64-bit) and DietPi Bullseye (32-bit & 64-bit)

Yes which is why after changing OS again back to Armbian Bullseye on suggestion from obj that it could by a system problem with that specific error, that error message has now gone.

I know adaptive gain is designed to use with SDR’s but is there any magic to incorporate Airspy units to be able to run with this???

Adaptive Gain: DietPi_RPi-ARMv8-Bullseye.img / RPi Model 4

Dongle: RadarBox24 FlightStick Green (Builtin SAW+LNA)
Antenna: V-Stub whip on mag-mount base on window sill.

https://flightaware.com/adsb/stats/user/abcd567#stats-76000

 

Messages > -3dBFS (6.2% of messages)

CLICK ON IMAGE TO SEE FULL SIZE

dietpi@DietPi:~$ sudo journalctl -u dump1090-fa | grep gain
Sep 29 17:39:24 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Sep 29 17:39:24 DietPi dump1090-fa[475]: adaptive: enabled adaptive gain control with gain limits 0.0dB (step 0) .. 58.6dB (step 29)
Sep 29 17:39:45 DietPi dump1090-fa[475]: adaptive: changing gain from 58.6dB (step 29) to 49.6dB (step 28) because: probing dynamic range gain lower bound
Sep 29 17:39:45 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to 49.6 dB (gain step 28)
Sep 29 18:39:55 DietPi dump1090-fa[475]: adaptive: start periodic scan for acceptable dynamic range at increased gain
Sep 29 18:39:55 DietPi dump1090-fa[475]: adaptive: changing gain from 49.6dB (step 28) to 58.6dB (step 29) because: periodic re-probing of dynamic range gain upper bound
Sep 29 18:39:55 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Sep 29 18:40:05 DietPi dump1090-fa[475]: adaptive: changing gain from 58.6dB (step 29) to 49.6dB (step 28) because: probing dynamic range gain lower bound
Sep 29 18:40:05 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to 49.6 dB (gain step 28)
Sep 29 19:40:15 DietPi dump1090-fa[475]: adaptive: start periodic scan for acceptable dynamic range at increased gain
Sep 29 19:40:15 DietPi dump1090-fa[475]: adaptive: changing gain from 49.6dB (step 28) to 58.6dB (step 29) because: periodic re-probing of dynamic range gain upper bound
Sep 29 19:40:15 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Sep 29 19:40:25 DietPi dump1090-fa[475]: adaptive: changing gain from 58.6dB (step 29) to 49.6dB (step 28) because: probing dynamic range gain lower bound
Sep 29 19:40:25 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to 49.6 dB (gain step 28)
Sep 29 20:40:35 DietPi dump1090-fa[475]: adaptive: start periodic scan for acceptable dynamic range at increased gain
Sep 29 20:40:35 DietPi dump1090-fa[475]: adaptive: changing gain from 49.6dB (step 28) to 58.6dB (step 29) because: periodic re-probing of dynamic range gain upper bound
Sep 29 20:40:35 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Sep 29 20:40:45 DietPi dump1090-fa[475]: adaptive: changing gain from 58.6dB (step 29) to 49.6dB (step 28) because: probing dynamic range gain lower bound
Sep 29 20:40:45 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to 49.6 dB (gain step 28)
Sep 29 21:40:54 DietPi dump1090-fa[475]: adaptive: start periodic scan for acceptable dynamic range at increased gain
Sep 29 21:40:54 DietPi dump1090-fa[475]: adaptive: changing gain from 49.6dB (step 28) to 58.6dB (step 29) because: periodic re-probing of dynamic range gain upper bound
Sep 29 21:40:54 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Sep 29 21:41:04 DietPi dump1090-fa[475]: adaptive: changing gain from 58.6dB (step 29) to 49.6dB (step 28) because: probing dynamic range gain lower bound
Sep 29 21:41:04 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to 49.6 dB (gain step 28)
Sep 29 22:41:14 DietPi dump1090-fa[475]: adaptive: start periodic scan for acceptable dynamic range at increased gain
Sep 29 22:41:14 DietPi dump1090-fa[475]: adaptive: changing gain from 49.6dB (step 28) to 58.6dB (step 29) because: periodic re-probing of dynamic range gain upper bound
Sep 29 22:41:14 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Sep 29 22:41:24 DietPi dump1090-fa[475]: adaptive: changing gain from 58.6dB (step 29) to 49.6dB (step 28) because: probing dynamic range gain lower bound
Sep 29 22:41:24 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to 49.6 dB (gain step 28)
Sep 29 23:41:34 DietPi dump1090-fa[475]: adaptive: start periodic scan for acceptable dynamic range at increased gain
Sep 29 23:41:34 DietPi dump1090-fa[475]: adaptive: changing gain from 49.6dB (step 28) to 58.6dB (step 29) because: periodic re-probing of dynamic range gain upper bound
Sep 29 23:41:34 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Sep 29 23:41:44 DietPi dump1090-fa[475]: adaptive: changing gain from 58.6dB (step 29) to 49.6dB (step 28) because: probing dynamic range gain lower bound
Sep 29 23:41:44 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to 49.6 dB (gain step 28)
Sep 30 00:41:54 DietPi dump1090-fa[475]: adaptive: start periodic scan for acceptable dynamic range at increased gain
Sep 30 00:41:54 DietPi dump1090-fa[475]: adaptive: changing gain from 49.6dB (step 28) to 58.6dB (step 29) because: periodic re-probing of dynamic range gain upper bound
Sep 30 00:41:54 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Sep 30 00:42:04 DietPi dump1090-fa[475]: adaptive: changing gain from 58.6dB (step 29) to 49.6dB (step 28) because: probing dynamic range gain lower bound
Sep 30 00:42:04 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to 49.6 dB (gain step 28)
Sep 30 01:42:14 DietPi dump1090-fa[475]: adaptive: start periodic scan for acceptable dynamic range at increased gain
Sep 30 01:42:14 DietPi dump1090-fa[475]: adaptive: changing gain from 49.6dB (step 28) to 58.6dB (step 29) because: periodic re-probing of dynamic range gain upper bound
Sep 30 01:42:14 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Sep 30 01:42:24 DietPi dump1090-fa[475]: adaptive: changing gain from 58.6dB (step 29) to 49.6dB (step 28) because: probing dynamic range gain lower bound
Sep 30 01:42:24 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to 49.6 dB (gain step 28)
Sep 30 02:42:34 DietPi dump1090-fa[475]: adaptive: start periodic scan for acceptable dynamic range at increased gain
Sep 30 02:42:34 DietPi dump1090-fa[475]: adaptive: changing gain from 49.6dB (step 28) to 58.6dB (step 29) because: periodic re-probing of dynamic range gain upper bound
Sep 30 02:42:34 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Sep 30 02:42:44 DietPi dump1090-fa[475]: adaptive: changing gain from 58.6dB (step 29) to 49.6dB (step 28) because: probing dynamic range gain lower bound
Sep 30 02:42:44 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to 49.6 dB (gain step 28)
Sep 30 03:42:54 DietPi dump1090-fa[475]: adaptive: start periodic scan for acceptable dynamic range at increased gain
Sep 30 03:42:54 DietPi dump1090-fa[475]: adaptive: changing gain from 49.6dB (step 28) to 58.6dB (step 29) because: periodic re-probing of dynamic range gain upper bound
Sep 30 03:42:54 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Sep 30 03:43:04 DietPi dump1090-fa[475]: adaptive: changing gain from 58.6dB (step 29) to 49.6dB (step 28) because: probing dynamic range gain lower bound
Sep 30 03:43:04 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to 49.6 dB (gain step 28)
Sep 30 04:43:13 DietPi dump1090-fa[475]: adaptive: start periodic scan for acceptable dynamic range at increased gain
Sep 30 04:43:13 DietPi dump1090-fa[475]: adaptive: changing gain from 49.6dB (step 28) to 58.6dB (step 29) because: periodic re-probing of dynamic range gain upper bound
Sep 30 04:43:13 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Sep 30 04:43:23 DietPi dump1090-fa[475]: adaptive: changing gain from 58.6dB (step 29) to 49.6dB (step 28) because: probing dynamic range gain lower bound
Sep 30 04:43:23 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to 49.6 dB (gain step 28)
Sep 30 05:43:33 DietPi dump1090-fa[475]: adaptive: start periodic scan for acceptable dynamic range at increased gain
Sep 30 05:43:33 DietPi dump1090-fa[475]: adaptive: changing gain from 49.6dB (step 28) to 58.6dB (step 29) because: periodic re-probing of dynamic range gain upper bound
Sep 30 05:43:33 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Sep 30 05:43:43 DietPi dump1090-fa[475]: adaptive: changing gain from 58.6dB (step 29) to 49.6dB (step 28) because: probing dynamic range gain lower bound
Sep 30 05:43:43 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to 49.6 dB (gain step 28)
Sep 30 06:43:53 DietPi dump1090-fa[475]: adaptive: start periodic scan for acceptable dynamic range at increased gain
Sep 30 06:43:53 DietPi dump1090-fa[475]: adaptive: changing gain from 49.6dB (step 28) to 58.6dB (step 29) because: periodic re-probing of dynamic range gain upper bound
Sep 30 06:43:53 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Sep 30 06:44:03 DietPi dump1090-fa[475]: adaptive: changing gain from 58.6dB (step 29) to 49.6dB (step 28) because: probing dynamic range gain lower bound
Sep 30 06:44:03 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to 49.6 dB (gain step 28)
Sep 30 07:44:13 DietPi dump1090-fa[475]: adaptive: start periodic scan for acceptable dynamic range at increased gain
Sep 30 07:44:13 DietPi dump1090-fa[475]: adaptive: changing gain from 49.6dB (step 28) to 58.6dB (step 29) because: periodic re-probing of dynamic range gain upper bound
Sep 30 07:44:13 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Sep 30 07:44:23 DietPi dump1090-fa[475]: adaptive: changing gain from 58.6dB (step 29) to 49.6dB (step 28) because: probing dynamic range gain lower bound
Sep 30 07:44:23 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to 49.6 dB (gain step 28)
Sep 30 08:44:33 DietPi dump1090-fa[475]: adaptive: start periodic scan for acceptable dynamic range at increased gain
Sep 30 08:44:33 DietPi dump1090-fa[475]: adaptive: changing gain from 49.6dB (step 28) to 58.6dB (step 29) because: periodic re-probing of dynamic range gain upper bound
Sep 30 08:44:33 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Sep 30 08:44:43 DietPi dump1090-fa[475]: adaptive: changing gain from 58.6dB (step 29) to 49.6dB (step 28) because: probing dynamic range gain lower bound
Sep 30 08:44:43 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to 49.6 dB (gain step 28)
Sep 30 09:44:53 DietPi dump1090-fa[475]: adaptive: start periodic scan for acceptable dynamic range at increased gain
Sep 30 09:44:53 DietPi dump1090-fa[475]: adaptive: changing gain from 49.6dB (step 28) to 58.6dB (step 29) because: periodic re-probing of dynamic range gain upper bound
Sep 30 09:44:53 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Sep 30 09:45:03 DietPi dump1090-fa[475]: adaptive: changing gain from 58.6dB (step 29) to 49.6dB (step 28) because: probing dynamic range gain lower bound
Sep 30 09:45:03 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to 49.6 dB (gain step 28)
Sep 30 10:45:13 DietPi dump1090-fa[475]: adaptive: start periodic scan for acceptable dynamic range at increased gain
Sep 30 10:45:13 DietPi dump1090-fa[475]: adaptive: changing gain from 49.6dB (step 28) to 58.6dB (step 29) because: periodic re-probing of dynamic range gain upper bound
Sep 30 10:45:13 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Sep 30 10:45:23 DietPi dump1090-fa[475]: adaptive: changing gain from 58.6dB (step 29) to 49.6dB (step 28) because: probing dynamic range gain lower bound
Sep 30 10:45:23 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to 49.6 dB (gain step 28)
Sep 30 11:45:33 DietPi dump1090-fa[475]: adaptive: start periodic scan for acceptable dynamic range at increased gain
Sep 30 11:45:33 DietPi dump1090-fa[475]: adaptive: changing gain from 49.6dB (step 28) to 58.6dB (step 29) because: periodic re-probing of dynamic range gain upper bound
Sep 30 11:45:33 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Sep 30 11:45:43 DietPi dump1090-fa[475]: adaptive: changing gain from 58.6dB (step 29) to 49.6dB (step 28) because: probing dynamic range gain lower bound
Sep 30 11:45:43 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to 49.6 dB (gain step 28)
Sep 30 12:45:52 DietPi dump1090-fa[475]: adaptive: start periodic scan for acceptable dynamic range at increased gain
Sep 30 12:45:52 DietPi dump1090-fa[475]: adaptive: changing gain from 49.6dB (step 28) to 58.6dB (step 29) because: periodic re-probing of dynamic range gain upper bound
Sep 30 12:45:52 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Sep 30 12:46:02 DietPi dump1090-fa[475]: adaptive: changing gain from 58.6dB (step 29) to 49.6dB (step 28) because: probing dynamic range gain lower bound
Sep 30 12:46:02 DietPi dump1090-fa[475]: rtlsdr: tuner gain set to 49.6 dB (gain step 28)
dietpi@DietPi:~$

I was running the latest Piaware 6.1 on my Ubuntu x86_64. Checking for updates I get offered one and I did accept it:

The following packages will be upgraded:
tcl-tls
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 64.7 kB of archives.
After this operation, 3,072 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 Index of /ubuntu focal/universe amd64 tcl-tls amd64 1.7.20-1 [64.7 kB]
Fetched 64.7 kB in 0s (661 kB/s)
(Reading database … 222739 files and directories currently installed.)
Preparing to unpack …/tcl-tls_1.7.20-1_amd64.deb …
Unpacking tcl-tls:amd64 (1.7.20-1) over (1.7.16-1+fa1) …
Setting up tcl-tls:amd64 (1.7.20-1) …

OK, nothing seems out of ordinary… except when I check the FA stats page. Big banner:

PiAware Update 6.1 Available
The following sites do not have the latest PiAware Software:

And feeder type is shown as: PiAware (Debian Package Add-on) 3.7.2
What’s going on?

So I have re-installed piaware and I see that all is good:
PiAware (Debian Package Add-on) 6.1
Except that tcl-tls it reverted to earlier version:

~$ sudo apt list --upgradable
Listing… Done
tcl-tls/focal 1.7.20-1 amd64 [upgradable from: 1.7.16-1+fa1]
N: There is 1 additional version. Please use the ‘-a’ switch to see it

Should I hold it back? Well… I did.
sudo apt-mark hold tcl-tls

When my bash-script to install piaware runs, it first builts tcl-tls from following source-code at Flightaware repository:

https://github.com/flightaware/tcltls-rebuild

As you can see, the script does not install tcl-tls from Ubuntu or Debian repository. It builds a special version tcl-tls-rebuilt from Flightaware provided source code. Replacing this special version of tcl-tls from Debian / Ubuntu repository during upgrade caused the mess you experienced.

:+1: :+1: :+1:

You did the right thing to run bash-script to re-install piaware, which also reinstalled tcl-tls-rebuild version.

You also did a right thing to put tcl-tls special version on hold by command sudo apt-mark hold tcl-tls, so that it will be protected from getting upgraded during future auto or manual upgrades.

2 Likes

I think the upgrade to 1.7.20 should be mostly harmless. I haven’t looked at if upstream have fixed the build or not. If they haven’t you may experience piaware sometimes hard-hanging if there are network problems (this is what the rebuild fixes) but it should otherwise generally work ok.

I think the “3.7.2” problem is something different.

1 Like

I am running readsb, not dump1090-fa maybe that matters?
The only advantage to that is the max distance marker.

I have been reading up on the advantages/disadvantages of using Adaptive Dynamic Range over a series of threads but as is usual for me these days the more I read the more confused I get! :thinking:

The first step seems to be issuing sudo systemctl status dump1090-fa but when I do this I get;

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: enabled)
   Active: active (running) since Sat 2022-01-29 08:17:07 GMT; 1 weeks 5 days ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 570 (dump1090-fa)
    Tasks: 3 (limit: 4915)
   CGroup: /system.slice/dump1090-fa.service
           └─570 /usr/bin/dump1090-fa --quiet --device-type rtlsdr --gain 60 --fix --lat xx.xxxxx --lon x.xxxxx --max-range 360 --net-ro-port 30002 --net-sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 30005 --json-location-accuracy 1 --lat xx.xxxxxx --lon xx.xxxxxx --write-json /run/dump1090-fa

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

Not sure why the Journal should have been rotated and the Log incomplete or unavailable nor if it is normal for my coordinates to appear twice - first to 5 decimal places and secondly to 6 decimal places?

I can see from both the output above and in /etc/default/dump1090-fa that RECEIVER_GAIN=60 which seems high to me but having said that I have no issues with coverage seeing out to 250 miles and I also see aircraft directly above me.

I notice from Graphs that my percentage of messages >-3dBFS is usually around 13-16% which seems higher than the ideal 5% from what I have read and look like this if it helps?

Just looking for some advice whether I would be better off setting Adaptive Dynamic Range from no to yes and whether I should play around with any other settings to optimise further?

I realise I should at least make some changes and then monitor the results which I intend to do but before I alter anything it would be good to have a clue of where to start and what I am doing! :crazy_face:

Powered via PoE the Pi4/8GB dedicated to ADS-B is in the loft hanging on 8m Westflex 103 connected to a Watson Radar Extender mounted on a 5m pole on the gable end of the house 100m ASL. I am currently using a RadarBox FlightStick (although I do have the FA Pro Stick plus which I always intended to test against the Flightstick but never got around to it and an AirSpy Mini but have been too frightened to alter my configs to get that to work :face_with_raised_eyebrow:), with no external LNA/Filter of any sort (although I do have a Kuhne 1090 kicking around somewhere) and am thinking of buying the dark blue narrow band FA 1090 to try here in the UK as I can imagine a lot of RFI flying around the vicinity but before I do I will need to get a handle on that lovely yellow/black waterfall graph showing if/where/how much interference I might be receiving.

I’m just looking to optimize my system but don’t want to impact anything as it has been working seamlessly sending data to RadarBox, FR24, FA and ADS-B Exchange for over a year now but you know what it’s like…I’m a bloke so always looking to make things bigger/better/faster! :laughing:

Thanks & kind regards,
-=Glyn=-

trying hard to use Raspberry Desktop on a thin client and save my rasp-pi for another FA location that power / size is important.
I tried to run the install but copy/paste the script I get : :~/Flightaware $ sudo bash -c “$(wget -O - https://raw.githubusercontent.com/abcd567a/piaware-ubuntu20-amd64/master/piaware.sh)”
–2022-06-29 16:28:21-- https://raw.githubusercontent.com/abcd567a/piaware-ubuntu20-amd64/master/piaware.sh
Resolving raw.githubusercontent.com (raw.githubusercontent.com)… 185.199.109.133, 185.199.110.133, 185.199.111.133, …
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.199.109.133|:443… connected.
HTTP request sent, awaiting response… 404 Not Found
2022-06-29 16:28:21 ERROR 404: Not Found.

@RdRocket16

You are using an outdated thread. Use one of these two:

OPTION-1 : Build & Install Package from source code

https://github.com/abcd567a/piaware-ubuntu20-amd64/blob/master/README.md

 

OPTION-2 : Install Prebuild Packages

Package Install of Piaware ver 7.2 on ARM64 / AARCH64 and AMD64 / x86_64 Machines

For Thin Client, please see this thread:

FYI: Alternatives to Raspberry Pi for this hobby

 

maybe im a bit lost, but I tried your scripts for Debian and I get an error installing piaware only:

I also tried, out of a bit of confusion, this script too - it fails also.

output from the first link:
Building dependency tree
Reading state information… Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
piaware:amd64 : Depends: libboost-program-options1.74.0:amd64 (>= 1.74.0) but it is not installable
Depends: libboost-regex1.74.0-icu67:amd64 but it is not installable
Depends: libc6:amd64 (>= 2.29) but 2.28-10+deb10u1 is to be installed
Depends: libffi7:amd64 (>= 3.3~20180313) but it is not installable
Depends: libgcc-s1:amd64 (>= 3.0) but it is not installable
Depends: libmpdec3:amd64 but it is not installable
Depends: libreadline8:amd64 (>= 7.0~beta) but it is not installable
Depends: tcllib:amd64 but it is not installable
E: Unable to correct problems, you have held broken packages.
this is from a brand new install

opps didnt see this initially.
but I tried both prebuilt 64 bit pi os and Debian 11 And and they both still fail
sorry, Im still learning linux and only barely understand the differences - I believe the Bullseye desktop version of Pi is a Debian distro -
however, it keeps saying I have these broken packages.

@RdRocket16

Can you please post output of following commands?

uname -a  

cat /etc/os-release  

lsb_release -a  

Ahhhh
I see.

i@raspberry:~/Downloads $ uname -a
Linux raspberry 4.19.0-13-amd64 #1 SMP Debian 4.19.160-2 (2020-11-28) x86_64 GNU/Linux
pi@raspberry:~/Downloads $
pi@raspberry:~/Downloads $
pi@raspberry:~/Downloads $
pi@raspberry:~/Downloads $ cat /etc/os-release
PRETTY_NAME=“Debian GNU/Linux 10 (buster)”
NAME=“Debian GNU/Linux”
VERSION_ID=“10”
VERSION=“10 (buster)”
VERSION_CODENAME=buster
ID=debian
HOME_URL=“https://www.debian.org/
SUPPORT_URL=“Debian -- User Support
BUG_REPORT_URL=“https://bugs.debian.org/
pi@raspberry:~/Downloads $
pi@raspberry:~/Downloads $
pi@raspberry:~/Downloads $
pi@raspberry:~/Downloads $ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 10 (buster)
Release: 10
Codename: buster

I thought since the Pi OS was on bullseye so was this.
Oops.
I think I might delete this os and try your suggestion of dietpi with your script for that.
:slight_smile: thanks for the help! It’s definitely a learning curve and I’m jumping distributions trying to find the right options!

@RdRocket16

I think this is the OS you have installed

 

You may modify automated installation script to change in it Bullseye to Buster, then run it on the one you have installed.

However I won’t recommend it as Buster is outdated OS. Better install Debian or DietPi Bullseye

piaware has some dependencies that can cause issues (mainly tcl i think).

I can’t help you with building piaware, but if you want a decoder and graphs, this guide works on any debian based system (which includes ubuntu, raspbian, dietpi):
https://github.com/wiedehopf/adsb-wiki/wiki/Raspbian-Lite:-ADS-B-receiver

But i’m sure @abcd567 scripts to build dump1090-fa work just as well :slight_smile:

@wiedehopf
@RdRocket16

STEP-1: Downloaded current installation script for piaware and dump1090-fa:

wget https://raw.githubusercontent.com/abcd567a/piaware-ubuntu20-amd64/master/install-piaware.sh

wget https://raw.githubusercontent.com/abcd567a/piaware-ubuntu20-amd64/master/install-dump1090-fa.sh

STEP-2: Downloaded scripts are for current OS Bullseye. Replaced all occurrences of word bullseye by buster in the above two downloaded script files by following commands:

sudo sed -i 's/bullseye/buster/g' install-piaware.sh

sudo sed -i 's/bullseye/buster/g' install-dump1090-fa.sh

STEP-3: Ran the modified installation scripts

sudo bash install-piaware.sh

sudo bash install-dump1090-fa.sh

 

 

CLICK ON SCREENSHOT TO SEE LARGER SIZE
CLICK AGAIN TO SEE FULL SIZE

 

 

1 Like

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