I was able to (after a "lot" of headaches), get from Buster to Bullseye.
Though I just got rid of connman today (the services are still in the /etc/systemd/system, but they're dead). In case anyone did this and their WiFi won't stay on at boot, get rid of connman, BUT, when you do, be sure to add a sudo reboot at the end or you'll be doing it manually AT the Pi, because it'll break all networking until a reboot, then NetworkManager has free reign.
So, today, I was in the process of trying to get the RSync to work with the Pi as a backup destination for a RAID, sadly, it bogged down to the point where it tossed the entire session out to the login window. Subsequent reboots, got me back to that same login window, which raspi-config was doing incorrectly for the Auto-Login, I've since fixed it manually. So, it boots up, right into the account, everything is working perfectly.
So why am I thinking of upgrading again? The window manager for Bullseye, I'm hoping to get away from it. The mutter window manager thinks it is "pretty" to do animations remotely. Anything "pretty" on a computer costs CPU time and with no way to turn the animations off, "pretty" becomes "pretty slow". Opening a window now causes a "roll out" animation, which takes about 3 seconds to complete when it is full screen (and the CPU spikes to over 60% just for that "pretty" behavior). If the animations and rounded corners were gone, I'd have nothing to worry about upgrading again, until software I use tells me the updates need another OS build.
But going from Bullseye to Bookworm seems daunting, has anyone done it successfully? With the increase of Linux users in the past decade, with distros that make it "simpler to upgrade", I'm surprised that Raspbian itself is in the dark ages with no "upgrade" software to actually automate going between builds safely and properly.
I am backing this system up to a second SD card (I use 2, one as operating and one as a backup, so if I break it, I can swap them and back to where I was before I broke it). And I may attempt to do the Bookworm jump, but would rather wait here a bit, since things are working and I don't always go right to the Pi's desktop to see it still running, since I can tell it is still running, because without it, the services the network uses aren't there and I'd know immediately.
So, have you done it?
GuruSR.
Though I just got rid of connman today (the services are still in the /etc/systemd/system, but they're dead). In case anyone did this and their WiFi won't stay on at boot, get rid of connman, BUT, when you do, be sure to add a sudo reboot at the end or you'll be doing it manually AT the Pi, because it'll break all networking until a reboot, then NetworkManager has free reign.
So, today, I was in the process of trying to get the RSync to work with the Pi as a backup destination for a RAID, sadly, it bogged down to the point where it tossed the entire session out to the login window. Subsequent reboots, got me back to that same login window, which raspi-config was doing incorrectly for the Auto-Login, I've since fixed it manually. So, it boots up, right into the account, everything is working perfectly.
So why am I thinking of upgrading again? The window manager for Bullseye, I'm hoping to get away from it. The mutter window manager thinks it is "pretty" to do animations remotely. Anything "pretty" on a computer costs CPU time and with no way to turn the animations off, "pretty" becomes "pretty slow". Opening a window now causes a "roll out" animation, which takes about 3 seconds to complete when it is full screen (and the CPU spikes to over 60% just for that "pretty" behavior). If the animations and rounded corners were gone, I'd have nothing to worry about upgrading again, until software I use tells me the updates need another OS build.
But going from Bullseye to Bookworm seems daunting, has anyone done it successfully? With the increase of Linux users in the past decade, with distros that make it "simpler to upgrade", I'm surprised that Raspbian itself is in the dark ages with no "upgrade" software to actually automate going between builds safely and properly.
I am backing this system up to a second SD card (I use 2, one as operating and one as a backup, so if I break it, I can swap them and back to where I was before I broke it). And I may attempt to do the Bookworm jump, but would rather wait here a bit, since things are working and I don't always go right to the Pi's desktop to see it still running, since I can tell it is still running, because without it, the services the network uses aren't there and I'd know immediately.
So, have you done it?
GuruSR.
Statistics: Posted by GuruSR — Wed Jan 08, 2025 9:11 pm