Bookworm PiAware 10 SD Card Images Now Available for Download!

[SweetPea11]

@LawrenceHill

I use Raspberry Pi Connect lite to connect to my pi3 without a gui. It gives you a terminal session. You need Bookworm on the pi3 but it works just fine

Thanks, good to know.

[abcd567]

@tomvdhorst

I’m not using 978 so I don’t understand why it is failing.

The piaware package contains following helpers, irrespective of what you use as decoder

• faup1090
• faup978
• fa-mlat-clent

The failure occured during making of faup978 helper. Please see below your error message.

@tomvdhorst

make[2]: *** [: faup978_main.o] Error 1

Run the script for piaware again. Most likely it will succeed.

 

[dvsvejk]

Maybe you are running out of memory?

I built from source all the FA packages on my system and was able to upgrade them without an issue, but yeah, when it hit the bit about faup978 the package build process slowed down markedly and took a few minutes to move forward.

[tomvdhorst]

Well gave it another go, rebooted prior to the installation when logged in prior to the reboot I saw that the MEM and SWAP file were completly in use. So there might have been an memory issue but since the others did run fine that didn’t come to mind this morning.

Ran the command again after the reboot and this time it completed without errors.

So my guess the rootcause of the error was operator induced since I didn’t do the reboot after the update of dump1090-fa as advised by the script

Thanks both for the guidance and advice @abcd567 @dvsvejk

[jimMerk2]

I got dump1090-fa, piaware and piaware-web version 10 working but
dump978-fa was a no-go. Got the following error:

g++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
make[2]: *** [<builtin>: dump978_main.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/home/pi/dump978/package-bookworm'
dh_auto_build: error: make -j4 "INSTALL=install --strip-program=true" VERSION=10.0 dump978-fa skyaware978 returned exit code 2
make[1]: *** [debian/rules:13: override_dh_auto_build] Error 2
make[1]: Leaving directory '/home/pi/dump978/package-bookworm'
make: *** [debian/rules:22: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
[ERROR] Error in line 113 when executing: sudo dpkg-buildpackage -b --no-sign

The last line before the error was:

g++ -g -O2 -ffile-prefix-map=/home/pi/dump978/package-bookworm=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -std=c++11 -Wall -Wno-psabi -Werror -O2 -g -Ilibs -Wdate-time -D_FORTIFY_SOURCE=2 -DVERSION=\"10.0\"  -c -o soapy_source.o soapy_source.cc

[SweetPea11]

@LawrenceHill

I use Raspberry Pi Connect lite to connect to my pi3 without a gui. It gives you a terminal session. You need Bookworm on the pi3 but it works just fine.

I have installed it on a PiZero2W and a Pi3B with great sucess.

Also running on Pi4 and Pi5 all running Bookworm.

Thanks for the suggestion.

S

[abcd567]

@jimMerk2

This may be due to memory (ram+swap) being full.
Please reboot Pi and try again.
Please see these posts:

@tomvdhorst

g++: fatal error: Killed signal terminated program cc1plus

@dvsvejk

Maybe you are running out of memory?

@tomvdhorst

Well gave it another go, rebooted prior to the installation when logged in prior to te reboot I saw that the MEM and SWAP file were completly in use. So there might have been an memory issue but since the others did run fine that didn’t come to mind this morning.

Ran the command again after the reboot and this time it completed without errors

[jimMerk2]

Yeah, it could be a memory problem. This is on a 2 GB RPi4. I’ve tried to compile it several times and sometimes it just freezes on that line I posted above (i.e doesn’t even show an error message). I’ll probably have to wait until a pre-complied version is available.

[dvsvejk]

A default setting in dpkg-buildpackage is to detect the number of processors on your system and match that to how many jobs can run in parallel. I’m guessing the number of jobs is too many for the limited memory you have (see the ‘waiting for unfinished jobs’ error msg in the log you posted).

One idea is to add -j1 to the dpkg-buildpackage command which will force jobs to run serially instead of in parallel. It will take longer to compile, but it may get you around the memory issue.

[abcd567]

@jimMerk2
@dvsvejk
@tomvdhorst

Building dump978-fa is memory-intensive, and fails if sufficient memory is not available

Anyone faced with memory problem during building of dump978-fa can increase memory by create a temporary swap file of say 2GB, so that total memory becomes 2GB ram + 0.5 GB swap +2 GB swa-file = 4.5 GB.

After the dump978-fa package is built successfully, the swap-file created by user can be deleted to free up disk space.

I have described in detail the method to create a swap-file in following post:

Trouble with PiAware 8.2 on Ubuntu 20.04 Installed on Odroid N2

I found an easy method of solving memory shortage on my OrangePiPC, running Armbian Bullseye. It has 1 GB RAM and 0.5 GB swap, i.e. total 1.5 GB which proved insufficient to build dump978-fa from source-code. As my microSD card has enough free space, I decided to create a 1 GB swap file, making total memory 2.5 GB (1 GB RAM + 0.5 GB original swap + 1 GB swap file created by me). With this arrtangement I could build dump978-fa. ORIGINAL MEMORY Click on screenshot to see larger size [image] …

 

NOTE:
(1) - On RPi, you cannot switch user to root. Instead use sudo with all commands mentioned in above noted post.

(2) You cannot delete swap file created by you unless you make swap off.
To delete the swap file you created, use following commands

sudo swapoff /my-swap
sudo rm /my-swap

Open file fstab for editing
sudo nano /etc/fstab

In above file, delete following line which you have added while creating your swap file
/my-swap none swap sw 0 0

 

[TonyLeverett]

I’m running Bookworm on a Pi4b, and running as root is possible.

[TonyLeverett]

For you (and any others interested), here’s a couple of ‘useful’ nuggets.
Go to the bash shell (either locally, or using ssh) and type the following line:
alias piaware=“journalctl -f -u piaware” - I’ve used ‘piaware’, but you can select any term you like.
then press Enter. clear the screen (clear), then invoke the alias typed above and you’ll get an update about the messages sent, receiver status, displayed, which is updated evert 5 minutes.
Use Ctrl-C to exit back to a bash prompt.

[abcd567]

@TonyLeverett

I’m running Bookworm on a Pi4b, and running as root is possible.

In Raspberry Pi OS, by default the password for root is unset. Swithing to user “root” is not possible unless password for root is first set. In RPi OS this is not considered good practice, and a better option is to use sudo with a non-root user such as “pi”

The idea is that if you are in front of a login prompt of someone else machine, you have to guess two things to get in: a user name and a password

If root logins are allowed you know every machine has a “root” user so that is one less thing to guess. Much easier, especially important if you have ssh enabled on the internet.

[jimMerk2]

Thanks, I added a 2 GB swap file and was able to successfully build dump978-fa.

I was going to ask why I should remove the swap file after using it. However, I found out that if I just left it in, dump1090-fa would not produce any messages. Don’t know why that was, but then removed the swap file and dump1090-fa started working again.

[NickWan]

How did you find that NetworkManager disabled wifi? Did you just run “nmcli radio”?
How did you turn the wireless LAN on?

Bookworm disables some devices by default. We’ve changed stuff to have wifi enabled by default.
So I’m curious why it was disabled for you.

[suffolk3000]

Playing with v 10 and cant log in
don config ssh.txt
have you got user pass please

[suffolk3000]

Remember fat fingers means wrong letters
config.txt ssf lolol
sorted that still no luck

[kostaskt]

Finally, I ended up with a beautiful SD PIAWARE CARD 10.0
THANKs abcd567 for spending time to do this for us.

login as: Pi
Pi@192.168.x.x’s password:
Linux raspberrypi 6.6.74+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.74-1+rpt1 (2025- 01-27) aarch64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon Mar 3 18:44:03 2025 from 192.168.1.5
Pi@raspberrypi:~ $ cat /proc/cpuinfo | grep Model
Model : Raspberry Pi 3 Model B Plus Rev 1.3
Pi@raspberrypi:~ $ uname -a
Linux raspberrypi 6.6.74+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.74-1+rpt1 (2025-01-27) aarch64 GNU/Linux
Pi@raspberrypi:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 12 (bookworm)
Release: 12
Codename: bookworm
Pi@raspberrypi:~ $ apt-cache policy piaware
piaware:
Installed: 10.0
Candidate: 10.0
Version table:
*** 10.0 100
100 /var/lib/dpkg/status
Pi@raspberrypi:~ $ apt-cache policy dump1090-fa
dump1090-fa:
Installed: 10.0
Candidate: 10.0
Version table:
*** 10.0 100
100 /var/lib/dpkg/status

[abcd567]

(1) Wrote piaware SD card image to microSD card using Win32DiskImager

(2) Opened drive letter of card writer. This opened /boot folder. In this folder created a blank file named ssh

(3) In same /boot folder, opened file piaware-config.txt

(4) In file piaware-config.txt, scrolled down and added WiFi credentials in following lines:
(replaced “MyWiFiNetwork” and “s3cr3t” by my WiFi credentials)

wireless-ssid MyWifiNetwork 
wireless-password s3cr3t 

(5) Scrolled to bottom of file piaware-config.txt, and below last line added following details

# Additional settings can be added below.

feeder-id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx 
rtlsdr-device-index 00001090 
uat-receiver-type sdr
uat-sdr-device driver=rtlsdr,serial=00000978 

(6) Saved file, ejected microSD card from Windows Desktop, slipped microSD card in RPi, and powered up.

(7) IMPORTANT: After first boot, checked current IP of RPi from router. It may be efferent from what it used to be before re-imaging

(8) Connected to RPi by SSH using IP found from router (item (7) above), and logged-in using following

• username: pi
• password: flightaware

 

(9) Configured WiFi STATIC network using Network Manager

sudo nmtui

 

 

 

 

 

Click on Screenshot to See Larger Size

 

[suffolk3000]

Thankyou so much abcd567) will do this over night