Minihack’s Build: Haswell i5-4250U NUC BOXD54250WYKH1 - 8GB RAM

[Sebinouse]

you can also change FB for "0a26000d"

it requires :
- a settings in the Bois : memory > 96Mo,
- a change in SSDT : buffer "0D 00 26 0A"
- a new patch for HDMI audio : 0105 0900 0004 0000 7010 000 > 0105 0900 0008 0000 8700 000

BTW HDMI 1.4 can go up to 3 840 x 2 160 , 30Hz

 

[franzzup]

you can also change FB for "0a26000d"

it requires :
- a settings in the Bois : memory > 96Mo,
- a change in SSDT : buffer "0D 00 26 0A"
- a new patch for HDMI audio : 0105 0900 0004 0000 7010 000 > 0105 0900 0008 0000 8700 000

BTW HDMI 1.4 can go up to 3 840 x 2 160 , 30Hz

Thanks... but I’m a bit out of my depth here. How should I edit the SSDT?

I’m assuming I need to edit MiniHack’s SSDT-1.aml, and I’m using MaciASL 1.3 (246). However, even when I try to open the unmodified SSDT-1.aml and save it again with no edits, I get an error starting at line 223:

223, 4090, Existing object has invalid type for Scope operator (_SB.PCI0 [Untyped])

which is the section specifying the IGPU as far as I understand.

Is there an inconsistency in the existing SSDT-1.aml, or should I be using a different tool to edit it? Here are the contents of the file as displayed by MaciASL, beginning at line 223. I’m also not sure how to insert the value of "0D 00 26 0A" that you suggest. Please advise.

Scope (_SB.PCI0)
{
    Device (IGPU)
    {
        Name (_ADR, 0x00020000)
        Method (_DSM, 4, NotSerialized)
        {
            If (LEqual (Arg2, Zero))
            {
                Return (Buffer (One)
                {
                    0x03
                })
            }


            Return (Package (0x04)
            {
                "AAPL,ig-platform-id", 
                Buffer (0x04)
                {
                    0x03, 0x00, 0x22, 0x0D
                }, 


                "hda-gfx", 
                Buffer (0x0A)
                {
                    "onboard-1"
                }
            })
        }
    }


    Device (HDAU)
    {


/* etc. */

 

[franzzup]

You can try RDM which allow you to choose resolution like SwitchResX (download link)

Thanks, that’s a nice tool. But AFAICS it just offers the same resolutions I can get in the Monitors system preference by holding the option key when I click on “Scaled”.

 

[franzzup]

BTW HDMI 1.4 can go up to 3 840 x 2 160 , 30Hz

Yes, in fact I think I may have been running that over HDMI in Mavericks.

I was just quoting the Intel specs for the Haswell i5 NUC, which say that higher resolutions may or may not be supported. Maybe that’s a hedge against any resolution limits imposed by Windows.

 

[Sebinouse]

I had the same error, sometimes it works and don't understand why :

to change the FB look for "0x03, 0x00, 0x22, 0x0D" and replace by "0x0D, 0x00, 0x26, 0x0A"

 

[Sebinouse]

Interesting post about SST MST 4K on 10.10 : Link

 

[franzzup]

I had the same error, sometimes it works and don't understand why :

to change the FB look for "0x03, 0x00, 0x22, 0x0D" and replace by "0x0D, 0x00, 0x26, 0x0A"

OK, thanks. That's what I thought.

I wasn’t able to get MaciASL to save the file. Since you say that doesn’t necessarily indicate an error with the SSDT, I patched the binary with Hex Fiend, but I can’t get the NUC to boot with the patched SSDT-1.aml. It hangs shortly after DSMOS. Here are the last lines from verbose boot, leaving out those I can identify as unrelated to graphics:

IOGraphics flags 0x43
AVVideoCard::probe()
DSMOS has arrived
AVVideoCard::start
hmm.. mismatch sizes: 3100 vs 20
PPGTT is enabled
IOPPF: XCPM mode

I set the IGP memory allocation to 32, 64, 128, 256 and 1024 MB in the BIOS, no difference.

 

[franzzup]

Interesting post about SST MST 4K on 10.10 : Link

Yes, interesting, but I doubt it applies to the NUC. All the Intel documentation seems to suggest that the HD 5000 only supports SST displays. While it does apparently support MST for multiple displays, all the resolutions mentioned are achievable individually over SST, as are the resolution Apple spec’s for the Macmini7,1.

 

[Sebinouse]

Yes, interesting, but I doubt it applies to the NUC...

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 wasn’t able to get MaciASL to save the file. Since you say that doesn’t necessarily indicate an error with the SSDT, I patched the binary with Hex Fiend, but I can’t get the NUC to boot with the patched SSDT-1.aml. It hangs shortly after DSMOS. Here are the last lines from verbose boot, leaving out those I can identify as unrelated to graphics:...

Hex edit should be OK, but you'll find the files I use on the attachments if this post.

I set the IGP memory allocation to 32, 64, 128, 256 and 1024 MB in the BIOS, no difference.

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.

 

[franzzup]

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?