What the New Quirks Keys in mackie100 projects Changelogs Refer To
Updated
The three keys added in Clover Configurator 5.29.0.0 — ClearTaskSwitchBit, DisableIoMapperMapping, and ResizeGpuBars — are advanced boot-configuration options that sit in the Quirks section of a Clover setup. Each belongs to a different Quirks category: Booter, Kernel, and UEFI respectively. They are low-level switches that change how the bootloader hands hardware and memory behavior to macOS, and they only matter if you are building or maintaining a Hackintosh-style boot configuration. The changelog lists the keys and their locations but does not explain what they do, so the practical meaning has to come from the corresponding bootloader documentation.
Where the keys sit in the configuration
Quirks are grouped by the boot stage they affect, and the changelog places each new key in one of those groups:
| Key | Quirks category | Stage affected |
|---|---|---|
ClearTaskSwitchBit |
Booter | Early boot / firmware handoff |
DisableIoMapperMapping |
Kernel | Kernel and memory mapping |
ResizeGpuBars |
UEFI | UEFI firmware and PCIe device setup |
This grouping is the main clue to what each key touches. A Booter quirk changes behavior before the kernel takes over; a Kernel quirk changes how the kernel sees memory or devices; a UEFI quirk changes what the firmware exposes to the OS.
Booter: ClearTaskSwitchBit
A Booter-stage quirk affects the transition from firmware to the macOS kernel. The name refers to a task-switch control bit, which is a CPU/firmware-level flag rather than a user-facing macOS setting. In practice, keys like this exist to work around firmware or CPU behavior that would otherwise interfere with booting. Treat it as a compatibility switch: you enable it only when a specific boot problem points to it, not as a default.
Kernel: DisableIoMapperMapping
This key sits in the Kernel Quirks group, which governs how the kernel maps memory and devices. The name points to I/O mapper mapping — the translation layer between devices and memory. Disabling that mapping is the kind of change made to avoid conflicts on certain hardware, and it can carry side effects for device access. It is an advanced option, not something to toggle without a documented reason.
UEFI: ResizeGpuBars
This is a UEFI-stage quirk, so it changes what the firmware presents to the OS before macOS starts. "GPU BARs" refers to Base Address Registers — the memory windows a PCIe device such as a graphics card exposes. Resizing them changes how much address space the GPU is given. This is relevant when a GPU's default BAR sizing causes problems, and it depends on both the firmware and the card supporting the change.
How to use these entries
The changelog is a release note, not a manual. To act on it:
- Confirm you are on Clover Configurator 5.29.0.0 or later, since earlier versions will not show these keys.
- Open the Quirks section and locate the matching category (Booter, Kernel, or UEFI).
- Read the bootloader's own documentation for that key before changing it — the changelog gives the name and location only.
- Change one key at a time and verify boot behavior after each change, so you can tell which switch caused an effect.
The expected result of a correct change is that a specific boot or hardware issue disappears; if nothing changes, the key was probably not the cause and should be reverted.
What the changelog does and does not tell you
The page evidence confirms the version, date (April 21, 2026), the three key names, and their Quirks categories. It does not describe the effect of each key, the hardware it targets, or recommended values. Those details belong to the bootloader documentation the keys originate from, and the site's own framing — Clover, OpenCore, bootloader, UEFI, Hackintosh — shows these are customization tools for advanced users rather than general macOS settings.
A useful way to read the entry: it is a signal that the configurator now exposes three more advanced switches, grouped by boot stage. Whether you need any of them depends on a concrete problem you are troubleshooting, not on the fact that they were added.