User Tools

Site Tools


bootloop

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
bootloop [2024/11/20 09:33] tortebootloop [2025/01/21 12:22] (current) torte
Line 1: Line 1:
-===== Sovol KlipperScreen (KLIPAD50) ===== +{{page>redirect#this_wiki_has_moved}} 
-==== Boot loops Black screen ====+https://torte71.github.io/InsideSovolKlipperScreen/bootloop.html 
 +{{page>redirect#section}} 
 +----
  
-== Some causes for the looping boot animation ==+====== Sovol KlipperScreen (Makerbase MKS KLIPAD50) ====== 
 +===== Boot loops / Black screen ("unbricking") ===== 
 + 
 +==== Some causes for the looping boot animation ====
   * Damaged "saved_variables.cfg"   * Damaged "saved_variables.cfg"
   * Other damaged configuration files (printer.cfg, moonraker.cfg, etc.)   * Other damaged configuration files (printer.cfg, moonraker.cfg, etc.)
 +  * KlipperScreen in a too recent version (depends on python-3.8, which is not available for Sovol's outdated armbian buster). See [[https://netztorte.de/3d/doku.php?id=updating#klipperscreen_python_38|klipperscreen_python_38]] for a fix.
  
-== 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 ''saved_variables.cfg'' as shown below   * Clean up the ''saved_variables.cfg'' as shown below
-  * Do a factory reset using Sovol's ''armbian-update.deb'' +  * If that did not help: Do a factory reset using Sovol's ''armbian-update.deb'' 
-  * Do a full reflash of the eMMC using Sovol's ''KLIPAD50_IMAGE''+  * If even that did not work: Do a full reflash of the eMMC using Sovol's ''KLIPAD50_IMAGE''
  
-== Cleaning up ''saved_variables.cfg'' ==+==== 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)   * 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:   * Replace the content of that file with the following lines, then save and reboot the device:
Line 30: Line 36:
 </code> </code>
  
-== Factory reset using Sovol's ''armbian-update.deb'' ==+==== Factory reset using Sovol's ''armbian-update.deb'' ====
   * **This will revert all your changes to the config files** (like printer.cfg, etc.).\\ If the device can still be reached by the web frontend, you may want to back up these files first.   * **This will revert all your changes to the config files** (like printer.cfg, etc.).\\ If the device can still be reached by the web frontend, you may want to back up these files first.
   * Download the ''armbian-update.deb'' for your device:   * Download the ''armbian-update.deb'' for your device:
Line 47: Line 53:
   * The update process is also shown in this video: https://www.youtube.com/watch?v=b2jUo1KnxZw&t=157s   * The update process is also shown in this video: https://www.youtube.com/watch?v=b2jUo1KnxZw&t=157s
  
-== Full reflash of the eMMC using Sovol's ''KLIPAD50_IMAGE'' ==+==== Full reflash of the eMMC using Sovol's ''KLIPAD50_IMAGE'' ====
   * It is recommended to get an USB-eMMC adapter like [[https://www.aliexpress.us/item/3256805428404625.html?spm=a2g0o.store_pc_allProduct.8148356.1.7bca1ad70ZKzwN&pdp_npi=4%40dis%21USD%21US%20%246.99%21US%20%241.99%21%21%216.99%211.99%21%40212aa2ac17038484556595237e184f%2112000033755356288%21sh%21US%21240163459%21&gatewayAdapt=glo2usa|this one]].\\ It allows you to flash the eMMC directly from your PC using software like e.g. [[https://www.balena.io/etcher/|Balena Etcher]]   * It is recommended to get an USB-eMMC adapter like [[https://www.aliexpress.us/item/3256805428404625.html?spm=a2g0o.store_pc_allProduct.8148356.1.7bca1ad70ZKzwN&pdp_npi=4%40dis%21USD%21US%20%246.99%21US%20%241.99%21%21%216.99%211.99%21%40212aa2ac17038484556595237e184f%2112000033755356288%21sh%21US%21240163459%21&gatewayAdapt=glo2usa|this one]].\\ It allows you to flash the eMMC directly from your PC using software like e.g. [[https://www.balena.io/etcher/|Balena Etcher]]
     * Follow Sovol's guide on how to flash the eMMC card: https://github.com/Sovol3d/SOVOL_KLIPAD50_SYSTEM     * Follow Sovol's guide on how to flash the eMMC card: https://github.com/Sovol3d/SOVOL_KLIPAD50_SYSTEM
Line 54: Line 60:
     * vasyl83's guide using two thumb drives: https://github.com/vasyl83/SV07update     * vasyl83's guide using two thumb drives: https://github.com/vasyl83/SV07update
     * 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