bootloop
This is an old revision of the document!
Sovol KlipperScreen (KLIPAD50)
Boot loops / Black screen
Some causes for the looping boot animation:
- Damaged “saved_variables.cfg”
- Other damaged configuration files (printer.cfg, moonraker.cfg, etc.)
Typical causes for the damaged files:
- No more space left on the filesystem
- Powering off the KlipperScreen by the switch without shutting it down first
- Incompatible or wrongly installed additional klipper macros
Some causes for a black screen:
- Updating the system without having the kernel and dtb file locked
(That became unlikely after Armbian Buster got removed from online archives in spring 2024.)
Fixes:
- Always make sure that there is enough space left on the filesystem first by removing old gcode files (and then reboot the device).
- Clean up the
saved_variables.cfg
as shown below - Do a factory reset using Sovol's
armbian-update.deb
- Do a full reflash of the eMMC using Sovol's
KLIPAD50_IMAGE
Cleaning up saved_variables.cfg
- Open that file in the web frontend (found in the
machine
tab in mainsail or the configuration tab{…}
in fluidd) - Replace the content of that file with the following lines, then save and reboot the device:
[Variables] filepath = '' last_file = '' was_interrupted = False
Factory reset using Sovol's armbian-update.deb
- Download the
armbian-update.deb
for your device: - If the above links have changed, find them on Sovol's pages:
- SV06 / SV06+: https://www.sovol3d.com/collections/fdm-parts/products/sovol-klipper-screen-for-sv06-sv06-plus
(scroll down to “Sovol SV06 Klipper Screen Firmware” or “Sovol SV06 Plus Klipper Screen Firmware”) - SV07: https://wiki.sovol3d.com/en/SV07 (look for “Firmware”, e.g. “SV07 1.0.17 Latest Firmware (5th Oct 2023)”)
- SV07+: https://wiki.sovol3d.com/en/SV07PLUS (look for “Firmware”, e.g. “SV07 Plus 1.0.8-07P Firmware (5th October 2023)”)
Full reflash of the eMMC using Sovol's KLIPAD50_IMAGE
bootloop.1732089588.txt.gz · Last modified: 2024/11/20 08:59 by torte