bootloop
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| bootloop [2024/11/20 09:33] – torte | bootloop [2025/01/21 12:22] (current) – torte | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== Sovol KlipperScreen (KLIPAD50) ===== | + | {{page> |
| - | ==== Boot loops / Black screen ==== | + | https:// |
| + | {{page> | ||
| + | ---- | ||
| - | == Some causes for the looping boot animation == | + | ====== Sovol KlipperScreen (Makerbase MKS KLIPAD50) ====== |
| + | ===== Boot loops / Black screen (" | ||
| + | |||
| + | ==== Some causes for the looping boot animation | ||
| * Damaged " | * Damaged " | ||
| * Other damaged configuration files (printer.cfg, | * Other damaged configuration files (printer.cfg, | ||
| + | * KlipperScreen in a too recent version (depends on python-3.8, which is not available for Sovol' | ||
| - | == Typical causes for the damaged files == | + | ==== Typical causes for the damaged files ==== |
| * No more space left on the filesystem | * No more space left on the filesystem | ||
| * Powering off the KlipperScreen by the switch without shutting it down first | * Powering off the KlipperScreen by the switch without shutting it down first | ||
| * Incompatible or wrongly installed additional klipper macros | * Incompatible or wrongly installed additional klipper macros | ||
| - | == Some causes for a black screen == | + | ==== 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.) | * 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 == | + | ==== Fixes ==== |
| * Always make sure that there is enough space left on the filesystem first by removing old gcode files (and then reboot the device). | * 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 '' | * Clean up the '' | ||
| - | * Do a factory reset using Sovol' | + | * If that did not help: Do a factory reset using Sovol' |
| - | * Do a full reflash of the eMMC using Sovol' | + | * If even that did not work: Do a full reflash of the eMMC using Sovol' |
| - | == Cleaning up '' | + | ==== Cleaning up '' |
| * Open that file in the web frontend (found in the '' | * Open that file in the web frontend (found in the '' | ||
| * Replace the content of that file with the following lines, then save and reboot the device: | * Replace the content of that file with the following lines, then save and reboot the device: | ||
| Line 30: | Line 36: | ||
| </ | </ | ||
| - | == Factory reset using Sovol' | + | ==== Factory reset using Sovol' |
| * **This will revert all your changes to the config files** (like printer.cfg, | * **This will revert all your changes to the config files** (like printer.cfg, | ||
| * Download the '' | * Download the '' | ||
| Line 47: | Line 53: | ||
| * The update process is also shown in this video: https:// | * The update process is also shown in this video: https:// | ||
| - | == Full reflash of the eMMC using Sovol' | + | ==== Full reflash of the eMMC using Sovol' |
| * It is recommended to get an USB-eMMC adapter like [[https:// | * It is recommended to get an USB-eMMC adapter like [[https:// | ||
| * Follow Sovol' | * Follow Sovol' | ||
| Line 54: | Line 60: | ||
| * vasyl83' | * vasyl83' | ||
| * You may also want to take a look on my guides how to [[booting|boot from external devices]] or [[access|getting access]] (both are quite technical) | * You may also want to take a look on my guides how to [[booting|boot from external devices]] or [[access|getting access]] (both are quite technical) | ||
| + | |||
bootloop.1732091635.txt.gz · Last modified: 2024/11/20 09:33 by torte
