CreatBot/GeneralKlipperScreen
7
0
Fork 0
forked from CreatBot/CreatBotKlipperScreen
Code Pull Requests Activity

docs: troubleshooting put the alternatives collapsed to not distract users from the important bits

Browse Source
This commit is contained in:
alfrix 2024-04-05 08:58:56 -03:00
parent 49a8fa8186
commit 1b07839553
1 changed files with 18 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
docs/Troubleshooting.md
View File

@ -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