Raspberry OS / Raspbian updated to Debian 11 "Bullseye"

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)

The Raspberry Imager with the (hidden) option to set the parameters for WiFi, hostname etc which can be opened by STRG-SHIFT-X seem to have an issue with the new image, even if it can be selected for installation.

After writing the image to the device, it shows an error that config.txt does not exist.
But it’s there.

Overclocking seem to be working. I used one of my spare Pi4 with 2Gig and the flag in config.txt

System:    Host: Raspi4 Kernel: 5.10.63-v7l+ armv7l bits: 32 compiler: gcc v: 10.2.1 Console: tty 0 
           Distro: Raspbian GNU/Linux 11 (bullseye) 
Machine:   Type: ARM Device System: Raspberry Pi 4 Model B Rev 1.2 details: BCM2711 rev: b03112 
Memory:    RAM: total: 1.9 GiB used: 217 MiB (11.1%) gpu: 76 MiB 
           RAM Report: unknown-error: Unknown dmidecode error. Unable to generate data. 
CPU:       Info: Quad Core model: ARMv7 v7l variant: cortex-a72 bits: 32 type: MCP arch: v7l rev: 3 
           bogomips: 1296 
           Speed: 1800 MHz min/max: 600/1800 MHz Core speeds (MHz): 1: 1800 2: 1800 3: 1800 4: 1800 
           Features: crc32 edsp evtstrm fastmult half idiva idivt lpae neon thumb tls vfp vfpd32 vfpv3 vfpv4

Haven’t tried it before and if it was already working on Buster. Stability needs check.

Which one of following upgrade commands you used?:

apt upgrade
apt dist-upgrade
apt full-upgrade

I am not sure what is the difference between the above 3 commands. May be some one who knows, or @obj kindly take the trouble to explain.


If you switch from buster to bullseye in the sources.list, the first command is obviously sufficient, that’s what i was using.

The main difference is the automatic resolution of dependency issues from what i found in other discussions.
But for me it was working flawless

I only needed to answer a couple of times if the existing config should be overwritten with a new default one.
I always selected “no” to keep my config files.

That can be a problem if the config structure changes, but it was not the case during my install/upgrade


quick correction after checking my history on the 3B. I needed to use a --fix-missing in between and utilized the update/upgrade again. But i did neither use dist nor full

  439  sudo nano sources.list
  440  sudo apt update
  441  sudo apt upgrade
  442  sudo apt --fix-missing
  443  sudo apt update
  444  sudo apt upgrade
  445  sudo reboot now


Yes, this happened with me also. Please see below:

I Googled to find answer to my question about difference between apt upgrade, apt dist-upgrade and apt full-upgrade.

Here is what I found:

(1) One confusing thing is difference between apt-get and apt. Which one to use where?

(2) In Google search results, I found another person claims that both dist-upgrade and full-upgrade are the same thing. I quote him below.


1 Like

Did somebody do something to server configuration this morning? I upgraded to bullseye a couple days ago. Without updating any of adsb software, everything was working fine. But this morning both dump1090-fa and dump978-fa quit working…

BTW if you have Pi 3B+ and are having trouble with Wifi being blocked every time you restart after upgrading to Bullseye, do this:

apt purge connman

Server configuration doesn’t affect your local decoders. You have a local problem.

1 Like

Reinstalling following this guide now… It’s taking a long time for those extra packages…

No, all ok with my 3 bullseye Pis


(1) Pi #1 with Piaware SD card image Buster on RPi model 4.
I upgraded it to Bullseye by adding bullseye repo to file /etc/apt/sources.list and then sudo apt-get update followed by sudo apt-get full-upgrade . It is 2 days now and is working ok. You can check it here:


(2) Pi #2 with Armbian Bullseye image on OrangePiPC.
The image was originally Bullseye, and no upgraging done by me. Working ok since one week. You can check it here:



(3) Pi #3 with Raspberry Pi OS Bullseye on RPi model 4.
The image was originally Bullseye, and no upgraging done by me. Working ok since two days You can check it here:



1 Like

As said, for me the update was done in approx 20 Minutes

maybe you missed the linked page of me

For my understanding apt-get is not required any longer and replaced by “apt” in newer distributions.

I never used apt-get so far the last two years

apt-listchanges: News

apt (2.1.16) unstable; urgency=medium

  Automatically remove unused kernels on apt {dist,full}-upgrade. To revert
  to previous behavior, set APT::Get::AutomaticRemove::Kernels to false or
  pass --no-auto-remove to the command. apt-get remains unchanged.

  Packages files can now set the Phased-Update-Percentage field to restrict
  update rollout to a specified percentage of machines. Previously, this has
  only been available to users of Ubuntu's update-manager tool. See
  apt_preferences(5) for details and how to configure multiple systems to get
  the same updates. Phased updates are disabled in chroots for now to not
  break buildd-style setups.

 -- Julian Andres Klode <jak@debian.org>  Fri, 08 Jan 2021 22:01:50 +0100

apt (1.9.11) experimental; urgency=medium

  apt(8) now waits for the lock indefinitely if connected to a tty, or
  for 120 seconds if not.


Press q to quit


It shits itself. Ask me how I know :blush:

1 Like

Not for me :wink: (20 characters)

Neither for me.

I have 2 Piaware SD Card Buster installs, both with graphs & many other feeders. I have upgraded both to Bullseye, and both are working very smoothly, without any issues, during upgrade process, as well as during normal operation. :slightly_smiling_face:

By the way I used:

sudo apt update 
sudo apt full-upgrade  

Each microSD card took about 30~35 minutes to upgrade.


Ah, that is interesting. The new names are not so easy to remember as the classic names but apparently were aimed at desktop type computers where adaptors can be added therefore names may change.

Understand you can be changed to old legacy names if required.


I think apt upgrade gives you a progress bar whilst it is doing so whereas apt-get upgrade leaves you guessing how long is left.