[solved] Intel 4400 GPU compatibility on GB-BXi5H-4200

• I installed OS X successfully using the -x maxmem=8192 flag
• I ran MultiBeast and installed the proper Realtek sound and network drivers
• I followed the instructions for 4400 support here and installed the FakePCIID for the HD4400 with KextBeast. The kext doesn't show up in kextstat and the system report shows an Intel HD Graphics 4400 GPU with 3MB RAM and no kext loaded at 1024x768.
• When that failed, I followed the suggestion of someone with the same machine and used IGPlatformID=0D220003. This also failed.
• I was able to force the resolution to the proper 1920x1200, but it's without acceleration and essentially unusable.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>EthernetBuiltIn</key>
    <string>Yes</string>
      <key>GraphicsEnabler</key>
    <string>No</string>
    <key>IGPEnabler</key>
    <string>Yes</string>
        <key>IGPDeviceID</key>
        <string>0412</string>
    <key>Kernel Flags</key>
    <string>kext-dev-mode=1</string>
    <key>Legacy Logo</key>
    <string>Yes</string>
    <key>Timeout</key>
    <string>2</string>
        <key>HDEFLayoutID</key>
        <string>03000000</string>
        <key>GenerateCStates</key>
        <string>Yes</string>
        <key>GeneratePStates</key>
        <string>Yes</string>
        <key>UseKernelCache</key>
        <string>Yes</string>
        <key>HDAEnabler</key>
        <string>Yes</string>
</dict>
</plist>

ameno86 said:

After re-reading the post and footnotes about Chimera boot flags a bunch of times, I realized that it mentioned the 4400 explicitly, and it occurred to me to use IGPlatformID and IGPDeviceID simultaneously, setting IGPlatformID to 0D220003 and IGPDeviceID to the FakePCIID kext ID of 0412. Unfortunately, this didn't make any difference at all. In fact, after dozens of reboots in the course of playing configuration roulette (and not even causing a crash), I'm starting to wonder if I haven't done something very wrong such that the chameleon boot plist just has no effect at all.

EDIT:
It appears that the IGPlatformID setting is working, as bdmesg shows:

Code:

Intel HD Graphics 4400 [8086:0a16] (rev 09)
Subsystem: [1458:d000] :: PciRoot(0x0)/Pci(0x2,0x0)
Using 0x)D220003 for ig-platform-id

Since my IGPlatofrm ID is 0D220003 and my IGPDeviceID is 0a26, this suggests the latter isn't working. Looking back again at the boot flag post, I see that 0a16 is a 44/4600 model, but not the default of 0412 and not the 0a26 I set based on the chart in that post. That entry on the chart, however, would seem to conflict the with documentation for FakePCIID on Github where it's stated that "8086:0a16 is HD4400 mobile."

So either the bootloader is more clever than I am and picking the right 0a16 ID no matter what I put in the boot plist or the 0a26 in the chart is incorrect. Either way, it I'm unable to get anywhere attempting to change device ID's (if that's even a possibility).

Click to expand...

ameno86 said:

That all seems very reasonable and essentially goes along with your posts and the FakeKExt documentation (though I'm still unable to figure out the apparent ID consistencies I mentioned between the post on boot options and the FakeKExt documentation). But it doesn't seem to work. In my latest configuration, I have the file below and I've never incorrectly used the hex notation you describe.

Code:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>EthernetBuiltIn</key>
    <string>Yes</string>
      <key>GraphicsEnabler</key>
    <string>No</string>
    <key>IGPEnabler</key>
    <string>Yes</string>
        <key>IGPlatformID</key>
        <string>0D220003</string>
        <key>IGPDeviceID</key>
        <string>0412</string>
    <key>Kernel Flags</key>
    <string>kext-dev-mode=1</string>
    <key>Legacy Logo</key>
    <string>Yes</string>
    <key>Timeout</key>
    <string>2</string>
        <key>HDEFLayoutID</key>
        <string>03000000</string>
        <key>GenerateCStates</key>
        <string>Yes</string>
        <key>GeneratePStates</key>
        <string>Yes</string>
        <key>UseKernelCache</key>
        <string>Yes</string>
        <key>HDAEnabler</key>
        <string>Yes</string>
</dict>
</plist>

EDIT: To be clear, the confusion I'm referring to is whether the 4400 is 0a26 (as in the chart on the boot options post) or 0a16 (as specified for the 4400 on the Github documentation). Though if I understand your last post correctly (and I'm not sure I do), that difference doesn't matter. I'll sadly admit to trying every ID mentioned in these posts, but I'm reasonably sure the KExt mechanism simply isn't functioning on my machine -- these ID's I'm inputting are irrelevant.

Click to expand...

ameno86 said:

I've attached the output of IOReg. But it may be appropriate at this point to reframe my question from "Is this recommended build's Intel 4400 compatible" to "Why isn't FakeKExt working on my computer."

Click to expand...

ameno86 said:

I have installed those before, but to make sure, I used KextWizard (you never know if KextBeast has worked as it provides no useful output) and made sure to clear caches and repair permissions. I've attached the IOReg output in case anything has changed, but I don't believe it has. The device still shows up as 0xa16.

This is a pretty simple install. There's one partition and OS X is the only OS I'll be using. All the other parameters in the plist seem to have an effect (including platform), just not the device ID injection, which appears to do nothing. But I'll trawl around and see if I'm somehow using the wrong one. But /Extra/org.chameleon.Boot.plist appears to be the only file of its sort on my system.

Click to expand...