![]() VirtualSMC.kext - Emulates the SMC chip on real macs. ![]() Most of the Kexts are available from the following repos: Goldfish64 Repo Once the following kexts have been downloaded and unzipped, I copy them directly into the /EFI/Clover/kexts/Other within the EFI partition of the boot loader drive that was prepared by Clover Builder. Personally, I prefer to install my kexts manually directly into the EFI partitions' /EFI/Clover/kexts folder. **NOTE: Clover configurator has a Kext Installer that we will look at. I’m only going to start with the bare essentials, because of the purpose is the keep the system running as close to a real Mac and lean as possible. ![]() We are going to begin by gathering kexts for the Hackintosh. In the vanilla method, all of your kexts are stored in /EFI/Clover/kexts folder which is inside of the hidden EFI partition, completely separate from the rest of the OS. A key thing to remember here is that normal Macs also use Kexts, and these are saved in /System/Library/Extensions by default.īut in our hackintosh, all of the modified kexts that we introduce, will be housed in the EFI partition maintained completely separately from the kexts that typically belong to MacOS. When you want to uninstall a kext all you have to do is remove it ( Source. It’s like having drivers contained in a single file without having to install them like on Windows. When you boot up your machine the code contained in these kexts is automatically injected into the operating system, after the UEFI drivers get injected. The word “Kext” is short for Kernel Extension. Kext files are basically the drivers for macOS. Then there are another set of configuration information called Kexts. In other words, UEFI drivers are the first drivers to be fed into the MacOS from the EFI partition as the system is starting. These are important drivers that get loaded before even MacOS is loaded into the system. UEFI Drivers and KextsĮarlier, we installed the UEFI drivers. VirtualSMC-64.efi : This is an automatic addition from the VirtualSMC kext. NTFS-64.efi : This enables the boot loader to see NTFS. It appears its function is to block files from being loaded and to inject files from pre-exit boot services for the kernel. I added three more drivers to enable various functions.įSInject.efi : This was added automatically during installation so I never deleted it. Alternatively, if you see VBoxHfs-64, it does the same thing. If you can’t see HFSPlus, don’t worry about it. HFSPlus.efi (or VBoxHfs-64.efi) : These are required for Clover to see and boot from HFS+ volumes.If AptioMemoryFix-64 gives you trouble, try one of these, but don't assume one is better than the other. There are several other alternate drivers including OsxAptioFixDrv.efi, OsxAptioFixDrv2.efi, OsxAptioFixDrv3.efi - these are not newer versions of the other, but rather three separate variants. For my motherboard, I had no issues with this alone, but as I was tinkering with other boards such as a the Gigabyte Z390 I found that this caused problems. AptioMemoryFix-64 : This includes fixes for NVRAM and better memory management.Usually in conjunction with AptioMemoryFix-64. APfsDriverLoader-64 : This allows the boot loader (Clover) to see and boot from APFS volumes by loading APFS.efi.You can begin by selecting 3 UEFI drivers as discussed below.įor Simplicity sake, to start off with, I will be only running 3 UEFI drivers: Under UEFI Drivers chose the following options:.Remember to check the "Clover for UEFI booting only" This will enable you to select the following option in your installation. Once you get to the destination select, remember to choose the USB drive and not the default hard drive/SSD. ![]()
0 Comments
Leave a Reply. |