Your piaware and dump1090-fa packages are compatible to Bullseye. There is no guarantee these will be compatible to Bookworm also. After upgrade of OS, these may or may not work. Only after upgrade of OS you will know. If existing install fails upon upgrade, you will need to do next steps to build packages from source code.
Well, I didnât get that far. There were 830 packages to upgrade. It got to where it said 99% complete and then just hung. After about 10 minutes I figured either it died or it was done but didnât know it (possible I guess). So did a ctrl C to get out and it said I was no longer connected to the host. Also the WiFi router didnât show the RPi any longer even after power down and power up with internal WiFi. (Had been using the USB adapter WifI). The SD card was hosed.
Oops! Sad to hear that. Never happened with me
.When I did it last month on a fresh Bullseye image, 467 packages were upgraded.
I have done it on one Raspberry and on my Mini-PC running my file server environment.
Both went well, but i was prepared to reinstall from scratch if needed.
No guarantee it works with every application
What was surprising to me was where it failed. I was pretty sure that the USB WiFi adapter would need to be reinstalled in order for it to work on Bookworm. So I was prepared to switch back to the internal Wifi after rebooting into Bookworm. (Do that by editing /boot/config.txt on a desktop machine.) But I didnât get that far. It failed while I was still in Bullseye.
Is PiAware 9.0.1 still reading settings from /boot/firmware/piaware-config.txt? I had to create a sym link in /boot in order to get the settings to show up. Should this be updated? I did a Raspbian bookworm 64 bit install fresh then installed the PiAware repo packages per instructions here:
Other issue Iâm running into is PiAware isnât connecting to the WiFi network I specify in piaware-config.txt. It shows up in piaware-config but doesnât attempt the connection or paste the information to /etc/wpa_supplicant.conf. What service is PiAware using to connect to the WiFi network?
It is the piaware SD card image which (still) has file /boot/piaware-config.txt
What you have done is a package install of piaware on Raspberypi OS image. This does NOT have the file piaware-config.txt
If you would have imaged your microsd card using Raspberrypi Imager, it has a provision to configure wifi at that stage.
If you did not configure wifi at that stage, then to configure wifi afterbooting, connect a network cable and ssh, OR connect a monitor & keyboard to RPi, and issue following command:
sudo nmtui
I explained poorly. I mounted the SD card on my Mac, placed the piaware-config.txt file in the BootFS partition. It seems on bookworm files you place there now live in /boot/firmware, not in /boot. piaware-config output didnât acknowledge these settings until I created the sym link which leads me to believe itâs still looking in /boot, not /boot/firmware.
My goal is to set SSID/pwd using piaware-config.txt so I can do this with a headless setup just mounting the SD card on a non-Linux machine (this worked just fine with previous PiAware releases).
Raspberrypi Imager is the easiest way to enable ssh and configure wifi at the time of writing the image to microSD card. It is available for Mac, Windows, and Linux Computers. Please brows following guide
https://www.raspberrypi.com/documentation/computers/getting-started.html#raspberry-pi-imager
Works great. Lasts a long time!
Unfortunately, Iâm trying to chase down how to do all of this within piaware-config.txt in the BootFS partition that worked in previous releases of PiAware.
I dug around on GitHub (scripts/generate-network-config). Looks like the variable âgenerate_network_configâ was last updated for buster. Is bookworm connection mechanism the same?
Pre-bookworm versions used dhcpcd for network configuration. The bookworm does not use dhcpcd. It uses network-manager.
1 Like
Answering my own question. Looks like there are commits not yet in master being worked on. Iâll wait and try back later. @obj might want to check that the new release is looking for piaware-config.txt in /boot/firmware now.
Thanks! Might see if I can install dhcpcd and make it work that way while the bookworm network commits are being worked out.
In NetworkManager, network can be configred for STATIC IP by any one of the following two mwthods:
(a) Using nmcli (Network Manager Command Line Interface) by following commands:
nmcli c
Click on Screenshot to See Larger size
sudo nmcli con mod "Wired connection 1" ipv4.addresses 192.168.12.34/24
sudo nmcli con mod "Wired connection 1" ipv4.gateway 192.168.12.1
sudo nmcli con mod "Wired connection 1" ipv4.dns 192.168.12.1,8.8.8.8,8.8.4.4,1.1.1.1
sudo reboot
sudo nmcli radio wifi on
sudo nmcli dev wifi connect "[my-wifi-ssid]" password "[my-wifi-password]" ifname wlan0
sudo nmcli con mod "[my-wifi-ssid]" ipv4.addresses 192.168.12.24/24
sudo nmcli con mod "[my-wifi-ssid]" ipv4.gateway 192.168.12.1
sudo nmcli con mod "[my-wifi-ssid]" ipv4.dns 192.18.12.1,8.8.8.8,8.8.4.4,1.1.1.1
sudo reboot
(b) Using nmtui (Network Manager Text User Interface) by following command:
sudo nmtui
In both the above methods, the configurations are saved as follows:
WiFi
In file:
/etc/NetworkManager/system-connections/[my-ssid].nmconnection
Click on Screenshot to See Larger Size
Wired
In file:
/etc/NetworkManager/system-connections/'Wired connection 1.nmconnection'
Click on Screenshot to See Larger Size
This is applicable to Rasperry Pi OS image Bookworm.
It is NOT for piaware SDCard image.
References:
(1) Headless Wi-Fi setup without the RPi Imager: bootfs/wpa_supplicant.conf not supported since Bookworm
(2) custom.toml example for Raspberry Pi OS ¡ GitHub
In RaspberryPi OS images earlier than Bookworm, after writing the image to microSD card, two files named âsshâ and âwpa_supplicant.confâ were created or copied in /boot partition which was visisble in card reader plugged into Win/Mac computers.
In bookworm, this has changed and adding files âsshâ and âwpa_supplicant.confâ has no effect. One is forced to use Rapberrypi Imager to configure WiFi and SSH.
However if Win32Imager is used, following workaround can be used to enable SSH and configure WiFi.
Create a text file named custom.toml.
IMPORTANT: When you create a new text file and name it âcustom.tomlâ, its full name will be âcustom.toml.txtâ. The extension .txt may or may not be visible dpending on your file explorerâs settin. Make sure that .txt is removed, so that fileâs full name is only custom.toml.
copy-paste following code in this file and save it on your Win / Mac computer.
Note: Replace [my-raspberrypi-password], [my-wifi-ssid], and [my-wifi-password] by their actual values.
config_version = 1
[system]
hostname = "raspberrypi"
[user]
name = "pi"
password = "[my-raspberrypi-password]"
password_encrypted = false
[ssh]
enabled = true
password_authentication = true
[wlan]
ssid = "[my-wifi-ssid]"
password = "[my-wifi-password]"
password_encrypted = false
hidden = false
country = "CA"
[locale]
keymap = "us"
timezone = "America/Toronto"
After writing image with Win32DiskImager, double-click the drive letter for card reader which has the microSD card on which you have written the Bookworm image. This will open the /boot partition of microSD card. Copy-paste the file custom.toml from your Win / Mac to the /boot folder of microSD card
After copy-pasting the file custom.toml in /boot partition, eject microSD card from Win / Mac computer, slip into Raspberry Pi and power up. When boot process completes, you will be able to SSH to RPi through WiFi
Although it is NOT necessary to connect aMonitor or network wire, just to watch what is happening, I connected a Monitor. The photo below shows what was displayed on monitor during boot.
