#0 1920x1200 59.95 1920 1968 2000 2080 1200 1203 1209 1235 154000 flags: phsync, nvsync; type: preferred, driver
#1 1600x1200 60.00 1600 1664 1856 2160 1200 1201 1204 1250 162000 flags: phsync, pvsync; type: driver
#2 1680x1050 59.88 1680 1728 1760 1840 1050 1053 1059 1080 119000 flags: phsync, nvsync; type: driver
#3 1280x1024 60.02 1280 1328 1440 1688 1024 1025 1028 1066 108000 flags: phsync, pvsync; type: driver
#4 1280x960 60.00 1280 1376 1488 1800 960 961 964 1000 108000 flags: phsync, pvsync; type: driver
#5 1024x768 60.00 1024 1048 1184 1344 768 771 777 806 65000 flags: nhsync, nvsync; type: driver
#6 800x600 60.32 800 840 968 1056 600 601 605 628 40000 flags: phsync, pvsync; type: driver
^ Those are the modes EDID shows as supported on the monitor, so the "1920x1080: 60" mode Kodi is looking for is indeed not in the list and .. something behaves badly. The only place I can think of where we hardcode something about 1920x1080 is the default screen resolution to use, which is "<setting id="videoscreen.screenmode" default="true">0192001080060.00000pstd</setting>" in /storage/.kodi/userdata/guisettings.xml, so perhaps stop Kodi and edit it to be "0192001200059.95000pstd" and see if that makes any difference? .. If that does have some effect it's a little odd as Kodi should handle things more gracefully. The other way to test around that would be to connect the board to a TV that has 1920x1080 modes.