RehabMan
Moderator
- Joined
- May 2, 2012
- Messages
- 181,058
- Motherboard
- Intel DH67BL
- CPU
- i7-2600K
- Graphics
- HD 3000
- Mac
- Mobile Phone
Intel HD Graphics on El Capitan
OS X supports a range of Intel HD Graphics devices, however not all the variants present in hackintosh devices are supported out of the box.
Haswell HD4200/HD4400/HD4600: Must inject device-id=0x0412.
config.plist/Devices/FakeID/IntelGFX=0x04128086
Broadwell HD5600 (10.11.0/10.11.1 only): Must inject device-id=0x1626.
config.plist/Devices/FakeID/IntelGFX=016268086
Note: These settings are already in the plist files linked from my Clover guide...
http://www.tonymacx86.com/el-capita...de-booting-os-x-installer-laptops-clover.html
FakePCIID Installation
In addition, the Haswell graphics accelerator kext (AppleIntelHD5000Graphics.kext) checks the PCI device-id against a set of known values. Because the HD4200/HD4400/HD4600(mobile) values are not accommodated by this check, you must install FakePCIID kexts for PCI device-id spoofing.
The latest release of FakePCIID can be found here:
https://bitbucket.org/RehabMan/os-x-fake-pci-id/downloads
The source code is located at:
https://github.com/RehabMan/OS-X-Fake-PCI-ID
Install both FakePCIID.kext and FakePCIID_Intel_HD_Graphics.kext (originally FakePCIID_HD4600_HD4400.kext) in /System/Library/Extensions, EFI/Clover/kexts (typically in EFI/Clover/kexts/Other), or /Library/Extensions (10.11+).
--
Note: This post, simplified for Clover only 10.11, based on original by the-darkvoid for Yosemite: http://www.tonymacx86.com/yosemite-...tel-hd4200-hd4400-hd4600-mobile-yosemite.html.
WhateverGreen.kext+Lilu.kext
WhateverGreen.kext (requires Lulu.kext) implements the same spoofing that is implemented by FakePCIID.kext+FakePCIID_Intel_HD_Graphics.kext.
As a result, when using WhateverGreen.kext, you will not need FakePCIID.kext + FakePCIID_Intel_HD_Graphics.kext.
Problem Reporting
Read FAQ, "Problem Reporting". Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
Use the gen_debug.sh tool mentioned in the FAQ, that way it is less likely you'll omit something.
OS X supports a range of Intel HD Graphics devices, however not all the variants present in hackintosh devices are supported out of the box.
Haswell HD4200/HD4400/HD4600: Must inject device-id=0x0412.
config.plist/Devices/FakeID/IntelGFX=0x04128086
Broadwell HD5600 (10.11.0/10.11.1 only): Must inject device-id=0x1626.
config.plist/Devices/FakeID/IntelGFX=016268086
Note: These settings are already in the plist files linked from my Clover guide...
http://www.tonymacx86.com/el-capita...de-booting-os-x-installer-laptops-clover.html
FakePCIID Installation
In addition, the Haswell graphics accelerator kext (AppleIntelHD5000Graphics.kext) checks the PCI device-id against a set of known values. Because the HD4200/HD4400/HD4600(mobile) values are not accommodated by this check, you must install FakePCIID kexts for PCI device-id spoofing.
The latest release of FakePCIID can be found here:
https://bitbucket.org/RehabMan/os-x-fake-pci-id/downloads
The source code is located at:
https://github.com/RehabMan/OS-X-Fake-PCI-ID
Install both FakePCIID.kext and FakePCIID_Intel_HD_Graphics.kext (originally FakePCIID_HD4600_HD4400.kext) in /System/Library/Extensions, EFI/Clover/kexts (typically in EFI/Clover/kexts/Other), or /Library/Extensions (10.11+).
--
Note: This post, simplified for Clover only 10.11, based on original by the-darkvoid for Yosemite: http://www.tonymacx86.com/yosemite-...tel-hd4200-hd4400-hd4600-mobile-yosemite.html.
WhateverGreen.kext+Lilu.kext
WhateverGreen.kext (requires Lulu.kext) implements the same spoofing that is implemented by FakePCIID.kext+FakePCIID_Intel_HD_Graphics.kext.
As a result, when using WhateverGreen.kext, you will not need FakePCIID.kext + FakePCIID_Intel_HD_Graphics.kext.
Problem Reporting
Read FAQ, "Problem Reporting". Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
Use the gen_debug.sh tool mentioned in the FAQ, that way it is less likely you'll omit something.
Last edited: