2.3 KiB
First Steps
The first step to troubleshooting any problem is getting the cause of the error.
- Find KlipperScreen.log:
!!! important This log file should be provided if you ask for support.
Depending on your setup the file could be accessible from the web interface alongside other logs
| Mainsail | Fluidd |
|---|---|
 |
 |
if you can't find it in the web interface, use sftp to grab the log (for example Filezilla, WinSCP)
Located at ~/printer_data/logsor in /tmp/ if the former doesn't exist.
If KlipperScreen.log doesn't exist, run systemctl status KlipperScreen
(or journalctl -xe -u KlipperScreen)
Check the file /var/log/Xorg.0.log where you can find issues with the X server.
Cannot open virtual Console
If you see this line in the logs (systemctl status KlipperScreen):
xf86OpenConsole: Cannot open virtual console 2 (Permission denied)
Screen shows console instead of KlipperScreen
You may see this line in the logs (systemctl status KlipperScreen):
KlipperScreen-start.sh: (EE) no screens found(EE)
Screen is all white or blank or no signal
If the screen never shows the console even during startup, Then it's typically an improperly installed screen,
You may see this line in the logs (systemctl status KlipperScreen):
KlipperScreen-start.sh: (EE) no screens found(EE)
The screen shows colors or 'No signal' when idle
In KliperScreen settings find 'Screen DPMS' and turn it off. Your screen doesn't seem to support turning off via software, the best you can do is to turn it all black.
Touch issues
Network panel doesn't list WI-FI networks
OctoPrint
KlipperScreen was never intended to be used with OctoPrint, and there is no support for it.
Other issues
If you found an issue not listed here, or can't make it work, please provide all the log files a description of your hw, and a description of the issue when asking for support.