A: Start with reading this wiki.
A: Don't be a fool.
PS: What else can be said here!?
A: The loading of an OS is divided into 8 steps, see Technical Background. Try to specify when exactly the process stops and which options were used for installation - then we can talk. Popular mistakes are:
PatchVBiosresults in a black screen. Try turning it off.
For a better analysis of what is happening, enable
DebugLog in section
GUI as follows.
Loading will be happening very slowly, becauseEFI/CLOVER/misc/debug.log will be updated at each step , but later you'll get the final information of the hang and see exactly what happened.
A: One of the possible reason is wrong partition File System. PBR sector boot1f32 requires namely FAT32 but not FAT16 or ExFAT. If you are not sure then it is recommended to reformat your partition with command
newfs_msdos -v EFI -F 32 /dev/rdisk0s1
A: This is the worst case of hardware incompatibility. Nowadays it does not appear anymore. Only a developer can help here by debugging the boot process in small steps. Normal users sadly cannot do anything, except trying to change BIOS settings or using the file boot7 instead of boot.
A: This means that the boot file was successfully loaded and is working but it cannot find the file CloverX64.efi. Either the according partition is not found or the whole device. Explore the options and try to figure out what is wrong.
A: With early versions of Intel's SATA drivers, HDD needed to be connected to the first SATA port(SATA 0). Furthermore, it is understandable that, even though already using a good well-working Chameleon, Chimera or XPC, you want to try Clover without removing them. It's possible to install both your old boot loader and Clover simultaneously and then the problem will be solved. And try to use the file boot7 if you have an uncommon SATA/SAS/RAID controller.
A: That's because you did not install the HFS+ driver
HFSPlus.efi or its legal alternative
A: Same reason as above. You are missing the NTFS.efi driver in this case.
PS: Both of these drivers cannot be found in the repository due to software license issues. This problem will occur if you do not use the installer and try to do everything by yourself.
A: At this moment the DSDT patch with the desired mask is applied. Ideally it should not hang here. The problem is that the vendor does not follow specifications, cannot program correctly or does not want to adapt the DSDT to OSX requirements. This can be verified in a simple way: by decompiling and compiling the DSDT - if it does not work, then the DSDT is faulty. Clover wants to correct this but sadly there are simply too many possible errors and all of them cannot be covered. You will need to choose a DSDT mask that loads the OS and afterwards one that does not crash the OS, and finally one that enables the OS to work. Alternatively disable automatic patching with
0x0000 and fix the DSDT by yourself.
A: This indicated a missing or incorrect DSDT. If automatic patching fails, add your own, manually customised, DSDT.
A: Your UEFI variant does not work natively with Clover. Use one of the available drivers to fix your EFI memory map.
A: Apart from the standard tip to turn on AHCI mode in BIOS, if it does not exist, find a matching kext for your IDE controller. Or you can try booting with the key
NoCaches. Loading will be slowed down because the controller needs more time to be initialised.
This issue arises only when Clover and the OS are on different devices.
A: Your FakeSMC is missing. If you use Chameleon, FakeSMC might be in the Extra folder. But Clover does not know such a folder. Instead, use the folder EFI/Clover/kexts/10.x.
A: This is a typical situation when the video card is not initialized. Try enabling or disabling
Graphics of your config.plist.
AMD Radeon cards will be initialized natively when
Graphics disabled, which will get you into the OS with some limitations, such as a non-working DVD Player app. For a fully working card, you will need to modify the framebuffer of your AMD Radeon card.
In other cases you can try booting in safe mode to use VESA mode and correct some things.
A: This is purely cosmetic and does not affect any functionality.
Name (_SUN, 0x2A)to them. SUN is the Slot User Number, can be chosen freely -
0x2Ain this case - and will be displayed in System Profiler.
Last edited by Kuming Aoba, 2015-04-29 06:15:24