This page will have common problems and common solutions to those problems.
The first step to troubleshooting any problem is getting the cause of the error.
- Check for the file
look at the contents by running
cat /tmp/KlipperScreen.log or grab the file over WinSCP or another sftp program.
This is the most important file, and should be provided if you ask for support.
If that file is non-existent, run
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:
This should have the line
allowed_users=anybody in it
cat /etc/group | grep tty
If your username is not listed under that line, you need to add it with the following command:
You may also need:
If it's still failing as a last resort add
Screen shows console instead of KlipperScreen
If you have multiple framebuffers, you may need to fix the X11 configuration, list the available framebuffers and check the current one:
If you more than one, try changing it:
for example: change
Once you have saved that file, restart KlipperScreen.
If you have multiple hdmi ports try the other one
Screen is all white or blank or no signal
If the screen never shows the console even during startup, Then it's tipically an improperly installed screen, follow the manufacturer instructions on how to physically connect the screen and install the proper drivers.
The screen starts flashing colors or stays all blue/white or shows '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 not working on debian Bullseye
Some dsi screens have issues where touch doesn't work with debian bullseye, the current fix (at least until upstream is fixed) consist in changing the driver:
raspi-config > go to Advanced > GL Driver > select G2 and reboot.
/boot/config.txt and change:
to:the touch rotation as described in the Hardware page.
KlipperScreen was never intended to be used with OctoPrint, and there is no support for it.
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.