- spl23
- Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator - Posts: 687
- Joined: Fri Dec 26, 2014 11:02 am
STICKY - How to upgrade a Buster image to Bullseye
First off - we really do not recommend doing this, and we don't support it!
The only recommended way to upgrade to bullseye is to download and flash a clean bullseye image, and transfer your data and applications across. But if you really want to try to upgrade an existing buster image to bullseye, this is a method we have found to work on a clean install of the last released buster image. This does of course not guarantee it will work on your image, which will have all sorts of subtle differences from the clean image as a result of changes made while you used it - but it works for us.
First - and I cannot stress this enough - use dd or the SD Card Copier application to MAKE A BACKUP OF YOUR CARD. There is a non-zero chance that this upgrade will trash your system and leave you with an unbootable card. So don't say we didn't warn you! (Did I mention that we do not recommend doing this...?)
Edit /etc/apt/sources.list, and replace every occurrence of the word "buster" with "bullseye".
Do the same for any .list files in /etc/apt/sources.list.d/
This will take a while to run. Answer "yes" to any questions during the install.
Again, this will take a while, and again, answer "yes" to any questions during the install.
When it completes, edit /boot/config.txt.
Comment out any lines which contain "dtoverlay=vc4-fkms-v3d" by putting a # sign at the start of the line.
At the bottom of the file, in the [all] section, add the line "dtoverlay=vc4-kms-v3d" - note that is "kms", not "fkms".
Now reboot and cross your fingers...
If your system comes back up, it should now be running bullseye. You will probably need to reset any custom display resolution you had before.
As above - we do not support this process; it may work for you, or it may not. If you get it to work, or if you have problems, feel free to use this thread to share your experiences to help each other. Good luck!
The only recommended way to upgrade to bullseye is to download and flash a clean bullseye image, and transfer your data and applications across. But if you really want to try to upgrade an existing buster image to bullseye, this is a method we have found to work on a clean install of the last released buster image. This does of course not guarantee it will work on your image, which will have all sorts of subtle differences from the clean image as a result of changes made while you used it - but it works for us.
First - and I cannot stress this enough - use dd or the SD Card Copier application to MAKE A BACKUP OF YOUR CARD. There is a non-zero chance that this upgrade will trash your system and leave you with an unbootable card. So don't say we didn't warn you! (Did I mention that we do not recommend doing this...?)
Edit /etc/apt/sources.list, and replace every occurrence of the word "buster" with "bullseye".
Do the same for any .list files in /etc/apt/sources.list.d/
Code: Select all
sudo apt updateCode: Select all
sudo apt install libgcc-8-dev gcc-8-baseCode: Select all
sudo apt full-upgradeWhen it completes, edit /boot/config.txt.
Comment out any lines which contain "dtoverlay=vc4-fkms-v3d" by putting a # sign at the start of the line.
At the bottom of the file, in the [all] section, add the line "dtoverlay=vc4-kms-v3d" - note that is "kms", not "fkms".
Now reboot and cross your fingers...
If your system comes back up, it should now be running bullseye. You will probably need to reset any custom display resolution you had before.
As above - we do not support this process; it may work for you, or it may not. If you get it to work, or if you have problems, feel free to use this thread to share your experiences to help each other. Good luck!
- DougieLawson
- Posts: 43604
- Joined: Sun Jun 16, 2013 11:19 pm
Re: STICKY - How to upgrade a Buster image to Bullseye
It's probably best for folks to continue to use RonR's tried and tested script from viewtopic.php?t=317888
That's known to work and does all of the /etc/apt stuff for you.
That's known to work and does all of the /etc/apt stuff for you.
Languages using left-hand whitespace for syntax are ridiculous
DMs sent on Bluesky or by LinkedIn will be answered next month.
Fake doctors - are all on my foes list.
The use of crystal balls and mind reading is prohibited.
DMs sent on Bluesky or by LinkedIn will be answered next month.
Fake doctors - are all on my foes list.
The use of crystal balls and mind reading is prohibited.
- spl23
- Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator - Posts: 687
- Joined: Fri Dec 26, 2014 11:02 am
Re: STICKY - How to upgrade a Buster image to Bullseye
Unless that script also makes the config changes to switch over to KMS, you will end up with tearing when dragging windows about and other visual nasties. If you do use that script, make sure you also make the changes to /boot/config.txt described in my first post above.
- DougieLawson
- Posts: 43604
- Joined: Sun Jun 16, 2013 11:19 pm
Re: STICKY - How to upgrade a Buster image to Bullseye
Isn't that just for RPi4Bs only (and therefore completely irrelevant to my, mostly headless, RPi3Bs, 3As, 2B, Zeros and 1Bs).spl23 wrote: ↑Mon Nov 08, 2021 11:38 amUnless that script also makes the config changes to switch over to KMS, you will end up with tearing when dragging windows about and other visual nasties. If you do use that script, make sure you also make the changes to /boot/config.txt described in my first post above.
Languages using left-hand whitespace for syntax are ridiculous
DMs sent on Bluesky or by LinkedIn will be answered next month.
Fake doctors - are all on my foes list.
The use of crystal balls and mind reading is prohibited.
DMs sent on Bluesky or by LinkedIn will be answered next month.
Fake doctors - are all on my foes list.
The use of crystal balls and mind reading is prohibited.
- spl23
- Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator - Posts: 687
- Joined: Fri Dec 26, 2014 11:02 am
Re: STICKY - How to upgrade a Buster image to Bullseye
No, in this release the KMS driver is the default for all models of the Pi.DougieLawson wrote: ↑Mon Nov 08, 2021 11:41 amIsn't that just for RPi4Bs only (and therefore completely irrelevant to my, mostly headless, RPi3Bs, 3As, 2B, Zeros and 1Bs).spl23 wrote: ↑Mon Nov 08, 2021 11:38 amUnless that script also makes the config changes to switch over to KMS, you will end up with tearing when dragging windows about and other visual nasties. If you do use that script, make sure you also make the changes to /boot/config.txt described in my first post above.
- jamesh
- Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator - Posts: 35174
- Joined: Sat Jul 30, 2011 7:41 pm
Re: STICKY - How to upgrade a Buster image to Bullseye
Yes, but you are not the only person reading this thread!!DougieLawson wrote: ↑Mon Nov 08, 2021 11:41 amIsn't that just for RPi4Bs only (and therefore completely irrelevant to my, mostly headless, RPi3Bs, 3As, 2B, Zeros and 1Bs).spl23 wrote: ↑Mon Nov 08, 2021 11:38 amUnless that script also makes the config changes to switch over to KMS, you will end up with tearing when dragging windows about and other visual nasties. If you do use that script, make sure you also make the changes to /boot/config.txt described in my first post above.
Software guy, working in the applications team.
Re: STICKY - How to upgrade a Buster image to Bullseye
hmmm.... as the "official" RPiOS32 Bullseye has been officially announced....
been contemplating on going this path, or the recommended path....
or should I wait until the dust settles.....?
been contemplating on going this path, or the recommended path....
or should I wait until the dust settles.....?
"Don't come to me with 'issues' for I don't know how to deal with those
Come to me with 'problems' and I'll help you find solutions"
Some people be like:
"Help me! Am drowning! But dont you dare touch me nor come near me!"
Come to me with 'problems' and I'll help you find solutions"
Some people be like:
"Help me! Am drowning! But dont you dare touch me nor come near me!"
Re: STICKY - How to upgrade a Buster image to Bullseye
I tried it on a Zero 2 with RPiOS Lite and just Node-Red installed.
It took a long time, longer than burning a fresh image and reinstalling Node-Red and my flows.
It required a fair bit of interation so couldn't be run unattended.
And finally, it either didn't boot or didn't connect to wifi.
It took a long time, longer than burning a fresh image and reinstalling Node-Red and my flows.
It required a fair bit of interation so couldn't be run unattended.
And finally, it either didn't boot or didn't connect to wifi.
Over and out
- HawaiianPi
- Posts: 7918
- Joined: Mon Apr 08, 2013 4:53 am
Re: STICKY - How to upgrade a Buster image to Bullseye
If you decide to go with the recommended path, the 64-bit images are also available.
downloads.raspberrypi.org/raspios_arm64/images/raspios_arm64-2021年11月08日/
downloads.raspberrypi.org/raspios_lite_arm64/images/raspios_lite_arm64-2021年11月08日/
My mind is like a browser. 27 tabs are open, 9 aren't responding,
lots of pop-ups, and where is that annoying music coming from?
lots of pop-ups, and where is that annoying music coming from?
Re: STICKY - How to upgrade a Buster image to Bullseye
Hi!
I'm running the 64bit version on a rpi 4/8G. The apt update gives me an error regarding the debian-security updates/bullseye repo which has no release file and therefore it's by default disabled. Should I override this error somehow or it's OK to leave it as it is ?
Thanks in advace for your reply
I'm running the 64bit version on a rpi 4/8G. The apt update gives me an error regarding the debian-security updates/bullseye repo which has no release file and therefore it's by default disabled. Should I override this error somehow or it's OK to leave it as it is ?
Thanks in advace for your reply
- aBUGSworstnightmare
- Posts: 13432
- Joined: Tue Jun 30, 2015 1:35 pm
Re: STICKY - How to upgrade a Buster image to Bullseye
Off-topic: KMS runs also nicely with 5.15 kernel on a Zero 2 W.spl23 wrote: ↑Mon Nov 08, 2021 11:46 amNo, in this release the KMS driver is the default for all models of the Pi.DougieLawson wrote: ↑Mon Nov 08, 2021 11:41 amIsn't that just for RPi4Bs only (and therefore completely irrelevant to my, mostly headless, RPi3Bs, 3As, 2B, Zeros and 1Bs).spl23 wrote: ↑Mon Nov 08, 2021 11:38 amUnless that script also makes the config changes to switch over to KMS, you will end up with tearing when dragging windows about and other visual nasties. If you do use that script, make sure you also make the changes to /boot/config.txt described in my first post above.
Nice to see the official release! Will start with a fresh image though (instead of attempting to update)
- GranducatodiToscana
- Posts: 18
- Joined: Mon Aug 09, 2021 9:07 pm
Re: STICKY - How to upgrade a Buster image to Bullseye
i've installed my buster on an external ssd. how i can upgrade it to bullseye without lost the settings and the files?
i've got a rpi400.
thank u
i've got a rpi400.
thank u
Raspberry Pi 400 addicted
- ralphrmartin
- Posts: 29
- Joined: Sat May 06, 2017 3:42 pm
Re: STICKY - How to upgrade a Buster image to Bullseye
Just followed the above instructions for a basic headless server running Plex and mpd, and all went well. Thanks!
- ralphrmartin
- Posts: 29
- Joined: Sat May 06, 2017 3:42 pm
Re: STICKY - How to upgrade a Buster image to Bullseye
Hmm tried upgrading another server running pihole, dns, and a unifi network controller, and couldn't log into it afterwards or access pihole. At that point I had to revert to a backup as it was a live system.
Re: STICKY - How to upgrade a Buster image to Bullseye
I've stumbled upon this one as well.nikal wrote: ↑Mon Nov 08, 2021 1:03 pmHi!
I'm running the 64bit version on a rpi 4/8G. The apt update gives me an error regarding the debian-security updates/bullseye repo which has no release file and therefore it's by default disabled. Should I override this error somehow or it's OK to leave it as it is ?
Thanks in advace for your reply
The original line in /etc/apt/sources.list
Code: Select all
deb http://deb.debian.org/debian-security/ buster/updates main contrib non-freeCode: Select all
deb http://security.debian.org/debian-security bullseye-security main contrib non-freeRe: STICKY - How to upgrade a Buster image to Bullseye
On my quite modified RPi4 system, the upgrade went as smooth as a former upgrade of some Debian buster to Debian bullseye system, except that connman got installed and activated while dhcpcd was and is still my main network config tool. As I have bridged eth0 and wlan0 into a br0 (WiFi AP functionality), network access got broken and the upgrade stopped. Luckily I had serial console access, so i could fix/restart the upgrade process.ralphrmartin wrote: ↑Mon Nov 08, 2021 5:13 pmHmm tried upgrading another server running pihole, dns, and a unifi network controller, and couldn't log into it afterwards or access pihole. At that point I had to revert to a backup as it was a live system.
Re: STICKY - How to upgrade a Buster image to Bullseye
What are the pros and cons of choosing 32 or 64 bits (explained to someone who doesn't speak 0s and 1s - and even hardly english) ?HawaiianPi wrote: ↑Mon Nov 08, 2021 12:47 pmIf you decide to go with the recommended path, the 64-bit images are also available.
https://www.k-sper.fr
Re: STICKY - How to upgrade a Buster image to Bullseye
This topic is about upgrading, there are plenty of discussions about 32-bit vs. 64-bit, for example viewtopic.php?t=275372
Another short answer is: If you ask this question, so don't know it, then do not choose a beta OS variant, but take the 32-bit variant.
- linuxusr80
- Posts: 1
- Joined: Mon Nov 08, 2021 7:52 pm
Re: STICKY - How to upgrade a Buster image to Bullseye
Please note if you have pihole installed, connman will enable itself on port 53. Disabling connman service resolves. in addition if you have a static ip address, eth0 is renamed and eth0 is disabled. you need to update in you dhcpcs.conf file.
Re: STICKY - How to upgrade a Buster image to Bullseye
Hmmm... I tried upgrading. My Pi got to the splash screen, but then the screen went blank, the green light went solid for ~10 seconds, then it went off and only the red light was on and didn't boot. It only booted properly when I used fkms in config.txt.
Re: STICKY - How to upgrade a Buster image to Bullseye
Somehow the boot- or startupprocess stalls and you need to connect a serial cable maybe or make sure you have working/reliable ssh access. The graphics stuff can have many surprises. You can add the following lines to the config.txt:
enable_uart=1
uart_2ndstage=1
The latter one is needed for example when you have problems very early in the bootprocess, it also matters if it is a Pi4 or Pi3-
Also a general tip is to examine the fresh Bullseye image, after you have booted with it once. It is just comparing a successful start with a failing one and hopefully you figure out what the problem is.
Re: STICKY - How to upgrade a Buster image to Bullseye
Upgrade went well on 64-bit, however I did manually need to change the window manager to "mutter".
The only minor issue I've seen so far is that the "Notifications" panel does not appear, and I can't see it in the list to add it.
Does anybody know the name of the package so I can install it manually?
The only minor issue I've seen so far is that the "Notifications" panel does not appear, and I can't see it in the list to add it.
Does anybody know the name of the package so I can install it manually?
Re: STICKY - How to upgrade a Buster image to Bullseye
I had used RonR's script to upgrade for testing on a fresh Buster.
I just did an fresh installation of the release image.
The Fresh install & reinstall apps took considerably less time and effort.
There were a few other differences I noted. WiringPi is missing from fresh install (as expected).
There are still a few lose ends.
dtparam=act_led_trigger=heartbeat didn't work.
ssh keys changed (not sure if the differences significant).
I just did an fresh installation of the release image.
The Fresh install & reinstall apps took considerably less time and effort.
There were a few other differences I noted. WiringPi is missing from fresh install (as expected).
There are still a few lose ends.
dtparam=act_led_trigger=heartbeat didn't work.
ssh keys changed (not sure if the differences significant).
Re: STICKY - How to upgrade a Buster image to Bullseye
Thanks for your reply. In the mean time I deleted the installation (I used it mostly for testing) and I will reinstall the nightly build based on bullseye.fik wrote: ↑Mon Nov 08, 2021 5:49 pmI've stumbled upon this one as well.nikal wrote: ↑Mon Nov 08, 2021 1:03 pmHi!
I'm running the 64bit version on a rpi 4/8G. The apt update gives me an error regarding the debian-security updates/bullseye repo which has no release file and therefore it's by default disabled. Should I override this error somehow or it's OK to leave it as it is ?
Thanks in advace for your reply
The original line in /etc/apt/sources.listshould be changed toCode: Select all
deb http://deb.debian.org/debian-security/ buster/updates main contrib non-freeCode: Select all
deb http://security.debian.org/debian-security bullseye-security main contrib non-free
Truth is that I used it to compile Vulkan GPU driver but after switching to bullseye and despite I faced no issues with the compilation, driver didn't load no matter what.
Re: STICKY - How to upgrade a Buster image to Bullseye
In case you have no (wired only) network after the update, check if you have this file:
The content of the file in my case was:
Delete this file to make dhcpcd run again.
Code: Select all
/etc/systemd/system/dhcpcd.service.d/wait.confCode: Select all
[Service]
ExecStart=
ExecStart=/usr/lib/dhcpcd5/dhcpcd -q -w
Jump to
- Community
- General discussion
- Announcements
- Other languages
- Deutsch
- Español
- Français
- Italiano
- Nederlands
- 日本語
- Polski
- Português
- Русский
- Türkçe
- User groups and events
- Raspberry Pi Official Magazine
- Using the Raspberry Pi
- Beginners
- Troubleshooting
- Advanced users
- Assistive technology and accessibility
- Education
- Picademy
- Teaching and learning resources
- Staffroom, classroom and projects
- Astro Pi
- Mathematica
- High Altitude Balloon
- Weather station
- Programming
- C/C++
- Java
- Python
- Scratch
- Other programming languages
- Windows 10 for IoT
- Wolfram Language
- Bare metal, Assembly language
- Graphics programming
- OpenGLES
- OpenVG
- OpenMAX
- General programming discussion
- Projects
- Networking and servers
- Automation, sensing and robotics
- Graphics, sound and multimedia
- Other projects
- Media centres
- Gaming
- AIY Projects
- Hardware and peripherals
- Camera board
- Compute Module
- Official Display
- HATs and other add-ons
- Device Tree
- Interfacing (DSI, CSI, I2C, etc.)
- Keyboard computers (400, 500, 500+)
- Raspberry Pi Pico
- General
- SDK
- MicroPython
- Other RP2040 boards
- Zephyr
- Rust
- AI Accelerator
- AI Camera - IMX500
- Hailo
- Software
- Raspberry Pi OS
- Raspberry Pi Connect
- Raspberry Pi Desktop for PC and Mac
- Beta testing
- Other
- Android
- Debian
- FreeBSD
- Gentoo
- Linux Kernel
- NetBSD
- openSUSE
- Plan 9
- Puppy
- Arch
- Pidora / Fedora
- RISCOS
- Ubuntu
- Ye Olde Pi Shoppe
- For sale
- Wanted
- Off topic
- Off topic discussion