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
13.6.6 works well on MBP 6,2; 8,1; 10,2.
Last edited:
Hello.
iMac14,1.
16Gb RAM, Samsung SSD 870 EVO.
OCLP 1.4.1
After update from 13.6.5 to 13.6.6, there were slowdowns during some operation.
When switching between windows and dragging various objects, files.
The cpu load jumps from 20 to 90, cpu temperature increases.
Programs used: phpstorm, transmit, firefox.
Rolled back to 13.6.5, the problem disappeared.
iMac14,1.
16Gb RAM, Samsung SSD 870 EVO.
OCLP 1.4.1
After update from 13.6.5 to 13.6.6, there were slowdowns during some operation.
When switching between windows and dragging various objects, files.
The cpu load jumps from 20 to 90, cpu temperature increases.
Programs used: phpstorm, transmit, firefox.
Rolled back to 13.6.5, the problem disappeared.
In these cases, I found that just once is enough, most of the times.
A developer recently informed me that cMPs often require multiple NVRAM resets to set things straight. 🤷♂️
Still applying post-install patches to Ventura 13.6.6 with OCLP 0.6.8. My Open Core EFI is generated with OCLP 1.5.0n (OCLP's generated EFI for MBP6,2 hasn't changed much recently, except for OCLP-Version in NVRAM). If I answer more, this will just be confusing. Note that I can still use OCLP 0.6.8 to apply post-install patches, because my MBP6,2 needs only the Nvidia non-metal patches. My Mac's Wi-Fi does not need patching to run Ventura.
EDIT: I'm not being aggressive with my OCLP testing in Ventura, because Ventura is still my production volume and it works well. No need for me to "go for it" as others have advised.
Can anyone using Xcode on Ventura report the following:
- Xcode version
- Mac model identifier
- Do you use iOS Simulator?
Recently broke my OCLP on MacBookPro9,1 by installing xcode 14.3 and/or launching iOS Simulator (it showed black screen and turned CPU to 600% load, then macOS visuals became glitchy and OS became laggy, this persisted after restart). Ended up reinstalling macOS and OCLP from scratch, but I think it was post-install patches, probably GPU-related ones
Related: https://github.com/chris1111/Geforce-Kepler-patcher/issues/29
P.S.: wondering if there's an Xcode version available for Ventura which could run Simulator on my hardware with no issues, but probably I won't be going as far is this to make it work
- Xcode version
- Mac model identifier
- Do you use iOS Simulator?
Recently broke my OCLP on MacBookPro9,1 by installing xcode 14.3 and/or launching iOS Simulator (it showed black screen and turned CPU to 600% load, then macOS visuals became glitchy and OS became laggy, this persisted after restart). Ended up reinstalling macOS and OCLP from scratch, but I think it was post-install patches, probably GPU-related ones
Related: https://github.com/chris1111/Geforce-Kepler-patcher/issues/29
P.S.: wondering if there's an Xcode version available for Ventura which could run Simulator on my hardware with no issues, but probably I won't be going as far is this to make it work
@vmz I have used XCode 14.3.1 and 15.2 in Ventura 13.6.5 on my MBP6,2 (both versions of XCode are installed simultaneously) ... but, I only use XCode to satisfy the iOS build requirements for Visual Studio / Xamarin and MAUI running in Windows 11. I have not yet needed to use iOS simulator in this configuration (and hope that I never need to).
I also have a MacMini8,1 which offers a much snappier (as expected) iOS build experience.
EDIT: I have connected an iPhone to my MBP6,2 for remote iOS testing from Visual Studio running in Windows 11. It works very well.
EDIT2: Visual Studio allows me to configure which remote version of XCode (14.3.1 or 15.2) to connect to for my iOS builds. This is important to me, because I needed XCode 14.3.1 for my Xamarin iOS builds and now I need XCode 15.2+ for my MAUI iOS builds.
EDIT3: @vmz Microsoft's recent Visual Studio 2022 updates for Windows have significantly improved VS/Windows interoperability with remote XCode. I just tested Visual Studio MAUI iOS builds (in Windows) connecting to remote XCode 15.2 running in Ventura 13.6.6 and the process is very smooth. I need to retract my previous Microsoft-bashing statements.
I also have a MacMini8,1 which offers a much snappier (as expected) iOS build experience.
EDIT: I have connected an iPhone to my MBP6,2 for remote iOS testing from Visual Studio running in Windows 11. It works very well.
EDIT2: Visual Studio allows me to configure which remote version of XCode (14.3.1 or 15.2) to connect to for my iOS builds. This is important to me, because I needed XCode 14.3.1 for my Xamarin iOS builds and now I need XCode 15.2+ for my MAUI iOS builds.
EDIT3: @vmz Microsoft's recent Visual Studio 2022 updates for Windows have significantly improved VS/Windows interoperability with remote XCode. I just tested Visual Studio MAUI iOS builds (in Windows) connecting to remote XCode 15.2 running in Ventura 13.6.6 and the process is very smooth. I need to retract my previous Microsoft-bashing statements.
Last edited:
I'm having an issue with my MBP 9,1 mid-2012, Ventura 10.6.4, OCLP 1.1.0. I recently purchased an OWC Envoy Pro enclosure for the SSD from a 2013 MacBook Air, and it apparently is not very compatible with my system. It takes a long time to mount the volume, any manipulations in Disk Utility are extremely slow, and worst of all, it's not possible - at all - to boot my Mac if the drive is connected to a USB port. I had hoped to possibly use it as a bootable external drive for dealing with issues in the future.
I've plugged into another system and have seen none of the above issues, so I have to suspect it has something to do with OCLP. I did a boot with OCLP debugging turned on, and I captured the spot where booting hangs-
00:661 00:005 OC: Driver OpenCanopy.efi at 1 () is being loaded... 00:667 00:006 OCABC: EfiBootRt candidate - <nil> 00:673 00:005 OCABC: IsEfiBootRt 0 (BP 1, Apple 0) 00:679 00:005 OCB: Arch filtering 0(167936)->8B2DD190(167936) caps 4 - Success 00:685 00:006 OCUI: Registered custom GUI protocol 00:691 00:005 OC: Driver OpenCanopy.efi at 1 is successfully loaded! 00:697 00:005 OC: Driver OpenLinuxBoot.efi at 2 () is being loaded... 00:710 00:013 OCABC: EfiBootRt candidate - <nil> 00:716 00:005 OCABC: IsEfiBootRt 0 (BP 1, Apple 0) 00:722 00:005 OCB: Arch filtering 0(126976)->8B2E7190(126976) caps 4 - Success 00:728 00:006 OC: Driver OpenLinuxBoot.efi at 2 is successfully loaded! 00:734 00:005 OC: Driver ResetNvramEntry.efi at 3 () is being loaded... 00:740 00:005 OCABC: EfiBootRt candidate - <nil> 00:746 00:005 OCABC: IsEfiBootRt 0 (BP 1, Apple 0) 00:752 00:005 OCB: Arch filtering 0(73728)->8B2F4190(73728) caps 4 - Success 00:758 00:006 OC: Driver ResetNvramEntry.efi at 3 is successfully loaded! 00:764 00:006 OC: Connecting drivers... 91:371 90:607 OC: Connecting drivers done...
There's a 90 second gap between Connecting drivers... and Connecting drivers done. The latter happened immediately after I pulled the USB cable out of my Mac, and the Mac then booted normally. All I saw was Connecting drivers............ for 90 seconds.
I wonder if anyone has an idea what could be the problem. I don't have problems with USB flash drives or mechanical drives.
I've plugged into another system and have seen none of the above issues, so I have to suspect it has something to do with OCLP. I did a boot with OCLP debugging turned on, and I captured the spot where booting hangs-
00:661 00:005 OC: Driver OpenCanopy.efi at 1 () is being loaded... 00:667 00:006 OCABC: EfiBootRt candidate - <nil> 00:673 00:005 OCABC: IsEfiBootRt 0 (BP 1, Apple 0) 00:679 00:005 OCB: Arch filtering 0(167936)->8B2DD190(167936) caps 4 - Success 00:685 00:006 OCUI: Registered custom GUI protocol 00:691 00:005 OC: Driver OpenCanopy.efi at 1 is successfully loaded! 00:697 00:005 OC: Driver OpenLinuxBoot.efi at 2 () is being loaded... 00:710 00:013 OCABC: EfiBootRt candidate - <nil> 00:716 00:005 OCABC: IsEfiBootRt 0 (BP 1, Apple 0) 00:722 00:005 OCB: Arch filtering 0(126976)->8B2E7190(126976) caps 4 - Success 00:728 00:006 OC: Driver OpenLinuxBoot.efi at 2 is successfully loaded! 00:734 00:005 OC: Driver ResetNvramEntry.efi at 3 () is being loaded... 00:740 00:005 OCABC: EfiBootRt candidate - <nil> 00:746 00:005 OCABC: IsEfiBootRt 0 (BP 1, Apple 0) 00:752 00:005 OCB: Arch filtering 0(73728)->8B2F4190(73728) caps 4 - Success 00:758 00:006 OC: Driver ResetNvramEntry.efi at 3 is successfully loaded! 00:764 00:006 OC: Connecting drivers... 91:371 90:607 OC: Connecting drivers done...
There's a 90 second gap between Connecting drivers... and Connecting drivers done. The latter happened immediately after I pulled the USB cable out of my Mac, and the Mac then booted normally. All I saw was Connecting drivers............ for 90 seconds.
I wonder if anyone has an idea what could be the problem. I don't have problems with USB flash drives or mechanical drives.
Hey, was there ever a fix for the "animated Memoji on the lock screen disappears leaving only the eyes" problem? I'm experiencing it too...on a 2013 15" MBP retina...in 2024!
If you were paid each time you said this....Reset NVRAM.
Since our Macs are using Acidanthera's RestrictEvents.kext, we can set revblock=media as per this. I haven't tested, but I suspect that setting the mediaanalysisd option in OCLP adds the revblock property to our OC config.plist.
Your Air is fully supported for Ventura, why OCLP? See https://forums.macrumors.com/threads/macos-13-ventura-on-unsupported-macs-thread.2346881/ 🤷♂️
Very perceptive. The post indicates OC Binaries, but not OCLP. Maybe confusing OCLP with OC? Hackintosh?
Sure ... and my boot disk is named Fred. Let me know how to interpret that.
Joking (bad joking) aside, it's a strange post. It's a Ventura 13.6.6 "About This Hack" screenshot with the statement "Updated to 14.3." I think it's a confused hackintosh owner, but eagerly await the response.
EDIT: @K two I should have paid closer attention to the CPU. If the posted screenshot accurately indicates the CPU (i5-5250u), the actual laptop is MacBookAir7,2 (Early 2015), so maybe OCLP is spoofing MacBookAir8,1.
Last edited: