FAQ made it clear, can't boot so picture and CLOVER without themes is in the zip.
As per FAQ, you must use an invalid ig-platform-id due to your 4k display.
Because you can't expect the internal display to work without patching for the pixel clock limit.
You can use CoreDisplayFixup.kext + Lilu.kext.
And you will probably need IntelGraphicsFixup.kext as well.
Remove ACPI/patched/SSDT.aml... it is not needed with config.plist/ACPI/SSDT/Generate/PluginType=true.
High Sierra is already installed, I just can’t get my graphics working: booting with correct ig-platform-id gives boot hang. Booting with invalid ig-platform-id makes it boot just fine, but it isn’t very pleasant to use.
I am already using CoreDisplayFixup and Lilu (they’re in /L/E/ as you suggested) but not IntelGraphicsFixup yet, I’ll try that next.
I generated SSDT with ssdtPRGen.sh for native power management. Do I still remove it?
No kextcache output provided, so no way to verify that you have CoreDisplayFixup.kext installed properly.
I'm not sure what you mean by "kextcache output",
Attached it.
First I edited DSDT, compiled, generated .aml file. Put it in EFI/CLOVER/ACPI/patched, but I didn't trust this. Besides config.plist is easierHECI should be renamed IMEI.
You're booting with an invalid ig-platform-id (graphics not expected to work properly).
First I edited DSDT, compiled, generated .aml file. Put it in EFI/CLOVER/ACPI/patched, but I didn't trust this. Besides config.plist is easier
I did config.plist->ACPI->DSDT->Patches: Find: <48454349> Replace: <494d4549> (These are hex for HECI and IMEI respectively)
I know.. I can't get it to boot at all with the correct(0x16260006, 0x161e0001 and 0x161e0000) ig-platform-id. What happens with correct ig-platform-id is it gets stuck during bootload. See pic attached. So I generate problem reporting files after booting with 0x12345678.
Side note: I properly set the framebuffer fix for 0x161e0001 and 0x161e0000 (I will be posting a pull request sometime soon on github). Now there's no KP for those anymore and I get the same result (stuck during bootload) for the three ig-platform-id's.
EDID is now injected.
Screen doesn't go black, it just stops loading so no need for external screen debugging.