Re: STICKY - How to upgrade a Buster image to Bullseye
Yes. That should work.frRySuuZ9FFDQw wrote: ↑Thu Dec 23, 2021 1:32 pmAhhh :D
yes, here I have a file, content:Code: Select all
pivpn-limit-bullseyeI assume when I remove this file then it should work?Code: Select all
Package: * Pin: release n=bullseye Pin-Priority: -1 Package: wireguard wireguard-dkms wireguard-tools Pin: release n=bullseye Pin-Priority: 100
I don't know if it will cause problems with your pivpn installation though.
Unreadable squiggle
- frRySuuZ9FFDQw
- Posts: 4
- Joined: Thu Dec 23, 2021 11:40 am
Re: STICKY - How to upgrade a Buster image to Bullseye
Just a short update.
I removed the file, the update started. After reboot the pi spits many error messages. :(
So I will restoring my backup.
Nevertheless thank you.
I removed the file, the update started. After reboot the pi spits many error messages. :(
So I will restoring my backup.
Nevertheless thank you.
Re: STICKY - How to upgrade a Buster image to Bullseye
Made a copy of my RPi SD card today, and used the OP instructions and have successfully updated to Bullseye from Buster. I am anything but an expert at this whole RPi world and didn't have a lot of faith in getting this done,, but am happy that it worked well. :D
Re: STICKY - How to upgrade a Buster image to Bullseye
Thanks @ spl23
I followed his suggestion to the letter and it worked perfectly.
It took quite a long time to update Buster following @pcmanbob's post and then upgraded to Bullseye .The only problem I had and may not quite sorted yet is Pihole.
Edit: the error I had with Pi-hole is described
here with a workaround.
I followed his suggestion to the letter and it worked perfectly.
It took quite a long time to update Buster following @pcmanbob's post and then upgraded to Bullseye .The only problem I had and may not quite sorted yet is Pihole.
Edit: the error I had with Pi-hole is described
here with a workaround.
Re: STICKY - How to upgrade a Buster image to Bullseye
Tried all the usual steps, have tried combinations of buster and bullseye, each time results in no upgrade, no packages to update/upgrade on the final dist-upgrade reboot still says buster on etc/os-release. and when trying to install any new packages it says:
Package XXXX is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
looks like it's completely skewed the sources.
IF I roll back the changes and update again it works fine and I'm able to install packages again.
Package XXXX is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
looks like it's completely skewed the sources.
IF I roll back the changes and update again it works fine and I'm able to install packages again.
Re: STICKY - How to upgrade a Buster image to Bullseye
@spl23
Thnx for the instrucions
May its a good idea to add the sed command to replace the sources.list entries with one command.
best regards
Thnx for the instrucions
May its a good idea to add the sed command to replace the sources.list entries with one command.
best regards
- pi-anazazi
- Posts: 1194
- Joined: Fri Feb 13, 2015 9:22 pm
Re: STICKY - How to upgrade a Buster image to Bullseye
For the record: removing this wait.conf (and I did apt purge rfkill, just to be on the safe side) is also necessary to get wifi access back after upgrading (had a very remote 3A, what a pain!)ElDavo wrote: ↑Tue Nov 09, 2021 5:40 pmIn 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:Code: Select all
/etc/systemd/system/dhcpcd.service.d/wait.confDelete this file to make dhcpcd run again.Code: Select all
[Service] ExecStart= ExecStart=/usr/lib/dhcpcd5/dhcpcd -q -w
Kind regards
anazazi
anazazi
Re: STICKY - How to upgrade a Buster image to Bullseye
I finally got round to upgrading my Pi4 from Buster to Bullseye. I always use the Raspi Lite distribution, so no desktop packages (and hopefully no connman).
After following the Debian upgrade guide, everything seemed successful until after a reboot.
I had the same dhcpcd wait issue as described here. It's a headless Pi connected via SSH so it's rather annoying to have to physically connect this up to KVM to see what the issue is.
The provided solution worked for me. No more DHCP errors.
I also did not choose the "wait for connection on boot" option in raspi-config, so I don't know how I ended up with the problem in the first place.
After following the Debian upgrade guide, everything seemed successful until after a reboot.
I had the same dhcpcd wait issue as described here. It's a headless Pi connected via SSH so it's rather annoying to have to physically connect this up to KVM to see what the issue is.
The provided solution worked for me. No more DHCP errors.
I also did not choose the "wait for connection on boot" option in raspi-config, so I don't know how I ended up with the problem in the first place.
Re: STICKY - How to upgrade a Buster image to Bullseye
Same here, except I didn't delete the file but changed the ExecStart. Still a PITA as I had to get the remote Pi sent to me so I could fix it.pi-anazazi wrote: ↑Sat Jan 29, 2022 7:41 pmFor the record: removing this wait.conf (and I did apt purge rfkill, just to be on the safe side) is also necessary to get wifi access back after upgrading (had a very remote 3A, what a pain!)ElDavo wrote: ↑Tue Nov 09, 2021 5:40 pmIn 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:Code: Select all
/etc/systemd/system/dhcpcd.service.d/wait.confDelete this file to make dhcpcd run again.Code: Select all
[Service] ExecStart= ExecStart=/usr/lib/dhcpcd5/dhcpcd -q -w
[edit]
Deleting the file also worked
[/edit]
- OldSchool77
- Posts: 1
- Joined: Sun Feb 06, 2022 8:33 pm
Re: STICKY - How to upgrade a Buster image to Bullseye
I have a highly configured Pi (multi-user etc) so I used a version of this to upgrade to Bullseye. After a few weird reboots and apt-get (apt didn't work) upgrades it worked really well. Beforehand I set the flag in config.txt and did a firmware update to switch kernel to 64 bit.
My question is how do I know if I am in 64 bit userland? Or is this automatic when I point to a Bullseye repository using a 64 bit kernel.
When I enter :
I get:
My question is how do I know if I am in 64 bit userland? Or is this automatic when I point to a Bullseye repository using a 64 bit kernel.
When I enter :
Code: Select all
cat /etc/os-releaseCode: Select all
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
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"
Re: STICKY - How to upgrade a Buster image to Bullseye
I just tried to upgrade, but during reboot, it locked up.
I reverted the boot config change and it booted fine.
Why did the boot config change cause a lockup?
I do have the 7" display/touch pad attached. Is it incompatible with vc4-kms-v3d overlay?`
I reverted the boot config change and it booted fine.
Why did the boot config change cause a lockup?
I do have the 7" display/touch pad attached. Is it incompatible with vc4-kms-v3d overlay?`
Re: STICKY - How to upgrade a Buster image to Bullseye
You run 32-bit userland and that stays 32-bit also when upgrading to BullseyeOldSchool77 wrote: ↑Sat Feb 19, 2022 7:51 pmMy question is how do I know if I am in 64 bit userland? Or is this automatic when I point to a Bullseye repository using a 64 bit kernel.
For 64-bit userland, /etc/os-release has different content; ID=debian NAME="Debian GNU/Linux"
Re: STICKY - How to upgrade a Buster image to Bullseye
I followed your steps, but I cannot find how to do this display resolution reset.
The taskbar is not visible, I cannot use the menu, and there is a black border around the screen.
I have tried to set in raspi-config and /boot/config.txt, without success.
Do you guys have an advice how to fix it?
Re: STICKY - How to upgrade a Buster image to Bullseye
@spl23 can the top post be updated with this information?
This is something I had to do in order to get ethernet working
the error, which is something like "has more than one ExecStart= setting, which is only allowed for Type=oneshot services. Refusing." can be seen with
also, another package was needed as a dependency for the first round of package installs
instead of
I needed this
otherwise I got the message from apt "This may mean that you have requested an impossible situation...."
This is something I had to do in order to get ethernet working
the error, which is something like "has more than one ExecStart= setting, which is only allowed for Type=oneshot services. Refusing." can be seen with
Code: Select all
sudo journalctl -xeElDavo wrote: ↑Tue Nov 09, 2021 5:40 pmIn 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:Code: Select all
/etc/systemd/system/dhcpcd.service.d/wait.confDelete this file to make dhcpcd run again.Code: Select all
[Service] ExecStart= ExecStart=/usr/lib/dhcpcd5/dhcpcd -q -w
also, another package was needed as a dependency for the first round of package installs
instead of
Code: Select all
sudo apt install libgcc-8-dev gcc-8-baseCode: Select all
sudo apt install libgcc-8-dev gcc-8-base libc6-devRe: STICKY - How to upgrade a Buster image to Bullseye
spl23 wrote: ↑Mon Nov 08, 2021 10:58 amFirst 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...?)
...
Hello.
First of all thank you Raspberry Pi Engineers team for this post. I'm glad i found it, it is already gave me relevant information i was missing regarding upgrade (i knew about gcc-8-base, but didn't know about libgcc-8-dev and all the "kms" stuff).
I've been playing around clean installation of bullseye OS for a few days without success.
Look at the following topic on forum: RPi 4 2Gb booting, but OS shows black screen
Recent reply there is mine. I've got RPi 4 2Gb, and clean install of any bullseye desktop results in blank screen and halted device.
The 64bit lite edition is booting, but doesn't get to interactive CLI and doesn't connect to network (either by cable or wifi) to enable terminal connection (it is not stuck though, it displays status updates when i connect/disconnect usb devices; i hope to discover that config.txt might be configured to poll network and connect during boot).
Therefore upgrading in-place from Buster currently is the only available option (and only using old fkms, when i use kms - same problem as with clean installation) for me which makes device boot successfully to desktop (it is missing the standard, apparently PIXEL desktop though, it's replaced by some generic one with distortions and artifacts).
I'd like to use 64bit OS for some future life cycle and compatibility reasons of my works and i cannot upgrade to 64bit Bullseye because no official 64bit buster image available in imager.
Given all above, the info in official Operating system images page regarding compatibility of Bullseye (32-bit) with any Rpi models, and Bullseye (64-bit) with RPi 4, is kind of misleading.
I haven't found any issue opened in git regarding this subject. Hope this issue will be addressed in future. (I've got basic SW testing qualifications, and ready for collaboration if needed.)
Thank you for your work. Keep it up :)
UPDATE: Since the time of this reply devs have updated something and old fkms graphics on new clean installation of Bullseye work without graphics distortions and artifacts on screen. Stopped testing the kms version, because it works on fkms and it is enough for me now.
Re: STICKY - How to upgrade a Buster image to Bullseye
I'm sure I'm just added to the flames here; but, just saying "it's not supported is <unprintable> and a cop out! Anyone spouting or supporting this sort of nonsense should NOT be allowed to use the title "Engineer" or even touch a keyboard, EVER again.
Like it or not, intended or not, the Raspberry Pi is a COMMERCIAL platform with users (like me) who DEPEND on the darn things WORKING 7x24, 365 days a year. Sure, it's hardware, and it fails; but failures can be accounted for and mitigated. What's CAN'T be mitigated is the HOURS required to re-image and re-build every time the OS updates.
NONE of the major OS Linux Vendors would even THINK of pulling this sort of <unprintable>, even with their "community editions"
I have at least 10 Pis, doing all sorts of things like irrigation control. home automation, providing DNS, controlling radios and more. I have backups for each and every one, and for many, I'm actually running redundant hardware. But, I should NOT have to go all the way to "bare metal" just to upgrade the OS.
Get it right, guys!
Clay Jackson
Like it or not, intended or not, the Raspberry Pi is a COMMERCIAL platform with users (like me) who DEPEND on the darn things WORKING 7x24, 365 days a year. Sure, it's hardware, and it fails; but failures can be accounted for and mitigated. What's CAN'T be mitigated is the HOURS required to re-image and re-build every time the OS updates.
NONE of the major OS Linux Vendors would even THINK of pulling this sort of <unprintable>, even with their "community editions"
I have at least 10 Pis, doing all sorts of things like irrigation control. home automation, providing DNS, controlling radios and more. I have backups for each and every one, and for many, I'm actually running redundant hardware. But, I should NOT have to go all the way to "bare metal" just to upgrade the OS.
Get it right, guys!
Clay Jackson
Re: STICKY - How to upgrade a Buster image to Bullseye
There were some changes to RPiOS that simply won't transfer properly, these changes are partly to make it more mainstream Debian so that hopefully upgrades will be easier in the future.
Re: STICKY - How to upgrade a Buster image to Bullseye
Major OS Linux Vendors like SuSE don't sell hardware. They provide 'unstable' (Debian terminology), mostly autogenerated for various SBC's and stay away from dedicated hardware blocks/features. Older Raspbian feels for me as some Debian 'hack', which means 'unstable'. If you want 'stability', then use native Debian. Debian Bullseye is kernel 5.10.x, not some 'rpikernelhack' that follows kernel.org latest mainline LTS. So maybe now it is time to make up you mind. You are 'stuck' with your hardware, but the good things is that Linux is open source, but you have to do it yourself. Or maybe look for some paid support/contract, like Major OS Linux Vendors do offer for Enterprise. Or use a rolling release distro like Arch, then there is no such thing as 'upgrade OS'.N7QNM wrote: ↑Mon Sep 05, 2022 8:46 pmLike it or not, intended or not, the Raspberry Pi is a COMMERCIAL platform with users (like me) who DEPEND on the darn things WORKING 7x24, 365 days a year. Sure, it's hardware, and it fails; but failures can be accounted for and mitigated. What's CAN'T be mitigated is the HOURS required to re-image and re-build every time the OS updates.
NONE of the major OS Linux Vendors would even THINK of pulling this sort of <unprintable>, even with their "community editions"
I have at least 10 Pis, doing all sorts of things like irrigation control. home automation, providing DNS, controlling radios and more. I have backups for each and every one, and for many, I'm actually running redundant hardware. But, I should NOT have to go all the way to "bare metal" just to upgrade the OS.
In the past, for Linux PC's, I also remember that a distro upgrade was far from flawless. Same for MS Windows. But nowadays, my experience is that it goes quite easy, you can even ignore this topic a just do what a Debian Wiki says about Buster->Bullseye upgrade. At least for headless/non-GUI. I would say compare with stuff like FriendlyARM, they just show on some Wiki that a board runs/works with some old kernel and then point to others that provide more convenient OS flavors.
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