(07-31-2024, 06:22 PM)Tim Curtis Wrote: I ended up purchasing the 10" version of the the display and after some testing with a Pi4 it turns out that no config.txt entries are needed but the method for automatically determining the correct screen size needs to use kmsprint instead of fbset.
/home/pi/.xinitrc
Code:# Capture screen size
#SCREENSIZE="$(fbset -s | awk '$1 == "geometry" { print $2","$3 }')"
SCREENSIZE="$(kmsprint | awk '$1 == "FB" { print $3 }' | awk -F"x" '{print $1","$2}')"
The correct KMS screen size for this display is 1600x900
Code:pi@moode9test:~ $ kmsprint | awk '$1 == "FB" { print $3 }' | awk -F"x" '{print $1","$2}'
1600,900
Another finding was that the Pi3B+ doesn't work well with this display. There are a lot of screen glitches and all kinds of issues with popup keyboard and modals.
With a Pi4 the display was glitch free, touch was fast and accurate and no issues with the popup keyboard or modals. I assume it will be same with Pi5. I don't have a spare 5 ATM but will get more of them at some point.
I'll prolly update the xinitrc script to use kmsprint for upcoming 9.0.6 release.
nice!
Yes, I encountered and confirm some issues with graphic glitches on the Pi 3B+ in the power-off/reboot menu.
I will use my spare Raspberry Pi 4, but I need to find another compatible DAC. I'm not sure which one to get. i got the miniboss dac
i got this output btw with that command
kmsprint | awk '$1 == "FB" { print $3 }' | awk -F"x" '{print $1","$2}'
1024,600
with the chromium-browser update to Version 126 i dont get anymore the error code 11
