When you "Build and Install Open Core" with the OCLP GUI, just make sure that AMFI and Library Validation are enabled in OCLP Settings (do not check the Disable boxes):About the AMFIPass, I've never used, but we could try it!
Last edited:
When you "Build and Install Open Core" with the OCLP GUI, just make sure that AMFI and Library Validation are enabled in OCLP Settings (do not check the Disable boxes):About the AMFIPass, I've never used, but we could try it!
Thank you for all your suggestions. This was very useful to me.To free up space perhaps you could move your user files to an external drive or store them in a cloud service.
My Sonoma uses 120 GB, Ventura 63 GB and Catalina 56 GB.
macOS .app-files are basically self-contained directory structures. Some apps need files in addition to that and they will then be created at the first run. If you you then delete an app using e.g. AppCleaner you must be careful so that you don't delete files used by other installations. If you have disk space it is easiest to have one instance of an app for every installation.
Very common to modify pmset on hackintoshes (PCs emulating Macs). I have a real MBP6,2 and a PC emulating a MBP6,2 (Dell Latitude E6410). I like my PC emulating the MBP6,2 better than the real Mac. On my emulated MBP6,2, I use the following pmsettings:This pmset option may help;
sudo pmset -b tcpkeepalive 0
None of my Montereys is patched. Not even the mac pro 5,1.OT: totally agree, but I'm warming up to Ventura. 13.6 is working very well in a test volume on my MBP6,2 patched with OCLP 1.0.1 Release. Monterey is still my favorite, but I currently see no reason not to upgrade to Ventura (for me). And Wi-Fi is natively supported with no root patches. Oh, and Ventura still runs latest Xcode.
EDIT: I am currently booting the following on my MBP6,2, each in its own APFS volume (note that for my testing, OCLP post-install patch versions do NOT have to be the same on each APFS volume). My Open Core EFI is generated with OCLP 1.0.1 (Release):
- Big Sur patched with OCLP 0.6.8 (Release)
- Monterey patched with OCLP 0.6.8 (Release)
- Ventura 13.5 patched with OCLP 0.6.8 (Release)
- Ventura 13.6 patched with OCLP 1.0.1 (Release)
- Sonoma 14.0 (Release) patched with OCLP 0.6.9 (latest Beta). Still in the process of securely creating a new test volume for Sonoma testing with OCLP 1.0.1
I don't have a choice. My MBP6,2 is non-metal Nvidia Tesla. You're fortunate to have graphics that don't require patching.None of my Montereys is patched. Not even the mac pro 5,1.
Not fortunate! I had to buy the graphics and the wifi/bluetooth module! 😄I don't have a choice. My MBP6,2 is non-metal Nvidia Tesla. You're fortunate to have graphics that don't require patching.
In my opinion, the MP5,1 is underrated. It's an awesome Mac. Apple could have continued "official" support for much longer if they wanted to.Not fortunate! I had to buy the graphics and the wifi/bluetooth module! 😄
I can assure you my Mac Pro makes all the tasks I need, more than capable. Equiped with Dual NVME, two ESATA and two USB 3,1 ports and Thunderbolt. And 3 mechanical Raid 1 in it´s 6 Sata bays. Usue it with two 30" Apple Displays.In my opinion, the MP5,1 is underrated. It's an awesome Mac. Apple could have continued "official" support for much longer if they wanted to.
Are we bragging now? 😂. Ok, I'll see your MP5,1 and raise with my HackMini8,1. I installed an i9-9900, 2 NVMe drives, 2TB SSD for TimeMachine. Sure, it only has UHD630 graphics, but it is a killer machine running Sonoma. EDIT: ... and 3 displays.I can assure you my Mac Pro makes all the tasks I need, more than capable. Equiped with Dual NVME, two ESATA and two USB 3,1 ports and Thunderbolt. And 3 mechanical Raid 1 in it´s 6 Sata bays. Usue it with two 30" Apple Displays.
If reformatting the drive you want to install onto is an option, you can try that. Has worked here with similar situations. Installer confused by remnants of older installs is my raw theoryAny idea what would cause this on a Mac Pro 5,1? I get nearly all the way through with the Sonoma installation, then this error.
Last one looks to me as if you were bootet natively and tried to choose the Sonoma-drive in the settings.Any idea what would cause this on a Mac Pro 5,1? I get nearly all the way through with the Sonoma installation, then this error.
Yes that was my theory as well, I completely erased the SSD but not the EFI partition of course. But still same issue.If reformatting the drive you want to install onto is an option, you can try that. Has worked here with similar situations. Installer confused by remnants of older installs is my raw theory![]()
Installer stick is still present and I did those steps.Last one looks to me as if you were bootet natively and tried to choose the Sonoma-drive in the settings.
You will have to reboot with the option-key pressed to call the macOS bootpicker. And then choose EFI-boot to get to the OpenCore bootpicker. If the installer-stick is not present anymore, OC needs to be installed to the Sonoma-drive's EFI Partition.
Again, if you can wipe it all and use an OCLP EFI on a USB for the install and then recreate the other partitions after that, that is what has worked for me a few times. Start fresh. Good luck.Yes that was my theory as well, I completely erased the SSD but not the EFI partition of course. But still same issue.
Installer stick is still present and I did those steps.
I'm going to try to go back to Monterey and re-do a OCLP 1.01 install to the EFI. Then blow out Monterey partition and start over.
Do I need to reinstall the Sonoma and Open Core?When you "Build and Install Open Core" with the OCLP GUI, just make sure that AMFI and Library Validation are enabled in OCLP Settings (do not check the Disable boxes):
View attachment 2295422
You only 'need' to 'Build and Install Open Core' with OCLP. It won't hurt and is advisable to use the same OCLP to re-apply post-install patches.Do I need to reinstall the Sonoma and Open Core?
I did it, but no successYou only 'need' to 'Build and Install Open Core' with OCLP. It won't hurt and is advisable to use the same OCLP to re-apply post-install patches.
When you post here, with questions like that, you really should show the Mac (year and model) you intend to use. Without that information no one can give you appropriate advice.Do I need to reinstall the Sonoma and Open Core?
Everything you said is correct. Go easy on him. He posted his info in the Ventura thread (not that you would know).When you post here, with questions like that, you really should show the Mac (year and model) you intend to use. Without that information no one can give you appropriate advice.
If you had read my previous posts, you would see that I was talking to deevee, whom I shared my MacBook model and system I'm running now. And I explained my problem quoting other people that had the same problem as mine inside this thread. Thank you for being SO rude!When you post here, with questions like that, you really should show the Mac (year and model) you intend to use. Without that information no one can give you appropriate advice.
I finally found your original post, several pages back. And... your issue is simply that the camera doesn't work using Safari. So use a different browser!
I assume English isn't your native language. Sonoma is the latest macOS (operating system) and as such, it is referred to as Sonoma, without "the".
As to whether or not you really need Sonoma, or need to reinstall it, how can anyone know that?
Do you intend to use software that requires Sonoma? Then you need it. Do you want to get the latest security updates? Only Sonoma gets them all. Ventura and Monterey get most of the important updates, but not all.
Most important, is your Mac on the list of supported models necessary to run Sonoma?
If not, you need OpenCore Legacy Patcher in order to boot Sonoma.
Monterey may work better than Sonoma on older Macs.
Read the OpenCore Legacy Patcher instructions again!
That post wasn't rude. Your post was sorely insufficient, and as such that is rude.If you had read my previous posts, you would see that I was talking to deevee, whom I shared my MacBook model and system I'm running now. And I explained my problem quoting other people that had the same problem as mine inside this thread. Thank you for being SO rude!
I already read all the documentation for OpenCore, but thanks anyway.
@davidlv I didn't know about this rule of mentioning someone when I'm replying older comments, I thought that quoting was enough. So, it's totally my fault, I'm sorry!That post wasn't rude. Your post was sorely insufficient, and as such that is rude.
If you were replying to someone specifically, you should use the usual, @some name before the text.
Otherwise your post is directed to everyone, and it had no information about your prior post or hardware.
Get real or admit your mistake, rather than call my post rude.