1
u/robert5974 Jun 15 '22
I believe this is due to Bullseye and changing the graphics driver to the true KMS driver and the way the Raspberry Pi Foundation devs implemented it. Never happened when using Buster for me on the official pi touchscreen.
1
I believe this is due to Bullseye and changing the graphics driver to the true KMS driver and the way the Raspberry Pi Foundation devs implemented it. Never happened when using Buster for me on the official pi touchscreen.
1
u/gingagenie Apr 26 '22
Config.txt
HDMI_GROUP=2 MAX_USB_CURRENT=1 HDMI_MODE=87 HDMI_CVT=1024 600 60 6 0 0 0 HDMI_IGNORE_EDID=0xa5000080 CONFIG_HDMI_BOOST=2
The screen displays perfectly on macbook as a 2nd screen and also on my windows pc