Clover Configurator Boot Tab: Every Setting on Page 6 Explained for Legacy Hackintoshes

The Boot tab in Clover Configurator (Page 6) is where many Hackintosh builders dump -v and kext-dev-mode=1 without a second thought. But for legacy builds targeting macOS 10.6 through 10.13, the fields on this page control everything from NVRAM emulation to sleep/wake behavior. Here's what each setting actually does and which ones are safe to tweak.

Anatomy of the Boot Tab

Clover Configurator’s “Boot” section (Page 6 in the sidebar) splits into three sub-sections: Arguments, Flags, and Options. The exact layout depends on the configurator version (v4.x or v5.x), but the underlying plist keys stay the same across Clover revisions r3000–r5100.

Boot Arguments

The free-text box under Boot Arguments accepts space-separated kernel flags. While -v (verbose) and debug=0x100 are common, less obvious entries like UIScale=2 (for HiDPI on older GPUs) or darkwake=0 (to prevent wake failures on Ivy Bridge) are frequently omitted. The following table lists the most relevant arguments for legacy macOS builds:

When building a new installation USB, start with only -v and kext-dev-mode=1 (if applicable) and gradually add flags as errors appear. Overloading the argument list with unnecessary flags can mask real issues.

Boot Flags – The Hidden Toggles

Below the argument box, Clover Configurator presents a series of checkboxes and radio buttons. Many of these map directly to boolean keys in the plist:

• Fast – Enables the “Fast Boot” option on newer firmware; generally safe to leave unchecked on legacy hardware as it can cause early USB detection failures.
• Neverhibernate – Prevents Clover from scanning for hibernation files. Useful for machines that resume from S3 but never require hibernation wake.
• XMPDetection – When disabled, Clover skips parsing XMP memory profiles. On some X79 boards this avoids a boot hang during memory initialization.
• NoEarlyProgress – Suppresses the Clover progress bar. Rarely needed, but can improve stability on certain Gigabyte Z77 boards.
• Legacy – Controls the boot mode for older operating systems. For macOS 10.6, set to “Legacy” (GRUB) or “LegacyBooter” depending on the SmBios.

One of the most misunderstood checkboxes is “Inject System ID”. When enabled, Clover injects a random UUID into the IORegistry. This is harmless for most users, but if you rely on a fixed network UUID (e.g., for Ethernet MAC-based licensing), disable it and manually set a custom SystemID in the SMBIOS section.

Why Page 6 Matters for Sleep and Wake

Sleep/wake failures on legacy Hackintoshes are often traced back to missing or conflicting boot arguments. The darkwake flag, originally introduced in Mountain Lion, is the most common fix. However, many users overlook the Wake sub-options located at the bottom of Page 6. The “HibernationFixup” kext alone is not always sufficient; the boot flag hibernatemode=0 (set in the arguments field) must match the value written to nvram. If you are using a Clover build without native NVRAM emulation, it is critical to enable “NVRAM” in the System Parameters page (Page 12) and verify that EmitStrings is checked.

For a deeper dive into diagnosing sleep issues, the IORegistryExplorer 3: The Essential Tool for Debugging Legacy Hackintoshes article explains how to locate the IODeviceTree:/efi/platform entries that Clover modifies. A mismatch between the wake-type property and the boot argument often results in a black screen after resume.

Boot Arguments and Graphics Injection

On Page 6, the “Graphics” sub-section (visible only after selecting the “Boot” tab in some Configurator versions) contains two crucial flags: “InjectIntel” and “InjectNvidia”. These are remnants of the GraphicsEnabler era. For Sandy Bridge HD 3000 (10.6–10.8), enabling InjectIntel with the correct ig-platform-id in the Devices section is necessary. For Kepler and older NVIDIA cards (GTX 600–900), the InjectNvidia flag set to Yes can replace the need for NvidiaGraphicsFixup.kext on 10.12 and earlier – but it is not recommended for 10.13 because Apple’s built-in drivers already handle those cards.

Risks of Misconfiguring Page 6

Changing boot arguments can cause a boot loop that is particularly difficult to recover from on systems without native NVRAM. If you accidentally set nv_disable=1 (disables NVIDIA acceleration) and your system requires it, the next boot will produce a grey screen. To recover, you must either edit the plist from another OS (e.g., a Linux live USB) or use the Clover boot menu’s options (press O on the boot entry) to manually override the boot arguments for that single session. Always keep a backup of your config.plist before editing the Boot section. A simple copy-paste of the plist file to a FAT32 USB drive is sufficient.

Another common pitfall: the timeout value on Page 6 should be set to 5 (seconds) for most builds. Setting it to 0 disables the boot menu, which makes it impossible to enter verbose mode or select a different boot device if the system fails. For testing new kernels, a timeout of 10 is safer.

Page 6 and Legacy Storage Controllers

When booting from older SATA or IDE drives, the Legacy boot mode drop-down on Page 6 must match the controller’s firmware. For PATA (IDE) drives connected via a JMicron chipset, “Legacy” (PBr) is the only reliable setting. For AHCI SATA, “LegacyBooter” (boot.efi) is preferred. The article Legacy Hackintosh Storage: SATA, IDE, and NVMe Compatibility Guide provides a complete compatibility matrix for each chipset generation.

Final Practical Note: Testing a New Boot Argument

Instead of editing the config.plist directly, use Clover Configurator’s “Boot” tab to add the argument, save the plist, and then reboot. If the system hangs, use the Options menu at the Clover boot selection screen (press O) to revert the Boot Args field to your previous working set. This non-destructive test is the only way to safely validate a new flag on a production system. Once confirmed, commit the change to the plist file.