When you see my other results (previous post), I think you’ll agree that following your process is the best way to go (at this time) if you want to work with Debian 12 and Klipper.
To simplify executing the Debian 12 upgrade steps outlined above, I created the simple script “Debian11to12.sh”: Debian11to12.zip (710 Bytes)
It’s not as automated as I would like (you still have to select “Y” or “Yes” in the sudo apt full-upgrade step) but it eliminates the copy and pasting.
I’m curious to see how the upgrade process works starting with MainsailOS, rather than with the basic (Debian 11 based) RPi OS - I’ll let you know how that works (should be easier than working with your .7z image).
Okay, I’ve tried the update process with the 32-Bit Mainsail OS on both a Raspberry Pi 4B and CM4 - both fail at the blue screen for the “Package configuration”:
The ^[[D and ^[[C strings are my trying to move the <Yes>/<No> selections. The Enter key does not work and after power cycling the two RPis do not boot properly.
So, your process does work but not on hosts loaded with MainsailOS and I wouldn’t recommend trying the update after Klipper is installed but it seems to work fine before Klipper is installed.
something is wrong with ur sdcard, hardware or i dont know.
in general these are special characters which the console dont know how to interpred
what keys have u pressed?
i extracted my 7z image again and wrote this extraced image on two different sdcards, and every sdcard works fine. it boots up and i can acces the webinterface, mainsail and fluidd:
this behavior with the blue screen yes no selection does not depend if klipper is installed or not.
if you restart your pi at this stage and if the update has not finished its normal that its “bricked” and cannot boot.
The SD Cards have been checked/reused without any issues on Raspberry Pi Imager with both predetermined OS’s (Raspberry Pi OS -32 & -64 bit, MainsailOS -32 & -64 bit) as well as CB1 custom OS’s (Armbian and Debian).
I’ve tried the process now with:
Tera Term (the screenshots you normally see)
PuTTY on Windows
Linux Terminal
Have you tried your process with an SD Card preloaded with Mainsail OS yourself?
/edit: maybe s.o. else can try my image if it works. would be a good start for people who are not so fimiliar with rpi or linux, and to be on the latest debian linux with the latest security patches is always good
I’m following this with a certain interest, less about the technical details, because I know it is working and did it already, but with the question why you are spending so much energy into it.
My personal opinion:
If it can be done with a reasonable amount of effort, then a clean installation is always preferable.
Major version updates within a distribution really only make sense if they are complex installations that are not simply moved quickly. And even here, the effort to rework and ensure full functionality is often greater than the actual time savings.
For such a simple installation like Klipper, I would never go down this upgrade path.
You’re going to have to be more explicit in your explanation of what’s happening here and what you expect. You’re asking me to spend more than an hour just doing the SD Card image (it takes that long to run Windows32 Disk Imager on the 33GB .img file) and I’m wondering if there is an easier way to figure out our differences.
Just to go what your instructions are:
Get a Raspberry Pi (4B) running. I presume accessing it via SSH.
Execute sudo rpi-eeprom-update -a command.
Once step 2. is done, sudo reboot.
Next, “try again my sdcard image”. I presume this means that
Okay, I’ve read through about rpi-eeprom-update and rather than go through all this blindly, wouldn’t it be easier to just to compare the bootloader versions on the Raspberry Pis we’re working with?
For example, for the RPi I’m going to put this image on, the vcgencmd bootloader_version command response is:
Now, when I run sudo rpi-eeprom-update, it indicates that there is an update available:
$ sudo rpi-eeprom-update
[sudo] password for biqu:
*** UPDATE AVAILABLE ***
BOOTLOADER: update available
CURRENT: Tue 26 Apr 10:24:28 UTC 2022 (1650968668)
LATEST: Wed 11 Jan 17:40:52 UTC 2023 (1673458852)
RELEASE: default (/lib/firmware/raspberrypi/bootloader/default)
Use raspi-config to change the release.
VL805_FW: Using bootloader EEPROM
VL805: up to date
CURRENT: 000138a1
LATEST: 000138a1
What do you get when you run these commands?
Regardless, I’m not sure why the bootloader version will affect an update process from Debian 11 to Debian 12 - could you explain what your thinking is here?
As I’ve discussed elsewhere, I’ve been writing some Katapult/Klipper installation scripts and I wanted to test them on all available OS versions available to me so that when I ask somebody to try them, I have a reasonable level of confidence that they will work (this is the CB1 discussion we’re having separately).
My thinking was that at some point the basic Raspberry Pi OS will be based on Debian 12 and I wanted to test my scripts on that. Using the process and images available I couldn’t do that but with the steps @Hundsbuah laid out above, I got a Debian 12 image and was able to test my scripts.
They work starting with a vanilla Debian 11 RPi 4B and CM4 OS (32 or 64 bit) which really meets my requirements and I can use this to test my scripts. This is really is where things should have ended for me.
I have not been able to get a working Debian 12 image, whether I download it from the Debian repository or use the image provided by @Hundsbuah - I went through the work trying to load the images as a) a favour to @Hundsbuah and b) intellectual curiosity.
Right now, my intellectual curiosity tank is running low, which is why the pushback in my previous reply to @Hundsbuah . I have the tools I need to test my scripts and I’m willing to try something but I want to understand what is expected before I tie up a system for a couple of hours and monitor it when there are other things I need to do.
If there’s something valuable to be gained from this then I’m all in. Otherwise, I’ve got what I need and I can move on.
im just curious by myself why its not working, because i dont understand it. but of course its ok if you dont have any time or dont want to spend hours of testing. its totally fine. no worries
Pi OS and Debian are very close relatives but have notable differences, e.g. in the camera stack and also others. A direct comparison might not be valid, at least not in all cases
E.g. with the CB1 you can easily test Debian 12 as the current release of Armbian fully supports it and is Bookworm based. (I’m currently printing with it and did previously with a Banana Pi BPI-M5)
What kind of differences would the camera stack (and other concurrent apps) make in terms of basic Klipper (and Moonraker and Mainsail) operation? I’m not sure how that would affect this test.
Thanx for the pointer. I’m using Armbian 23.8.1 which, according to Distrowatch is Bookworm.
