JerryK13

Thank you for the reply. None of the displays are fast enough to display the diagnostic screen. The rainbow screen is displayed and then the framebuffer. After switching to KMS,...

It is exactly the same on the TV. The /sys/devices/platform/gpu/drm/card1/card1-HDMI-A-1/edid is the same as after switching source (you just have to remember to remove the loaded edid from the cmdline...

I've setup the Pi to startx on tty7 (lightdm) and did some testing. All the testing is on the monitor. With `drm.edid_firmware=edid video=HDMI-A-1:1920x1080@60` in cmdlinte.txt and HDMI connected before booting...

> I don't think you've run the test I described in my previous post. My understanding was that if you to boot to console (with hdmi attached), you see some...

And it is exactly the same on the TV. I can even use the monitors edid in the cmdline.txt and produce the same results (get output by plugging the HDMI...

It reports `throttled=0x0`. Both of displays are old (2009 and 2012). I tried it now with again two different even older monitors (these are not FHD) that only have DVI...

The `drm.debug=0x14` was already included in ~~the default of the foundation supplied image (and my kern.log and syslog were already couple of GB in size. I wander if the periodic...

Yes, you are right! I've must have missed copy&pasting that while messing with loading the edid from file before opening this report. Sorry for the miss information.

I can confirm that with the rpi-update commit 20169be87eee199ab8c958a02ef923597f15f944 the firmware to kms handover works on both displays from the opening comment! Good work!