Clover General discussion

verdazil · February 5

10 minutes ago, SevenTheAppleKitty said:

The USB allergy isn't an issue with OS X but rather the BIOS of the machine I'm installing to

If you use a flash drive with a Windows or Linux installer, do you experience the same problems?

LockDown · February 5

It could be CSM

nevermind... I didnt notice your sig

Edited February 5 by LockDown

Matgen84 · February 5

13 hours ago, SevenTheAppleKitty said:

is it possible to install from DVD? it appears the laptop I'm trying to hackintosh is allergic to booting with a USB drive plugged in

@SevenTheAppleKitty According to laptop hardware (Legacy Core 2 Duo), I don't think (just my opinion) installation of modern macOS is possible !!!

SevenTheAppleKitty · February 6

20 hours ago, verdazil said:

If you use a flash drive with a Windows or Linux installer, do you experience the same problems?

iMade a debian installer USB, and it seemed to not mind this time..? I guess it just really doesn't like certain USBs sometimes because I swear I had this issue on a different OS

11 hours ago, Matgen84 said:

@SevenTheAppleKitty According to laptop hardware (Legacy Core 2 Duo), I don't think (just my opinion) installation of modern macOS is possible !!!

I'm planning to install 10.7 Lion in specific, so I think I'll be fine (even if I think i'll lack wifi drivers...)

verdazil · February 6

2 hours ago, SevenTheAppleKitty said:

iMade a debian installer USB, and it seemed to not mind this time..? I guess it just really doesn't like certain USBs sometimes because I swear I had this issue on a different OS

This looks more like a misconfigured bootloader.

Max.1974 · February 9

Very Nice my friend ! Thanks

MakAsrock · February 10

Release-5168

Spoiler

📌 Summary:

This Release replaces the hardcoded BlockSkywalk option with a fully extensible, menu-integrated, and OS-aware mechanism called KextsToBlock.
It also includes upstream synchronization from brunch master and improvements to CPU/SMBIOS detection.

✨ Key Features:

🔹 1. New KextsToBlock system

Replaces the single-purpose BlockSkywalk flag.
Supports multiple kexts.
Each entry can be:
Enabled/disabled,
Filtered by macOS version (MatchOS),
Toggled via Clover UI menu,
Exported correctly to OpenCore Kernel -> Block.
🔹 2. Menu integration

New submenu “Kexts to block”.
Each rule appears as a checkbox item.
Menu state is synced back into runtime config.
🔹 3. Config format update

Removed:

   <dict>
        <key>KernelAndKextPatches</key>
        <dict>
            <key>BlockSkywalk</key>
            <true/>
        </dict>
    </dict>

Added:

            <key>KextsToBlock</key>
            <array>
                <dict>
                    <key>Comment</key>
                    <string>Allow IOSkywalk Downgrade</string>
                    <key>Disabled</key>
                    <false/>
                    <key>MatchOS</key>
                    <string>14.x,15.x,26.x</string>
                    <key>Name</key>
                    <string>com.apple.iokit.IOSkywalkFamily</string>
                </dict>
                <dict>
                    <key>Comment</key>
                    <string>Allow Block AppleEthernetRL</string>
                    <key>Disabled</key>
                    <true/>
                    <key>MatchOS</key>
                    <string>26.x</string>
                    <key>Name</key>
                    <string>com.apple.driver.AppleEthernetRL</string>
                </dict>
            </array>

Introduced new class: KEXT_TO_BLOCK
Fields: Comment, Name, Disabled, MatchOS, MenuItem, Label
Method: ShouldBlock(const MacOsVersion&)
Added filtering logic in:

LOADER_ENTRY::FilterKextsToBlock();

Clover config generation dynamically builds Kernel -> Block entries based on active rules.
Removed all traces of BlockSkywalk from structures, config parsing, menu, and OC export logic.

Includes:

Updated CPU detection:
Added: Nehalem EX, Westmere, Raptor Lake, Meteor Lake, Arrow Lake.
Improved SMBIOS selection:
i9 → iMac20,2
Comet/Rocket Lake → iMac20,1
New Intel → MacPro7,1
MacPro7,1 enhancements:
ECC enabled,
Max RAM increased to 1.5 TB,
Correct slot layout.
Cleaned comments and minor logic refinements.

🧠 Why this matters

Removes hardcoded behavior.
Makes kext blocking scalable, configurable, and future-proof.
Aligns Clover with OpenCore’s flexible kernel blocking model.
Improves maintainability and UI consistency.

✅ Compatibility

Existing configs using BlockSkywalk continue to work via migration to KextsToBlock.

No behavior change for users unless they opt to add new block rules.

You can download it from my GitHub repository.

Spoiler

Edited February 12 by MakAsrock

carlo_67 · February 10

thanks Mario 🤔

LockDown · February 11

@MakAsrock

It works 👍

On thing though... the release version does not have your KextsToBlock. Artifact has it

MakAsrock · February 11

24 minutes ago, LockDown said:

@MakAsrock

It works 👍

On thing though... the release version does not have your KextsToBlock. Artifact has it

For some reason, config-sample.plist wasn't added during compilation. 🙁 Now everything is in place. 🙂

Edited February 11 by MakAsrock

LockDown · February 11

Perfect👍

Thanks @MakAsrock

jlrycm · February 12

On 2/10/2026 at 11:01 AM, MakAsrock said:
Release-5168
Reveal hidden contents
📌 Summary:

This Release replaces the hardcoded BlockSkywalk option with a fully extensible, menu-integrated, and OS-aware mechanism called KextsToBlock.
It also includes upstream synchronization from brunch master and improvements to CPU/SMBIOS detection.

✨ Key Features:

🔹 1. New KextsToBlock system

Replaces the single-purpose BlockSkywalk flag.
Supports multiple kexts.
Each entry can be:
Enabled/disabled,
Filtered by macOS version (MatchOS),
Toggled via Clover UI menu,
Exported correctly to OpenCore Kernel -> Block.
🔹 2. Menu integration

New submenu “Kexts to block”.
Each rule appears as a checkbox item.
Menu state is synced back into runtime config.
🔹 3. Config format update

Removed:
   <dict>
        <key>KernelAndKextPatches</key>
        <dict>
            <key>BlockSkywalk</key>
            <true/>
        </dict>
    </dict>
Added:
            <key>KextsToBlock</key>
            <array>
                <dict>
                    <key>Comment</key>
                    <string>Allow IOSkywalk Downgrade</string>
                    <key>Disabled</key>
                    <false/>
                    <key>MatchOS</key>
                    <string>14.x,15.x,26.x</string>
                    <key>Name</key>
                    <string>com.apple.iokit.IOSkywalkFamily</string>
                </dict>
                <dict>
                    <key>Comment</key>
                    <string>Allow Block AppleEthernetRL</string>
                    <key>Disabled</key>
                    <true/>
                    <key>MatchOS</key>
                    <string>26.x</string>
                    <key>Name</key>
                    <string>com.apple.driver.AppleEthernetRL</string>
                </dict>
            </array>
Introduced new class: KEXT_TO_BLOCK
Fields: Comment, Name, Disabled, MatchOS, MenuItem, Label
Method: ShouldBlock(const MacOsVersion&)
Added filtering logic in:
LOADER_ENTRY::FilterKextsToBlock();
Clover config generation dynamically builds Kernel -> Block entries based on active rules.
Removed all traces of BlockSkywalk from structures, config parsing, menu, and OC export logic.

Includes:

Updated CPU detection:
Added: Nehalem EX, Westmere, Raptor Lake, Meteor Lake, Arrow Lake.
Improved SMBIOS selection:
i9 → iMac20,2
Comet/Rocket Lake → iMac20,1
New Intel → MacPro7,1
MacPro7,1 enhancements:
ECC enabled,
Max RAM increased to 1.5 TB,
Correct slot layout.
Cleaned comments and minor logic refinements.

🧠 Why this matters

Removes hardcoded behavior.
Makes kext blocking scalable, configurable, and future-proof.
Aligns Clover with OpenCore’s flexible kernel blocking model.
Improves maintainability and UI consistency.

✅ Compatibility

Existing configs using BlockSkywalk continue to work via migration to KextsToBlock.

No behavior change for users unless they opt to add new block rules.
You can download it from my GitHub repository.

Reveal hidden contents

@MakAsrock I loaded macOS 26.3 using the latest clover commit which includes the MacPro 7,1 memory fix and now it looks like the memory diagram when loading OpenCore and clicking on more info next to the memory. However, I get a message saying that I installed more than the maximum allowed which is not accurate. I would share here my clover config.plist so that you can take a look at it and see if there is something preventing me from seeing the memory diagram free of errors like in OpenCore.

Slice · February 12

@MakAsrock, @Hnanoto

I am waiting you in the thread

MakAsrock · February 12

8 hours ago, jlrycm said:

@MakAsrock I loaded macOS 26.3 using the latest clover commit which includes the MacPro 7,1 memory fix and now it looks like the memory diagram when loading OpenCore and clicking on more info next to the memory. However, I get a message saying that I installed more than the maximum allowed which is not accurate. I would share here my clover config.plist so that you can take a look at it and see if there is something preventing me from seeing the memory diagram free of errors like in OpenCore.

You need to use the RestrictEvents.kext to remove this warning.
And in the boot arguments, evpatch=memtab,sbvmm,cpuname,ctrsmt revcpu=1 ctrsmt=full and whatever else you usually add next.
My fix only addresses the incorrect memory slot order display on Mac Pro 7.1 models because I don't know how it might affect other models.
Previously, the slot rotation was not displayed correctly.
I don't have a fleet of computers to test this with other SMBOS. 🙂

Edited February 12 by MakAsrock

jlrycm · February 12

1 hour ago, MakAsrock said:

You need to use the RestrictEvents.kext to remove this warning.
And in the boot arguments, evpatch=memtab,sbvmm,cpuname,ctrsmt revcpu=1 ctrsmt=full and whatever else you usually add next.
My fix only addresses the incorrect memory slot order display on Mac Pro 7.1 models because I don't know how it might affect other models.
Previously, the slot rotation was not displayed correctly.
I don't have a fleet of computers to test this with other SMBOS. 🙂

Let me check as I don’t remember well my RestrictedEvents boot args defined in clover.

MakAsrock · February 12

4 hours ago, jlrycm said:

Let me check as I don’t remember well my RestrictedEvents boot args defined in clover.

For my Hack Pro7.1, the arguments for Tahoe are:

amfi=0x80 ipc_control_port_options=0 revpatch=memtab,pci,sbvmm,cpuname revcpu=1 ctrsmt=full

For Ventura are:

revpatch=memtab,pci,sbvmm,cpuname revcpu=1 ctrsmt=full

MakAsrock · February 13

I ran into a problem on GitHub. I had the “Enable release immutability” option enabled, which disallows modifying assets and tags once a release is published.

I didn’t notice this at first, and when I tried to update the release with tag 5168, I wasn’t able to do so. As a result, this tag became unusable.

The release is now published as 5169 instead.

Should I change the tag to 5168.1, or leave everything as it is?

I apologize for the confusion and any inconvenience this may have caused. Thank you for your understanding.

Matgen84 · February 13

1 hour ago, MakAsrock said:

I ran into a problem on GitHub. I had the “Enable release immutability” option enabled, which disallows modifying assets and tags once a release is published.

I didn’t notice this at first, and when I tried to update the release with tag 5168, I wasn’t able to do so. As a result, this tag became unusable.

The release is now published as 5169 instead.

Should I change the tag to 5168.1, or leave everything as it is?

I apologize for the confusion and any inconvenience this may have caused. Thank you for your understanding.

Hi @MakAsrock Since end of October, Immutable releases are now generally available. GitHub release page with "enable release immutability" checked. (Source GitHub). "Under your repository name, click Settings. If you cannot see the "Settings" tab, select the dropdown menu, then click Settings. Scroll down to the "Releases" section, then select Enable release immutability." Just my opinion, 5168.1 is better than 5169, in this case.

Sorry for OFF-TOPIC !

Edited February 13 by Matgen84

MakAsrock · February 13

47 minutes ago, Matgen84 said:

Hi @MakAsrock Since end of October, Immutable releases are now generally available. GitHub release page with "enable release immutability" checked. (Source GitHub). "Under your repository name, click Settings. If you cannot see the "Settings" tab, select the dropdown menu, then click Settings. Scroll down to the "Releases" section, then select Enable release immutability." Just my opinion, 5168.1 is better than 5169, in this case.

Sorry for OFF-TOPIC !

I removed the Enable release immutability setting, but the phantom tag remained.
I apologize if this is off-topic. 🙄

jlrycm · February 13

On 2/12/2026 at 11:05 AM, MakAsrock said:
For my Hack Pro7.1, the arguments for Tahoe are:
amfi=0x80 ipc_control_port_options=0 revpatch=memtab,pci,sbvmm,cpuname revcpu=1 ctrsmt=full
For Ventura are:
revpatch=memtab,pci,sbvmm,cpuname revcpu=1 ctrsmt=full

If I use memtab in clover boot args (which is the only boot arg I was missing), the error message appearing in the memory tab disappears but the memory lanes diagram looks like a Hackintosh as opposed to how it looks when booting through OpenCore and defining custom memory settings in the config.file as explained in the Dortania guide link below

https://dortania.github.io/OpenCore-Post-Install/universal/memory.html#mapping-our-memory

i recall chatting with @miliuco about this in a PM thread and concluded RestrictEvents and Custom Memory in Clover do not have the same result as in OpenCore.

MakAsrock · February 14

16 hours ago, jlrycm said:

If I use memtab in clover boot args (which is the only boot arg I was missing), the error message appearing in the memory tab disappears but the memory lanes diagram looks like a Hackintosh as opposed to how it looks when booting through OpenCore and defining custom memory settings in the config.file as explained in the Dortania guide link below

https://dortania.github.io/OpenCore-Post-Install/universal/memory.html#mapping-our-memory

i recall chatting with @miliuco about this in a PM thread and concluded RestrictEvents and Custom Memory in Clover do not have the same result as in OpenCore.

Tell me, did you select SMBIOS for Mac Pro 7.1? If not, everything will display as before.

If Slice gives the go-ahead, I'll remake it for other models, but I don't know how it might affect older models.

jlrycm · February 14

1 hour ago, MakAsrock said:

Tell me, did you select SMBIOS for Mac Pro 7.1? If not, everything will display as before.

If Slice gives the go-ahead, I'll remake it for other models, but I don't know how it might affect older models.

Yes, I’ve been using MacPro 7,1 since 2023.

Edited February 14 by jlrycm

Max.1974 · February 14

Hi all this version from Clover is doing well thanks to all!

image.png.5d33cfafdfd2b0d3e6e6256d05f3b126.png

MakAsrock · February 14

4 hours ago, jlrycm said:

Yes, I’ve been using MacPro 7,1 since 2023.

Then the order of the memory slots must match their physical location.
I have them inserted and they are displayed the same way.

Powered by Clover revision: 5168 (HEAD, commit 0e10cb1a9):

.

Edited February 14 by MakAsrock

jlrycm · February 15

5 hours ago, MakAsrock said:

Then the order of the memory slots must match their physical location.
I have them inserted and they are displayed the same way.

Powered by Clover revision: 5168 (HEAD, commit 0e10cb1a9):

.

All good here, similar to you except that I declared 12 slots and four slots occupied. No errors.

I was just hoping the diagram above would look like a real MacPro in Clover which is what OpenCore accomplishes through the custom memory entries.

Edited February 15 by jlrycm

Clover General discussion

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites