<< Solved >> Can't get graphics acceleration from Intel UHD 630 of i3-8100 on mojave 10.14.2

[jaymonkey]

@poles,

As @P1LGRIM has already stated you have miss-matched FakeSMC & USBInjectALL in /L/E to /EFI/CLOVER/kexts/Other,

Suggest you download the latest FakeSMC build by rehabman, Install updated FakeSMC and Sensor kexts to /L/E, copy updated FakeSMC to /EFI/CLOVER/kexts/Other and remove all other kexts from /EFI/CLOVER/kexts/Other.

Set the Clover Option System Parameters -> Inject Kexts to Detect, it is currently set to Yes which will cause issues as the FakeSMC in Clover does not match the one in /L/E ...

Why are you using NullCPUPowerManagement.kext ? you should remove it.

One more thing I checked in the kernal log that with using Lilu 1.3.1 & WhatEverGreen 1.2.7 it still failed to load WhatEverGreen in both cases. I think the new Lilu still can't load some of its plugins.

If you think Lilu is not loading then try version 1.2.9 with WhatEverGreen version 1.2.7 and set Device Properties again.

I also found some other i3 CFL users facing the same issue.

Its possible that they may well be an issue with i3 CFL CPU, since I don't have one its not possible for me to test, Suggest you report the issue on the Official Clover support thread ... it might also be worth reporting the issue on the WEG support thread too to ensure that WEG supports i3 CFL IGPU.

However many other users have are using WEG with CFL UHD 630 IGPU from using the Lilu Guide with out problems so i think the issue is more likely your MacOS configuration is at fault, missed-matched kexts and a badly configured config-plist.

As noted by @shuhung in post #30 it is working on his i3 CFL system ...

Cheers
Jay

 

[poles]

@jaymonkey,

Thanks.

If you think Lilu is not loading then try version 1.2.9 with WhatEverGreen version 1.2.7 and set Device Properties again.

I started with Lilu 1.2.9 & WEG 1.2.4 and from that time it's failed to load.

Its possible that they may well be an issue with i3 CFL CPU, since I don't have one its not possible for me to test, Suggest you report the issue on the Official Clover support thread ... it might also be worth reporting the issue on the WEG support thread too to ensure that WEG supports i3 CFL IGPU.

WEG github doesn't have any problem reporting thread. I know only Insanlymac forum WEG support thread. is it official? If you know any other WEG support forum please share the link.
I will definitely post on Clover support.

However many other users have are using WEG with CFL UHD 630 IGPU from using the Lilu Guide with out problems so i think the issue is more likely your MacOS configuration is at fault, missed-matched kexts and a badly configured config-plist.

I will try a clean install once again.

As noted by @shuhung in post #30 it is working on his i3 CFL system

Isn't the motherboard also plays a crucial part?

 

[shuhung]

As noted by @shuhung in post #30 it is working on his i3 CFL system ...

I don’t have CFL i3 CPU but tricking KBL HD630 as CFL UHD630, just put poles config.plist to my USB flash drive and boot from it, it work, although use same CFL kexts, may not same as real UHD630.

 

[poles]

I don’t have CFL i3 CPU but tricking KBL HD630 as CFL UHD630, just put poles config.plist to my USB flash drive and boot from it, it work, although use same CFL kexts, may not same as real UHD630.

Which means the config file is correct.

 

[shuhung]

Which means the config file is correct.

Your attached config_fbpatcher.plist work not config.plist on debug folder.

 

[poles]

@jaymonkey,

1. I clean installed macOS 10.14.2 using bootable usb created with Unibeast 9.
2. Currently booted with USB's config.
3. Should I patch graphics using Multibeast 11 or directly use lilu+WEG?

 

[poles]

Your attached config_fbpatcher.plist work not config.plist on debug folder.

I know.

 

[jaymonkey]

I don’t have CFL i3 CPU but tricking KBL HD630 as CFL UHD630, just put poles config.plist to my USB flash drive and boot from it, it work, although use same CFL kexts, may not same as real UHD630.

Ok .. understood ...

Should I patch graphics using Multibeast 11 or directly use lilu+WEG?

@poles,

I don't use Multibeast at all, its sometimes useful for installing some legacy hardware kexts but i find it tends to make too many assumptions which can cause problems.

If you can try not to use it and manually install everything you need, you'll have more control over what versions to use and how things are configured, so best to download Lilu and its plug-in's directly from the appropriate Git-Hub project page and install them in to /L/E using the method detailed in the Lilu Guide.

Suggest you use Lilu version 1.2.9 to begin with ... as you seemed to run into issues with 1.3.0/1.3.1.

Cheers
Jay

 

[shuhung]

If you can try not to use it and manually install everything you need, you'll have more control over what versions to use and how things are configured, so best to download Lilu and its plug-in's directly from the appropriate Git-Hub project page and install them in to /L/E using the method detailed in the Lilu Guide.

Suggest you use Lilu version 1.2.9 to begin with ... as you seemed to run into issues with 1.3.0/1.3.1.

Why not place in Clover/kexts/other, if prefer to install inside /Library/Extensions, should install dummy kext LiluFriend to ensure lilu load earlier than other kexts.

See below link for detail.

https://github.com/PMheart/LiluFriend


From lilu 1.3.1 link

v1.3.1
• Lowered version compatibility to 1.2.0 to let plugins load
Note: This release is functionally not different from 1.3.0, but it fixes plugin loading from /Library/Extensions if absolutely necessary.

https://github.com/acidanthera/Lilu/releases

 

[jaymonkey]

Why not place in Clover/kexts/other, if prefer to install inside /Library/Extensions, should install dummy kext LiluFriend to ensure lilu load earlier than other kexts.

@shuhung,

Since all kexts in /L/E are placed at the top of the kernel cache there is no need to use LiluFriend, it only really helps with MacOS version 10.10.X and earlier when everything was placed in /S/L/E ... before Apple made /L/E the endorsed location for all 3rd party kexts.

See this guide for all the reasons why you should use /L/E :-

https://www.tonymacx86.com/threads/guide-installing-kexts-macos-sierra-high-sierra-mojave.268964/

Cheers
Jay