wiki:linux:upgrading_raspbian_buster_bullseye

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
wiki:linux:upgrading_raspbian_buster_bullseye [2025/01/07 12:37] – removed - external edit (Unknown date) 127.0.0.1wiki:linux:upgrading_raspbian_buster_bullseye [2025/01/07 12:37] (current) – ↷ Links adapted because of a move operation Greg
Line 1: Line 1:
 +===== Upgrading from Debian Buster to Bullseye Notes =====
 +
 +Typically upgrading between Debian releases (e.g. from 10 to 11) is pretty smooth. You just need to edit your ''%%/etc/apt/sources.list%%'' file and replace any instances of "buster" with "bullseye" or whatever the release names are that you're upgrading to/from. But when I was upgrading my Raspberry Pis from Buster to Bullseye I ran into an issue with DHCPCD that prevented the system from getting a DHCP address when rebooting. Plus SystemD's "predictable interface names" setting forced itself back on and also broke things.
 +
 +I'd recommend making these changes //after// the update, and //before// you reboot so you don't have to hit up the physical console.
 +
 +=== Fix DHCPCD ===
 +
 +DHCPCD can't start after the upgrade because the location of the binary changed, and the SystemD unit file wasn't updated. This may have been one of the file changes that I was prompted on whether to keep or change during the upgrade, but either way the fix is to update ''%%/etc/systemd/system/dhcpcd.service.d/wait.conf%%'' to read:
 +
 +<code>
 +[Service]
 +ExecStart=
 +ExecStart=/usr/sbin/dhcpcd -q -w
 +</code>
 +
 +**Note:** I'm not quite sure why there were two ''%%ExecStart=%%'' lines, but it only uses the latest (second) value so it doesn't affect anything that I can tell, and I don't want to remove it in case it's needed somehow.
 +
 +=== Disable Predictable Interface Names ===
 +
 +Now this fix is just a personal preference, but the "predictable interface names" on my Raspberry Pi machines are always awful and I much prefer the old ''%%eth0%%''-esque names. This does introduce the possibility for a race condition where another network interface may take the name before the primary network interface initializes, but on Raspberry Pi you're likely not going to be adding many (if any) extra network interfaces. Thus I leave the new interface names on for my non-Raspberry Pi servers, and use the old names for my Raspberry Pis.
 +
 +The simplest way to make this change is to use ''%%raspi-config%%'' which is the Raspberry Pi system config tool. First run that tool as root/with sudo, and go to Advanced Options.
 +
 +{{:raspi-config-1.png?direct&400|}}
 +
 +Select Network Interface Names.
 +
 +{{wiki:linux:install_davinci_resolve:raspi-config-2.png?direct&400|}}
 +
 +You'll be prompted whether you want them enabled or disabled, so select "No" for disabled.
 +
 +{{wiki:linux:install_davinci_resolve:raspi-config-3.png?direct&400|}}
 +
 +Hit tab twice and enter to finish.
 +
 +{{wiki:linux:install_davinci_resolve:raspi-config-4.png?direct&400|}}
 +
 +Finally reboot your system. (Or do so later...)
 +
 +{{wiki:linux:install_davinci_resolve:raspi-config-5.png?direct&400|}}
 +
 +=== Reboot ===
 +
 +Now you can safely reboot the system (if you haven't already triggered it from the config tool) to let the package upgrades take over, or just restart the ''%%dhcpcd%%'' service if you've already rebooted post-upgrade and are trying to fix the networking.
 +
 +Good luck!