deeveedee Posted April 1 Share Posted April 1 (edited) 2 hours ago, MakAsrock said: Re-enable legacy hardware patches (Intel, NVIDIA, AMD, legacy wireless, etc.) Only include these patches when the system's XNU major version is less than 25 (Tahoe) @kgp If the XNU version conditions are implemented properly (haven't tested, but I assume they are), you won't see the changes if you're patching Tahoe. Edited April 1 by deeveedee 3 Link to comment https://www.insanelymac.com/forum/topic/362543-the-oclp-plus-3x-tahoe-patch-set/page/2/#findComment-2848638 Share on other sites More sharing options...
kgp Posted April 1 Share Posted April 1 13 minutes ago, deeveedee said: @kgp If the XNU version conditions are implemented properly (haven't tested, but I assume they are), you won't see the changes if you're patching Tahoe. Without wanting to start a discussion I don't see any need to use any OCLP 3.x.x version under Sequoia or Sonoma. There is a stable and well approved 2.4.1 release of the OCLP developers for respective systems. 3 Link to comment https://www.insanelymac.com/forum/topic/362543-the-oclp-plus-3x-tahoe-patch-set/page/2/#findComment-2848642 Share on other sites More sharing options...
MakAsrock Posted April 1 Author Share Posted April 1 (edited) 29 minutes ago, deeveedee said: @kgp If the XNU version conditions are implemented properly (haven't tested, but I assume they are), you won't see the changes if you're patching Tahoe. In Tahoe, you'll only see what was in the previous release, but there will be fewer questions, like, "Why am I getting an error?" Because the patch folders now match the existing ones. 😉 Edited April 1 by MakAsrock 3 Link to comment https://www.insanelymac.com/forum/topic/362543-the-oclp-plus-3x-tahoe-patch-set/page/2/#findComment-2848643 Share on other sites More sharing options...
deeveedee Posted April 1 Share Posted April 1 (edited) The same could be said for many of the tools that people create. These new versions of OCLP-Mod by MakAsrock include legacy patches (like javascript for non-AVX moved to RestrictEvents.kext) that are not yet in the OCLP 2.x release. Someday, there will hopefully be a stable and well-approved 3.x released by the OCLP Devs. Edited April 1 by deeveedee 2 Link to comment https://www.insanelymac.com/forum/topic/362543-the-oclp-plus-3x-tahoe-patch-set/page/2/#findComment-2848644 Share on other sites More sharing options...
MakAsrock Posted April 1 Author Share Posted April 1 (edited) 18 minutes ago, deeveedee said: The same could be said for many of the tools that people create. These new versions of OCLP-Mod by MakAsrock include legacy patches (like javascript for non-AVX moved to RestrictEvents.kext) that are not yet in the OCLP 2.x release. Someday, there will hopefully be a stable and well-approved 3.x released by the OCLP Devs. These new versions of OCLP-Plus that I've created include legacy patches (e.g., JavaScript for non-AVX versions has been moved to RestrictEvents.kext) that were included in the OCLP 2.x release, which is where I got them from, by the way. 😉 The only new thing is that instead of disabling these patches, I introduced a filter by macOS version. Edited April 1 by MakAsrock 3 Link to comment https://www.insanelymac.com/forum/topic/362543-the-oclp-plus-3x-tahoe-patch-set/page/2/#findComment-2848647 Share on other sites More sharing options...
deeveedee Posted April 1 Share Posted April 1 14 minutes ago, MakAsrock said: These new versions of OCLP-Plus that I've created include legacy patches (e.g., JavaScript for non-AVX versions has been moved to RestrictEvents.kext) that were included in the OCLP 2.x release, which is where I got them from, by the way. 😉 Ok. Our definitions of 'release' are different. Javascript for non-AVX in RestrictEvents is in a nightly build of OCLP 2.5.0 that hasn't yet been part of a release build. 2 Link to comment https://www.insanelymac.com/forum/topic/362543-the-oclp-plus-3x-tahoe-patch-set/page/2/#findComment-2848648 Share on other sites More sharing options...
MakAsrock Posted April 1 Author Share Posted April 1 (edited) 1 hour ago, kgp said: My dear friend, many thanks for your continued work on OCLP-Plus. From my current experience on macOS Tahoe (XNU ≥ 25), re-enabling legacy GPU patches unfortunately does not seem to provide any practical benefit on affected systems. In fact, these patches often fail during the root patch process and may leave the system in an inconsistent state, which can subsequently impact otherwise working components such as AppleHDA and ModernWireless. For this reason, I currently observe better overall stability when completely avoiding legacy GPU patches on Tahoe and focusing solely on ModernAudio and ModernWireless. Systems requiring legacy GPU support are, in my opinion, still better served with OCLP 2.4.1 under Sonoma or Sequoia. Just wanted to share these observations — hopefully helpful for further refinement. Cheers, KGP 👍🏼 Hi KGP, Thank you for your feedback! It seems there might be a slight misunderstanding regarding the logic I implemented. Actually, we are on the same page. The code if self._xnu_major < os_data.tahoe.value is specifically designed to disable those legacy GPU patches for macOS Tahoe and newer. By using the "less than" (<) operator, the hardware variants for Intel (Iron Lake through Skylake), Nvidia (Tesla/Kepler), and AMD (Terascale/Legacy GCN) are only added to the list if the system version is older than Tahoe. For Tahoe (XNU 24) and future releases, these patches are now skipped entirely. This prevents the root patching failures and instability (affecting AppleHDA/Wireless) that you correctly pointed out. The goal was precisely to follow the approach you mentioned: keeping Tahoe clean of legacy GPU overhead while maintaining support for older OS versions where those patches still function correctly. Cheers! 🤗 P.P.S. It's my own fault and I've corrected the description to be more accurate: Legacy patches (Intel/Nvidia/AMD/Wireless) re-enabled for XNU < 25. Strict filter for Tahoe (XNU 25+): Legacy patches excluded to prevent instability (AppleHDA/Wireless) and root patching failures. ModernWireless/Audio remain enabled for all versions (including Tahoe). Maintained original patch detection order. Edited April 1 by MakAsrock 3 1 Link to comment https://www.insanelymac.com/forum/topic/362543-the-oclp-plus-3x-tahoe-patch-set/page/2/#findComment-2848649 Share on other sites More sharing options...
MakAsrock Posted April 1 Author Share Posted April 1 29 minutes ago, deeveedee said: Ok. Our definitions of 'release' are different. Javascript for non-AVX in RestrictEvents is in a nightly build of OCLP 2.5.0 that hasn't yet been part of a release build. dhinakg detect.py: Fix missing import b9df76e · 2 weeks ago 3 Link to comment https://www.insanelymac.com/forum/topic/362543-the-oclp-plus-3x-tahoe-patch-set/page/2/#findComment-2848650 Share on other sites More sharing options...
deeveedee Posted April 1 Share Posted April 1 (edited) I have finally met someone who's as stubborn as I am. Glad to see us defending our own opinions in a friendly manner. Edited April 1 by deeveedee 2 1 1 Link to comment https://www.insanelymac.com/forum/topic/362543-the-oclp-plus-3x-tahoe-patch-set/page/2/#findComment-2848651 Share on other sites More sharing options...
MakAsrock Posted April 3 Author Share Posted April 3 (edited) Fixed Failed to create macOS Installer: APFS disks may not be used as bootable media. Before: After: Need to download it again. Sorry for the inconvenience. Edited April 3 by MakAsrock 3 Link to comment https://www.insanelymac.com/forum/topic/362543-the-oclp-plus-3x-tahoe-patch-set/page/2/#findComment-2848694 Share on other sites More sharing options...
MakAsrock Posted April 10 Author Share Posted April 10 (edited) The new macOS 26.4.1 (25E253) Powered by Clover revision: 5172 (master, commit 6020c4917) is installed, and the icons have returned. OCLP-Plus 3.1.9 (Tahoe Patch Set) Wi-Fi and sound are working. Kernal_Debug_Kit_26.4.1_build_25E253.dmg is Apple's, not at dortania. . Edited April 10 by MakAsrock 2 Link to comment https://www.insanelymac.com/forum/topic/362543-the-oclp-plus-3x-tahoe-patch-set/page/2/#findComment-2848925 Share on other sites More sharing options...
MakAsrock Posted April 10 Author Share Posted April 10 (edited) Shabbat Shalom. Kernel Debug Kit 26.4.1 build 25E253 Edited April 10 by MakAsrock 1 Link to comment https://www.insanelymac.com/forum/topic/362543-the-oclp-plus-3x-tahoe-patch-set/page/2/#findComment-2848945 Share on other sites More sharing options...
ilovepeace Posted April 13 Share Posted April 13 Users running OCLP-Plus 3.1.9 on a MacBookPro11,5 (Mid-2015) may encounter a "Subprocess failed" error with Return Code 75, or an application crash during the Post-Install Root Patching process. The Issue: The logs reveal a Python NameError: name 'cpu_missing_avx' is not defined. This is a regression in the OCLP-Plus fork that prevents the software from validating CPU features on Darwin 24 (macOS Sequoia). Additionally, a "Resource busy" error occurs when the system fails to mount the root volume for patching. 3 Link to comment https://www.insanelymac.com/forum/topic/362543-the-oclp-plus-3x-tahoe-patch-set/page/2/#findComment-2849060 Share on other sites More sharing options...
kaoskinkae Posted April 13 Share Posted April 13 I have three computers. On two of them, the OCPL-Plus 3.19 patch works perfectly, but on the second computer (the only one with Intel Wi-Fi and an iMac 17.1), it says "unsupported device" or the patch appears grayed out. If I enable the sound, it activates, but it only patches the sound. I followed the guide perfectly. 2 Link to comment https://www.insanelymac.com/forum/topic/362543-the-oclp-plus-3x-tahoe-patch-set/page/2/#findComment-2849063 Share on other sites More sharing options...
MakAsrock Posted April 13 Author Share Posted April 13 (edited) 11 hours ago, ilovepeace said: Users running OCLP-Plus 3.1.9 on a MacBookPro11,5 (Mid-2015) may encounter a "Subprocess failed" error with Return Code 75, or an application crash during the Post-Install Root Patching process. The Issue: The logs reveal a Python NameError: name 'cpu_missing_avx' is not defined. This is a regression in the OCLP-Plus fork that prevents the software from validating CPU features on Darwin 24 (macOS Sequoia). Additionally, a "Resource busy" error occurs when the system fails to mount the root volume for patching. This will not happen anymore. Removed cpu_missing_av completely. Redownload. 🤗 OCLP-Plus_3.1.9_2026-04-13_15-58-33-423510.log Edited April 13 by MakAsrock 2 Link to comment https://www.insanelymac.com/forum/topic/362543-the-oclp-plus-3x-tahoe-patch-set/page/2/#findComment-2849075 Share on other sites More sharing options...
MakAsrock Posted April 13 Author Share Posted April 13 5 hours ago, kaoskinkae said: I have three computers. On two of them, the OCPL-Plus 3.19 patch works perfectly, but on the second computer (the only one with Intel Wi-Fi and an iMac 17.1), it says "unsupported device" or the patch appears grayed out. If I enable the sound, it activates, but it only patches the sound. I followed the guide perfectly. My patcher doesn't support Intel Wi-Fi at all. To enable Intel Wi-Fi, use OpenIntelWireless 😉 Link to comment https://www.insanelymac.com/forum/topic/362543-the-oclp-plus-3x-tahoe-patch-set/page/2/#findComment-2849078 Share on other sites More sharing options...
kgp Posted April 13 Share Posted April 13 5 hours ago, kaoskinkae said: I have three computers. On two of them, the OCPL-Plus 3.19 patch works perfectly, but on the second computer (the only one with Intel Wi-Fi and an iMac 17.1), it says "unsupported device" or the patch appears grayed out. If I enable the sound, it activates, but it only patches the sound. I followed the guide perfectly. OCLP 3.0.0 Nightly (amfipassbeta variant) supports Intel-Wi-Fi with Broadcom spoofing following my explicit guidelines. 2 Link to comment https://www.insanelymac.com/forum/topic/362543-the-oclp-plus-3x-tahoe-patch-set/page/2/#findComment-2849079 Share on other sites More sharing options...
kaoskinkae Posted April 13 Share Posted April 13 1 minute ago, kgp said: OCLP 3.0.0 Nightly (variante amfipassbeta) admite Intel-Wi-Fi con suplantación de Broadcom siguiendo mis directrices explícitas. https://github.com/5T33Z0/OCLP4Hackintosh I followed this guide perfectly, I even spoke with the guide's creator, but it didn't work for my Intel OLD2. 2 Link to comment https://www.insanelymac.com/forum/topic/362543-the-oclp-plus-3x-tahoe-patch-set/page/2/#findComment-2849080 Share on other sites More sharing options...
MakAsrock Posted April 13 Author Share Posted April 13 (edited) 34 minutes ago, kgp said: OCLP 3.0.0 Nightly (amfipassbeta variant) supports Intel-Wi-Fi with Broadcom spoofing following my explicit guidelines. The same can be done in OCLP-Plus bat we need to mask Intel Wi-Fi as Broadcom. 🤗 Edited April 13 by MakAsrock 2 Link to comment https://www.insanelymac.com/forum/topic/362543-the-oclp-plus-3x-tahoe-patch-set/page/2/#findComment-2849081 Share on other sites More sharing options...
kgp Posted April 13 Share Posted April 13 Just now, MakAsrock said: The same can be done in OCLP-Plus. 🤗 Then I would not write that it does not work with Intel Wi-Fi 😉 1 Link to comment https://www.insanelymac.com/forum/topic/362543-the-oclp-plus-3x-tahoe-patch-set/page/2/#findComment-2849082 Share on other sites More sharing options...
MakAsrock Posted April 13 Author Share Posted April 13 (edited) 12 minutes ago, kgp said: Then I would not write that it does not work with Intel Wi-Fi 😉 So we need to mask Intel Wi-Fi as Broadcom. By default, legacy Wi-Fi is enabled only for operating systems below Tahoe. 🤗 Edited April 13 by MakAsrock 2 Link to comment https://www.insanelymac.com/forum/topic/362543-the-oclp-plus-3x-tahoe-patch-set/page/2/#findComment-2849083 Share on other sites More sharing options...
MakAsrock Posted April 13 Author Share Posted April 13 (edited) Cleanup config.plist and update AMFI boot arguments - Remove redundant `Misc -> BlessOverride` for `bootmgfw.efi` - Remove redundant `-lilubetaall` boot argument - Replace `amfi=0x80` and `ipc_control_port_options=0` with `-amfipassbeta` - Update documentation to reflect these changes - Removed minor flaws. Minor correction Removed erroneous definition if self._xnu_major == os_data.tahoe.value: return "12.5-25 🚫 Intel Wi-Fi (AirportItlwm) is NOT supported If you need these fixes, please download CLP-Plus again. Edited April 17 by MakAsrock 1 Link to comment https://www.insanelymac.com/forum/topic/362543-the-oclp-plus-3x-tahoe-patch-set/page/2/#findComment-2849094 Share on other sites More sharing options...
MakAsrock Posted April 18 Author Share Posted April 18 (edited) OCLP-Plus 3.2.0 Revert MacPro7,1 to SupportedSMBIOS to allow selection in GUI due to general compatibility issues. Updated Max OS Supported for Intel Macs: only iMac20,x, MBP16,1/2/4, and MacPro7,1. Capped other Intel models (e.g. MBP 15,x, iMac 19,x) at sequoia. Spoiler Root Patching Log: - Starting Patch Process - Determining Required Patch set for Darwin 25 KDK already installed (KDK_26.4.1_25E253.kdk), skipping - Verifying whether Root Patching possible - Patcher is capable of patching - Mounted Universal-Binaries.dmg - Running sanity checks before patching - Running patches for MacPro7,1 - Running Preflight Checks before patching - Found SkylightPlugins folder, removing old plugins - Cleaning Auxiliary Kernel Collection - Relocating EnergyDriver.kext kext to /Library/Relocated Extensions KDK already installed (KDK_26.4.1_25E253.kdk), skipping - Found KDK at: /Library/Developer/KDKs/KDK_26.4.1_25E253.kdk - Merging KDK with Root Volume: KDK_26.4.1_25E253.kdk - Successfully merged KDK with Root Volume - Finished Preflight, starting patching - Installing Patchset: Modern Wireless - Handling Installs in: /usr/libexec - Found existing wifip2pd, overwriting... - Handling Installs in: /System/Library/PrivateFrameworks - Installing: IO80211.framework - Installing: WiFiPeerToPeer.framework - Installing Patchset: Modern Audio - Handling Installs in: /System/Library/Extensions - Installing: AppleHDA.kext - Writing patchset information to Root Volume - Checking if RSRMonitor is needed - No kexts found with GPUCompanionBundles, skipping RSRMonitor - Installing com.dortania.opencore-legacy-patcher.auto-patch.plist - Installing com.dortania.opencore-legacy-patcher.macos-update.plist - Installing com.dortania.opencore-legacy-patcher.os-caching.plist - Rebuilding Boot and System Kernel Collections Installing Kernel Collection syncing utility - Unmounting root volume - Patching complete Please reboot the machine for patches to take effect Edited April 20 by MakAsrock 4 1 Link to comment https://www.insanelymac.com/forum/topic/362543-the-oclp-plus-3x-tahoe-patch-set/page/2/#findComment-2849269 Share on other sites More sharing options...
dogansan Posted April 19 Share Posted April 19 I have Intel WI-FI BE200 and I could only make Bluetooth work but all my attempts failed with itlwm open driver solution. Do you think this method enable us BE200 wifi to work? 2 Link to comment https://www.insanelymac.com/forum/topic/362543-the-oclp-plus-3x-tahoe-patch-set/page/2/#findComment-2849287 Share on other sites More sharing options...
MakAsrock Posted April 19 Author Share Posted April 19 (edited) On 4/18/2026 at 5:54 PM, MakAsrock said: OCLP-Plus 3.2.0 Revert MacPro7,1 to SupportedSMBIOS to allow selection in GUI due to general compatibility issues. Updated Max OS Supported for Intel Macs: only iMac20,x, MBP16,1/2/4, and MacPro7,1. Capped other Intel models (e.g. MBP 15,x, iMac 19,x) at sequoia. Reveal hidden contents Root Patching Log: - Starting Patch Process - Determining Required Patch set for Darwin 25 KDK already installed (KDK_26.4.1_25E253.kdk), skipping - Verifying whether Root Patching possible - Patcher is capable of patching - Mounted Universal-Binaries.dmg - Running sanity checks before patching - Running patches for MacPro7,1 - Running Preflight Checks before patching - Found SkylightPlugins folder, removing old plugins - Cleaning Auxiliary Kernel Collection - Relocating EnergyDriver.kext kext to /Library/Relocated Extensions KDK already installed (KDK_26.4.1_25E253.kdk), skipping - Found KDK at: /Library/Developer/KDKs/KDK_26.4.1_25E253.kdk - Merging KDK with Root Volume: KDK_26.4.1_25E253.kdk - Successfully merged KDK with Root Volume - Finished Preflight, starting patching - Installing Patchset: Modern Wireless - Handling Installs in: /usr/libexec - Found existing wifip2pd, overwriting... - Handling Installs in: /System/Library/PrivateFrameworks - Installing: IO80211.framework - Installing: WiFiPeerToPeer.framework - Installing Patchset: Modern Audio - Handling Installs in: /System/Library/Extensions - Installing: AppleHDA.kext - Writing patchset information to Root Volume - Checking if RSRMonitor is needed - No kexts found with GPUCompanionBundles, skipping RSRMonitor - Installing com.dortania.opencore-legacy-patcher.auto-patch.plist - Installing com.dortania.opencore-legacy-patcher.macos-update.plist - Installing com.dortania.opencore-legacy-patcher.os-caching.plist - Rebuilding Boot and System Kernel Collections Installing Kernel Collection syncing utility - Unmounting root volume - Patching complete Please reboot the machine for patches to take effect Revert MacPro7,1 to SupportedSMBIOS to allow selection in GUI due to general compatibility issues between Macintosh and Hackintosh. 🙁 16 hours ago, dogansan said: I have Intel WI-FI BE200 and I could only make Bluetooth work but all my attempts failed with itlwm open driver solution. Do you think this method enable us BE200 wifi to work? Unfortunately, I don't know how to do this, so I don't plan to include Intel WI-FI support in my project in the near future. 🙁 Try AirportItlwm.kext (Ventura) with Broadcom spoofing by following my guidelines and taking my Intel EFI distribution as the baseline 😉 If you have any problems, upload your EFI folder and IOReg file here, or if you prefer, just send me a private message with the link or file and maybe I can help you out 🤗 Edited April 20 by MakAsrock 2 Link to comment https://www.insanelymac.com/forum/topic/362543-the-oclp-plus-3x-tahoe-patch-set/page/2/#findComment-2849297 Share on other sites More sharing options...
Recommended Posts