CreatBot/CreatBotKlipperScreen
7
0
Fork 1
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: update touch section

Browse Source
This commit is contained in:
alfrix 2024-02-29 08:35:15 -03:00
parent 0570706bbe
commit 543dc97d21
1 changed files with 35 additions and 23 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
docs/Troubleshooting/Touch_issues.md
View File

@ -1,13 +1,25 @@
# Touchscreen issues
If the screen is connected over USB, issues with the cable may cause similar symptoms. For that, please see [this guide](Physical_Install.md#cable-issues).
Contents:
## Touch not working on RaspberryOS and derivatives
* [Touch not working](#touch-not-working)
* [Touch rotation and matrix](#touch-rotation-and-matrix)
* [Touch calibration](#touch-calibration)
Beware that this document focuses on RaspberryOS but most of it should apply to any other Debian based distros
## Touch not working
If the screen is connected over USB, the cable may cause issues.
For that, please see [this guide](Physical_Install.md#cable-issues).
??? abstract "DSI screens touch not working on RaspberryOS / MainsailOS version Debian 11 Bullseye"
Some DSI screens have issues where touch doesn't work with the default configuration.
The current workaround/temporary fix involves changing the kernel driver module used for these displays.
Open `/boot/config.txt` for editing using `sudo nano /boot/config.txt` and change
`sudo nano /boot/config.txt` and change
```sh
dtoverlay=vc4-kms-v3d
@ -21,7 +33,7 @@ dtoverlay=vc4-fkms-v3d
Close the nano editor using `ctrl`+`x` (exit), then `y` for yes (save).
**Reboot** to apply changes.
**Reboot** to apply changes. `sudo reboot`
If that doesn't fix it, you can try commenting these lines out, resulting in:
@ -30,7 +42,7 @@ If that doesn't fix it, you can try commenting these lines out, resulting in:
# max_framebuffers=2
```
**Reboot** to apply changes.
**Reboot** to apply changes. `sudo reboot`
## Touch rotation and matrix