- Joined
- Jan 10, 2012
- Messages
- 5
- Motherboard
- CustoMac Mini
- CPU
- i3 2105
- Graphics
- HD3000
- Mac
- Classic Mac
- Mobile Phone
EFI/Clover/kexts/Other
I cannot get the chown -R command to work, it always comes back with illegal user name.
EFI/Clover/kexts/Other
I cannot get the chown -R command to work, it always comes back with illegal user name.
I just tried this another way, I installed Sierra on a hard drive, then ran the patch script for 10_12_0, removed the IONVMe kext, placed the HACKNVMe kext into the same directory (S/L/E), and An error pops up a short while later that the kext cannot be used, and to contact my vendor.. Any ideas?
You are better off using the KextBeast to install kexts in /S/L/E/ or /L/E/. (See the tonymacx86 Downloads for KextBeast.) Drag/drop the kext to the Desktop. Delete the copy in the /S/L/E/. Run KextBeast and selection the location. KextBeast will change the kext(s) permission to the appropriate permissions and rebuild caches.I just tried this another way, I installed Sierra on a hard drive, then ran the patch script for 10_12_0, removed the IONVMe kext, placed the HACKNVMe kext into the same directory (S/L/E), and An error pops up a short while later that the kext cannot be used, and to contact my vendor.. Any ideas?
diskutil list
sudo kextcache -system-prelinked-kernel
sudo kextcache -system-caches
sudo spctl --master-disable
However, you can put the kext in the /EFI/EFI/Clover/kexts/other/ folder.
Good catch! I've updated the above post with how to clear caches.Please note that Clover will not inject kexts from Clover/kexts if FakeSMC.kext is in kernel cache (eg. FakeSMC.kext was installed to the system volume) and config.plist/SystemParameters/InjectKexts=Detect.
Good catch! I've updated the above post with how to clear caches.
Hmmm. I missed the memo on that item. However, if he used the UniBeast/MultiBeast installation method, FakeSMC is in the /L/E/ folder. But, what does FakeSMC have to do with his moving HACKNVMe kext? I've lost lock on this problem (pilot talk).Rebuilding kernel cache will not help. As long as FakeSMC.kext is installed to the system volume and InjectKexts=Detect, Clover/kexts is ignored.
If you install FakeSMC.kext to the system volume and are using InjectKexts=Detect, all kexts you need must be installed to the system volume.
Hmmm. I missed the memo on that item. However, if he used the UniBeast/MultiBeast installation method, FakeSMC is in the /L/E/ folder. But, what does FakeSMC have to do with his moving HACKNVMe kext? I've lost lock on this problem (pilot talk).