So doe s that mean that our kext now no longer get included in kextcache ?
Yes.
There has been a lot of discussion about this over the years but now Apple are reducing our options as we go forward. Nothing about Hackintoshing is "official" but this is the best way from now on.
You may have to simplify your method of dealing with kexts. The latest version of Clover and third-party kexts should work for both of Mojave and Catalina, as r5102 worked well for my H61 build in February, even back to High Sierra (now Catalina however). r4770 should be a bit outdated nowadays.
I have written a shell script that will remove the MultiBeast installed kexts from /Library/Extensions.
Download and unzip the attached file. Then in Terminal cd to the directory that contains the unzipped file.
Usage example:
sudo ./Beast-Clean.sh "Test APFS"
"Test APFS" is a test volume of mine. Replace with your volume name.
The path to what? If you mean the path to the downloaded script, it's in your Download folder. Here's an easy, one command line method.can you provide a screenshot of your Finder and the path? I’m a bit confused what the volume should be.
$ cd ~/Downloads/
$ sudo ./Beast-Clean.sh "Macintosh HD"
The path to what? If you mean the path to the downloaded script, it's in your Download folder. Here's an easy, one command line method.
- Open up the Terminal. In the Terminal window, type "sudo " (space after the sudo command). Don't hit Return yet!- Open a Finder window for your Download folder, unzip the download by double clicking on it.- Now, just highlight the "Beast-Clean.sh" script. Then drag and drop it into the Terminal window. Add a space to the end of the command.- Add your macOS drive to the end of the script command in Quotes. My drive is named Macintosh HD, so I would have "Macintosh HD" in quotes.- Now press Return.- Enter your password at the prompt.
This is what the Terminal window would look like if I was using the script after I unzip the downloaded file:
Code:$ cd ~/Downloads/ $ sudo ./Beast-Clean.sh "Macintosh HD"
I also have a Haswell processor Hack, 4790K with 10.14. Works great. Not much reason to upgrade, hardly anything is CPU intensive and the gains in CPU speed haven't been that dramatic.Sorry for being unclear. I’m on that recent Clover r5102, after a bad experience with a different install of Clover r5105 I found somewhere that really messed up my system. (Moral of the story: just stick with tonymac configurations, and don’t update Clover on a perfectly good system.) The 4770 I was referring to was my i7-4770 processor, vintage mid-2014, which is otherwise still entirely acceptable.
It depends on how Clover or OpenCore handle in future versions of macOS. At least kexts inside the EFI partition don’t pop up a warning dialog in 10.15.4.
So in a future macOS, when legacy kexts are blocked, they will still load properly if they are in the Clover folder? So not really blocked?