Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Safari 16.5.2 update is available for Monterey 12.6.7. The Safari update applied without issues on my MBP6,2. After the Safari update, I applied OCLP-AMFIPass-Beta4 post-install patches. All completed without issues. Monterey 12.6.7 continues to run very well on my MBP6,2 patched with OCLP-AMFIPass-Beta4 (AMFI / LV fully enabled, AMFIPass.kext 1.3.1).
 
  • Like
Reactions: m4v3r1ck
How do I turn off this notification? I even deleted OCLP as an application, but it still comes up!
Screen Shot 2023-07-16 at 4.03.39 PM.png
 
@BeatCrazy
You need to look into the subfolder /Library/Application Support/Dortania

When you root patch with OCLP, it automatically installs the OCLP app in that subfolder.

Deleting the OCLP app from that subfolder every time after root patching will stop that pop-up.
 
Last edited:
  • Like
Reactions: BeatCrazy
And remove the ability to root patch after OS updates, bad idea.
There is one much simpler, though:
View attachment 2233547
I forgot to mention, I had already unchecked that box, but the app is ignoring the setting.

I'm on 12.6.7 on my 5,1 Mac Pro... I'm pretty sure I'm done with macOS updates beyond my current one. If something does come out, I could always reinstall OCLP so I can do root patches.
 
  • Like
Reactions: TimmuJapan
iMac (27-inch, Mid 2011), upgraded video-card to AMD Radeon Pro WX 4150 4Gb MXM (Polaris)
I have update High Sierra to Monterey by OCLP 0.6.1. OCLP update to 0.6.7

I can't use some software features with hardware virtualization.
My terminal print by sysctl -a | grep machdep.cpu.features
Code:
machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX SMX EST TM2 SSSE3 CX16 TPR PDCM SSE4.1 SSE4.2 x2APIC POPCNT AES PCID XSAVE OSXSAVE TSCTMR AVX1.0

Software who can't use hardware virtualization say that need supported SSE4.1 and F16C CPU instructions..but my CPU is Intel Core i5-2400 (3.1GHz) who supports SSE4.1 and F16C.

What I need/can do to enable F16C in MacOS supported CPU?
 
Last edited:
How do I turn off this notification? I even deleted OCLP as an application, but it still comes up!
This alert happens when your Open Core EFI config.plist contains a value for OCLP-version that is older than your OCLP post-install patches (e.g., you have applied post-install patches with OCLP 0.6.7, but your EFI is generated with OCLP 0.6.6). Unless you are trying to test a custom EFI/patch configuration (like I do occasionally with my hackintoshes), then you should establish an OCLP upgrade procedure where you always use the same version of OCLP to generate your OC EFI (Build and Install Open Core) and apply post-install patches and you should only be using Release versions of OCLP.

You can easily see the value of OCLP-version by following the instructions here.

You can see the version of OCLP by using "Get info" on your OCLP app.

In summary: Whenever you upgrade to a newer version of OCLP, always "Build and Install Open Core" and apply post-install patches with the new version of OCLP (don't apply post-install patches without "Build and Install Open Core").
 
Last edited:
This alert happens when your Open Core EFI config.plist contains a value for OCLP-version that is older than your OCLP post-install patches (e.g., you have applied post-install patches with OCLP 0.6.7, but your EFI is generated with OCLP 0.6.6). Unless you are trying to test a custom EFI/patch configuration (like I do occasionally with my hackintoshes), then you should establish an OCLP upgrade procedure where you always use the same version of OCLP to generate your OC EFI (Build and Install Open Core) and apply post-install patches and you should only be using Release versions of OCLP.

You can easily see the value of OCLP-version by following the instructions here.

You can see the version of OCLP by using "Get info" on your OCLP app.

In summary: Whenever you upgrade to a newer version of OCLP, always "Build and Install Open Core" and apply post-install patches with the new version of OCLP (don't apply post-install patches without "Build and Install Open Core").
Very helpful, thanks.

I will try to get on 0.6.7 and 'stay' there. Since I plan on sticking with Monterey, and things are very stable for me, I'll be fine with no incremental updates.
 
The app you have removed?
Dude, no offense, but you need to re-read and try to understand what I wrote originally. Please read post #8906 again. I just added the word “sub” in front of folder to try and help make it more clear for you.

I didn’t say delete OCLP from your regular applications folder. I didn’t say remove OCLP from your system.

You may not be aware of this, but in addition to OCLP existing in your regular applications folder, when you root patch with OCLP it automatically installs itself a second time in a sub folder, and I described this sub folder’s location in post #8,906. Deleting this second and separate copy of OCLP from that subfolder will stop the pop-up that @BeatCrazy is asking about. Deleting this second and separate copy of OCLP from that subfolder WILL NOT remove OCLP from the regular applications folder or your dock or your system in general. For most use cases of OCLP, it is fine and good to leave the second copy of OCLP in the [ /Library/Application Support/Dortania ] subfolder, but there are some use cases, where it’s convenient to remove OCLP from that subfolder(as deeveedee mentioned above, custom EFIs, or hybrid hackintosh OCLP-opencore EFIs). For some advanced users, it might be the right choice to remove the second and separate copy of OCLP that exists in the subfolder referenced above, and For @BeatCrazy particular situation, this might be the case. The solution that I offered and the solution that @deeveedee offered is viable.

Let me repeat, what I have suggested in #8906 will not delete OCLP from your system or remove the ability to root patch in the future as @hwojtek is 100% falsely suggesting.⤵️

And remove the ability to root patch after OS updates, bad idea.
There is one much simpler, though:

Please re-read what I wrote in #8906.
You do not “remove the ability to root patch after an OS updates” by removing the second and separate copy of OCLP in the [ /Library/Application Support/Dortania ] folder.
 
Last edited:
Now that's a seriously long way of saying "I was not precise enough".
Well, apparently, I wasn’t precise enough for you and only you.

The solution that I offered actually resolves @BeatCrazy ’s issue, whereas the solution that you offered does not. You also went out of your way to post misinformation on this board and claim that a real solution to a particular issue was a bad idea, because you didn’t read carefully / understand information that has already been reposted here several times.
1689712666391.gif
 
Last edited:
Hi - Installed Monterey 12.6.7 on a MBP mid 2012. All looks to be working just fine. Its just that the fan is on, continuously and there are no apps installed, I am not even using it. Fan on. OCLP root patches and everything done successfully.

Would you recommend a downgrade? Maybe its just more this mac can cope with.
 
@mychalme What version of OCLP are you using to "Build and Install Open Core" and apply post-install patches? On Discord, Devs are discouraging advice which some are giving to use old versions of OCLP. For my own experience, OCLP newer versions work best.

EDIT: One other thought... When you first install a new macOS, the installation will continue to require CPU and disk resources for a while after the install appears to be finished. Wait a while (not really sure how to quantify "a while") to see if your CPU calms down after the new macOS installation. Also, you may want to modify Spotlight indexing to reduce the volumes and folders indexed by Spotlight (System Preferences -> Spotlight). On my MBP6,2, I am booting Monterey 12.6.7, I use OCLP-AMFIPass-Beta4 (a fork of OCLP 0.6.7) and I disable most Spotlight indexing. I recognize that our experiences with OCLP will vary depending on our Mac Model and the apps we use.
 
Last edited:
  • Like
Reactions: mychalme
@mychalme What version of OCLP are you using to "Build and Install Open Core" and apply post-install patches? On Discord, Devs are discouraging advice which some are giving to use old versions of OCLP. For my own experience, OCLP newer versions work best.

EDIT: One other thought... When you first install a new macOS, the installation will continue to require CPU and disk resources for a while after the install appears to be finished. Wait a while (not really sure how to quantify "a while") to see if your CPU calms down after the new macOS installation. Also, you may want to modify Spotlight indexing to reduce the volumes and folders indexed by Spotlight (System Preferences -> Spotlight). On my MBP6,2, I am booting Monterey 12.6.7, I use OCLP-AMFIPass-Beta4 (a fork of OCLP 0.6.7) and I disable most Spotlight indexing. I recognize that our experiences with OCLP will vary depending on our Mac Model and the apps we use.
Thanks so much Deeveedee - it appears you are very correct. I downloaded the latest version of OCLP, repatched and rebooted a few times. The fan has completed stopped now. So relieved that I don't (for the moment) need to roll back. Everything seems to be working just fine at this moment and now the fan is quiet after revving for quite a few reboots, it is silent. (yay!). So great to give some extra life to my MBP. I just unchecked the SW upgrades, as I was running patched before and it upgraded on its own and then, it would not boot (hence the reinstall).
 
Last edited:
  • Like
Reactions: deeveedee
@mychalme What version of OCLP are you using to "Build and Install Open Core" and apply post-install patches? On Discord, Devs are discouraging advice which some are giving to use old versions of OCLP. For my own experience, OCLP newer versions work best.
I haven't seen it discouraged. 😯
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.