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

docs: update to try avoid a common missuses of the docs

Browse Source
This commit is contained in:
alfrix 2023-09-12 00:25:10 -03:00
parent 75ee5c4740
commit d5bf8c21cb
3 changed files with 27 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
docs/Contact.md
View File

@ -1,11 +1,23 @@
# Contact
There are several ways to contact people who can assist with issues. Discord is going to be the quickest response as
there will be more people in the chat who can help.
There are several ways to contact people who can assist with issues.
Discord is probably going to provide the quickest response as there are more people in the chat who can help.
## GitHub Issues
You may submit a GitHub issue request for any problems you are having.
## Klipper Community Discord
[Look for the channel `#klipper-screen`](https://discord.klipper3d.org/)
## Issues or improvements to the docs or the application
You may submit a GitHub issue request for any bugs you encounter.
or a Pull Request with translations, features, doc fixes.
or open an issue describing the changes.
or even provide ideas for a feature.
[Github repository](https://github.com/KlipperScreen/KlipperScreen/)

11
docs/Troubleshooting.md
View File

@ -57,11 +57,16 @@ cat /var/log/Xorg.0.log
```sh
KlipperScreen-start.sh: (EE) no screens found(EE)
```
[First check the screen](Troubleshooting/Physical_Install.md)
[Check the screen](Troubleshooting/Physical_Install.md)
[Maybe it's the wrong framebuffer](Troubleshooting/Framebuffer.md)
## Screen is always white / black / blank or no 'No signal'
[Maybe it's the wrong framebuffer](Troubleshooting/Framebuffer.md)
If you can't fix it, [try using a desktop distro as described here.](Troubleshooting/Last_resort.md)
If you want to contribute a solution: [Contact](Contact.md)
## 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.

3
docs/Troubleshooting/Framebuffer.md
View File

@ -40,6 +40,9 @@ check if one of those or similar exist with:
ls /usr/share/X11/xorg.conf.d/
```
!!! failure "Critical"
***DO NOT CREATE A FILE***, and only edit if there is more than 1 framebuffer
!!! example
you found 99-fbturbo.conf: