Slice is glad to present a new EFI bootloader. CLOVER Now version 2 rEFIt based.
It is open source based on different projects: Chameleon, rEFIt, XNU, VirtualBox. The main is EDK2 latest revision. I also want to thank all who help Slice with the development. Credits and copyrights remain in the sources. http://cloverefiboot.sourceforge.net/
If you have a question please provide outputs from DarwinDumper (formed from Trauma tool). Thanks Trauma! Continued by blackosx and STLVNUB.
How to do UEFI boot
How to use - common words
Calculator for Automatic DSDT fix
Instructions for GraphicsInjector
Any kexts patching with some Samples
Hiding unnecessary menu entries
Instruction for DSDT corrections to do DeviceInjection works
About kexts injection
Instructions for P- and C-states generator
Patching DSDT to get Sleep working
CPU settings and geekbench
ACPI tables loading
How to make orange icons to be metallic
How to make software RAID (by Magnifico)
How to modify InstallESD.dmg (by shiecldk)
Using extra kexts and skipping kernelcache
Choosing EFI drivers
Automatic config.plist creating
Custom DSDT patches
How to do sleep/wake working with UEFI BOOT
DeviceID substitution (FakeID)
Using Custom OS Icons
Error allocating pages while starting OS
So at boot you will have two options: boot macOS Mojave or Windows 10
STEP 2 - Using a drive without Windows 10 installed
Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
Proceed with a Windows 10 UEFI install.
After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover.
If Windows 10 is not detected or able to boot, then verify you installed Windows 10 as UEFI and not MBR ----> ( Read step 2 - For a drive with Windows 10 installed )
STEP 2 - Using a drive with Windows 10 already installed
Verify your Windows install is GPT / UEFI or MBR / Legacy BIOS.
If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen.
But if Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
then this is most likely because Windows drive is MBR ( Legacy BIOS ). You can easily convert MBR to GPT using Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again )
If Windows 10 install is MBR / Legacy BIOS then simply convert to GPT / UEFI following instructions below ( read video summary and view video )
** To use Windows 10 MBR2GPT tool you must have Windows 10 version 1703 ( creators update ) or later and less than 3 partitions on
the Windows 10 drive **
Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management )
Reboot into Windows PE ( Advanced Startup )
Convert from MBR Legacy BIOS to GPT UEFI ( using commands below )
Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )
After conversion Windows 10 is ready to use at the Clover boot menu
STEP 3 - Stop Windows Boot manager from overriding Clover boot manager
How to stop Windows boot manager from overriding your Hackintosh Clover boot manager when using dual booting between macOS and Windows
As I have 3 Monitors connected, my RX 570 gets arround 50°C while ideling/ web browsing etc. The problem is, that this temp is apparently just the threshold, when the fans start to spin. So the fans start spinning for a minute then they stop for a while again... This is very annoying for me as the rest of my hackintosh is nearly quiet (SSD, 120mm low RPM cpu fan, nearly silent PSU,...), especially when Im using the pc to revise for school. Does somebody know wether its possible to "change" the threshold till the fans start spinning? Like it would probably not be a problem for the gpu at all, if the temp rises to 55°C but therefore be soundless....
So I'm finally joining the grown-ups and trying to set up a new(ish) hack. In the past I've used legacy Clover with my old Gigabyte board and thought I knew what I was doing. But I've been trying to get a UEFI Clover-based install to work and it's going nowhere.
My new system (listed as SysB in sig) is a Gigabyte Z97X-UD3H-BK rev1.1 with firmware F6, an i7 4790K CPU and 4x4GB Corsair 1866MHz. I have the firmware settings set as per various guides and thought this should be a pretty painless transition...
I have successfully run the installer for El Cap several times, but can't get the machine to boot reliably - it seems to change behaviour each boot. Sometimes boot hangs at the Gigabyte logo after choosing boot volume via F12, sometimes it boots to clover but displays no bootable drives, sometimes displays ElCap SSD in Clover but wont boot from it with kernel cache error, and occasionally it will boot all the way.
What I'd like to know is:
Should I update the mobo firmware to the latest version? This board has two more recent Bios software downloads, but they wont allow me to drop back to the version currently installed. I'm nervous to update unless this is likely to be the culprit.
Is this just a UEFI issue? If the simple answer is just go legacy mode, maybe I should just avoid the issue...
FInally, does anyone else have a working clover install on this board they could share with me? I think I've got it set up as it should be but the strange inconsistent boot behaviour makes me wonder...