Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 13 Ventura on Unsupported Macs Thread
- Thread starter 0xCUBE
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
@brennovich I am emulating an MBP6,2 on a PC and sleep works perfectly and I don't hibernate. We have different devices. You should add an APFS volume and test it. The OCLP experience with one SMBIOS model cannot in any way predict the experience on another.
macOS 13.7.8 installed atop 13.7.7 OTA, OCLP 2.4.0, runs as expected.
👏
👏
Thanks a lot.
This helped me to find Safari 18.1.1 for Sonoma.
Can also download it without 'curl' .
Finally instead of warcart utility is simply to use The Unarchiver app
Recently updated my Mac Pro 5,1 to 13.7.8 and OCLP to 2.4.1. Now Safari won't load any webpages (A problem repeatedly occurred with ...) and Chrome causing the mac to freeze up.
In trying to sort through the responses here, is the solution to install a previous version of Safari? I'm running 18.6
And is there any solution to the Chrome issue? I'm assuming they are related.
Thanks
In trying to sort through the responses here, is the solution to install a previous version of Safari? I'm running 18.6
And is there any solution to the Chrome issue? I'm assuming they are related.
Thanks
Yes.. better install Safari 18.1.1 In my old iMac it is the only Safari that also works with Mac OS Sonoma
and yes.. in my iMac Safari cause problems with chrome and app store
So I just download Safari 18.1.1. (I think its posted above) and install? And this overwrites the current version I have installed? Because I don't think you can uninstall Safari its part of the OS.
In my Ventura test volume, I upgraded to 13.7.8 (22H730) and Safari 18.6. Safari 18.6 does not work for me on any of the websites that I visited, including this one. I re-installed Safari Version 18.1.1 (18619.2.8.111.7, 18619) and website functionality that I tested is restored. For non-metal Nvidia, it appears to me that Safari 18.1.1 is the latest Safari version that runs reasonably well in Ventura. Note that I am applying Nvidia Tesla post-install patches with OCLP 2.4.0 for this test.
Yes.. it's same to Sonoma
I always do complete installations. Even if it takes more time.
I'm using Safaria 26.0.1 with Sonoma 14.8.1. I only use it to visit this website and the InsanelyMac website and don't have any issues. Same for Sequoia. It is only with Ventura that I need to remain with Safari 18.1.1.
I perform all of my updates via OTA (which always downloads the full installer since OCLP breaks the APFS seal), so there's no difference between applying the full installer and updating via OTA. I don't see any performance difference between 13.7.7 and 13.7.8 after allowing 13.7.8 to run its post-install processes for a while. If the slowness persists, you could always try to re-apply OCLP post-install patches.
[I posted this on Sequoia thread, will leave it here too in case it helps anyone]
Just some tips on dual booting MacOS, with the last supported OS on one volume plus an OCLP MacOS on another volume. I'm dual booting my 2012 Macbook Pro and had some headaches of high cpu usage and slowness while switching OSes, after a long time trouble shooting this is what I found out:
Mac OS was never designed to dual boot between versions, it's designed to upgrade the OS only, and therefore when you start up the newer OS it immediately detects an older indexing Spotlight DB and starts to update it to the new version, hence the slowness on start, I was getting the new OS installed feeling every time, seeing a high mds_stores process cpu usage. And when I return to the older OS it detected a unsupported Spotlight DB, discards it and started over the indexing.
There's two solutions for this, you either disable Spotlight on every volume that are accessed from both OSes, by adding the volume on Spotlight Privacy list, inside Spotlight settings. This sets a flag on the volume itself, so both OSes will know not to index that volume. You will lose the ability to search for files using Spotlight for that volume.
The other option is prevent the auto-mount of the volume that you don't want Spotlight touching, by adding the Volume UUID using "sudo vifs", Google this for more precise instructions.
I use a combination of both, by preventing the OS to mount the other OS volume, thus keeping Spotlight, and I have other Volumes for personal files storage with Spotlight disabled, so I can access them on whichever OS is running.
Additionally, for the last supported MacOS to run "vanilla", with all security enabled, you have to uncheck NVRAM WriteFlash on OCLP, rebuild and install OpenCore, and perform the NVRAM reset once, by holding Option-Command-P-R keys when powering on. After that you should only boot to the supported OS by holding the Option key (leave OCLP for newer OS only). This will keep both OS NVRAM settings clompletely separated. You can check the security by running: csrutil status
Just some tips on dual booting MacOS, with the last supported OS on one volume plus an OCLP MacOS on another volume. I'm dual booting my 2012 Macbook Pro and had some headaches of high cpu usage and slowness while switching OSes, after a long time trouble shooting this is what I found out:
Mac OS was never designed to dual boot between versions, it's designed to upgrade the OS only, and therefore when you start up the newer OS it immediately detects an older indexing Spotlight DB and starts to update it to the new version, hence the slowness on start, I was getting the new OS installed feeling every time, seeing a high mds_stores process cpu usage. And when I return to the older OS it detected a unsupported Spotlight DB, discards it and started over the indexing.
There's two solutions for this, you either disable Spotlight on every volume that are accessed from both OSes, by adding the volume on Spotlight Privacy list, inside Spotlight settings. This sets a flag on the volume itself, so both OSes will know not to index that volume. You will lose the ability to search for files using Spotlight for that volume.
The other option is prevent the auto-mount of the volume that you don't want Spotlight touching, by adding the Volume UUID using "sudo vifs", Google this for more precise instructions.
I use a combination of both, by preventing the OS to mount the other OS volume, thus keeping Spotlight, and I have other Volumes for personal files storage with Spotlight disabled, so I can access them on whichever OS is running.
Additionally, for the last supported MacOS to run "vanilla", with all security enabled, you have to uncheck NVRAM WriteFlash on OCLP, rebuild and install OpenCore, and perform the NVRAM reset once, by holding Option-Command-P-R keys when powering on. After that you should only boot to the supported OS by holding the Option key (leave OCLP for newer OS only). This will keep both OS NVRAM settings clompletely separated. You can check the security by running: csrutil status