[Solved] No Boot Post Installation After MultiBeast and Clover Configurator

[JCMunsonII]

Greetings!

While I succesfully installed El Capitan, configuring it fails.

After following Stork's HERO build guide, and setting FakeCPUID/IntelGFX/ig-platform-id, installing the three kexts & ssdt.aml, the system hangs on reboot.

The last two lines are:

IOAPIC: Version 0x20 Vectors 64:87
ACPI

MB config, Clover config.plist, ssdt.aml and screenshot attached.

Thank you for the help!

Jon

EDIT: Added the CLOVER system.

 

[JCMunsonII]

I see a problem in the config.plist:

<key>Device</key>
<string>IntelGFX</string>
<key>Key</key>
<string>AAPL,GfxYTile</string>
<key>Value</key>
<string>AQAAAA==</string>

should be:

<key>Device</key>
<string>IntelGFX</string>
<key>Key</key>
<string>AAPL,GfxYTile</string>
<key>Value</key>
<data>
AQAAAA==
</data>

I was unable to select "data" from the drop-down list in Clover Configurator - not sure why.

 

[JCMunsonII]

Interesting... When I'm in Xcode editing the config.plist, it won't take "AQAAAA==" as a "data" entry - it converts it to "<41514141 41413d3d>". Is that what is supposed to happen??? When I revert it back to "string," I see the "AQAAAA==" entry...

 

[JCMunsonII]

Issue may be more than this, but, it does involve at least one kext. Now to narrow it down. I know it is NOT CodecCommand (@RehabMan's version), nor the PCIID kexts.

 

[JCMunsonII]

OK - I am back in (and writing from the CustoMac - YES!).

I moved the FakeSMC.kext, FakePCI*.kext, CodecCommander.kext, and USBInjectAll.kext back. The display is now working as expected (for the iGPU) - I have scaling available and the projector icon is not displaying top-right. I'm sure I have graphics acceleration as well, but not sure how to check that. Shows ~1.5GB of VRAM in Profiler.

Q: If I move the "invalid" kext back, will the system halt, or, will it just keep running until a reboot?

 

[JCMunsonII]

OK, I have put back a number of kexts. The following kexts caused an "installed improperly" message, and probably led to the failure-to-boot:

FakeSMC sensor kexts
PromiseSTEX.kext
SoftRAID.kext

Are any of those going to present an issue if they are not present?

 

[JCMunsonII]

This is solved - "improperly installed" kexts appeared to be the culprit.