macOS 13 Ventura on Unsupported Macs Thread

[K two]

And what is wrong? With my comment I brought my opponent’s statement to its logical conclusion.
(By the way, explain what OT is?)

Off-topic and illogical 🤔

 

[TigerA]

the vast majority of unexpected issues seen with OCLP can be overcome by a correct SMC reset and/or a NVRAM reset from OpenCanopy applying the Space bar at boot and indexing all the way to the right and selecting or using a wired KB and mouse following the Apple-mandated method until three (3) chimes occur.

Thx K two. reseting SMC 3x times (not once, not twice, but 3x times) seems fixed hardware crash on wakeup (from sleep) for my 2011 iMac12,2 K3100 running 13.6.3 with OCLP ver 1.3.0 👍

 

[JedNZ]

I experimented with a spare drive with Ventura on my cMP5,1 and steep sideways of the minefields by heeding the warnings from other people's failed experiences, so it's really useful to hear how others go, and to listen to the wise amongst us who help steer us away from clifftops or come to our rescue at the bottom of the cliff .

I actually skipped Ventura in the end on my production cMPs5,1 and instead went straight to Sonoma, and despite a disastrous balls up of my own making that hosed my Monterey system I was upgrading, I am now successfully running Sonoma 14.2 (slight issue with Apple Watch unlock) on two cMP5,1 machines. The disaster resulted in me installing fro scratch - amazing how many apps I don't use and haven't had a need to re-install.

EDITED: Forgot to include my reason for posting - the point I was making was that I took a long, hard think about installing Ventura and only got truly interested around the time Sonoma was first released, and then saw how fast the devs went in updating OCLP for Sonoma, hence why I skipped Ventura altogether and went for Sonoma. That's all.

 

[VintageMacGS]

Similarly OpenCore 1.3.0 has rendered my MacBook Pro mid 2012 unbootable. Was running the latest Ventura 13.6 and wasn't have any issues with OCLP 1.2.1
Don't know where/how else to get the word out (not possible for me to raise the alarm on their github), but I'd strongly advise not downloading and installing 1.3.0

The following is stated on the GitHub page for version 1.3.0:

"With the release of OpenCore Legacy Patcher v1.3.0, this build is primarily targeted for macOS 14.2 and Macs with Metal 3802-based Graphics Cards."

I used 1.3.0 today to install Sonoma 14.2 with no problems on a Mac Mini Late 2012. Since Ventura wasn't mentioned, I guess I would have waited a bit before using it with that system.

 

[TigerA]

Thx K two. reseting SMC 3x times (not once, not twice, but 3x times) seems fixed hardware crash on wakeup (from sleep) for my 2011 iMac12,2 K3100 running 13.6.3 with OCLP ver 1.3.0 👍

Spoke too soon: The issue came back again and it's very persistent. Also noticed the display is running crazy as well. As the post above said, I am going back to OCLP ver 1.2.1 for Ventura 13.6.3.

 

[RK78]

Unless someone knows with certainty, you'd have to examine the commits to determine whether any post-install patch changes may affect your Mini4,1.

I have gone back and forth between 1.2.x and 0.6.8 post-install patches without issues on my MBP6,2 (but behavior on one MacModel does not imply anything on another model). The safest way to experiment is to add an APFS volume, install 13.6.1 in the new volume, Migrate from your original 13.6.1 (before applying root-patches to the new APFS volume) and then apply OCLP 0.6.8 post-install patches.

Thanks, but looks like the caveats plus the possible need to add a second volume as backup make this a forbidding enterprise, so not something I'm going to attempt anytime soon.

However, one nagging question: if the 0.6.8 post-install patch were to mess things up, might that easily be corrected by re-doing the 1.2.1 post install? Or does that also fall into the unknown?

 

[deeveedee]

However, one nagging question: if the 0.6.8 post-install patch were to mess things up, might that easily be corrected by re-doing the 1.2.1 post install? Or does that also fall into the unknown?

I'm the wrong person to ask. I don't operate on any critical volumes with in-place upgrades. All of my critical volumes are upgraded in a new APFS volume.

 

[trifero]

Deleted

 

[barneyman]

Hi,

installed 13.6.3 this morning and now a myriad of issues...

Apple Music won't play anything - the songs are greyed out
just basic internet seems dodgy - with various errors when trying to get to some sites
cant connect through to my work stuff on Microsoft remote desktop
mail doesn't connect either

is it something to do with my Intego anti virus software I wonder?
tried both wifi and ethernet - neither seems to make a difference...

I have a 2017 3.4 ghz quad-core intel core i5

everything was fine yesterday and now all this! - what the easiest way to go back to the previous version?

 

[trifero]

Hi,

installed 13.6.3 this morning and now a myriad of issues...

Apple Music won't play anything - the songs are greyed out
just basic internet seems dodgy - with various errors when trying to get to some sites
cant connect through to my work stuff on Microsoft remote desktop
mail doesn't connect either

is it something to do with my Intego anti virus software I wonder?
tried both wifi and ethernet - neither seems to make a difference...

I have a 2017 3.4 ghz quad-core intel core i5

everything was fine yesterday and now all this! - what the easiest way to go back to the previous version?

Use your backup made before updating. You make backups, right?

 

[barneyman]

Use your backup made before updating. You make backups, right?

Yep, got Time Machine but wondered if anyone experienced similar issues?

 

[deeveedee]

everything was fine yesterday and now all this! - what the easiest way to go back to the previous version?

Not trying to be a smart-a$$, just repeating my recommendation. The easiest way to revert to a previous version is to never have done an in-place upgrade in the first place. If it's a critical volume - don't perform an in-place upgrade. Instead, add a new APFS volume, install the new macOS in the new volume and migrate from the original volume before applying OCLP post-install patches. After migration complete, apply OCLP post-install patches to the new volume and test. Read this. At the very least, never perform an upgrade without a solid recovery plan.

EDIT: If you want to test the in-place upgrade, first clone your original volume to a new APFS volume and perform the upgrade in the new volume. Leave your original volume untouched until you are certain that the new volume is working.

 

[K two]

The KDK for macOS 13.6.3 is now available, here: https://github.com/dortania/KdkSupportPkg

 

[shmasser]

For those who are interested:
Installed on Ventura 13.5 OCLP 0.6.8 >>> 1.3.0. All previously described defects are in place.
However, now after even a short-term sleep mode, screen image artifacts appear:
Screen flickering, triangles and empty parts of windows. No elements are active - there is no response to mouse clicks. The only thing that helps is rebooting by long pressing the power button.
I did all the resets according to the recommendations several times - it did not help.

I had to go back to OCLP 0.6.8, apparently this is the best option for Ventura at this stage

 

[K two]

For those who are interested:
Installed on Ventura 13.5 OCLP 0.6.8 >>> 1.3.0. All previously described defects are in place.
However, now after even a short-term sleep mode, screen image artifacts appear:
Screen flickering, triangles and empty parts of windows. No elements are active - there is no response to mouse clicks. The only thing that helps is rebooting by long pressing the power button.
I did all the resets according to the recommendations several times - it did not help.

I had to go back to OCLP 0.6.8, apparently this is the best option for Ventura at this stage

Current versions of MacOS i.e. 13.6.3 and OCLP v.1.3.0 will likely overcome those graphics issues. And confirm the KDK in the Library>Developer ƒ is up to date. The KDK for 13.6.3 is here: https://github.com/dortania/KdkSupportPkg 😉

 

[K two]

Thanks, but looks like the caveats plus the possible need to add a second volume as backup make this a forbidding enterprise, so not something I'm going to attempt anytime soon.

However, one nagging question: if the 0.6.8 post-install patch were to mess things up, might that easily be corrected by re-doing the 1.2.1 post install? Or does that also fall into the unknown?

Yes, 1.2.1 will overwrite previous patches.

 

[K two]

macOS v.13.6.4RC1 is avail. OTA. Please note: Apparently, this release has been pulled. 🤷‍♂️

 

[LlamaLarry]

Any issues with MBP 9,1 currently running Catalina? Hoping to do an in place upgrade on my cousin's MBP while she is visiting and so far most of my OCLP setups usually end up going the fresh install route. I've never made a separate OS partition on the same machine either, if there are some guides or tips on how to handle that I could at least leave her working OS available just in case.

 

[makra]

My MBP 9,1 is running Ventura without any issues.

Partitions: Don't! Use a new volume instead. That worked fine for me, as long as I wanted to keep Catalina, too.
Just the other day I upgraded a 2014 MBA 6,1 from Big Sur to Ventura. Problem: I had two partitions, because I had kept High Sierra for some 32bit apps on a second partition. Because the two partitions filled the entire SSD, I couldn't install the OC EFI. I had to erase the disk and restore from a backup.

 

[deeveedee]

... if there are some guides or tips on how to handle that I could at least leave her working OS available just in case.

This should give you some ideas.

@LlamaLarry I just realized I posted the wrong link for you. Try this.

 

[LlamaLarry]

Howdy, I did see that it didn't look like what you were hoping, but I did figure it out and do pretty much what the correct post said. All in all everything worked well. I did have the first attempt die out with "error preparing software update", but a second attempt with an NVRAM reset after the first reboot seemed to do the trick.

Did a Migration Assistant carry over which seemed like it was working, but when we were all done the Applications were only in the original Catalina volume and the Ventura volume just had the stock Apple apps. The apps on the other volume seemed to be working, was jus not expecting that.

 

[Heat_Fan89]

Does anyone here have Ventura running on a 2012 Mini with 8GB of RAM with an internal SSD? How's the performance?

 

[phaser32]

Hi everyone, I'm reading about some problems with oclp and Ventura 13.6.3
I currently have on my Imac Late 2012 Ventura 13.6.1 with oclp 0.6.8 and I don't have any kind of problem. Do you recommend updating or is it better to wait? Thanks everyone for your attention.

 

[deeveedee]

Howdy, I did see that it didn't look like what you were hoping, but I did figure it out and do pretty much what the correct post said. All in all everything worked well. I did have the first attempt die out with "error preparing software update", but a second attempt with an NVRAM reset after the first reboot seemed to do the trick.

Did a Migration Assistant carry over which seemed like it was working, but when we were all done the Applications were only in the original Catalina volume and the Ventura volume just had the stock Apple apps. The apps on the other volume seemed to be working, was jus not expecting that.

Glad you figured out my mistake. On my MBP6,2, I always perform migration of everything (using Migration Assistant) as the last step of the macOS installation when prompted. I am able to migrate this way whether I am using a macOS installer directly downloaded from Apple or using a macOS installer created with OCLP.

EDIT: Could it be that the migration assistant knows that the Catalina apps are not compatible with Ventura?

 

[deeveedee]

Hi everyone, I'm reading about some problems with oclp and Ventura 13.6.3
I currently have on my Imac Late 2012 Ventura 13.6.1 with oclp 0.6.8 and I don't have any kind of problem. Do you recommend updating or is it better to wait? Thanks everyone for your attention.

My experience with my MBP6,2 can't predict your experience on your iMac, so take this for what it's worth... I am running Ventura 13.6.3 booting with an Open Core EFI generated with OCLP 1.3.0 and post-install patches applied with OCLP 0.6.8. My reasons for doing this are stated here. There are improvements to the Open Core EFI in OCLP versions after 0.6.8 that benefit Ventura. For my MBP6,2, there are no improvements in OCLP root patches in OCLP versions newer than 0.6.8. Since Ventura 13.6.3 is my "production" macOS, I am staying with OCLP 0.6.8 root patches until I see the need to upgrade root patches (and I haven't yet). I use OCLP 1.3.0 root patches for my Sonoma testing.

My Open Core EFI has the following properties:

• Advanced > Feature Unlock: Partial
• Security > Disable Library Validation: unchecked (Library Validation enabled)
• Security > Disable AMFI: unchecked (AMFI enabled)