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.
I´m on Monterey, even on my native supported Ventura/Sonoma macs. Really can´t see a difference. And I HATE so much that System Preferences and other stuff.
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):
  1. Big Sur patched with OCLP 0.6.8 (Release)
  2. Monterey patched with OCLP 0.6.8 (Release)
  3. Ventura 13.5 patched with OCLP 0.6.8 (Release)
  4. Ventura 13.6 patched with OCLP 1.0.1 (Release)
  5. 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
 
Last edited:
  • Like
Reactions: 0134168
About the AMFIPass, I've never used, but we could try it!
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):

Screenshot 2023-10-14 at 10.25.51 AM.png
 
Last edited:
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.
Thank you for all your suggestions. This was very useful to me.
 
This pmset option may help;
sudo pmset -b tcpkeepalive 0
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:
  • sudo pmset -a displaysleep 3;
  • sudo pmset -a autopoweroff 0;
  • sudo pmset -a powernap 0;
  • sudo pmset -a standby 0;
  • sudo pmset -a proximitywake 0;
  • sudo pmset -a tcpkeepalive 0;
  • sudo pmset -a hibernatemode 0;
  • sudo pmset -a disksleep 3;
  • sudo pmset -a sleep 5;

    This may rub some the wrong way, but now that we're all using Open Core to boot our unsupported Macs, we're kind of all running hackintoshes. This Open Core documentation might be helpful.
EDIT: ... and my apologies to the Devs. I hardly use the real MBP6,2. If I had known my diagnostics/analytics were being sent from my hackintosh to you all, I would have figured out a way to disable them. Must have been very confusing to get diagnostics from a hackintosh.
 
Last edited:
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):
  1. Big Sur patched with OCLP 0.6.8 (Release)
  2. Monterey patched with OCLP 0.6.8 (Release)
  3. Ventura 13.5 patched with OCLP 0.6.8 (Release)
  4. Ventura 13.6 patched with OCLP 1.0.1 (Release)
  5. 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
None of my Montereys is patched. Not even the mac pro 5,1.
 
  • Like
Reactions: deeveedee
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.
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.
 

Attachments

  • Captura de Pantalla 2023-10-14 a las 17.05.56.jpg
    Captura de Pantalla 2023-10-14 a las 17.05.56.jpg
    85.8 KB · Views: 55
  • Like
Reactions: deeveedee
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.
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.

EDIT2: I know you weren't bragging ... just proud (and you should be. that's an awesome system). I couldn't resist. :cool:
 
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.
error 1.png

error 2.jpeg

error 3.png
 
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.
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 ;)
 
  • Like
Reactions: deeveedee
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.
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.
 
  • Like
Reactions: deeveedee
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 ;)
Yes that was my theory as well, I completely erased the SSD but not the EFI partition of course. But still same issue.
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.
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.
 
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.
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.
 
I don't usually do betas, so I'm mainly asking this out of interest: How is the latest Sonoma beta with OCLP 1.0.1, and the latest nightly on the later macs such as 2015 and newer. The older non metal macs don't apply to me. The oldest mac I have is a late 2013, 13" MBP. The newest Mac I have is my late 2015 27" iMac. Right now just using Monterey, with Sonoma installed on an external drive v 14.0 with OpenCore 1.0.1
 
Do I need to reinstall the Sonoma and Open Core?
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!
 
Last edited:
  • Like
Reactions: K two
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.
Everything you said is correct. Go easy on him. He posted his info in the Ventura thread (not that you would know).

EDIT: I sent him over here, so it's kindof my fault.
 
Last edited:
  • Love
Reactions: davidlv
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!
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.
 
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.
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, @ mark before the name and 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.
 
Last edited:
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.
@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!

About being rude, I think that correcting such a small thing, as the use of "the", yes it sounds a little bit rude ;)

EDIT: I don't see anybody using the "usual" @ mark as you said to answer old posts, maybe the problem is with me.
 
Last edited:
@davidlv and @alissonss This is OT. Please take this to the Sonoma Security Thread. 😂

Sorry - couldn't resist. Let's give each other the benefit of the doubt. We're on the same side here, even though it may not look that way at times.

@alissonss Ok - just to save myself and make it look like this post isn't a complete waste of space, do you know how to post your Open Core config.plist? If not, this is a good exercise for you. Figure out how to find and copy the Open Core config.plist in your Mac's EFI. Then post it here for our review. Thanks.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.