- Jan 16, 2017
- Gigabyte H370N Wifi
- UHD 630
- Mobile Phone
Hi, thanks for replying. I have every intention to utilize Other for kext placement. No kexts have ever been placed in S/L/E, just in LE. Now back to my original question: Why is USBPorts.kext incorrect when placed in E/C/k/O? I was just pointing out that if using LE, the ports were mapped correctly. I will move kexts back to EFI, but I'd like to ensure USBPorts.kext is functioning as expected. Also, I used your New Beginners Guide to create the kext file. Not sure why I posted my original question (last year) in the other (older) guide. Any hints?Nothing is wrong with USBPorts.kext being put in 'Other'. In fact it is safer to use it in EFI/CLOVER/kexts/Other or EFI/OC/Kexts for Catalina and Big Sur.
For a start, no third-party kext should go in S/L/E for Catalina or later. Period. This is because of new kernel protection put in place by Apple.
This guide doesn't use USBPorts.kext. This guide was a slightly older method of configuration, relying on USBInjectAll.kext and and SSDT-UIAC.aml. In the New Beginner's Guide we create and use USBPorts.kext.
The reason for the preference between the techniques is because USBPorts.kext contains no executable code. This is important for the latest macOS's. It is a method of altering the ACPI by loading, or injecting, the changes we need as a kext would. Because it has no executable it does not ring any alarm-bells for Catalina or Big Sur. It doesn't get blocked. If you put it in the EFI location macOS doesn't even get a sniff of it. Run the Terminal command 'kextstat' (when you get it all working) and you will see it is apparently not there.