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
OCLP Developers - I'm reporting this in case this helps you to isolate an issue with OCLP.
When I enable "System Preferences > Accessibility > Display > Reduce Transparency" in Big Sur 11.7.6 ("Reduce Transparency" is a setting I would enable to improve graphics performance when using DosDude's patcher on my MBP6,2 running Catalina), Finder kept crashing and my system was unusable. I need to leave "Reduce Transparency" disabled when running Big Sur.
When I enable "System Preferences > Accessibility > Display > Reduce Transparency" in Big Sur 11.7.6 ("Reduce Transparency" is a setting I would enable to improve graphics performance when using DosDude's patcher on my MBP6,2 running Catalina), Finder kept crashing and my system was unusable. I need to leave "Reduce Transparency" disabled when running Big Sur.
I would uninstall all your Symantec anti-malware/internet security software and try again.
Similar experience/outcome as 22F62, LS working but Apple TV not playing videos/streams.
Several people, as well as Alfon_sico, have asked that same question several times over the last several months, and some seemingly can't understand that making a CCC backup (or equivalent) and using that backup after wiping the disk will ensure that the data is preserved. Considering the time used to ask that question over and over again, and ponder the many answers saying "no, unfortunately," making that backup would also be time saving.
That answer, "No" has been posted by at least two members who are directly associated with the development of OCLP, so I consider that answer to be correct and not just someone's imagination.
Can someone correct me about this? I thought that if you have a Time Machine backup of 13.3.1, you should be able to install 13.2.1 to a new APFS volume and then Migrate Data/Apps from the 13.3.1 Time machine backup to the new 13.2.1 Volume.
I second your question, as my MBP4,1 running Ventura 13.3.1 crashes on Sleep (Nvidia driver related kernel panic). Maybe using the web driver wold solve this serious problem?
I'll use my MBP13 mid2012 as a daily driver for common tasks. Sometimes there are lags, but I consider those minor and linked to workload on "old" hardware. At times there are heaps of processes running at the same time like indexing etc, that temporarily take up all the capacity.
Does Wi-Fi/Bluetooth work? Yes. I also never experienced issues issues with using the keyboard or trackpad in 13.3.1.
Is it worth installing it? Depending on what you need to do and Ventura is necessary, yes.
16gb are usually completely in use on this machine. RAM doesn't necessarily makes it faster, but it for sure makes the machine not running slower (less swaps). I did create a second volume (add AFPS container) and installed 13.4b using 0.6.5 which also runs without any issues. I don't use any specific software though, that would push the hardware to its limits. From my own experience, I wouldn't expect the SSD to run way faster than it does now, however that also varies depending on the build.
Using beta versions and issues that could happen during the testing phase, I needed to restore from a Time Machine backup sometimes in order to perform a downgrade. So make sure you got at least on recent working backup at hand in case and an uptodate bootable USB stick with the latest version installed.
Last edited:
Yes, that should work. The reason is simple; from the perspective of the installer application, there is no difference between a new APFS Volume and a wiped APFS Volume. Of course, you must be working with a disk that has enough space free to complete the install. Deleting the original volume to gain some space could be advisable too if space is limited. In essence, this whole process is not going to save time or effort, which is what that poster was looking for.
I have a lot of problems (it was crashing) with my MacMini 7.1.
Therefore, yesterday I wiped the disk and installed Ventura from the scratch using OLCP 6.5
After the installation it seemed that my problems were resolved. Worked about 4 h without hiccup.
Therefore I left the machine running over night to complete the synchronisation from iCloud.
This morning, I tried to use the machine but it did not respond anymore.
Rebooting the machine, resulted into a screen where the progress bar stopped halfway.
I also tried to boot the EFI from the usb stick, but the same result.
It is so sad, that the machine is not usable anymore.
Now I am considering to install MacOS 12 which is still supported by Apple.
I also noted that I do not get the chime at the beginning of the boot.
But before doing so, the question to the developer of the patch, is there a trick to recover my macMini?
Therefore, yesterday I wiped the disk and installed Ventura from the scratch using OLCP 6.5
After the installation it seemed that my problems were resolved. Worked about 4 h without hiccup.
Therefore I left the machine running over night to complete the synchronisation from iCloud.
This morning, I tried to use the machine but it did not respond anymore.
Rebooting the machine, resulted into a screen where the progress bar stopped halfway.
I also tried to boot the EFI from the usb stick, but the same result.
It is so sad, that the machine is not usable anymore.
Now I am considering to install MacOS 12 which is still supported by Apple.
I also noted that I do not get the chime at the beginning of the boot.
But before doing so, the question to the developer of the patch, is there a trick to recover my macMini?
Last edited:
Not sure if someone recommended this but setting Feature Unlock to partially enabled in OCLP settings and rebuilding your EFI might help you with those crashes
Reporting my webdriver experiment results here in case they help someone else: I attempted to install NVidia WebDrivers (387.10.10.10.40.140) on my MBP6,2 (NVidia Tesla) running Ventura 13.3.1 and patched with OCLP 0.6.5. I used CorpNewt's Web-Driver-Toolkit here. The patched webdriver installation started and appeared to be running fine until the last step, where the driver install failed. I ran OCLP 0.6.5 to repatch and OCLP reported the removal of the web patches, so the webdrivers were at least partially installed.
I do not understand this. Feature Unlock was enabled and the following features have been check marked.
NVMePowermanagement, Content Caching and APFS Trim. The rest was unchecked.
What should I further disable or enable?
Set Feature Unlock to partially enabled or disabled instead of enabled, don't forget to re-run build and install OpenCore.
@educovas and @Marty56 - this is an example of where treating OCLP like a black box without understanding Open Core may not be best for the end user (just my opinion). You can achieve the "partial unlock" by adding boot-args to your config.plist (see FeatureUnlock documentation here). You can disable FeatureUnlock.kext by disabling its associated "Kernel > Add" entry in your OC config.plist. Without knowing your level of understanding of Open Core, I don't know if that helps you. Does that help? I think that at some point, regardless of how "set it and forget it" OCLP attempts to be, knowing how it works and what it does is helpful.
Talking about Nvidia drivers… many, many Nvidia problems have been solved, in these months: a really great work by the devs! One however still remains, at least in my case: some windows still won’t show up in Acronis Cyber Protect Home Office (ACPHO) for Mac, such as the setup windows and also some other ones (while using the app). I remember that once, as an experiment, I installed the (non-Metal) Nvidia web drivers, which strangely cured the problem; but of course they cannot be used as ordinary drivers on my Metal MBP11,3. Someone suggested to fix the problem by myself: but that’s of course not an option, as I’m not practical with modifying kernel extensions and similar things. Does anyone know why this problem still exists, with ACPHO and the Metal Intel/Nvidia drivers…? Just curious about why some windows won’t show up. BTW, the problem persists also if one switches to iGPU-only or dGPU-only, besides with the normal automatic switching; the only way to set up the program is to start in safe mode and do it from there, where all windows show up normally, albeit very slowly. (On my MBP11,1, without root patches, everything works: all windows show up correctly…)
* How it appears (no setup window above the main one, which also becomes grey):
* How it should appear (with setup window; image taken from the web and a Windows setup, but it’s quite similar on the Mac):
* How it appears (no setup window above the main one, which also becomes grey):
* How it should appear (with setup window; image taken from the web and a Windows setup, but it’s quite similar on the Mac):
Last edited:
Not every user knows how to edit the config.plist, that's why I'm recommending the OCLP GUI way
No: it has never worked, neither in Monterey nor in Ventura, with any OCLP version - very strange… Do they maybe use some special, non-standard windows…? This ACPHO window glitch was absent only in (natively supported) Big Sur: i.e., without applying root patches…
I think Kepler has some rendering issues since early Monterey with Xcode, maybe it's a similar problem
Yes, you are right. This technology is only usable for nerds who want to spend much of their life time fiddling around on old machines to save a few bugs.
I took your advice and switch back to Monterey and will use it until Apple stopps providing security updates.
Then I will buy a new macMini which is not too expensive and avoid frustration on having achieved nothing after spending a weekend on this stuff.