High Sierra 10.3.4 Problem with iGPU Intel UHD630 i3-8100

zzmadd

New member
Joined
Apr 11, 2018
macOS
10.15.1
Mobo
Asus Rog Strix Z370-I Gaming
CPU
i3-8100
GPU
iGPU Intel UHD 630
#1
Hi all,

following the guide I was able to run quite nicely the Intel UHD630 iGPU until 10.3.3.
I had used method 3, modified the files, copied necessary kext into EFI/CLOVER/kexts/Other
had FinalCutProX running, hardware acceleration running very little flickering.
Then I updated to 10.13.4, reModded the files as per method 3, didn't touch config.plis as it was already set BUT even though hardware acceleration is still recognised, I am experiencing huge flickering. Resolution has always been 1080p/60Hz
I updated all the lilu, fake, shiki, intelgraphicsfixup etc etc kexts to latest versions.
Now I switched back to method one to use the PC as the flickering was so bad I couldn't use it.

Anybody has an idea how to fix this?
Thanks
 

someguy

New member
Joined
Apr 9, 2018
macOS
10.13.3
Mobo
Aorus Gaming 5
CPU
8700K
GPU
GTX 970
#2
On the new update I couldn’t even get iGPU working following the steps. I think we have to wait for Hackintosher to update the guide maybe for the latest High sierra release?
 

zzmadd

New member
Joined
Apr 11, 2018
macOS
10.15.1
Mobo
Asus Rog Strix Z370-I Gaming
CPU
i3-8100
GPU
iGPU Intel UHD 630
#3
Hi,
thanks for your reply.
It helps to know other people have similar issues.
BTW it worked really nicely in 10.13.3 and was bootable in 10.13.4 BUT I experienced huge flickering and the system was unusable.
Also I tried to have both GPUs running (internal and GT 1030) connecting the monitor to the GT 1030 and even though acceleration was recognised, FinalCutPro output, I mean the rendered files, showed artefacts and were not usable.
Hopw someone implements it again.
BTW Rehabman uses a different technique to enable iGPU on the i3-8100 that involves copying files to L / E, has anyone tried that?
 

Hackintosher

Administrator
Joined
Jan 21, 2018
macOS
10.15.0
Mobo
Gigabyte Z370N WIFI
CPU
i3-8100
GPU
UHD 630 Graphics
#4
Hi,
thanks for your reply.
It helps to know other people have similar issues.
BTW it worked really nicely in 10.13.3 and was bootable in 10.13.4 BUT I experienced huge flickering and the system was unusable.
Also I tried to have both GPUs running (internal and GT 1030) connecting the monitor to the GT 1030 and even though acceleration was recognised, FinalCutPro output, I mean the rendered files, showed artefacts and were not usable.
Hopw someone implements it again.
BTW Rehabman uses a different technique to enable iGPU on the i3-8100 that involves copying files to L / E, has anyone tried that?
I'm here and have acceleration on my i3-8100 on 10.13.4 running with Method 3.

Looks like Apple 0x3E918086 is no longer working so change Fake ID IntelGFX = 0x3E928086

If it still doesn't work after that then either there is something wrong with your EFI or you didn't patch the frame buffers correctly. If you have any more problems let me know and I'll give you my 10.13.4 i3 EFI I'm typing this on.
 
Likes: zzmadd

zzmadd

New member
Joined
Apr 11, 2018
macOS
10.15.1
Mobo
Asus Rog Strix Z370-I Gaming
CPU
i3-8100
GPU
iGPU Intel UHD 630
#5
I'm here and have acceleration on my i3-8100 on 10.13.4 running with Method 3.

Looks like Apple 0x3E918086 is no longer working so change Fake ID IntelGFX = 0x3E928086

If it still doesn't work after that then either there is something wrong with your EFI or you didn't patch the frame buffers correctly. If you have any more problems let me know and I'll give you my 10.13.4 i3 EFI I'm typing this on.
Thanks for the reply!
First test has been to have both my GT 1030 and UHD630 running.
The do work together as per method 3 with FakeID as you suggested
Monitor on the GT 1030, UHD enabled for hardware acceleration purposes
AND
for example a rendering in Final Cut Pro X takes half what it takes with the GT 1030
So hardware acceleration works
BUT
The rendering output video file is corrupted, shows black areas, meaning the flickering or the not proper implementation is still happening
Now I test the system with just the UHD 630
 

Hackintosher

Administrator
Joined
Jan 21, 2018
macOS
10.15.0
Mobo
Gigabyte Z370N WIFI
CPU
i3-8100
GPU
UHD 630 Graphics
#6
On the new update I couldn’t even get iGPU working following the steps. I think we have to wait for Hackintosher to update the guide maybe for the latest High sierra release?
You should also try changing IntelGFX to 0x3E928086 and see if it works.
 

zzmadd

New member
Joined
Apr 11, 2018
macOS
10.15.1
Mobo
Asus Rog Strix Z370-I Gaming
CPU
i3-8100
GPU
iGPU Intel UHD 630
#7
0x3E928086 doesn't work here, huge flickering.
Well...disabling Inject Intel now it's working with 0x3E928086
So it seems it's better.
UPDATE:
But without Inject Intel there's no hardware acceleration
even though it sees 1536MB Vram and it's usable,
but all the app that use Metal and hardware acceleration won't even start
UPDATE:
Switching to iMac 17,1 definition from 18,3 made everything working
BUT...towards the end of a rendering in Final Cut Pro X the screen went black and there was no way other than to switch off the PC
 
Last edited:

Hackintosher

Administrator
Joined
Jan 21, 2018
macOS
10.15.0
Mobo
Gigabyte Z370N WIFI
CPU
i3-8100
GPU
UHD 630 Graphics
#8
0x3E928086 doesn't work here, huge flickering.
Well...disabling Inject Intel now it's working with 0x3E928086
So it seems it's better.
UPDATE:
But without Inject Intel there's no hardware acceleration
even though it sees 1536MB Vram and it's usable,
but all the app that use Metal and hardware acceleration won't even start
UPDATE:
Switching to iMac 17,1 definition from 18,3 made everything working
BUT...towards the end of a rendering in Final Cut Pro X the screen went black and there was no way other than to switch off the PC
If you are only using the iGPU you need to use iMac 18,1 to fix graphical issues.
 
Likes: zzmadd

zzmadd

New member
Joined
Apr 11, 2018
macOS
10.15.1
Mobo
Asus Rog Strix Z370-I Gaming
CPU
i3-8100
GPU
iGPU Intel UHD 630
#9
If you are only using the iGPU you need to use iMac 18,1 to fix graphical issues.
Thanks!
I confirm 17,1 and 18,1 both work with internal graphics.
Awesome!
What definition should I use when I use both iGPU and discrete GPU?
 

kw123

New member
Joined
Apr 18, 2018
macOS
10.13.4
Mobo
Gigabyte B360M-HD3
CPU
i3-8100
GPU
intel UHD 630
#11
hi, i have follow the step but if i set the Fake ID IntelGFX = 0x3E928086 it boot until the end of loading bar on below Apple logo, my monitor will be disconnect, i even try the method1, 2,3 it doesnt work. My os is 10.13.4
 

iamdvsone

New member
Joined
Apr 15, 2018
macOS
10.13.4, 10.13.3
Mobo
Gigbyte z370 gaming 5 & Asus z370-f gaming`
CPU
I7 8700K
GPU
Gigabyte RX Vega 64
#12
Likes: kw123

poles

New member
Joined
Nov 28, 2018
macOS
10.13.6
Mobo
MSI Z370 Pro
CPU
i3 8100
GPU
UHD 630
#15
@Hackintosher : This method (3) worked perfectly fine for me on 10.13.4 as I'm using i3 8100. But after upgrading my system to 10.13.6 I used the same process but it didn't work for me. System rebooting repeatedly on the half way of booting. Should I try in config.plist with the following:

Fake ID IntelGFX = 0x3E928086 with System Definition 18,1 or 18,3 ?

But I got a question. Do I have to edit the AppleIntelKBLGraphics.kext & AppleIntelKBLGraphicsFramebuffer.kext and replace 0x3E918086 with 0x3E928086 also?

System:
MSI Z370 PRO / i3 8100 / UHD 630 / 10.13.6