How To Improve To Raspberry Pi OS 11 Bullseye (From Buster)

Raspberry Pi OS 11 Bullseye

Raspberry Pi OS "Bullseye" (primarily based on Debian 11 Bullseye) has been launched lately, and this text covers the directions for upgrading from the older Raspberry Pi OS Buster to this new Bullseye model. This could work with any Raspberry Pi mannequin.

Raspberry Pi OS Bullseye comes with main modifications, together with:

  • It now makes use of GTK3 as a substitute of GTK2
  • Changed Openbox window supervisor with Mutter on methods with greater than 2GB of RAM (in case your RPi has 2GB of RAM or much less, it'll proceed to make use of Openbox)
  • A brand new notification supervisor is on the market within the taskbar; notifications at the moment are displayed in chronological order within the high proper nook of the display, and are hidden after fifteen seconds (they are often configured from Panel Preferences -> Look)
  • New graphical device to put in system and utility updates
  • The KMS (kernel modesetting) driver, which was an experimental choice till now, is now the usual video driver
  • New digital camera driver
  • Many different modifications, together with Chromium browser up to date to model 92 (optimized to assist {hardware} accelerated video playback on the Raspberry Pi)

It is value noting from the beginning that upgrading Raspberry Pi OS from Buster (primarily based on Debian 10 Buster) to Bullseye (primarily based on Debian 11 Bullseye) isn't formally supported as a result of there are essential modifications between main Debian model upgrades, and the beneficial option to get it's to create a brand new SD card with the brand new launch. The system might break (some issues might not work, it could not have the ability to boot, and many others.) when upgrading! Additionally, it'll take significantly longer to improve to Raspberry Pi OS Bullseye than to carry out a clear set up.

Nonetheless, I for one have a closely custom-made Raspberry Pi OS and I needed to maintain my customizations, so I opted to improve from Buster to Bullseye. In case you wish to improve too, beneath you've got all of the steps required to improve Raspberry Pi OS 10 Buster to 11 Bullseye, in addition to some points I've encountered throughout / after the improve, and options. Whereas this could work with any Raspberry Pi mannequin, notice that I examined this on a Raspberry Pi 4.

You may additionally like: How To Cast YouTube Videos From Your Phone To Raspberry Pi Using YouTube On TV (

The right way to improve Raspberry Pi OS 10 Buster to 11 Bullseye

1. Again up your present set up in case the OS is tousled after the improve, and also you wish to revert it to its preliminary state. The simplest means to do that is to make use of the SD Card Copier device that comes preinstalled with Raspberry Pi OS (it is accessible within the menu, within the Equipment class).

2. Search and change all cases of buster with bullseye in /and many others/apt/sources.record and /and many others/apt/sources.record.d/raspi.record

You may both do that manually, utilizing a textual content editor, or use the instructions beneath to do that:

sudo sed -i 's/buster/bullseye/g' /and many others/apt/sources.record

sudo sed -i 's/buster/bullseye/g' /and many others/apt/sources.record.d/raspi.record

3. Replace the software program sources, set up gcc-8 (the improve cannot proceed with out it), then improve your Raspberry Pi OS from Buster to Bullseye.

sudo apt replace

sudo apt set up libgcc-8-dev gcc-8-base

sudo apt full-upgrade

With out putting in gcc-8, you will get an error when attempting to run sudo apt full-upgrade, saying that "Some packages couldn't be put in. [...] The next packages have unmet dependencies: libc6-dev : Breaks: libgcc-8-dev (< however 8.3.0-6+rpi1 is to be put in".

On the finish of the apt full-upgrade command, I acquired the next warning: "APT had deliberate for dpkg to do greater than it reported again...". Should you encounter this challenge too, this could repair it:

sudo apt set up -f

sudo apt full-upgrade

After this, all the pieces was upgraded efficiently.

4. Take away leftover packages

sudo apt autoremove

5. Allow KMS. That is now utilized by default when utilizing a contemporary Raspberry Pi OS Bullseye picture, however not when upgrading from Buster to Bullseye - on this case we have to allow it manually (with out it you will run into visible points corresponding to stutter).

You may have to edit the /boot/config.txt file and remark out (put "#" in entrance of the road) any strains containing dtoverlay=vc4-fkms-v3d, then scroll to the underside to the [all] part and below it, add dtoverlay=vc4-kms-v3d (as you possibly can see, that is now utilizing "kms" as a substitute of "fkms"). You too can do that by utilizing the next instructions:

sudo sed -i 's/dtoverlay=vc4-fkms-v3d/#dtoverlay=vc4-fkms-v3d/g' /boot/config.txt

sudo sed -i 's/[all]/[all]ndtoverlay=vc4-kms-v3d/' /boot/config.txt

Put up-upgrade notes

I take advantage of the Wifi on my Raspberry Pi 4, and after upgrading to Raspberry Pi OS 11 Bullseye and rebooting, the community panel applet exhibits my community as disconnected, and upon clicking on it, it exhibits a message saying "No wi-fi interfaces discovered":

no wireless interfaces found Raspberry Pi OS 11 bullseye

This seems to be associated to the truth that with Bullseye, Connman is used to deal with community settings. To repair this, I went to the Menu -> Preferences -> Connman Settings -> Wi-fi, then clicked on the wi-fi community I wish to connect with, then clicked the Join button. When clicking the gear icon subsequent to a wi-fi community, there's additionally an choice to autoconnect (disabled by default).

It's possible you'll take away the panel community applet which now not works correctly, and change it with the one which works. To take away it, proper click on it and select Take away "Wi-fi & Wired Community From Panel. Then so as to add the one which works, proper click on the panel, select Add / Take away Panel Objects - > Add and add the Handle Networks panel plugin:

Raspberry Pi OS 11 Bullseye wireless

One other challenge I've encountered is that Chromium 92 crashes when visiting (doesn't occur the primary time, solely on subsequent visits). This isn't associated to upgrading from Buster to Bullseye as a result of it additionally happens on new installs. Proper now I am utilizing a work-around to get it to work (due to kerry_s): setting Chromium to routinely delete the YouTube cookies when Chromium is closed. If you wish to do that too, open the Chromium settings, seek for Cookies, then scroll to All the time clear cookies when home windows are closed, and add [*.] there. One other work-around could be to put in the Debian-provided Chromium (bundle title "chromium", at present model 90), however utilizing that you simply use the hardware-accelerated video playback that is accessible within the Raspberry Pi OS model of Chromium (bundle title "chromium-browser, at present model 92).

Source link

Leave a Reply

Your email address will not be published. Required fields are marked *