Contribute
Register

How to enable 'Kaby Lake' Intel 6xx Graphics (10.12.6+)

Status
Not open for further replies.
Actually I have an Intel i7 7700 (HD 630) and my configuration is:
  • Clover 4268
  • IntelGraphicsFixUp kext
  • Inject Intel = true
  • IntelGraphicsDVMTFixup kext
  • ig-platform-id = 0x59120000
  • IntelGFX = 0x59128086

Important: I recommend you use the Clover Kext injection (put all your kexts in /EFI/CLOVER/Kexts/Other) instead of S*/L*/E* folder. ;)

This has got me a lot further, thank you! Seeing the IntelGraphicsDVMTFixup reminded me to double check my BIOS settings and they had been reset, so upping that to 128 MB has helped a lot. I can now boot reliably in a reasonable amount of time with the ig-platform-id and IntelGFX values you posted.

However, my graphics show as "Intel HD Graphics 630 5 MB" and I'm still unable to use resolutions higher than 1280x1024. Do you know what I can try to get full VRAM and higher resolutions? I still have Lilu and IntelGraphicsFixup 1.2.0 installed in /L/E and have removed FakePCIID and FakePCIID_Intel_HD_Graphics.

Can I ask why you recommend storing my kexts in the EFI partition? All the instructions I've seen say to use /S/L/E or /L/E.
 
Last edited:
This has got me a lot further, thank you! Seeing the IntelGraphicsDVMTFixup reminded me to double check my BIOS settings and they had been reset, so upping that to 128 MB has helped a lot. I can now boot reliably in a reasonable amount of time with the ig-platform-id and IntelGFX values you posted.

However, my graphics show as "Intel HD Graphics 630 5 MB" and I'm still unable to use resolutions higher than 1280x1024. Do you know what I can try to get full VRAM and higher resolutions? I still have Lilu and IntelGraphicsFixup 1.2.0 installed in /L/E and have removed FakePCIID and FakePCIID_Intel_HD_Graphics.

Can I ask why you recommend storing my kexts in the EFI partition? All the instructions I've seen say to use /S/L/E or /L/E.

About the resolution
Until you reach graphics acceleration and the correct configuration, you can't set the property resolution. I could try to help you with this, but I think that you should create a new post in Post installation > Graphics forum.

I recommend you read some user success builds with similar hardware as you. For example: https://www.tonymacx86.com/threads/...x-hero-i7-7700k-32gb-ram-intel-630-hd.222316/ (see his Intel HD 630 configuration and his steps)

Kexts in EFI vs kexts in S*/L*/E*
Actually, in the hackintosh community most people use Clover bootloader. Clover has a lot of great features like DSDT patches on the fly that are really useful. Other feature is Kext loading, this allows you put the kext files in Kexts/10.x (according your macOS version) or /Kexts/Other and Clover set for you the property permissions and handle cache to load the kexts correctly. So, you can forget set permissions and clean cache every time that you install a new kext. Besides that you will have the files more tidy.
 
About the resolution
Until you reach graphics acceleration and the correct configuration, you can't set the property resolution. I could try to help you with this, but I think that you should create a new post in Post installation > Graphics forum.

I recommend you read some user success builds with similar hardware as you. For example: https://www.tonymacx86.com/threads/...x-hero-i7-7700k-32gb-ram-intel-630-hd.222316/ (see his Intel HD 630 configuration and his steps)

Kexts in EFI vs kexts in S*/L*/E*
Actually, in the hackintosh community most people use Clover bootloader. Clover has a lot of great features like DSDT patches on the fly that are really useful. Other feature is Kext loading, this allows you put the kext files in Kexts/10.x (according your macOS version) or /Kexts/Other and Clover set for you the property permissions and handle cache to load the kexts correctly. So, you can forget set permissions and clean cache every time that you install a new kext. Besides that you will have the files more tidy.

I assumed the resolution would be fixed later, although if 1080p works I'll be happy :) I have looked at a few guides but there seems to be a few differences between 10.12.5, 12.12.6, and 10.13, so I find that they mostly don't make things better :( I've been playing around with little tweaks (change GFX0 to IGPU patch, 0x59128086 IntelGFX, -disablegfxhardware), but nothing is getting proper IGPU support. I think I will back with a fresh mind.

Regarding EFI vs /L/E, that makes total sense, and I'll start doing that, thanks! :)

Thank you for all your help!
 
I'm having various problems with getting any ports on my igpu to work alongside my primary Nvidia gtx 1060. I moved to Imac 18,3 with 10.12.6 and am cleaning out my configs a bit. (nvme spoofing also collapsed with 18,3, reverted to pikeralpha patches)

Display appears majorly garbled when connected to igpu via hdmi or displayport, and if I increase the shared ram in bios from 64mb to 128mb, it restarts the system instead of bringing up the login screen (with HDMI connected). IOReg and EFI>Clover attached. It also seems to restart if I try to run it with the garbled screen, feels like there is a memory allocation issue somewhere.

I normally don't use it, but I want to figure out what is making it borked, one thing that is strange is that the framebuffer shows all the connectors of the same type.

<code>
kextstat|grep -y acpiplat
13 1 0xffffff7f83b46000 0x66000 0x66000 com.apple.driver.AppleACPIPlatform (5.0) 65E05472-6AE7-3308-8CC8-FA6CB0DB2AEE <12 11 7 6 5 4 3 1>
kextstat|grep -y appleintelcpu
kextstat|grep -y applelpc
kextstat|grep -y applehda
93 1 0xffffff7f83779000 0x1d000 0x1d000 com.apple.driver.AppleHDAController (279.48) ED51F180-19C8-3DE1-AF81-0E389D98ADDE <92 91 78 12 7 6 5 4 3 1>
118 0 0xffffff7f838fb000 0xb5000 0xb5000 com.apple.driver.AppleHDA (279.48) 806B8C17-50CA-3C6B-90B3-195F38D8FB89 <117 95 93 92 91 78 6 5 4 3 1>
119 0 0xffffff7f83775000 0x2000 0x2000 com.apple.driver.AppleHDAHardwareConfigDriver (279.48) 14690424-1048-3F1D-8A3D-41657C97EB67 <4 3>
sudo touch /System/Library/Extensions && sudo kextcache -u /
Password:
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext XHCI-200-series-injector.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext USBInjectAll.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext NvidiaGraphicsFixup.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext Lilu.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext IntelMausiEthernet.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext IntelGraphicsFixup.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext PinConfigs.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext AppleALC.kext
KernelCache ID: BC3D886F4C10C278E281073C40D35709
</code>
 

Attachments

  • GFX0toIGPU_64MB.zip
    1.2 MB · Views: 97
Last edited:
need help, so far, everything was fine, but after the last 13.1 upgrade my hack stopped on black screen.

Clover in use:

* SMBIOS iMac18,3
* “ig-platform-id”: 0x59120000
* Devices - “Fake ID”: 0x59128086
* Boot “-disablegfxfirmware”
* GFX0 to IGPU
* Intel Inject "On"

Clover/other: AppleALC.kext, FakeSMC.kext, IntelMausiEthernet.kext, HackrNVMeFamily-10_12_4.kext, HackrNVMeFamily-10_12_4.kext, Lilu.kext, Shiki.kext

my Mobo: GA-Z170X-UD5 TH
CPU: i7-7700K
Samsung 960 PRO M.2
Internal SSD with class-code spoof

Connection via HDMI to Monitor - Samsung S27A950D


Please, maybe someone has already success on similar configuration?
 
need help, so far, everything was fine, but after the last 13.1 upgrade my hack stopped on black screen.

You have the wrong HackrNVMeFamily kexts for 13.1, but besides, you don't need code spoofing for high sierra, so get rid of those.
Get the latest versions of the rest of your kexts and replace them applealc, fakesmc, lilu and shiki below, but if your hackrnvme is stuck at 10_12_4 I have a strong suspicion you are using an old version of clover and its uefi drivers, update those as well. All in all, probably not a gpu problem but we would know better if you booted with -v


https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek/downloads/
https://github.com/vit9696/Lilu/releases
https://github.com/vit9696/AppleALC/releases
https://github.com/vit9696/Shiki/releases
https://bitbucket.org/RehabMan/os-x-intel-network/downloads/
 
... but if your hackrnvme is stuck at 10_12_4 I have a strong suspicion you are using an old version of clover and its uefi drivers, update those as well.

I used my HackrNVMeFamily-10_12_4.kext on each Sierra upgrade sine 10_12_4 to 10_13_0 and it worked great, and few day ago it's working also on new 10_13_1, but I don't know what happened, just today I started up and got black screen.

and till last update this configuration every time worked:

ig-platform-id: 0x193B0000
“Fake ID”: 0x193B8086

therefor I don't change HackrNVMeFamily-10_12_4.kext

but now nothing to work:(
 
therefor I don't change HackrNVMeFamily-10_12_4.kext
but now nothing to work:(

And it will continue not working if you don't report the problem in a way that people can address, boot -v and report what it says there. Probably, you didn't update one of the kexts before an update, or have an old clover or something. You can make high sierra usb using unibeast and see if you can boot your normal drive from there.
 
I've been persevering but have only been able to get more/different errors. Using Multibeast 10's config (plus -v and with or without drop cpupm) I get "AE_ALREADY_EXISTS" errors, and with another (custom) config it will hang after some text about the IGPU firmware. configs and errors attached... does anyone have any ideas?

config.custom.error.jpeg config.multibeast.error.jpeg
 

Attachments

  • config.custom.plist
    5.3 KB · Views: 210
  • config.multibeast-10.plist
    6.2 KB · Views: 225
I've been persevering but have only been able to get more/different errors. Using Multibeast 10's config (plus -v and with or without drop cpupm) I get "AE_ALREADY_EXISTS" errors, and with another (custom) config it will hang after some text about the IGPU firmware. configs and errors attached... does anyone have any ideas?

View attachment 291302 View attachment 291303
try the one I modified. It's hard to tell without knowing what you have for kexts and such.
 

Attachments

  • config.custom.plist
    5.8 KB · Views: 238
Status
Not open for further replies.
Back
Top