what can be the reason that clover doesn't load the kext files put into /CLOVER/kexts/Other
I have in my system I try to build, the Network Kext and it doesn't load it / start the NIC.
A kernel extension (kext) will load only if it finds a compatible device. We can run IORegistryExplorer to see if the network device is visible to macOS. If so, IORegistryExplorer will show its DeviceID and VendorID. We can then open the kext in Finder (right-click --> Show Package Contents) and open the info.plist file. If the DeviceID and VendorID of your network device are present, then the kext should load.
If the kext is copied only to CLOVER/kexts/Other and Inject Kexts is set to Detect, then it will not be injected if FakeSMC or VirtualSMC is installed in /Library/Extensions.
In this case, install the network kext in to /Library/Extensions and rebuild kernel cache by running Kext Utility. Then reboot.
Have you upgraded your Asus X99 system to Catalina?
If not, the upgrade is non-trivial, but not too difficult. Having just completed the upgrade, here's a mini-guide:
*** Mini-Guide for Upgrading Asus X99 Deluxe II from Mojave to Catalina ***
Step 1: Make a full bootable backup of Mojave.
Step 2: Make Preparations in Mojave.
Before we can start the Catalina installer, we must make several modifications to the Mojave EFI folder. Don't worry, these modifications are compatible with both Mojave and Catalina.
Login to Mojave and mount EFI partition of the Mojave SSD.
In the CLOVER/kexts/Other folder we must update the following (all of which are available for download from the Acidanthera GitHubsite):
Lilu --> 1.3.9 or newer
WhateverGreen --> 1.3.4 or newer
AppleALC --> 1.4.3 or newer
Delete BrcmPatchRAM2.kext and replace with BrcmPatchRAM3.kext from the Acidanthera BrcmPatchRAM repository on GitHub.
Copy BrcmBluetoothInjector.kext (included in the BrcmPatchRAM download) to the same CLOVER/kexts/Other folder.
Replace BrcmFirmwareData.kext with the latest version (also included in BrcmPatchRAM download).
To make it easier to enter, simply find and replace the entire KernelToPatch section in your config.plist using an editor like BBEdit or PListPro or TextEdit (in Plain Text mode). KernelToPatch entries begin around line 1016: View attachment 434114
Note 1: After we add slide=128, we cannot use this to boot Mojave. If for any reason you must boot back to Mojave, simply remove slide=128. No other changes are needed for Mojave.
Note 2: After entering the KernelToPatch section, be sure to open config.plist in Clover Configurator. If no error message pops up, then it means you made the changes correctly.
Step 3: Begin Catalina Upgrade.
Now you can invoke Catalina Upgrade from the System Preferences --> Software Update. Again, if you need to boot Mojave, remove slide=128.
Thank you for the great upgrade guide CaseySJ. It will certainly come in handy when I upgrade to Catalina. As of now, I have to stay with Mojave due to 32bit plugins for some of my software.
My apologies, but after successfully following this build more than 7 or 8 months ago, I've just forgotten how to do even the basics. As there are now more than 900 pages, I'm daunted by getting back up to speed. The issue I'm having is that I can't update from the original 10.14.3 to 10.14.6. It downloads the updater and reboots and goes clover with a ton of options (I have clones of my OS, just in case) but then when I pick "boot MacOS Mojave" it just boots back up and ignores the 10.14.6 upgrade. I can see the "install MacOS data" folder on the root, but it doesn't try to upgrade.
Can anyone point me to a simple step by step for this? Do I need to update clover (I couldn't even remember how to do that...)
Again, apologies for the simpleton here, but any directions would be appreciated.
Issue is no sleep. Everything else works. Had decided I didn’t care if sleep didn’t work.
Set monitor to turn off at 15 minutes and cleared everything else in energy saving except power nap. Why I left power nap on I can’t remember.
It sleeps, wakes, and sleeps again properly.
I don’t know why.
It looks like the files were in fact copied from source EFI to destination EFI, but the checksums of the source and destination directories mismatched at the end.
Please check manually whether the source and destination EFI folders appear to be identical.
I have an event to attend today so replies will be delayed.
My apologies, but after successfully following this build more than 7 or 8 months ago, I've just forgotten how to do even the basics. As there are now more than 900 pages, I'm daunted by getting back up to speed. The issue I'm having is that I can't update from the original 10.14.3 to 10.14.6. It downloads the updater and reboots and goes clover with a ton of options (I have clones of my OS, just in case) but then when I pick "boot MacOS Mojave" it just boots back up and ignores the 10.14.6 upgrade. I can see the "install MacOS data" folder on the root, but it doesn't try to upgrade.
Can anyone point me to a simple step by step for this? Do I need to update clover (I couldn't even remember how to do that...)
Again, apologies for the simpleton here, but any directions would be appreciated.
Mac'os mojave 10.14.5 is OuT (Build 18F132) AMD Vega Cards Working OOB without fan speed problems ;) Mojave 10.14.4 Port Limit Removal Patch not working any more
Alright! I've finally pulled the trigger and I'll cross fingers that I'm able to make it run correctly. Here's the components
- Motherboard: Asus Prime Z370-A II (because I need the Thunderbolt 3 header)
- CPU: i9-9900k
- RAM: 2x16GB 3200mhz HyperX Predator
- GPU: Sapphire RX 5700 8GB GDDR6
- SSD: 2x Sabrent Rocket 1TB (one for backup)
- Cooler: Bequiet Dark Rock 4 Pro
- Thunderbolt: Gigabyte Titan Ridge
Thanks so much for all the help and knowledge @CaseySJ and many other users share. Did you created by any chance a mini-guide on how to do your own SSDT (or DSDT?) to enable hot-plug on the Titan Ridge?. I'm not entirely sure how I can do it once I got it installed on my motherboard.
Not sure when did this happen, my Catalina drive is read-only now, unable to create new folder and drop the files. I try to change permission from drive info, but doesn't work, please show me the trick how to enable it.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
