macOS 13 Ventura on Unsupported Macs Thread

[deeveedee]

Just a SUGGESTION - Found these settings to work just fine. Launch codes unmolested. Snark, intended. 😉
Enjoy

Thank you. My husband (God rest his soul) (he's not dead, just wishful thinking) tells me my Ego is too big and I've also been told that my 'Ego is too big' in a private message by someone whose name I won't disclose. I think the exact words were 'your ego runs amok which weakens your contentions' but I can't be sure. I try to keep my Ego in check.

Thanks again for your help.

 

[mardecissab]

Are you using "pc" as a generic way to refer to your Mac, or is it actually a pc "hackintosh?" If a hackintosh, you might find more help over at InsanelyMac. That's where my cousin spends most of her time.

No, sorry for the confusion.
Was a generic way.
It is an Apple MacBook Pro late 2011 13". With 500SSD, 16gb RAM and with a original airport wireless card upgrade from a mid 2012 MBP.

thanks!

 

[davidlv]

Thank you. My husband (God rest his soul) (he's not dead, just wishful thinking) tells me my Ego is too big and I've also been told that my 'Ego is too big' in a private message by someone whose name I won't disclose. I think the exact words were 'your ego runs amok which weakens your contentions' but I can't be sure. I try to keep my Ego in check.

Thanks again for your help.

@deeveedee Pardon the intrusion. Did you notice that K two mentioned that Ventura has an RC update to 13.6.1 available on the developer channel? Installed fine on my iMac 15,1 running it from an external SSD.
Weee.... off we go into the sunset .....

 

[MacinMan]

From my experience, I haven't noticed any real differences between Ventura and Sonoma on my iMac 17,1. I started with Ventura to see how it was doing at this point, worked well, so I decided to see if i could skip Ventura and just go to Sonoma when it came out. So far, I haven't had any new problems in Sonoma that didn't already exist in Ventura, and that really hasn't been too many. In fact, running Sonoma 14.0 with Open Core 1.0.1 currently without issues.

They've done a good job to get an unsupported machine on the latest OS on release day, as if you were on a supported machine. I like the fact that I'll be able to grow with the latest OS now, as I did when it was officially supported.

One thing I appreciate about the open Core project is, I can see what the latest version of macOS is like on my current mac, and really give it a fair evaluation as to if I want to even bother spending the money for a new mac, or if I want something else because Apple isn't giving me what I'm looking for anymore.

 

[rehkram]

I prefer Sonoma to Ventura. I'm not really sure why, perhaps because it's still got that "new OS" smell, and I was definitely getting bored with Ventura.

When Ventura achieved stability halfway through the beta versions it became slightly ho hum at that point, to me anyway. I was ready for more beta testing. So I guess I've become a masochist thanks to you guys & gals.

 

[MacinMan]

I prefer Sonoma to Ventura. I'm not really sure why, perhaps because it's still got that "new OS" smell.

Well one reason could be that Ventura was the first version to introduce a lot new features, Sonoma is the polished version, like leopard to snow leopard.

 

[rehkram]

Could be. I hate myself for enjoying the random animated flyover screen savers & wallpapers though.

 

[deeveedee]

@deeveedee Pardon the intrusion. Did you notice that K two mentioned that Ventura has an RC update to 13.6.1 available on the developer channel? Installed fine on my iMac 15,1 running it from an external SSD.
Weee.... off we go into the sunset .....

You are never intruding! Always welcome. I don't have Beta channel enabled on my Ventura 13.6 volume. Waiting for the Release.

 

[rehkram]

Hey deeveedee, are you using that dynamic auto resizing of volumes (rather than specifying static, sized partitions) to keep your various macOS installs separate? I was doing that for a few months with Catalina & Big Sur(?) trouble free, then one day it started malfunctioning.

I ended up doing a clean install and it came right, and I then installed the second OS (Catalina) to an external SSD drive. Just a heads up. I'll see if I can find where I posted my travails on MacRumors, I think it was during Big Sur.

That episode confirmed my faith in the KIS principal. After all, we have zero visibility into the OS disk management code, only faith which may or may not be misplaced. Dynamic resizing? What could possibly go wrong?

 

[deeveedee]

Hey deeveedee, are you using that dynamic auto resizing of volumes (rather than specifying static, sized partitions) to keep your various macOS installs separate? I was doing that for a few months with Catalina & Big Sur(?) trouble free, then one day it started malfunctioning.

I ended up doing a clean install and it came right, and I then installed the second OS (Catalina) to an external SSD drive. Just a heads up. I'll see if I can find where I posted my travails on MacRumors, I think it was during Big Sur.

That episode confirmed my faith in the KIS principal. After all, we have zero visibility into the OS disk management code, only faith which may or may not be misplaced. Dynamic resizing? What could possibly go wrong?

I am allowing macOS to auto-adjust the size of APFS volumes. I have a single APFS container and then use DiskUtility to add APFS volumes as I need them (and to delete them when I no longer need them). When I need to test a new version of macOS or new OCLP post-install patches, I'll usually add a new APFS volume and perform a clean macOS install to that new volume. Then I apply post-install patches to the new volume using the version of OCLP that I want to test. I only have a single Open Core EFI (which is thus the same EFI for the different macOS volumes and is currently the OC EFI generated by OCLP 1.0.1 upgraded to OC 0.9.5), but I may have different versions of OCLP post-install patches for my test purposes.

;TLDR? Yes - I let macOS auto-resize APFS volumes in the APFS container and I have no problems.

EDIT: I should note that Catalina and below is not in my suite of macOS versions that I'm currently testing. I am only testing Big Sur, Monterey, Ventura (with Sonoma currently isolated in a separate test suite). I never have a High Sierra and a Big Sur+ volume installed at the same time. And I should also note that I have only used DosDude patcher with Mojave and Catalina - I have not tested OCLP with Mojave and Catalina.

 

[deeveedee]

I don't have an Apple TV subscription, but I just noticed that I can watch Apple TV trailers on my MBP6,2 running Ventura 13.6 patched with OCLP 0.6.8. I wasn't able to watch Apple TV trailers in earlier OCLP/Ventura testing. When did that happen? Very cool.

 

[rehkram]

The Apple TV+ trailers have worked throughout, IIRC. It's the newer full length movies that wouldn't play. Selecting them would dump you straight back to where you came from. The theory was, last time I checked, it was to do with DRM (he said vaguely). I need to test it again.

 

[mikelets456]

The Apple TV+ trailers have worked throughout, IIRC. It's the newer full length movies that wouldn't play. Selecting them would dump you straight back to where you came from. The theory was, last time I checked, it was to do with DRM (he said vaguely). I need to test it again.

I don't know about this problem too much, but I bought a new Apple TV and got 3 months free of Apple TV+....Watching everything on my 11,4 with OCLP 1.0.1 and Sonoma works fine. I don't know if I had a problem before because I didn't have a subscription while on 0.6.8 and Ventura.

 

[bixby]

Hello,
My main machine is a early 2015 13" MBP with 16GB RAM. It is running on MacOS 12.7 which is the latest official release.
Now I have been thinking about using OCLP to update it to MacOS 13 or 14.
Most of my tasks are around Python programming in VSC, Excel, and some light work in Lightroom. For peripherals I am using a WIFI printer (shouldn't be an issue) and 2 Garmin devices.
My main concern is stability. Would it make more sense to update to MacOS 13 because it's been around for a while and will still get updates?

So there are 3 options:
- OCLP -> Ventura / 13
- OCLP -> Sonoma / 14
- do nothing and stay with 12.7

What would you recommend? I'd really appreciate any comments!

 

[ps866mker]

There‘s always the risk. I suggest backup everything and then try it. If it doesn’t work out, revert back. At the end of the day if it aint broke….

 

[K two]

AppleTV+ works perfectly with a subscription. 😎

 

[deeveedee]

AppleTV+ works perfectly with a subscription. 😎

It's on our list. We've had to cut back on most subscriptions. Amazing how they add up.

 

[Macdctr]

comment deleted . . .

 

[spn0381]

Hi

I have a MacBook Pro A1286, with a fried AMD Gpu... i have blu raws on my screen
I would like to use OCLP building Ventura bypassing the AMD GPU... I have found this way:

Dortania guide

---

"Unable to switch GPUs on 2011 15" and 17" MacBook Pros
Currently, with OpenCore Legacy Patcher, GPU switching between the iGPU and dGPU is broken. The simplest way to set a specific GPU is to disable the dGPU when you wish to remain on the more power efficient iGPU.

The best way to achieve this is to boot to Recovery (or Single User Mode if the dGPU refuses to function at all) and run the following command:

nvram FA4CE28D-B62F-4C99-9CC3-6815686E30F9:gpu-power-prefs=%01%00%00%00
This will disable the dGPU and allow the iGPU to function in Big Sur. Note that external display outputs are directly routed to the dGPU and therefore can no longer be used. Solutions such as DisplayLink Adapters (opens new window)can work around this limitation, however, note that you'll need to use older drivers (5.2.6):

• DisplayLink USB Graphics Software for macOS - For Mojave and Catalina - 5.2.6(opens new window)

Note: This driver only provides partial support in macOS, full graphics acceleration is not currently available on displays driven by DisplayLink."

---

anyone has ever tryed? Is the right way or there is a easyest way?


thank you


UPDATE: It works!

 

[nothingtoseehere]

With my 13inch Early 2015, I currently stay on macOS 12 as it should get security updates for a year to come. But this is only my personal decision, not an advice.
As much as I love this cherished oldie, I have to admit that my MBA 15" M2 is a far superior machine. Much faster, cooler, no fans, no staingate yet... Maybe I will shelve the 2015 MBP next year.

 

[MacinMan]

With my 13inch Early 2015, I currently stay on macOS 12 as it should get security updates for a year to come. But this is only my personal decision, not an advice.
As much as I love this cherished oldie, I have to admit that my MBA 15" M2 is a far superior machine. Much faster, cooler, no fans, no staingate yet... Maybe I will shelve the 2015 MBP next year.

I have a Late 2015, 27" iMac, and Monterey is still supported for another year. In the time I've tried OCLP, I haven't found anything beyond Monterey really care about in terms of new features. Yes, there is the concern of security updates, and more software will require newer versions of macOS. However, I've already considered this and a majority of software I use now is open source / cross platform. People here have mentioned Xcode as a reason to do OCLP, I have Xcode installed, but only for Homebrew, not for anything Apple specific, so those tools come with Linux, or a BSD install. I can't comment on Apple Silicon Macs as I don't own one, and don't plan on considering one until Apple does a larger iMac. (unless circumstances force me to.) I currently prefer X86 as it's a platform I feel gives me more options than just Apple, I was done with "Apple Only" a long time ago. In fact, I don't even consider myself an "Apple User" anymore, now someone who "just uses and enjoys apple products"

 

[deeveedee]

Hi

I have a MacBook Pro A1286, with a fried AMD Gpu... i have blu raws on my screen
I would like to use OCLP building Ventura bypassing the AMD GPU... I have found this way:

Dortania guide

---

UPDATE: It works!

Just to confirm, you found advice in a Dortania guide and it worked for you on your Mac? That's good to know. If you find any Dortania suggestions for fixing sleep/wake issues, there are some looking for those solutions in the Sonoma thread.

 

[deeveedee]

What would you recommend? I'd really appreciate any comments!

If you have enough storage space, you might want to add an APFS volume and perform a clean install of macOS in the new APFS volume by following the steps below. This allows you to keep your original macOS volume while you test the new one.

1. Add a new APFS volume
2. Use OCLP to create a new USB installer for the version of macOS that you want to test
3. Use OCLP to "Build and Install OpenCore" to the USB installer that you created in Step 2. The "Build and Install Open Core" process installs Open Core to the USB thumb drive's EFI. You must boot your Mac with an Open Core EFI in order to boot an unsupported version of MacOS
4. Boot your Mac from the USB installer (booting with the USB's Open Core EFI) and run the macOS installer. Install macOS to the new APFS volume that you created in Step 1
5. During the new macOS install, when the macOS installer reboots, continue to boot from your USB installer (booting with the USB's EFI)
6. As the last step of the macOS installation (when prompted), migrate data/apps/settings from your original macOS volume
7. After the new macOS is installed and migration is complete, use OCLP to apply post-install patches to your new macOS volume
8. Boot from the USB installer and select the new macOS from Open Core's boot-picker
9. Test the new macOS
10. You must boot your new macOS volume with the Open Core EFI, so continue to boot from your USB thumb drive to test the new macOS (at some point, you will want to install Open Core to your SSD's EFI using OCLP's "Build and Install Open Core")

You now have two macOS volumes: your original volume that works well for you and your new volume that you are testing. You can choose to boot either one (boot the original volume without Open Core and boot the new volume with Open Core). This method leaves your original volume untouched, so that you can easily revert to it if you need to. Having a Time Machine or other fully recoverable backup of your original volume is highly recommended before you start this experiment.

When you are happy with your new macOS and you no longer want to boot your new macOS using the USB thumb drive, "Build and Install Open Core" to your SSD

EDIT: I use this technique to boot multiple, unsupported versions of macOS on my Mac. This allows me to test a new version of macOS while I'm still using my original macOS for "production use." When I'm satisfied that the new version of macOS is working well, the new version of macOS becomes my "production" version and I retain the older version of macOS as a backup. I also use this technique whenever I want to make a major modification to my macOS configuration, so I may have two APFS volumes with the same version of macOS - one volume is my original, untouched volume and the other volume is my sandbox. If I screw up the sandbox, I delete the APFS volume and start over without screwing up my original volume.

EDIT2: Be careful if you migrate to a new macOS volume from a volume with Time Machine configured. The new macOS volume will have the same Time Machine settings, so if you are testing the new and old macOS volume, you may clobber your Time Machine backup from two macOS volumes.

EDIT3: If booting with a new Open Core EFI and/or switching from one version of macOS to another, I've found it helpful to Reset NVRAM before booting with the new EFI and/or macOS. Upon booting with Open Core, tap space bar to show extended OC boot menu and select "Reset NVRAM." Then boot with new OC EFI / macOS.

EDIT4: Unless you know what you're doing, having High Sierra (or older) on the same physical disk as Big Sur or newer macOS will cause problems. You can search for technical details about this. If you need access to High Sierra or older macOS while you are testing/using Big Sur or newer, keep the old and new macOS versions on different physical disks. This may require you to physically swap physical disks depending on your Mac/configuration. If you need 32-bit apps, you may have success with macOS Mojave which can be installed on the same physical disk as Big Sur and newer.

 

[stephengrenfell]

I have had no problems using MA from TM or from another macOS volume as part of the creation of a new macOS Volume. I always perform the MA as the last step of a clean macOS install to a new APFS volume. Never any problems. I think where you have problems is if you try to use MA into a macOS volume to which you have already applied OCLP post-install patches.

I use Time Machine on every single one of my OCLP Macs without an issue.

Like deeeedee says, using Migration Assistant on a clean macOS install has worked every single time, but if I try to MA after I've gone through initial setup it has failed every single time. I have one MBP that has needed to be redone several times for one reason or another and it's only been the last couple that I realized/remembered the right order to do the MA portion.

OK thanks for your replies.

 

[stephengrenfell]

I have upgraded my iMac 12.2 (with metal capable GPU GTX780M) from OCLP 0.3.1 Bug Sur 11.3 to OCLP 1.0.1 Ventura 13.6

Everything seems to work fine, except that I keep getting two pop-up error messages.

What can I do to solve this ?.

Thanks