Kexts in .../CLOVER/kexts/other/ or /Library/Extensions/

[loggedout]

Once your system is stable and booting from your system drive (not via USB) remove all 3rd party kexts from the Clover/Kexts/Other folder and install them in the /Library/Extensions folder on your system drive including FakeSMC (use KextBeast from the downloads section if you don't know how to do it using terminal commands), but leave a copy of FakeSMC in Clover/Kexts/Other. This way the MacOS kernel can access the kexts and cache them properly. Kext's injected by Clover live outside the MacOS Kernel.

Injecting all your 3rd party kext's via clover is not good for system stability as the kernel can not access them.

I had all my kexts in Clover/Kexts/Other since I started my Hackintosh before just switching from random patches to Lilu + WEG + AppleALC. When I did that on HS, I switched to putting everything in L/E and nothing in Clover/Kexts/Other. I then started the update without adding anything to Clover/Kexts/Other. Will it just not work at all now? It looks to be in the middle of the install; should I stop it, restore my HS clone, and restart after adding the kexts to Clover/Kexts/Other?

 

[jaymonkey]

I had all my kexts in Clover/Kexts/Other since I started my Hackintosh before just switching from random patches to Lilu + WEG + AppleALC. When I did that on HS, I switched to putting everything in L/E and nothing in Clover/Kexts/Other. I then started the update without adding anything to Clover/Kexts/Other. Will it just not work at all now? It looks to be in the middle of the install; should I stop it, restore my HS clone, and restart after adding the kexts to Clover/Kexts/Other?

@loggedout,

As i said in that post you should have a copy of FakeSMC in Clover/Kexts/Other as well as /L/E for this very reason.

If you boot the installer or recovery Clover will inject FakeSMC from Clover/Kexts/Other
If you boot MacOS the kernel will load FakeSMC from /L/E

Kext's injected by Clover run outside of the MacOS kernel's memory space.

Kext's loaded by the MacOs run inside the kernel's memory space and can be dynamically addressed, they are also cached so that they load faster during boot up resulting in a more stable system


Jay

 

[loggedout]

@loggedout,

As i said in that post you should have a copy of FakeSMC in Clover/Kexts/Other as well as /L/E for this very reason.

If you boot the installer or recovery Clover will inject FakeSMC from Clover/Kexts/Other
If you boot MacOS the kernel will load FakeSMC from /L/E

Jay

Thanks. I ended up stopping the install and reverting to HS. It did appear to be stuck. Once I put FakeSMC in its rightful place, the install went smoothly (I even saw the grey Installing macOS throughout the process which I usually don't see during upgrades). All of my kexts in L/E stayed there, too. Now I just need to get dual monitors working again, but that's for another thread.