My point is : "Mac-7DF21CB3ED6977E5/ MacBookAir6,2" is blacklisted on this kext and not "Mac-35C5E08120C7EEAF / Macmini7,1". It might be for MST but maybe not only ... maybe it can unlock other resolutions ...
I don’t quite follow—I was just thinking along these lines:
1. Apple advertises 3840 x 2160 @ 30 Hz for the MacMini7,1 (Intel HD 5000) but only 2560 x 1600 @ 60 Hz for the MacBookAir6,1 (also Intel HD 5000).
2. The Haswell i5 NUC hardware is perfectly capable of 3840 x 2160 @ 30 Hz. It works fine under Mavericks, and indeed the other day while recovering from one of my recent experiments I booted from the 10.10.1 install USB key I had created based on MiniHack’s guide, and it booted Yosemite at 3840 x 2160 @ 30 Hz, but with no GPU support. (I. e., slow/tearing video, etc.)
3. So in theory if one could convince Apple’s HD 5000 drivers that the NUC is a MacMini7,1, it should support the higher resolutions.
4. As an aside, I believe that all resolutions Apple has supported to date have been SST with the exception of the Mac Pro in certain configurations with a certain, limited set of monitors. So I don’t think SST/MST is relevant here. I had my ASUS PB287Q set to DisplayPort 1.1, i. e. SST, while I was using the higher resolutions in Mavericks. (In fact, at one point, enabling DP 1.2 would hard-crash the monitor itself, and I would have to power-cycle it.)
Hex edit should be OK, but you'll find the files I use on the attachments if this post.
For my part, with 0D and IGP men alloc 32 or 64 it just reboots just before displaying desktop. If I try 128, everything is fine. Something is definitively wrong with your SSDT injection.
Thanks for the files. That’s definitely a different set from what I’ve been using, I have a fairly old set of SSDT*.aml as supplied by MiniHack.
I tried replacing the SSDT.aml, SSDT-1.aml and SSDT-2.aml with your SSDT.aml and SSDT-[1-3].aml, but then I get the same boot failure I described previously with my hand-patched SSDT-1.aml. (IGP set to 256 or 128 MB.)
My NUC is still at BIOS v33, which I’ve seen no need to update since everything else is working fine, including 4K resolutions under Mavericks. Do you think that might be an issue?