From 1b078395537ccd4dc6fea5d097e63b3d63208f21 Mon Sep 17 00:00:00 2001 From: alfrix Date: Fri, 5 Apr 2024 08:58:56 -0300 Subject: [PATCH] docs: troubleshooting put the alternatives collapsed to not distract users from the important bits --- docs/Troubleshooting.md | 32 ++++++++++++++++++-------------- 1 file changed, 18 insertions(+), 14 deletions(-) diff --git a/docs/Troubleshooting.md b/docs/Troubleshooting.md index 8b0158ba..89f3bcb4 100644 --- a/docs/Troubleshooting.md +++ b/docs/Troubleshooting.md @@ -16,8 +16,14 @@ Depending on your setup the file could be accessible from the web interface alon |:-------------------------------------------------------:|:---------------------------------------------------:| | ![mainsail_logs](img/troubleshooting/logs_mainsail.png) | ![fluidd_logs](img/troubleshooting/logs_fluidd.png) | -if you can't find it in the web interface, use sftp to grab the log (for example Filezilla, WinSCP) -Located at `~/printer_data/logs`or in `/tmp/` if the former doesn't exist. +if you can't find it in the web interface, you will need to grab the system logs as explained below + +??? tip "Alternative: Using sftp to grab the logs" + It is possible to use sftp to grab the log, with an application like Filezilla or WinSCP + + With some file-browsers like Dolphin, just type the address for example: `sftp://pi@192.168.1.105/home/` + + Locate the logs at `~/printer_data/logs`or in `/tmp/` if the former doesn't exist. ## System logs @@ -32,20 +38,18 @@ cp -n /tmp/KlipperScreen.log ~/printer_data/logs/KlipperScreen.log ``` This will copy all the relevant logs to the folder described above, so they can be downloaded from the browser. -You may need to press refresh or reload the page +With the method described in the first section. You may need to press refresh or reload the page -Alternatively you can inspect them directly on the terminal: - -!!! warning - Please do not copy-paste the output of the terminal when providing info for an issue, - most of the time this output will be incomplete, use the method described above - -```sh -systemctl status KlipperScreen -journalctl -xe -u KlipperScreen -cat /var/log/Xorg.0.log -``` +??? tip "Alternative: inspect them directly on the terminal:" + !!! warning + Please do not copy-paste the output of the terminal when providing info for an issue, + most of the time this output will be incomplete, use the method described above + ```sh + systemctl status KlipperScreen + journalctl -xe -u KlipperScreen + cat /var/log/Xorg.0.log + ``` ## Screen shows console instead of KlipperScreen