popcornmix

Can you try adding ``hdmi_drive=2`` to config.txt (without fkms driver). (If not try ``hdmi_drive=1``) Also try ``hdmi_group=2`` (If not try ``hdmi_group=1``)

Output of ``vcgencmd dispmanx_list`` when not displaying an image might be interesting.

> vcgencmd dispmanx_list - no output with dtoverlay=vc4-fkms-v3d disabled Interesting. If you disable "boot to desktop" in raspberry pi configuration, is there any difference.

So booting to CLI is working (without fkms)? (i.e. hdmi console is visible?)

can you add ``start_debug=1`` and (without fkms and desktop enabled) report output of: ``` sudo vcdbg log msg sudo vcdbg log assert ```

Okay, I can reproduce.

Can you try booting to console, running: ```sudo rm /usr/share/X11/xorg.conf.d/99-fbturbo.conf``` (don't worry it gets recreated every boot) and then ``startx``

You have fkms disabled?

Are you running startx from ssh? You should be running it from keyboard (without sudo). That fix will only last one boot. A permanent fix would be to edit: /usr/lib/systemd/scripts/gldriver_test.sh...

Okay, thanks for report and testing. @XECDesign could you update /usr/lib/systemd/scripts/gldriver_test.sh to this: http://paste.debian.net/1111724/ (I've tweaked it slightly from previous version) It also treats aarch64 (along with fkms/kms) as a...