Help! Can't get HD 4600 fully recognized

[Draekia]

UPDATE: I fixed the problem (at the suggestion of another kind and patient user here in the chatroom), seriously, by moving my hdmi cable to the other port on my motherboard. Seriously. After all of the codes. Lesson of the day: don't neglect the chances you're being an idiot and there is an insanely simple solution.

 

Also, I'm using the 0x0D220003 ig-platform-id

 

For posterity:

 

So, while I have tried installing with Uni/Chameleon in the past, they led me to only really unstable and buggy installations. 

I decided to go with Clover and now my system is functional, but I can't get the IGP to be fully recognized. 

my setup:

 

OS X 10.9.4 (vanilla) and newest (as of 3 days ago) Clover 2795 revision.
GA-h87n-wifi Rev 2.0 f7 bios
8gb RAM
i3 4340 CPU
HDTV over HDMI as a monitor (will play with sound after I at least get graphics and full-screen monitor support!)

Edit! I forgot to mention that I'm using a HDTV as a monitor, so I'm not expecting crazy resolution, just want full screen and no more graphic artifacts/flickering.

Config.plist here: https://dl.dropboxusercontent.com/u/45125714/config.plist

I built this machine along some "recommended" build guidelines, so I've no idea why it has been such a headache.

Any idea how to fix this? I'll happily share my .plist/etc if necessary, but I am beginning to think that some of my problems are processor specific or (perhaps) bios revision caused as I can't seem to even get full-screen video when I boot into the bios (delete key)! On an earlier, but unstable, f4 revision, I could at least get full-screen there so... I'm confused.

Pictures speak louder than words:

[jamiethemorris]

Did you specify an ig-platform-id? attach your config.plist.

[Draekia]

I did, and I will first thing in the morning. I don't know why I'm not getting updated when people reply to my posts.

[Draekia]

Did you specify an ig-platform-id? attach your config.plist.

I uploaded it just now, had a bit of a life issue this morning.

[jamiethemorris]

I'll take a look at it soon, but I looked at the pics and the first thing that jumped out at me is that your vendor and device id ate swapped. Vendor id should be 8086 and device id should be 0416. Also probably better to use 0412 instead for the device id.

 

I hope everything is OK with your life issue.

 

P.S. I never get notified of replies either lately, dunno why.

[jamiethemorris]

Yeah, your FakeID for your IntelGFX was backwards, it should be like this:

<key>IntelGFX</key>
<string>0x04128086</string>

Oh, and it's normal not to have full resolution in the BIOS. I don't think there's anything wrong with your build.

[Draekia]

Yeah, your FakeID for your IntelGFX was backwards, it should be like this:

<key>IntelGFX</key>
<string>0x04128086</string>

Oh, and it's normal not to have full resolution in the BIOS. I don't think there's anything wrong with your build.

 

Hmm okay, so I thought I had tried that before and I got my old result of a crash to black and instant-reboot. I tried booting in safe mode to the same effect.

 

Thanks for the advice! Back to my drawing board, I suppose.

 

Edit: And I should add that I tried with 0x04168086 to the same crash

[RehabMan]

Yeah, your FakeID for your IntelGFX was backwards, it should be like this:

<key>IntelGFX</key>
<string>0x04128086</string>

Oh, and it's normal not to have full resolution in the BIOS. I don't think there's anything wrong with your build.

 

Why would you inject a device-id that is already recognized and same as native id?

 

IOPCIPrimaryMatch from AppleIntelFramebufferAzul.kext: 0x0c268086 0x0c168086 0x0c068086 0x0d268086 0x0a268086 0x0a2e8086 0x0a168086 0x04268086 0x04168086 0x04068086 0x0d228086 0x04128086

 

People do crazy stuff 'round here...

[Draekia]

Why would you inject a device-id that is already recognized and same as native id?

 

IOPCIPrimaryMatch from AppleIntelFramebufferAzul.kext: 0x0c268086 0x0c168086 0x0c068086 0x0d268086 0x0a268086 0x0a2e8086 0x0a168086 0x04268086 0x04168086 0x04068086 0x0d228086 0x04128086

 

People do crazy stuff 'round here...

Should I just be leaving the fields blank in the plist, then?

[RehabMan]

Should I just be leaving the fields blank in the plist, then?

Yes. Focus on injecting the correct ig-platform-id.

[jamiethemorris]

Why would you inject a device-id that is already recognized and same as native id?

 

IOPCIPrimaryMatch from AppleIntelFramebufferAzul.kext: 0x0c268086 0x0c168086 0x0c068086 0x0d268086 0x0a268086 0x0a2e8086 0x0a168086 0x04268086 0x04168086 0x04068086 0x0d228086 0x04128086

 

People do crazy stuff 'round here...

I'm guessing he read to do that in one of the Yosemite threads since they took out 0416. I just noticed that it was backwards. Does leaving it in make a difference, as in, does the kext work differently depending on the device id?

[RehabMan]

I'm guessing he read to do that in one of the Yosemite threads since they took out 0416. I just noticed that it was backwards. Does leaving it in make a difference, as in, does the kext work differently depending on the device id?

This is post installation 10.9.

 

Leaving it in if specified incorrectly makes a huge difference. It disables the driver/device when it would normally be recognized.

 

Leaving it in if specified correctly would make no difference at all, assuming the native id is the same and already recognized. It is unknown as to whether the driver makes any changes based on the device-id matched. Certainly, it loads the same code. Whether that code changes its actions based on the device-id in ioreg would require deep analysis of the code.

[Draekia]

Edit: I fixed it by moving my HDMI cable one port up. Physically. As in the actual cable and plug.

 

I... don't... understand how I was oblivious to the obvious... Sorry and thank you so much!

 

 

 

Yes. Focus on injecting the correct ig-platform-id.

So, I've so far injected every single code I saw at this link and with a 0x0 for the Fake ID I'm at least booting, but still nothing changes at all.

 

I've also gone through the ones listed as supported by the kexts on this page and this page.

 

My display-cfg remains blank. 

 

I must be retarded because there has to be an obvious error.

 

Also, I had to re-do my config.plist because one stopped loading my efi drive (no idea why) or itself at all, it's working again... I think, since I have the proper XMP profile loading. Alas, no graphics acceleration.

 

New config

[RehabMan]

...

New config

I don't think the ig-platform-id 80860c26 is valid.

 

See here for valid ids: http://www.insanelymac.com/_/osx86/intel-hd4000-and-haswell-inject-aaplig-platfor-r1005

[Draekia]

I don't think the ig-platform-id 80860c26 is valid.

 

See here for valid ids: http://www.insanelymac.com/_/osx86/intel-hd4000-and-haswell-inject-aaplig-platfor-r1005

 

 

You are correct, it was. It all actually boiled down to my using a different HDMI port.  Now I've got full graphics acceleration, I just need to fix iMessage and hdmi audio.

 

Thank you so much, though!

[pierbrt]

Hi, just finished to fix it.

 

I have a clover-based 10.9.4 install on HD4600 only and with full QE/CI.

 

I checked what HD4xxx/HD5xxx graphics controllers are handled by those two kexts:

AppleIntelHD5000Graphics.kext

AppleIntelFramebufferAzul.kext

 

(see <key>IOPCIPrimaryMatch</key>

<string>0x00908086 0x00918086 0x00928086 0x0c268086 0x0c168086 0x0c068086 0x0c228086 0x0d268086 0x0a268086 0x0a168086 0x04268086 0x04168086 0x04068086 0x0d228086 0x04128086 0x0a2e8086</string>

 

my HD4600 was detected by DPCIManager as: Vendor(8086), Device(4016) with no Device Name description

 

In clover config I thus injected one of the recognised strings: 0x04168086 as a Fake-ID 

<key>FakeID</key>

<dict>

    <key>IntelGFX</key>

    <string>0x04168086</string>

    <key>LAN</key>

   <string>0x153b8086</string>

</dict>

 

Now my DCPIManager detects it as: Vendor(8086),Device(4016), Device Name(Intel Corp. 4th Gen Core Processor Integrated Graphics Controller)

 

and I have full QE/CI graphics!!!