RatOs 2.0 installed - lost PI touchscreen
Just updated to the latest release. Everything seems to be perfect except for my PI 7" touchscreen is no longer accepting touches.... It is displaying correctly, and everything else seems to be working perfect. Love the klicky probe! (which is why I was on alpha).
Any help on getting the touchscreen working would be appreciated.
31 Replies
adverse-sapphire•16mo ago
So I found this issue reported with bullseye:
https://klipperscreen.readthedocs.io/en/latest/Troubleshooting/
Troubleshooting - KlipperScreen
KlipperScreen documentation.
adverse-sapphire•16mo ago
doing that (changing config.txt for dtoverlay=vc4-fkms-v3d) gets me SOME random OFF inputs... I tried every matrix transformation to get it right, but I cannot get the touch inputs to line up with the screen.
adverse-sapphire•16mo ago
Took a FEW HOURS to figure it out. But the RatOs 2.0 release doesn't support offical PI 7" touchscreen because of bullseye issue. The following needs to be put in your config.txt file!
adverse-sapphire•16mo ago
Notice the trial lines hashed out. You only need the one added, and since I have a PI 3b+ I put it there.
ugh, i wish this wasn't so horrible. There's just no way to make this userfriendly.
Touch screen support sucks big time in bullseye. Feels half baked.
adverse-sapphire•16mo ago
@miklschmidt maybe have this reported as an issue on github with a work around then. I would think a lot of people use a touchscreen with their ratrig. Is the problem isolated to 7" PI screen? If not, then each workaround needs to be documented. With that single line added, the latest RatOs 2.0 runs like a dream in every way I can measure so far.
Literally impossible. I can't list how to configure each and every combination of pi model and whatever random screen is out there. I have made sure that RatOS works with the most used one (BTT Pi TFT), and that's the best i can do. For unsupported hardware, google. First principle of RatOS is no cli interaction, i will not tell people to ssh into their pi's if i can avoid it.
The klipperscreen docs and google will have to do for this.
This is a Raspberry Pi OS thing, not a RatOS thing.
That said, if one has a screen that doesn't work out of the box and one knows what to do to make it work, make a post in #ratos-plugins-and-macros for it.
passive-yellow•16mo ago
I have a BTT Pi TFT and my touch didn't work, I found the troubleshooting mentioned above (https://klipperscreen.readthedocs.io/en/latest/Troubleshooting/#touch-not-working-on-debian-bullseye) and changed to G2 GL driver but then my boot-up halted and prompted me to login. I made some brave tries to make some changes in the pi so that it would automatically login but then I was left in the "text prompt", I tried to change the settings to auto-login in GUI but that setting was rejected.. This was to advanced for me, which is a shame because I was looking forward to trying RatOS 2.0
Kudos anyway cus you have obviously put a lot of work into this!
Troubleshooting - KlipperScreen
KlipperScreen documentation.
What pi model and what image architecture (32 or 64bit)? I (and others) have tested the btt pi tft on both pi3 and pi4's and it works out of the box, so either your setup is unique or .. i don't know 🙂
passive-yellow•16mo ago
I have a Pi3B and installed the 32bit. I got unsure whether to take 32 or 64bit so I went for the 32bit..
Which one is to prefer on my Pi3B, 32 or 64bit?
I will gladly reinstall and try again
Actually it’s a Pi 3 B+, if it makes any difference..
You can use 64-bit on the B+
I've only tested on B, maybe there's a difference there. I hate how every model require different settings.
passive-yellow•16mo ago
That I can understand!
So would you recommend me trying 64bit then?
If it's not too much of an issue, would be interesting to know if it works out of the box on 64-bit
passive-yellow•16mo ago
No problem at all! And after all, it's not working at all at the moment 😉
I will get back when I'm done
Ok..
No that's not necessary 🙂
passive-yellow•16mo ago
Crap, I messed up the conversation 😄 I suck at this.
I'll get back as soon as I can..
passive-yellow•16mo ago
This is strange, this has been the same on both my printers with two different control cards and three different screens (two HDMI and this one, BTT PI TFT50); if the screen is attached when starting the raspberry the first time, it stays at this screen and no hotspot appears in my phone? Why?
passive-yellow•16mo ago
The good news this time, I think, is that the touch works 🙂 (so far)
It has now been more than 7 minutes since this screen appeared
(And my computer does not see any hot spots either)
passive-yellow•16mo ago
passive-yellow•16mo ago
I pressed 'Retry' and this screen came. Still no hot spot though..
What about on your phone?
passive-yellow•16mo ago
No hotspot anywhere 😦 Not on my phone, not on my computer and not on my iPad, I waited more than 30 minutes. I shut down my pi and disconnected the screen, started the Pi again and then the hotspot came and I could do the setup. From the browser on my computer I then made all the updates, RatOS first, then shut the printer down, connected the screen and started the Pi and the touch is gone...
It appears as the 64bit was no better than the 32bit in this regard..
If there is anything I can provide that is of any help please let me know..
The hotspot script only creates it if it can't connect to wifi. I am guessing connecting the screen does something that makes the script think it is already connected to wifi and thus doesn't start hotspot
No i tested with this screen, no hotspot issues
@tmicke There's one thing i'd like you to try.
At the very bottom of /boot/config.txt add:
and if that doesn't work, try
I need to see if i can reproduce your issue and reach out to btt if it doesn't work
passive-yellow•16mo ago
Just to be sure I did it right; I put the SD card in my computer and added that line just above the [All] line. I have a Mac and used Visual Studio Code
With the first one, dtoverlay=vc4-kms-v3d, the screen came on but no touch, printer was accessible via Web UI
With the second one, dtoverlay=vc4-fkms-v3d, the screen didn't turn on, printer was accessible via Web UI
You've done it right. I've reached out to BTT.
passive-yellow•16mo ago
Nice, I hope this can benefit us all and that it isn't to much extra work for you
me2, let's see what they say
Can you try
dtoverlay=rpi-ft5406 ?
At least that works for me, BTT's Alan came to the rescue 🙂passive-yellow•16mo ago
It worked 🙂
Thank you!
metropolitan-bronze•6mo ago
After ripping my hair out trying everything, this worked for me. I got klipperscreen going, then lost my Pi Camera... Then fixed it and lost KlipperScreen. Haha. FINALLY I found this. Thank you.
Huh strange, this has been the default for Pi3's for 9 months (since 2.0.1): https://github.com/Rat-OS/RatOS/commit/fdad0c5bb933d98cedd441b6ccba287331f52161