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.
Clean or conventional installation of macOS 13.2 with OCLP 0.6.1 via USB3 card reader on a native USB 2 port or a card reader in my display (actually a USB 3 hub ...) doesn't work here. With about remaining 12 minutes of the installation procedure this error suddenly appears:

An offered restart always brings me back to this point.

Update from 13.0 to 13.1 caused that error on my MBP 10,2 and 9,1. This time, the 10,2 update went flawlessly, but I had to reboot my 9,1 manually three times to get past this error. Apart from that, everything seems to have worked out well.
 
Installed on a 2009 Mac Mini via OCLP 0.6.1. Works fine with acceleration, but hard locks when awakening the screen (not sleep). Have to mess with some settings to see if there's something in my power settings causing this. If not, I'll chalk it up to beta drivers and wait for updates. Great work, nevertheless!

EDIT: Turn off the screensaver, or choose an old, non-metal screensaver on the older machines. This is what was causing crashes on this Mini.
 
Last edited:
Thank all developers for the amazing work! All machines are up and running Ventura 13.2 with OCLP 0.6.1 with one exception. Did I miss something here:

I have a Fenvi PCI-card T919 WiFi & BT4.0 BCM94360CD on my 5.1 cMP. In Monterey it worked out of the box, now in Ventura Wifi works, BT doesn’t

In post install root patching it did't show up. I tried both aforementioned terminal commands killing bluetoothd with no result. Any suggestions? Thank you!!!
 
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
  • Like
Reactions: BDP008 and NataliaC
Not planning to dive into Ventura and 0.6.x yet, but a point of clarification in case I go mad as a hatter (I knew I shouldn't have played with mercury as a child) and do it anyway? It looks as if, as long as I have a USB hub between my input devices and the built-in USB I should be fine (Mac Pro 4,1/5,1)? Does this also pertain to installed USB 3 cards? Finally, does this disable the ability to intercept the Mac boot process? I've always found that process to be extremely flaky (generally impossible) with anything except a keyboard plugged directly into one of the Mac Pro's original USB ports.
 
One thing I should mention since moving to Ventura and its not a big deal to me:

After cloning using CCC, the Destination computer now needs re-post-patching for Acceleration.. This was not the case in Monterey.
No Biggie
 
  • Like
Reactions: NataliaC
I can happily report that 0.6.1 fixed all the issues I had with 0.6.0 and 13.2 with my late 2015 retina iMac.

Thanks to all the devs for their hard work!
Are the slow chrome load issues finally fixed? that was the main issue I had with Ventura on my iMac. Checking the known issues page doesn't show the issue listed anymore, so am wondering if it's safe to upgrade the iMac yet.

Late 2015, 27" iMac here.
 
Thank you for your extensive response! Sadly, I don't have CCC. Would I really need it? Or do you think resetting the PRAM is most important here and might even do the trick on its own?
You can download CCC and use it free for a month on trial, no limits to the software during that time. It is one of the best backup apps around and the dev is great at responding to requests. Well worth the cost in my opinion.
You may not absolutely need it, but running the installer file from the app folder on a CCC backup, or even using a bootable USB memory stick and pointing the installer at that CCC backup disk saves a lot of time using the migration app. Not to mention the piece of mind knowing you have your data saved to an external disk.
I am not sure that doing the pram zap will solve your issue, but the OCLP docs recommend it, so it is worth a try. Some things get written to the nvram during installs and in some cases that data can prevent an install from working. The only issue I have with it is that it turns on the loud BONG at startup, which I always turn off in the Sound preference pane!
Good luck! You should do a Google search for that error you mentioned, it may be useful.
 
Last edited:
Big thank you to all that have made this possible. I took the leap and updated all of my unsupported Macs to Ventura in the last 12 hours. All were performed via OTA, not clean installs. A few notes:

MacBook Pro 11,1 (Mid 2014): No issues to report at this time. Working perfectly.
iMac 12,2 27" i7 with K3100M/SSD upgrades: Mission Control doesn't exist it seems. Wi-Fi pane in Settings does not display. Wi-Fi seems to be working per the network pane.
iMac 12,1 21.5" i5 with SSD upgrade: Same issue with Wi-Fi pane in Settings.

Oddly, the welcome tips don't work on either of the iMac's either.
 
Last edited:
Good news!
Ventura 13.2 and the latest OCLP 0.6.1 in standard mode (so, no SMBIOS spoofing) work very very very very well on my 14.2 iMac (see my Signature for full specs). No problem, no bugs. (see attached screenshot). To me it looks 100 times better than Catalina, smoother, faster, snappier... and 10% better than Ventura 13.1

Bad news...
They are still about "Continuity Camera" and also its alternative applications, including "Camo Studio". So, "Camo" doesn't work (@khronokernel, on the other hand, in the OCLP problem list, says it should work...).
In fact my hardware supports "Camo" in Catalina just fine and "Camo" works fine in my iMac running macOS 10.15.7; but "Camo" doesn't work in macOS Ventura. Mah...

So... Automatic background removal from images also still doesn't work with Ventura 13.2 and its option is disabled in both Preview and Photos. Again it's worth pointing out that my hardware may do automatic background removal of images. The application "Super PhotoCut Pro", for example, works great in my iMac with Ventura and removes the background of even very large or complex images in a moment!
So... I wonder if maybe the "OCLP Post Install Patch" can make Preview and Photo think that the video card is compatible with Metal 3 or if "OCLP Post Install Patch" can unlock the "Remove Background" feature in some other way.

Have a nice week everyone! :)

macOS 13.2 13.2 (22D49) Ventura.jpg
 
Are the slow chrome load issues finally fixed? that was the main issue I had with Ventura on my iMac. Checking the known issues page doesn't show the issue listed anymore, so am wondering if it's safe to upgrade the iMac yet.

Late 2015, 27" iMac here.
Nothing in the release notes about a change on hardware decode/encode...
So I suppose it's not fixed.
 
  • Like
Reactions: Sanmiguel71
It's still in the issues:
Hardware Encode/Decode (ex. slow initial Chrome loading)​
Non-Functional​
AMD GCN 1-3​
strange, when I went to the link Mr Macintosh had sent me on twitter, I didn't see it listed there when I looked for it.
 
It's still in the "open issues" and I haven't seen any update in commit logs.
So I suppose it's not fixed.
But I hope I am wrong, it's the only issue I have seen.
 
It's not in the list, but it's no longer on the known issues page either. Also the person I asked mentioned an acceleration issue with 2015 machines being fixed.
FYI---I apologize, I thought you had a 2015 MacBook Pro so I downloaded Chrome and it is fast on the MBP with 0.6.1 and 13.2.....I don't know if there was a problem before but just to let you know.
 
On checking further, this seems to be model specific: the 15" MBP 2016 is affected but not the 13" MBA 2017. Just going to try root patching again on the former.
After messing around a bit, I also realized that the screen brightness adjustment from the keyboard and Sys Prefs Displays is disabled on the two TB screens connected to the MBA 2017. The internal screen brightness adjustment works as expected. Reverting the root patches from 0.6.0 and repatching with 0.6.1 fixed this problem.
 
I ran into trouble yesterday with OCLP 0.6.0 and my 2015 27 inch iMac - root patches gave odd colours and no graphics acceleration. So, I erased my disk and went back to 13.1 clean, and then 13.2 clean with 0.6.1 when it came out later in the day. In hindsight I should have just waited for 0.6.1 - oh well. The root patches worked on 0.6.1 so I then tried to use migration assistant to bring back all my files from a Time Machine backup. Migration completed, but then the fun began - the machine enters a boot loop with the bar progressing about a third of the way then the machine reboots (with a very tinny chime) and this repeats until I force shut down. Any ideas how to proceed? IMac late 2015 27 inch, all stock hardware from apple. I’d be very grateful for suggestions.
 
Are the slow chrome load issues finally fixed? that was the main issue I had with Ventura on my iMac. Checking the known issues page doesn't show the issue listed anymore, so am wondering if it's safe to upgrade the iMac yet.

Late 2015, 27" iMac here.
It is for this reason that I bid farewell to Ventura.
Not just Chrome, but also youtube, infuse Pro and more.

Late 2015, 27" iMac (i7 6700k+R9 M395X)
 
  • Like
Reactions: MacinMan
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.