Hmm. I'm pretty sure I'd tried dtoverlay=vc4-kms-v3d and display_auto_detect=1 already, though maybe not both at the same time.
I've now definitely tried that combination, and also dtoverlay=vc4-kms-v3d separately and in combination - none of these appear to have any effect.
(and to avoid the possibility of failing to pick up changes in the build system, I've been mounting /dev/mmcblk0p1 on the live system, editing config.txt in there directly and rebooting).
This is built from buildroot-2024-08 so fairly recent; kernel is 6.6.20 and in dmesg there is this version info:Are there any other diagnostics I can gather to explain what is going on?
I've now definitely tried that combination, and also dtoverlay=vc4-kms-v3d separately and in combination - none of these appear to have any effect.
(and to avoid the possibility of failing to pick up changes in the build system, I've been mounting /dev/mmcblk0p1 on the live system, editing config.txt in there directly and rebooting).
This is built from buildroot-2024-08 so fairly recent; kernel is 6.6.20 and in dmesg there is this version info:
Code:
[ 0.044058] raspberrypi-firmware soc:firmware: Attached to firmware from 2024-04-17T17:27:09, variant start[ 0.048077] raspberrypi-firmware soc:firmware: Firmware hash is 86ccc427f35fdc604edc511881cdf579df945fb4Statistics: Posted by arg001 — Mon Oct 07, 2024 10:45 am