gcode_storage
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
gcode_storage [2024/10/18 14:48] – torte | gcode_storage [2025/01/21 12:27] (current) – torte | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== Sovol KlipperScreen ===== | + | {{page> |
+ | https:// | ||
+ | {{page> | ||
+ | ---- | ||
+ | |||
+ | ===== Sovol KlipperScreen | ||
==== Expand G-Code storage space ==== | ==== Expand G-Code storage space ==== | ||
Line 145: | Line 150: | ||
* In ''/ | * In ''/ | ||
* Use the partitions UUID in ''/ | * Use the partitions UUID in ''/ | ||
- | * Make the filesystem writable for users ('' | + | * Make the filesystem writable for users ('' |
=== A last tip === | === 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 end up on the systems file system instead of the usb-drive. | + | 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. |
gcode_storage.1729255728.txt.gz · Last modified: 2024/10/18 14:48 by torte