Update ends in black screen

[DarkStar3003]

Hello

I have installed sovolized-v25.5.0-trunk.87-01 on my Klipper Screen (SV06+). Everything works fine until I try to update via Mainsail. Every attempt ends in a black screen, even via SSH I can no longer access.

I could not find any information on the website, so I ask here.
Is an update possible?
If so, how do I have to do it correctly so as not to destroy the system?

Sorry if something should be incomprehensible. My English is not very good, I translated with DeepL.

Best regards!

[torte71]

Oh sh*t... there seems to be some new kernel update that inhibits boot.
Kernel updates did work flawlessly until now.
At least it is reproducible.

[DarkStar3003]

Hello

Thanks for the information.

What should I do? Wait for a new image, or reinstall and do not update.

Best regards!

[torte71]

I think it's the best to reflash the image and lock the kernel before doing system updates:
sudo apt-mark hold linux-image-current-rockchip64

(Or don't update the system, if you don't know how to log in using putty/ssh).

I will report back, once that kernel issue is resolved.

[DarkStar3003]

Vielen Dank, so mache ich das.

[dav970]

I too fell prey to the kernel upgrade (had flashed sovolized-v25.5.0-trunk.87-01-bookworm)

Reflashed with sovolized-v25.2.0.05 and when I tried to lock the kernel it came back as already locked. Ran every update and all is well.

NOTE: kiauh shows system updates available I assume due to kernel being "out of date"

Thank you for excellent work. The web site is "5 star"

[torte71]

That bootloop issue should have been fixed in recent versions (the bootloader needed to be updated from v2022.07 to v2025.01).

There is a new "klipperized" image containing that updated bootloader: v25.2.3-standard-01
(The version numbering scheme has changed, the releases with "standard" in their name are more recent than e.g. v25.5.0-trunk.87 or v25.2.0.05. Yes, it's a little bit confusing.)

The bootloader ("u-boot") can be updated in former images.
Here is a guide that shows the process of updating the bootloader and rewriting the bootsector.

It is also possible to upgrade former images to the most recent version, see the upgrading guide (it also contains the steps to upgrade the bootloader). Upgrading has the advantage that it will leave your klipper config/setup as it is.

After upgrading the bootloader, kernel updates are possible again (without breaking the system).
Though it is also a good option to just lock a working kernel version - that is the most reliable way preventing issues like this specific bootloop problem. I am positive, that boot problems like this are fixed for the future, but well... bugs tend to appear unexpected and uninvited.

[dav970]

Thank you for the clarification!

In place upgrade worked a perfectly. Now should I lock the kernel again or leave it and hope for the best?

sudo apt-mark hold linux-image-current-rockchip64 is still correct or new kernel requires an edit?

[torte71]

That apt-mark command is still valid.

I can't tell, what is best for your needs (apart from taking regular backups).
Most reliable is not updating anything from a working system (and not making anything accessible from outside your home network, as it may contain unfixed security holes).
Locking the kernel is a very reliable option and it is very unlikely, that something will break because of not updating the kernel. Regarding security aspects, it is not very likely that kernel bugs can be exploited through remote network communication (e.g. exposed SSH port, obico-anywhere & co.). But in the end, "not very likely" is the opposite of "impossible".
Keeping everything up-to-date is usually the best option security-wise, but it has the highest risk of incompatible updates.
Choose your poison.

I personally don't expect any more of such showstopper bugs.
But I can't foresee the future, and it is always possible that some updates break something that we need - that doesn't have to be a kernel update. Network setup, USB handling, Python versions (and whatever else) - there's so much in userspace with the potential of breaking things.

What is "likely"?
I would have rated it frickin' unlikely, that this bootloop problem suddenly pops up after silently dwelling for several years (the mks-klipad50 is not the only board affected).

Backup.
Everything not backed up is obsolete by definition.
That's probably the best, I can say about this question.

[dav970]

My klipad sh*t the bed today. It was off my network so I initiated a reboot from the touchscreen. It appeared to shut down normally (GUI closed then many lines of sideways text scrolled by). But on restart green LED only and black screen.

I'll reflash in a bit but I was wondering if Armbian is back to keneral incompatibility issues.

[torte71]

As I am currently on holiday, I can't check before 2 weeks. But I'll have a look after that for sure.

[torte71]

@dav970 I could not detect any incompatibilities: I just did an "apt upgrade" and rebooted, but everything is still working as expected (LEDs are both blinking, KlipperScreen GUI shows up).

[dav970]

@torte71 My apologies, I should have updated this. I've determined the issue with my unit is in the 24V power system. I (accidently) discovered it runs perfectly on 5V supplied VIA the "download" USB port.

Sovol has released tools to write an image to the EMMC on their SV06 Ace mainboard. I was attempting to use those tools which is why I connected to the download port. I never did get the Klipad to go into DFU mode but I didn't try very hard after I discovered that the unit will boot normally when supplied 5V.