4.4 KiB
Troubleshooting
First Steps
The first step to troubleshooting any problem is getting the cause of the error.
- Find KlipperScreen.log:
!!! warning "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.
System logs
If KlipperScreen.log doesn't exist open a terminal in the host (typically from SSH) and copy all the relevant logs to the folder described above that can be seen and copied from the webui:
systemctl status KlipperScreen > ~/printer_data/logs/KliperScreen_systemctl.log
journalctl -xe -u KlipperScreen > ~/printer_data/logs/KliperScreen_journalctl.log
cp /var/log/Xorg.0.log ~/printer_data/logs/KliperScreen_Xorg.log
Alternatively you can inspect them directly on the terminal:
systemctl status KlipperScreen
journalctl -xe -u KlipperScreen
cat /var/log/Xorg.0.log
Screen shows console instead of KlipperScreen
!!! abstract "If you see this line in the system logs:"
sh xf86OpenConsole: Cannot open virtual console 2 (Permission denied)
Follow this steps
!!! abstract "If you see this line in the system logs:"
sh xinit[948]: /usr/lib/xorg/Xorg: symbol lookup error: /usr/lib/xorg/modules/drivers/fbturbo_drv.so: undefined symbol: shadowUpdatePackedWeak
Follow this steps
!!! abstract "If you see this line in the system logs:"
sh KlipperScreen-start.sh: (EE) no screens found(EE)
This is usually not the main cause of the error. Start by checking the screen
Drivers not installed or misconfigured can cause this too, continue looking the logs for more clues.
!!! abstract "If you see this line in the system logs:"
sh modprobe: FATAL: Module g2d_23 not found in directory /lib/modules/6.1.21-v8+
This error is common on RaspberryOS when using FBturbo, it's not a related issue.
!!! abstract "If you see this line in the system logs:"
sh (EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
This has been known to happen on RaspberryOS Bookworm Lite on Pi5
```sh
sudo nano /etc/X11/xorg.conf.d/99-vc4.conf
```
paste this into the file:
```
Section "OutputClass"
Identifier "vc4"
MatchDriver "vc4"
Driver "modesetting"
Option "PrimaryGPU" "true"
EndSection
```
reboot
Maybe it's the wrong framebuffer
If you can't fix it, try using a desktop distro as described here.
If you want to contribute a solution: Contact
Screen is always white / black or No signal
If the screen never shows the console even during startup, Then it's typically an improperly installed screen.
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.
KlipperScreen will enable an internal screensaver to make it all black, and hopefully avoid burn-in. If you find a way of turning it off, please share it: Contact
Touch issues
Network panel doesn't list WI-FI networks
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