Differences

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

--- gcode_storage [2024/10/18 14:44] – [GCode storage] torte
+++ gcode_storage [2025/01/21 12:27] (current) – torte
@@ Line 1: / Line 1: @@
-===== Sovol KlipperScreen =====
+{{page>redirect#this_wiki_has_moved}}
-==== GCode storage ====
+https://torte71.github.io/InsideSovolKlipperScreen/gcode_storage.html
+{{page>redirect#section}}
+----
+===== Sovol KlipperScreen (Makerbase MKS KLIPAD50) =====
+==== Expand G-Code storage space ====
 Experienced Linux users: Scroll down to [[#for_the_linux_gurus|For the linux gurus]] for a short sum-up what is required.
@@ Line 145: / Line 150: @@
   * In ''/etc/fstab'' use the parameters ''nofail,x-systemd.device-timeout=9'' to allow booting if that drive is not inserted
   * Use the partitions UUID in ''/etc/fstab'', this makes the automounter ignore this drive
-  * Make the filesystem writable for users (''chmod -r mks:mks <YOUR_MOUNTPOINT>'').
+  * Make the filesystem writable for users (''chown -R mks:mks <YOUR_MOUNTPOINT>'').
-Quick tip: When there is no usb-drive inserted, create a directory called "NO_USB_MOUNTED" in the gcode directory. If the usb-drive is not inserted or broken, this directory will be visible and you know, that gcode files will end up on the systems default file system instead of the usb-drive.
+=== A last tip ===
+When there is no usb-drive inserted, create a directory called "_NO_USB_MOUNTED_" (or whatever name you like) in the gcode directory. If the usb-drive is not inserted or broken, this directory will be visible and you know, that gcode files will not end up on the usb-drive, but on the internal file system.