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

docs: improve troubleshooting close #537

Browse Source
This commit is contained in:
alfrix 2022-03-10 09:13:03 -03:00
parent b379363cf2
commit cee3243729
1 changed files with 40 additions and 27 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

67
docs/Troubleshooting.md
View File

@ -1,58 +1,66 @@
# Troubleshooting
This page will have common problems and common solutions to those problems. This page will have common problems and common solutions to those problems.
## First Steps # First Steps
The first step to troubleshooting any problem is getting the cause of the error. The first step to troubleshooting any problem is getting the cause of the error.
Check for the file `/tmp/KlipperScreen.log` and look at the contents by running
`cat /tmp/KlipperScreen.log` or grab the file over WinSCP or another sftp program.
If that file is non-existent, run `journalctl -xe -u KlipperScreen` and check `/var/log/Xorg.0.log` * Check for the file `/tmp/KlipperScreen.log`
where you can find issues with the X server.
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.
## Common Errors If that file is non-existent, run `journalctl -xe -u KlipperScreen`
### Problems occurring before the log file appears Check the file `/var/log/Xorg.0.log` where you can find issues with the X server.
This section will detail problems that may happen before the log file has been created. Each section will start with a ## Cannot open virtual Console
relevant line from the journalctl output.
#### Cannot open virtual Console
``` ```
xf86OpenConsole: Cannot open virtual console 2 (Permission denied) xf86OpenConsole: Cannot open virtual console 2 (Permission denied)
``` ```
* Check /etc/X11/Xwrapper.conf * Check /etc/X11/Xwrapper.conf
Run `cat /etc/X11/Xwrapper.conf`
This should have the line `allowed_users=anybody` in it This should have the line `allowed_users=anybody` in it
* Check /etc/group * Check /etc/group
Run the command `cat /etc/group | grep tty`. If your username is not listed under that line, you need to add it with the Run `cat /etc/group | grep tty`
following command (if your username is not 'pi' change 'pi' to your username):
`usermod -a -G tty pi` If your username is not listed under that line, you need to add it with the following command:
`usermod -a -G tty pi` (if your username is not 'pi' change 'pi' to your username)
If it's still failing, try: `sudo apt install xserver-xorg-legacy`
### Problems occurring with the log file ## Screen shows console instead of KlipperScreen
#### Screen shows console instead of KlipperScreen If you have multiple framebuffers, you may need to fix the X11 configuration.
Run the command `ls /dev/fb*`. If you have multiple devices, you may need to fix the X11 configuration.
Run the command `cat /usr/share/X11/xorg.conf.d/99-fbturbo.conf | grep /dev/fb`. Try modifying the file ( `ls /dev/fb*` will list the available framebuffers
`sudo nano /usr/share/X11/xorg.conf.d/99-fbturbo.conf`) and change `/dev/fb0` to a different file listed in the
previous command (i.e. `/dev/fb1`). `cat /usr/share/X11/xorg.conf.d/99-fbturbo.conf | grep /dev/fb` will show you the current one
If you have another fb, try changing it:
`sudo nano /usr/share/X11/xorg.conf.d/99-fbturbo.conf`
for example: change `/dev/fb0` to `/dev/fb1`
Once you have saved that file, restart KlipperScreen and it should show up on your display. Once you have saved that file, restart KlipperScreen and it should show up on your display.
#### Screen is all white or blank ## Screen is all white or blank or no signal
Improperly installed screen, follow the manufacturer instructions on how to physically connect the screen and install If the screen never shows the console even during startup, Then it's tipically an improperly installed screen,
the proper drivers. follow the manufacturer instructions on how to physically connect the screen and install the proper drivers.
### Touch not working on debian Bullseye ## Touch not working on debian Bullseye
Some dsi screens have issues where touch doesn't work with debian bullseye, the current fix Some dsi screens have issues where touch doesn't work with debian bullseye, the current fix
(at least until upstream is fixed) consist in runnig `raspi-config`> go to Advanced > GL Driver (at least until upstream is fixed) consist in changing the driver:
select G2 and reboot.
Run `raspi-config` > go to Advanced > GL Driver > select G2 and reboot.
![config](img/troubleshooting/gldriver.png) ![config](img/troubleshooting/gldriver.png)
@ -66,3 +74,8 @@ to:
and reboot, that should make the touch work, if your screen is rotated 180 degrees, then you may need to adjust and reboot, that should make the touch work, if your screen is rotated 180 degrees, then you may need to adjust
[the touch rotation](Hardware.md) as described in the Hardware page. [the touch rotation](Hardware.md) as described in the Hardware page.
## 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.