Contribute
Register

Sebinouse's Build : CustoMacMini 2014 - Intel NUC Haswell i5-4250U - El Capitan

Status
Not open for further replies.
No joy, unfortunately. Same issues - should I start looking into these KEXT solutions I see around YouTube for the HD 4400? They seem of mixed success and you're far more knowledgeable.

Damn !

Can you check which framebuffer is used with DCPIManager (http://sourceforge.net/projects/dpcimanager/) ?

Does it boot without SSDT-3.aml ?

If you want to try kext, I would recommend FakePCIID_HD4600_HD4400.kext and FakePCIID.kext in EFI/.../10.11/ (https://github.com/the-darkvoid/OS-X-Fake-PCI-ID)
 
Damn !

Can you check which framebuffer is used with DCPIManager (http://sourceforge.net/projects/dpcimanager/) ?

Does it boot without SSDT-3.aml ?

If you want to try kext, I would recommend FakePCIID_HD4600_HD4400.kext and FakePCIID.kext in EFI/.../10.11/ (https://github.com/the-darkvoid/OS-X-Fake-PCI-ID)


It boots without SSDT-3.aml and exhibits the same behavior; DPCI manager doesn't reveal the frame buffer in the status:

Screen Shot 2015-11-22 at 5.02.52 PM.png

This might be more revealing for you than it is to me.

EDIT:

KEXT instructions were not successful, but doing these instructions:

http://www.insanelymac.com/forum/topic/304267-intel-hd4400-full-qeci-in-yosemite-1010210103/

Has helped a little. DCPI now shows the framebuffer at 0x0D220003
 
I assumed you had QE/CI working with previous guides (see post#1) but was it true ? I just advised you to revert to Minihack's FrameBuffer.

The more I read about HD4400, the less it seems compatible with our HD5000 ...

The best way to make it work, according to me, is to revert to original settings (BIOS/Video and MacOSX 10.11 kexts) and use the two kexts from my previous post.

You can also try the Clover's "FakeID" "ig-platform-id"
Code:
<key>FakeID</key>
  <dict>
    <key>IntelGFX</key>
    <string>0x0a168086</string>
  </dict>
Code:
<key>ig-platform-id</key>
<string>0x0a260006</string>
 
I assumed you had QE/CI working with previous guides (see post#1) but was it true ? I just advised you to revert to Minihack's FrameBuffer.

The more I read about HD4400, the less it seems compatible with our HD5000 ...

The best way to make it work, according to me, is to revert to original settings (BIOS/Video and MacOSX 10.11 kexts) and use the two kexts from my previous post.

You can also try the Clover's "FakeID" "ig-platform-id"
Code:
<key>FakeID</key>
  <dict>
    <key>IntelGFX</key>
    <string>0x0a168086</string>
  </dict>
Code:
<key>ig-platform-id</key>
<string>0x0a260006</string>

HD5000 is supported natively. No need for FakeID (nor FakePCIID).

But ig-platform-id 0xa260006 is generally specific to laptops as the first connector in the framebuffer is LVDS. Better to use a desktop ig-platform-id (probably 0xd220003).

Which ig-platform-id does a real Macmini7,x use?
 
HD5000 is supported natively. No need for FakeID (nor FakePCIID).
I do confirm ! ;)
We can even choose between several FB :
0x0d220003 (Bios IGP min mem = 32Mo)
0x0a26000d (Bios IGP min mem > 96Mo, bigger FB/Cursor size to allow QHD/4K ?)

But ig-platform-id 0xa260006 is generally specific to laptops as the first connector in the framebuffer is LVDS. Better to use a desktop ig-platform-id (probably 0xd220003).
Which ig-platform-id does a real Macmini7,x use?

Thanks for the explanation, I did not understand this choice ... and now it's clear !
Both platforms above have DP,DP,DP connector layout.

I don't have a genuine MM7,1 so I have no clue but I wouldn't be surprised if it was 0x0a26000d.
 
I do confirm ! ;)
We can even choose between several FB :
0x0d220003 (Bios IGP min mem = 32Mo)
0x0a26000d (Bios IGP min mem > 96Mo, bigger FB/Cursor size to allow QHD/4K ?)



Thanks for the explanation, I did not understand this choice ... and now it's clear !
Both platforms above have DP,DP,DP connector layout.

I don't have a genuine MM7,1 so I have no clue but I wouldn't be surprised if it was 0x0a26000d.

Sometimes you can find them on the internet (ioreg dumps from Apple products). Newer ones are harder to find though.

No matter which you choose, make sure your DVMT-prealloc matches the ig-platform-id BIOS memory allocation.
 
Thanks Sebinouse, good work as always. I can confirm:

Haswell NUC
16 GB RAM (2 x Samsung M471B1G73DB0-YK0)
Samsung 850 EVO mSATA 1 TB
HGST HTS541515A9E630 1.5 TB
Brcm4331 Wi-Fi
ASUS PB287Q 4K monitor

Kernel panic in the Brcm driver until I removed SSDT-4.aml as noted by PaulyGlocke.

I removed the Trim Enabler patch as I don’t trust the firmware of drives not vetted by Apple.

On the PB287Q I can now get full 4K resolution over DisplayPort as long as DP is set to 1.2 in the monitor OSD. Using SwitchResX I enabled 3840 x 2160 @ 45 Hz, 3200 x 1800 @ 60 Hz and 3008 x 1692 @ 60 Hz.

With DP 1.1 I can get 3840 x 2160 @ 30 Hz. If I go higher to 45 Hz, the machine appears to crash hard.

I would expect 30 Hz to work over HDMI as well.
 
What I haven’t figured out is how to create scaled HiDPI resolutions.

I’d like to run my 4K monitor at 3008 x 1692 or 3200 x 1800 HiDPI scaled down to 3840 x 2160. (I. e., everything drawn in 2x at 6016 x 3384 or 6400 x 3600 and scaled down by the Intel HD 5000.) I’ve tried creating scaled resolutions with SwitchResX, etc., but they show up as invalid.

So currently I’m sending 3200 x 1800 @ 60 Hz to the monitor, which is upscaling to 4K. Better than upscaled 2560 x 1440, but not ideal.
 
On the PB287Q I can now get full 4K resolution over DisplayPort as long as DP is set to 1.2 in the monitor OSD. Using SwitchResX I enabled 3840 x 2160 @ 60 Hz, 3200 x 1800 @ 60 Hz and 3008 x 1692 @ 60 Hz.

With DP 1.1 I can get 3840 x 2160 @ 30 Hz. If I go higher to 45 Hz, the machine appears to crash hard.

I would expect 30 Hz to work over HDMI as well.
Thanks for the feedback ... finally we have 4K on our Nuc !!!

What I haven’t figured out is how to create scaled HiDPI resolutions.

Did you try this : link

Edit : Sorry, wrong link, I was thinking about this one
 
First, correction, I made a typo. 3840 x 2160 doesn’t work at 60 Hz. (I updated my post above.) If I create corresponding resolutions in SwitchResX, they come up as “invalid”. The highest I can take 3840 x 2160 is 45 Hz. 3200 x 1800 and lower do work at 60 Hz.

Second, when I open System Preferences → Monitors and option-click on the Resolution: Scaled radio button, I see the resolutions listed below. So I do have access to scaled HiDPI resolutions, just not ones greater than 2x one half the physical resolution. I set the “base resolution for scaling” to 6016 x 3384 using SwitchResX but to no avail.

System Preferences → Monitors offers the following resolutions:

3840 x 2160
3360 x 1890
3200 x 1800
3008 x 1692
2560 x 1600
2560 x 1440
2304 x 1296
2048 x 1152
1600 x 1200
1600 x 900
1344 x 1008
1344 x 756
1280 x 960
1024 x 768
1024 x 576
800 x 600
720 x 576
640 x 480
1920 x 1080 (HiDPI)
1680 x 945 (HiDPI)
1600 x 900 (HiDPI)
1504 x 846 (HiDPI)
1280 x 800 (HiDPI)
1280 x 720 (HiDPI)
1152 x 648 (HiDPI)
1024 x 576 (HiDPI)
960 x 540 (Interlaced HiDPI)
960 x 540 (HiDPI)
800 x 600 (HiDPI)
800 x 450 (HiDPI)
1080p
1080i
720p
480p
 
Status
Not open for further replies.
Back
Top