Raspberry OS / Raspbian updated to Debian 11 "Bullseye"

Friend of mine still running Jessie - he is now going to upgrade, eventually

Geoff

I’m pretty sure that one or two of my Pis are on Jessie and some others still running Stretch. If they work, and they’re not external facing, I see no reason to change them.

2 Likes

I do have Debian 11 installed on my primary laptop.
But my local cloud device is still on Ubuntu Server 20.04 LTS, even if meanwhile 21.10 STS is out

If my primary laptop crashes - shit happens
If my cloud device crashes - my wife will deny serving food until it’s fixed

2 Likes

It’s not that it’s difficult to do, but that there can be unexpected consequences for doing so. It really depends on what packages you have installed and what changes have been made to the system configuration. In many cases upgrading will go smoothly, but there will always be a few circumstances where something unforeseen happens and things go a bit wrong.

Especially when the Pi is mounted 30ft up in the air :smiley:

1 Like

 

Posted one month ago (on Oct 8, 2021)

Upgraded Raspberry Pi OS Buster to Bullseye

 

It is a very lengthy upgrade process (took about 45 minutes)

 

1 Like

One thing to bear in mind, if you are using the old predictable interface names of ETH0 and WLAN0 they will not be available anymore in the bullseye release.
I have static IP’s for all devices and the upgraded pi appeared with a DHCP address.
So when you do an inplace upgrade and reboot at the end the PI will be online with a dhcp address and you have to change the interfacename to enxb… for an ethernetconnection and or wlx… for a wirelessconnection.
These can be adapted in the dhcpcd.conf file and this will reenable the static IP adressing again

1 Like

Aye, a friend had exactly this when he updated his Pihole last week, I noticed the interface name had changed when he sent me a screenshot of his ifconfig display.

Seems like a somewhat bonkers change.

the old names were supported until Buster but already abandonned since Jessie.
Knowing this can save so considerable time troubleshooting :wink:

There is a good reason behind it, but it’s not necessarily relevant for a simple installation such as a raspberry pi. The intention is to make network names predictable - as in they are consistent for each interface between boots. Previously there were circumstances which could result in a names moving around various physical interface which could be problematic where a system is connected to more than one network.

There is a page on the Debian wiki talking about it: NetworkInterfaceNames - Debian Wiki

come on, that keeps you fit

That can be also the case with intermittent releases. However always a good option to get a fresh install removing all the shit installed over the years

 

2021-10-30-raspios-bullseye-armhf-lite.zip

After writing above image to microSD card, and successfully building & installing piaware, dump1090-fa, dump978-fa, and piaware-web packages on it, I successfully installed following also:

  • Graphs by @wiedehopf
  • Flightradar24 feeder (fr24feed)
  • Planefinder feeder (pfclient)
  • Radarbox24 feeder (rbfeeder)
  • Adsbexchange feeder
  • OpenSky feeder

 

4 Likes

I appreciate the “if it’s not broke…” logic but we do not plan to build new packages for jessie forever (PiAware 6 might be the last ones) so you’ll be on an old version.

(Plus, if it’s on the network – even if not directly exposed to the world – you really do want security updates, and they’re no longer available for jessie)

2 Likes

My Pis as of today:

(1) RPi Model 4 - Piaware SD card image Buster 6.1

 

(2) OrangePiPC - Armbian Bullseye with piaware 6.1, dump1090-fa 6.1, dump978-fa 6.1

 

(3) RPi model4 - DietPi Bullseye 64-bit with piaware 6.1, dump1090-fa 6.1, and dump978-fa 6.1

 

(4) RPi model 4 - Raspberry Pi OS Bullseye with piaware 6.1, dump1090-fa 6.1, and dump978-fa 6.1

 

1 Like

I have stopped disturbing commissioned/running install for upgrade. Now I have started using a spare microSD Card and a spare Pi.

I write latest image to spare microSD card, slip it into spare Pi, install and configure feeders, graphs and any other required software, let it run for a while, and if all is ok, replace old card of main Pi with freshly prepared spare microSD card.

This is a very safe way to upgrade.

 

 

1 Like

I wasn’t specifically referring to Pis running ADS-B, they are definitely external facing. A couple that spring to mind are ones that run little Christmas trees with flashing LEDs :slight_smile: :christmas_tree:

1 Like

We will see this on your installation?
Hopefully it will not impact LHR traffic because of confused pilots :rofl:

1 Like

I’ve got two of them, one gets set up in my office and the other one is in the front room :slight_smile:

:laughing:

1 Like

Piaware SD Card image ver 6.1 - Upgraded from Buster to Bullseye :slightly_smiling_face:

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

This was just an experiment. It has no advantage as Buster is still supported. Although after running for 18 hrs, I did not notice any issues, but there are no warranties, and if you want to try it, do it on your own risk.

(1) Edited file /etc/apt/sources.list

1.1 - Added following line to add raspberrypi’s Bullseye repo:
deb http://raspbian.raspberrypi.org/raspbian/ bullseye main contrib non-free rpi

1.2 - Commented out following line to comment out Flightaware’s Buster repo:
#deb http://flightaware.com/mirror/raspbian/raspbian/ buster main contrib non-free rpi

(Please see screenshot below).

 

(2) Updated & upgraded
sudo apt-get update
sudo apt-get full-upgrade

Upgrade command took about 40 minutes to complete. After comletion, rebooted Pi. The OS is upgraded to Bullseye. Please see screenshot below.

image

 

1 Like

I sucessfully ran an upgrade of my Raspberry 3B by changing the sources list from buster to bullseye, followed by apt update and apt upgrade

On that device the additional feeders for Radarbox and Planefinder are running, data is coming from readsb installed on the same Pi3 which catches the stream from my Jetvision device

In addition the WeeWX weather station is running on it.

All went fine, still working after reboot.
I only needed to manually start the weewx service it was flagged as “dead”.

As neither dump1090 nor piaware is running on it (this is going to FA directly from the Jetvision device) i cannot answer if this would work as well.

Update was done in approx 15-20 Minutes (did not check stop watch)