Contribute
Register

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

Has anyone observed the warning "relocation failed" when attempting to install the latest AppleALC.kext (1.5.4) in /L/E? Is this a problem and does this preclude installation of AppleALC.kext in /L/E? Details below...

I'm still installing kexts in /L/E with CLOVER r5122 and Catalina 10.15.7. When attempting to install the latest AppleALC.kext (1.5.4), executing 'kextcache -i /' results in the warning below (repeated 4 times). Acidanthera doesn't consider this to be a problem since it doesn't affect OC kext injection and they no longer support CLOVER and kexts installed in /L/E. This warning does not occur with AppleALC.kext 1.5.3. Does anyone know if this warning is a problem for AppleALC.kext installed in /L/E? Thank you.

Code:
kxld[as.vit9696.AppleALC]: Warning: relocation failed because some class in this kext didn't use the OSDeclareDefaultStructors and OSDefineMetaClassAndStructors, or didn't export all vtable symbols, so it still references IOService::_RESERVEDIOService0(), which has been patched with another symbol for binary compatibility. Please make sure all classes that inherit from OSObject use these macros.
Even thought Acidanthera does not support installation of kexts in /Library/Extensions, Vit9696 has fixed the AppleALC.kext issue that caused the errors I had reported. AppleALC.kext 1.5.5 should no longer have these errors and will install without issues in /Library/Extensions.
 
I would say the Hackintool is the easier way to do this..Nomsayin'?
 
I would say the Hackintool is the easier way to do this..Nomsayin'?

@roboman01,

The use of Hackintool to install kexts in /L/.E is covered in Section 6 of the guide in post #1.

Cheers
Jay
 
@roboman01,

The use of Hackintool to install kexts in /L/.E is covered in Section 6 of the guide in post #1.

Cheers
Jay
Somehow in Big Sur Lilu+NVMeFix in /L/E does not load NVMeFix only Lilu. This is on MacBook Pro without OC. With OC everything loads but installed in /EFI/OC/Kexts
 
I would say the guide is only for pre-macOS 11 with Clover. From macOS 11, /L/E should not be considered for either Clover or OpenCore.
 
I realize this is an old topic, but I have a question. I have read the first 12 pages and cleaned up my kexts as you describe. And things are working fine. But I looked into my /S/E file and find the kexts shown in the attached file. This is on my #3 Hackintosh with the Z370 board. The only ones I had in Other were the ones you talk about, and I really have no idea where all of the others came from. ( bear in mind that I built my first hack at 76, four years ago) How do I determine if I need them?? Thanks for any help
 

Attachments

  • kexts 7:19.jpeg
    kexts 7:19.jpeg
    61.2 KB · Views: 73
I realize this is an old topic, but I have a question. I have read the first 12 pages and cleaned up my kexts as you describe. And things are working fine. But I looked into my /S/E file and find the kexts shown in the attached file. This is on my #3 Hackintosh with the Z370 board. The only ones I had in Other were the ones you talk about, and I really have no idea where all of the others came from. ( bear in mind that I built my first hack at 76, four years ago) How do I determine if I need them?? Thanks for any help
ACS6x.kext
ArcMSR.kext
ATTOCelerityFC8.kext
ATTOExpressSASHBA2.kext
ATTOExpressSASRAID2.kext
CalDigitHDProDrv.kext
HighPointIOP.kext
HighPointRR.kext
PromiseSTEX.kext
SoftRAID.kext
are part of MacOS, you can leave them there, they're generally useless.
As for the rest of them, some are drivers installed by some peripheral (HP, Logitech) or some utility (SoundFlower). It's up to you to know whether you're using them or not. Ideally, you should uninstall them properly, if you don't need them any more, but if you leave them there nothing bad should happen. ;-)
In case of doubt, copy their name and search on the web for their use and origin.

I'm not talking about FakeSMC, Lilu, etc. I guess you know what they are, just check that you haven't got them in both Other AND L/E.
All those "hacking" extensions should be at the same place, so if they are already in Other, delete them from L/E (or the other way around depending on your preferences...)
 
Thanks Nodarkthings for the quick response. I guess the only two that I question are the 200 and 300 XHCI injector kexts. I seem to remember that they were recommended for the orginal installation
 
Yes as long as Lilu + VirtualSMC is installed in /L/E and "Inject Kexts" is set to "Detect" then Clover will not inject Kexts, I use this myself on all my Hacks.




Do not use Finder to copt the kexts, use Hackintool's Install kexts feature, or use the Terminal method as detailed in the guide.




Examine the output of the kextcache command (the last block of red text in hackingtool), or simply execute the command at anytime in terminal :-

Code:
sudo kextcache -i /


Each line will show the path from which the kext was loaded by the kernel.

Cheers
Jay
OK, now I run sudo kextcache -i / and came up with the attached file. Can you explain to me why it says they are all loaded twice? I don't understand this. Thanks
 

Attachments

  • kextload order.txt
    4.8 KB · Views: 83
OK, now I run sudo kextcache -i / and came up with the attached file. Can you explain to me why it says they are all loaded twice? I don't understand this. Thanks
that is fine, they are only loaded the once, although most just keep their 3rd party kexts in their EFI
 
Back
Top