The rtl-sdr.rules issue is not universal with all Bookworm OSes. For me it occured only on DietPi x86_64. On all other Bookworm OSes I have tried (64-bit RPi, 64-bit Armbian, 32-bit Armbian, Debian12 x86_64, and DietPi x86-64), it occured only on the DietPi x86_64.
Ok I didnāt notice that subtlety. Will try upgrade later.
As long as they havenāt fixed the usb issue in the vanilla image Iām sticking to Bullseye.
Most thin clients are perfectly capable of 64 bit OS but thereās still 2 years of support on Bullseye 
My HP ThinClientT520 died couple of months ago.
I am now using Android 11 TV Box H96 Max which I have purchased for US $30 (including power supply unit) + free shipping, from AliExpress.
RockChip 3318 CPU, 4GB ram, 32GB eMMC flash as SSD. I re-imaged it with Armbian Bookworm Lite (version for TV Box Rockchip 3318), and installed piaware, piaware-web, dump1090-fa, and dump978-fa. All working OK.
Click on the Screenshot to See Larger Size
Android TV-Box-H96Max
Itās Android 11 OS was replaced by me by Armbian OS Bookworm Lite (headless).
Click on the Photo ONCE to See Larger Size
Click AGAIN to See FULL Size
2 Likes
You guys are amazing! Color me impressed.
Ok tried @tech0 upgrade approach. It hung at 99% again. The final line was: Created symlink /etc/systemd/system/multi-user.target.wants/NetworkManager.service ā /lib/systemd/system/NetworkManager.service. And there was no longer an ssh connection.
Another minor problem was the sed commands, Needed to take out the quotes. So they are just:
sudo sed -i s/bullseye/bookworm/g /etc/apt/sources.list
sudo sed -i s/bullseye/bookworm/g /etc/apt/sources.list.d/*
Just a thought - are you both running the same base OS? I get the feeling @tech0 has a pure Debian install. In that case a Bullseye > Bookworm in place upgrade is pretty straightforward. If you have a Pi OS, then the in place route is not so straightforward (migration to Network Manager and kernel repackaging in Pi OS Bookworm come to mind as hurdles which an in place upgrade could struggle with).
Iām able to get a TC620 for 40 euro including:
8GB RAM
Quadcore processor
32 GB SSD
Oiginal Powersupply
I have 8 of them currently, 1 Windows system acting as a file server, 1 Debian12 Bookworm testbed, 6 Dietpi Bullseye systems. 2 Bullseye systems are active feeders, 1 is acting as a combined local view for Piaware. 3 are awaiting other purposes so thereās enough test capacity at the moment
2 Likes
Iām running a Raspberry Pi OS as indicated by the output of the following commands. (I inserted a space in each URL to block interpreting the link.) The wifi is blocked by rfkill because the RPi is powered by POE+ and communicates over Ethernet.
pi@cs1:~ $ cat /etc/apt/sources.list.d/raspi.list
deb http ://archive.raspberrypi.org/debian/ bookworm main
pi@cs1:~ $ cat /etc/os-release
PRETTY_NAME=āRaspbian GNU/Linux 12 (bookworm)ā
NAME=āRaspbian GNU/Linuxā
VERSION_ID=ā12ā
VERSION=ā12 (bookworm)ā
VERSION_CODENAME=bookworm
ID=raspbian
ID_LIKE=debian
HOME_URL=āhttp ://www.raspbian.org/ā
SUPPORT_URL=āhttp ://www.raspbian.org/RaspbianForumsā
BUG_REPORT_URL=āhttp ://www.raspbian.org/RaspbianBugsā
Well, my guess did not turn out to be a cause of Jimās issues 
It would seem not having wifi in use helped with your in place upgrade path. Maybe something for him to consider. Or maybe installing/configuring network manager in Bullseye before upgrading to Bookworm would smooth the way. I suppose he will let us know how things turned out for him.
I have Raspberry Pi OS also. The problem might be that I use a BrosTrend USB WiFi adapter. Iām pretty sure the Brostrend driver needs to be reinstalled for Bookworm. However I thought I would be able to do the upgrade using the BrosTrend Wifi, then switch to the on-board WiFi, and do a reboot, then do the reinstall of the Brostrend driver and switch back to BrosTrend Wifi. I guess that doesnāt work. Probably need to switch to the on-board WiFi first before doing the upgrade.
I donāt really understand how an upgrade works. That is, how are you able to move files in place while the system is running and not disturb the running system?
@jimMerk2
If you do not have something special on current Bullseye install which you want to preserve, there is no logic in command-line upgrding Bullseye to Bookworm. In this case easier and clean solution is to re-image with Bookworm image. If you are worried about reinstalling other feeders and graphs, then it is not a problem. It takes me less than an hour to make a fresh install of following on a re-imaged microSD card.
- piaware
- dump1090-fa
- dump978-fa
- piaware-web
- @wiedehopfās graphs
- Flightradar24 feeder
- Radarbox24 feeder
- Planefinder feeder
- OpenSkyNetwork feeder
- Adsbexchange feeder
- Adsbfi feeder
- RadarVirtuel feeder
- Mixer to see combined feed of my 4 receivers locally on one map.
1 Like
@abcd567 I donāt have anything special on the current Bullseye install, just a lot of things. For example, to compile anything, you need to have all the compiler and build tools. Those all need to be installed again. Having said that, I have burned another SD card with Bookworm and installed the BrosTrend USB WiFi driver in anticipation of starting anew.
Regarding, doing an upgrade, I donāt think it can be done over WiFi. I do have a 75 ft ethernet cable I could string up temporarily If I have to.
Couple of months ago, I successfully upgraded bullseye to bookworm on WiFi, but I never used an external WiFi adaptor, it was on built-in WiFi adaptor of Pi4.
Was able to do an upgrade from Bullseye to Bookworm by using ethernet. However, after the upgrade, was not able to ssh over Wifi using either the USB Wifi adapter or on board WiFi. I could only use ethernet to access the RPi. I saw something on Raspberry Pi forum that said to put a new copy of wpa_supplicant.conf file and empty ssh file in /boot partition to fix this. I tried that but it didnāt fix the problem. So for now Iām done trying to do a command line upgrade.
If nothing else this hobby is a great excuse to eat tins of chocolates and biscuits.
2 Likes
The Pi OS developers explicitly recommend that you do not try to upgrade an existing install to bookworm, because of exactly the sort of problems youāre running into. Itās going to be much less painful to just reimage.
2 Likes
I assume youāre referring to this:
where the last paragraph says:
āThis time, because the changes to the underlying architecture are so significant, we are not suggesting any procedure for upgrading a Bullseye image to Bookworm; any attempt to do this will almost certainly end up with a non-booting desktop and data loss. The only way to get Bookworm is either to create an SD card using Raspberry Pi Imager, or to download and flash a Bookworm image from here with your tool of choice.ā
I saw that but thought they were mostly talking about the Desktop version where a new display system ā Wayland was adopted. But apparently thereās a lot more to the upgrade that can go wrong than just that.
Before you re-image a microSD card, retrive & save feeder keys
Before you write fresh image, retrieve feeder keys from existing image, copy-paste and save these in Notepad on your desktop/laptop.
1.1 - Piaware feeder-id
Following command will print feeder-id
cat /var/cache/piaware/feeder_id
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx
1.2 - Plane finder share-code
Give following command
cat /etc/pfclient-config.json
It will output following long line. Your Planefinder sharecode is the last item zzzzzzzzz in this long line
{"tcp_address":"127.0.0.1","tcp_port":"30005","select_timeout":"10","data_upload_interval":"10","connection_type":"1","aircraft_timeout":"30","data_format":"1","latitude":"xx.xxxx","longitude":"yy.yyyy","sharecode":"zzzzzzzzzzzz"}
1.3 - Flightradar24 key:
Give following command
cat /etc/fr24feed.ini
Following line in output of above command has your fr24 key:
fr24key="xxxxxxxxxxxxxxxx"
1.4 - Radarbox24 key:
Give following command:
cat /etc/rbfeeder.ini
Following line in output of above command has you RB24 key
key=xxxxxxxxxxxxxxxxxxxxxx
3 Likes