11-10-2024, 10:06 PM
(This post was last modified: 11-10-2024, 10:07 PM by Tim Curtis.)
I don't think it's a moode bug because the script that starts the local display only queries for the screen size, it does not update it.
You could try running the command below and see if it reports the right screen size.
If /boot/firmware/config.txt contains #dtoverlay=vc4-kms-v3d (with the pound sign)
If /boot/firmware/config.txt contains dtoverlay=vc4-kms-v3d (without the pound sign)
You could try running the command below and see if it reports the right screen size.
If /boot/firmware/config.txt contains #dtoverlay=vc4-kms-v3d (with the pound sign)
Code:
fbset -s | awk '$1 == "geometry" {print $2","$3}'
If /boot/firmware/config.txt contains dtoverlay=vc4-kms-v3d (without the pound sign)
Code:
kmsprint | awk '$1 == "FB" {print $3}' | awk -F"x" '{print $1","$2}'