Contribute
Register

[GUIDE] Installing 3rd Party Kexts - El Capitan, Sierra, High Sierra, Mojave, Catalina

Jay, do you still recommend to put kexts into L/E? I'm asking because Stork's comment in the 10.15.3 update thread seem to contradict this :

Starting in February 2020, Apple will "clamp down" on non Apple approved kexts. So, update Lilu, WhatEverGreen and AppleALC, placing them in your /EFI/.../Clover/kexts/other/. Remove these kexts from the /Library/Extensions/ folder. If you haven't already, move any other hackintosh kexts from /Library/Extensions/ folder to the .../Clover/kexts/other/ folder. Then run the following Terminal command to rebuild the macOS cache:
Code:
sudo kextcache -system-prelinked-kernel
sudo kextcache -system-caches

So what do you recommend: L/E or others folder?
 
Jay, do you still recommend to put kexts into L/E? I'm asking because Stork's comment in the 10.15.3 update thread seem to contradict this


@elgipsy,

See this post for my thoughts on this :-


Basically developers will always need to circumvent such limitations in order to test alpha and beta versions of kexts before submitting them to Apple ... so i personally don't see this as a major problem.

The "Allow Unapproved kexts" bit mask has already been implemented in MacOS and the current version of Clover so it should be just a case of using that to negate the requirement.

Cheers
Jay
 
I am using mac 10.15.3. The kext works in /Other but some don't work in /L/E like ethernet, voodooi2c
Is this my fault? or is it because of the mac 10.15.3 update
 
10. Summary

1. Copy FakeSMC and only critical kext's needed to run the MacOS Installer, Updater or Recovery to EFI/Clover/kexts/Other2. Install all 3rd party kexts (including FakeSMC) required to run MacOS in /Library/Extensions3. Set Clover -> System Parameters -> Inject Kexts to "Detect"


I have one more question, if you don`t mind:
I understand that FakeSMC should be in L/E/ AND in /Clover/kexts/Other/ and all other critical kexts, too,
if needed. (LiLu, USBinjectAll, WhateverGreen)...
Should these critical kexts be in /L/E too, or only in /Other?
You have explained, clover is only looking for FakeSMC when when set to "Detect", not for other kexts.
So are they loaded twice then if I have them in both?
Hope you get what I mean.
 
Should these critical kexts be in /L/E too, or only in /Other? You have explained, clover is only looking for FakeSMC when when set to "Detect", not for other kexts. So are they loaded twice then if I have them in both? Hope you get what I mean.


@PEKA62,

When the Clover option, "Inject Kexts" is set to "Detect" Clover will check that FakeSMC (or Lilu + VirtualSMC) is installed in /L/E, if it is then Clover will not inject any Kexts and leaves MacOS to load all 3rd party kexts from /L/E.

So the answer your question is Yes, you should install all 3rd party kexts in /L/E and only copy the critical ones to /EFI/Clover/Kexts/Other which will only be used when booting Installer, Updater or Recovery.

Hope that helps to clarify ...

Cheers
Jay
 
Thank you @jaymonkey
So best practice would be to have all kexts in L/E/ for regular use (because auf integration in Kernel memory) and MOVE the critical ones to /EFI/Clover/Kexts/Other/ before booting updater. And move them back to /L/E/ after update.
have all kexts in /L/E

and "copy" essential kexts to clover
 
When the Clover option, "Inject Kexts" is set to "Detect" Clover will check that FakeSMC (or Lilu + VirtualSMC) is installed in /L/E, if it is then Clover will not inject any Kexts and leaves MacOS to load all 3rd party kexts from /L/E.
Got it now. Thank You.
 
I am troubleshooting my Catalina SSD install (get blank screen on boot) - and I have Mojave running fine - so I keep trying different things in boot args but nothing is working. I am hoping that kext rebuild on the Catalina disk will help. I tried booting with -f but that did not help. I cannot get into the OS at all - safe mode does not boot. I have latest Lilu, WG in /L/E and latest Clover. Can I use Hackintool and rebuild kext cache in /L/E on a non-booted disk? Or what is the best way to do this? Most terminal commands and applications want to run on the currently booted disk.
 
Back
Top