macOS 13 Ventura on Unsupported Macs Thread

[deeveedee]

@davidlv & @Toby Goodbar - I'd have been surprised if deleting the contents of EFI and rebuilding/installing OpenCore EFI would have fixed the problem. The EFI contains none of the post-install root patches for NVidia Tesla. The only way I have recovered from a similar condition is the following:

1. Try using OCLP to "Revert Root Patches" and then reinstall root patches
2. If #1 doesn't work, create a new APFS volume and use a USB installer (with Open Core EFI) to install macOS to the new APFS volume. Migrate data/apps to the new macOS volume from the old (non-working).

 

[davidlv]

@davidlv & @Toby Goodbar - I'd have been surprised if deleting the contents of EFI and rebuilding/installing OpenCore EFI would have fixed the problem. The EFI contains none of the post-install root patches for NVidia Tesla. The only way I have recovered from a similar condition is the following:

1. Try using OCLP to "Revert Root Patches" and then reinstall root patches
2. If #1 doesn't work, create a new APFS volume and use a USB installer (with Open Core EFI) to install macOS to the new APFS volume. Migrate data/apps to the new macOS volume from the old (non-working).

@deeveedee You may very well be right. In the past, I did delete the EFI content, zapped the pram and probably reinstalled the root patches on my iMac 15,1 to get it working again. But considering that the target hardware is completely different, @Toby Goodbar would be best advised to at least try your suggestion.
In a completely different situation, the latest AMFIPass version of OCLP resolved an issue I had with that iMac after dumping the Ventura 13.5 beta and trying to reinstall 13.4.1. At first nothing worked, but in the end, installing Monterey and then updating to Ventura OTA with the AMFIPass OCLP installed resolved everything and it saved at least 6GB of space on the limited 128 Apple SSD blade (remmanant of a 1TB Fusion drive).

 

[MacinMan]

I don't really use my Mac to watch videos, but I don't want to have issues with video content (on internet) or slow or buggy apps because they don't have access to HEVC decoder.
For the moment, I keep Ventura on a second partition for Xcode 14.3+ needs and keep Monterey as main system
Except this very annoying HEVC problem, all seems smooth and solid on Ventura, thanks to OCLP developers !

I respect what you do for your own system, but my question was, can I disable HEV support on my system since I don't need it I want to know what my options are for my own system, not someone else's preferences in this situation. Thank You

 

[MacinMan]

Too bad about that! Have you tried to install Big Sur? I assume that is compatible with your MBP (it is according to MacTracker and this site

macOS compatibility: Here's the latest version your Mac can run

Find out what version of macOS your Mac can run with our macOS compatibility checker & which version of macOS is best for your Mac

www.macworld.com

I've made the mistake of loosing open core booting in the past when doing a PRAM reset. I easily got it back by holding option on boot and reselecting the OpenCore boot loader. This post sounds like what happened to me, so that's why i'm offering this suggestion.

 

[coasterOneEightThree]

I use the screen capture app Telestream ScreenFlow 10.0.9 (31959). Every QuickTime movie shot on my iPhone and imported into ScreenFlow is completely black when playing. Outside of ScreenFlow the .mov file looks and plays as expected. Could this be an issue with the NVIDIA Kepler patches (using the newest nightly build of version 0.6.8)? This worked until recently.

 

[Sven G]

After having used the OCLP AMFIPass beta (now on b4) for some time, everything seems well, on both my MBPs (11,3 and 11,1): let’s hope that it will soon be merged into the main branch; and also that some research can then be done on an IMHO very important feature: that is, to be able to enable SIP as much as possible, on root patched machines, also on Ventura and Sonoma (the maximum fully working configuration on my MBP11,3, so far, has been 0x800, with SIP fully enabled but SSV disabled; but only up to Monterey: on Ventura, it still mandatorily requires the default 0x803)…

 

[MacinMan]

After doing some thinking, I've decided to really take advantage of having an older mac. Rather than focusing on installing OCLP, and running Ventura, I've decided to install a copy of Mojave. I have a few games I still want to have around that were never upgraded to run in 64-bit, and because they require 3D graphics acceleration, a VM won't work. Windows would work in a VM for them, but that would just introduce extra overhead than just running Mojave on bare metal.

 

[deeveedee]

IMHO very important feature: i.e., enabling SIP as much as possible, also on Ventura (the maximum working configuration so far has been 0x800 - with SIP fully enabled but SSV disabled, - but only up to Monterey)…

I would think that the ability to more fully enable SIP would depend on the Mac identifier / graphics (maybe with a new Wi-Fi patch). My MBP6,2 currently needs NVidia kexts, so bit 1 (ALLOW_UNTRUSTED_KEXTS) is currently required. Could OCLP Devs sign the NVidia kexts?

EDIT: I just found this and am reading it to learn more.

 

[K two]

The OCLP-Sonoma password B.S. is still being circulated. Reading and understanding the OCLP documention, fully reveals the Sonoma-centric version of OCLP is readily available w/o any limts whatsoever. The sole limit is ignorance and spreading counterproductive B.S. on these forums.🤨

 

[luckyduke23]

Hi Folks, I was not reading here for quite a while. So please don't kill me if this issue was already handled

A week ago I have updated to MacOS 13.4.1 and also finally from OCLP 0.6.6 to 0.6.7. All works fine but
I recognized an update issue with OCLP. When using OCLP's internal update feature something goes wrong. The whole process seemed to work fine including application and post patching. But when I then opened OCLP I was still on version 0.6.6. instead of 0.6.7. So I download 0.6.7 directly from GitHub and after installation, application and post patch I really was on version 0.6.7 finally. I did not put much attention to this issue but now that my brother had same problem today, I tried to submit an issue report on GitHub. But presently no new issues are accepted. So if this issue is still unknown to the majority, I hope one of the developers will read this.

 

[rehkram]

Hi Folks, I was not reading here for quite a while. So please don't kill me if this issue was already handled

A week ago I have updated to MacOS 13.4.1 and also finally from OCLP 0.6.6 to 0.6.7. All works fine but
I recognized an update issue with OCLP. When using OCLP's internal update feature something goes wrong. The whole process seemed to work fine including application and post patching. But when I then opened OCLP I was still on version 0.6.6. instead of 0.6.7. So I download 0.6.7 directly from GitHub and after installation, application and post patch I really was on version 0.6.7 finally. I did not put much attention to this issue but now that my brother had same problem today, I tried to submit an issue report on GitHub. But presently no new issues are accepted. So if this issue is still unknown to the majority, I hope one of the developers will read this.

The answer is that the OCLP GUI app from 0.6.7 and upwards does not reside in /Applications anymore, you need to create an alias to it in /Applications pointing to its new location.

You only have to create the alias once; future releases of OCLP should just work out of the box, which will be much better. See this Mr Macintosh video for the full explanation and how to set it up.

 

[davidlv]

The answer is that the OCLP GUI app from 0.6.7 and upwards does not reside in /Applications anymore, you need to create an alias to it in /Applications pointing to its new location.

You only have to create the alias once; future releases of OCLP should just work out of the box, which will be much better. See this Mr Macintosh video for the full explanation and how to set it up.

That explanation is correct, except for the lack of a new location. In short, the OCLP application should reside in Library/Application Support/Dortania.
Install it there and make an alias to it, and put that alias in the /Applications folder.

 

[ElSooz]

Hello; I just want to report (in case it is useful to anybody) that every few days I come in and find my Mac unresponsive with the keyboard hot and have to power-cycle to regain access. Find below a snippet of the the panic log with the complete log attached also. Apparently WindowServer is the culprit. Does anyone have thoughts on this?

MacBookPro11,3 (15”, late 2013): OCLP amfipass-b4 + macOS 13.4 Ventura (root patched for Intel Haswell and Nvidia Kepler);

panic(cpu 2 caller 0xffffff801db79941): userspace watchdog timeout: no successful checkins from WindowServer in 120 seconds
WindowServer has not exited since first loaded
service: logd, total successful checkins in 79439 seconds: 7909, last successful checkin: 0 seconds ago
service: WindowServer, total successful checkins in 79297 seconds: 7893, last successful checkin: 120 seconds ago
service: opendirectoryd, total successful checkins in 79439 seconds: 7908, last successful checkin: 0 seconds ago
service: configd, total successful checkins in 79439 seconds: 7908, last successful checkin: 0 seconds ago

 

[davidlv]

Hello; I just want to report (in case it is useful to anybody) that every few days I come in and find my Mac unresponsive with the keyboard hot and have to power-cycle to regain access. Find below a snippet of the the panic log with the complete log attached also. Apparently WindowServer is the culprit. Does anyone have thoughts on this?

MacBookPro11,3 (15”, late 2013): OCLP amfipass-b4 + macOS 13.4 Ventura (root patched for Intel Haswell and Nvidia Kepler);

panic(cpu 2 caller 0xffffff801db79941): userspace watchdog timeout: no successful checkins from WindowServer in 120 seconds
WindowServer has not exited since first loaded
service: logd, total successful checkins in 79439 seconds: 7909, last successful checkin: 0 seconds ago
service: WindowServer, total successful checkins in 79297 seconds: 7893, last successful checkin: 120 seconds ago
service: opendirectoryd, total successful checkins in 79439 seconds: 7908, last successful checkin: 0 seconds ago
service: configd, total successful checkins in 79439 seconds: 7908, last successful checkin: 0 seconds ago

You might report this to the Discord channel for the AMFIPass version;

Release AMFIPass Beta Test · dortania/OpenCore-Legacy-Patcher

AMFIPass Public Beta Test READ THE WHOLE THING FIRST Hello testers! I am proud to announce that we will now be opening a public beta test for a build of OCLP that adds AMFIPass¹ - a way to use your...

github.com

 

[DaveMac1]

Deleted

 

[Earl Urley]

Anyone running Ventura 13.4.1 on a 6,1 MP? I heard the race condition was fixed but there's still an issue with power consumption?

 

[amaze1499]

Update to 22G5059d done via OTA using 0.6.8n. No issues. Apple TV works. Weather freezes frequently but does not crash/close. I did not see any other issues for the time being.

 

[Earl Urley]

So, something weird happened the other day, I booted a 2015 rMBP with OCLP 0.6.7 and Ventura 13.4.1 installed, normal login, but when I get to the desktop, the Dock is stuttering when animating icons, and all of a sudden YouTube videos and protected HTTP sites like Max, Amazon Prime, and Tubi are refusing to play any videos, and Amazon Prime stops cold with an incompatible browser error.

I re-run OCLP and it tells me that the root patches were applied around the same time I updated to 13.4.1 from 13.4 so I just revert and re-run the root patches (for Intel Haswell.)

Reboot and everything is back to normal. I suppose it's possible for some other update to nerf the boot patches somehow?

 

[K two]

On this Mini7,1 w/OCLP068n-13.5b4 AppleTV still broken, Weather app MTLCompilerService crash remains, force quit required. These two bugs have been present since 13.4.🤨

 

[webg3]

Hello; I just want to report (in case it is useful to anybody) that every few days I come in and find my Mac unresponsive with the keyboard hot and have to power-cycle to regain access. Find below a snippet of the the panic log with the complete log attached also. Apparently WindowServer is the culprit. Does anyone have thoughts on this?

MacBookPro11,3 (15”, late 2013): OCLP amfipass-b4 + macOS 13.4 Ventura (root patched for Intel Haswell and Nvidia Kepler);

panic(cpu 2 caller 0xffffff801db79941): userspace watchdog timeout: no successful checkins from WindowServer in 120 seconds
WindowServer has not exited since first loaded
service: logd, total successful checkins in 79439 seconds: 7909, last successful checkin: 0 seconds ago
service: WindowServer, total successful checkins in 79297 seconds: 7893, last successful checkin: 120 seconds ago
service: opendirectoryd, total successful checkins in 79439 seconds: 7908, last successful checkin: 0 seconds ago
service: configd, total successful checkins in 79439 seconds: 7908, last successful checkin: 0 seconds ago

I share the same problems when using only OCLP (any version) with the latest updates, be it Big Sur, Monterey and Ventura.

Solution: add some kexts that OCLP doesn't have

AGPM-Override.kext
CPUFriend.kext
CPUFriendDataProvider.kext
HibernationFixup.kext
WhateverGreen.kext

 

[europlus]

Can you elaborate on that a little? It is not clear from your post, but we can assume you reverted back to OCLP 0.6.6 and left the post install root patches from 0.6.7. Right?
What are your sleep settings, Code: pmset -g
You might try hibernation mode 0, as shown below.
I have an iMac 15,1 that runs fine with these implemented, running 0.6.8n Ventura 13.5b3:
Code to run in terminal:
sudo pmset -a hibernatemode 0 standby 0 autopoweroff 0

sudo rm /private/var/vm/sleepimage
--Ignore any message saying there is no such file

Create a blanked zero-byte file so the OS cannot rewrite the file:

sudo touch /private/var/vm/sleepimage

Make file immutable:
(sudo chflags nouchg ... to revert)

sudo chflags uchg /private/var/vm/sleepimage

Apologies, real life is really getting in the way at the moment.

Yes, I "reverted back to OCLP 0.6.6 and left the post install root patches from 0.6.7", sorry that wasn't clearer.

Current sleep settings returned by pmset -g:

System-wide power settings:
Currently in use:
 standby              0
 Sleep On Power Button 1
 womp                 1
 halfdim              1
 hibernatefile        /var/vm/sleepimage
 powernap             0
 autorestart          1
 networkoversleep     0
 disksleep            0
 standbydelayhigh     86400
 sleep                0 (sleep prevented by FAHClient, sharingd, bluetoothd)
 autopoweroffdelay    28800
 hibernatemode        0
 autopoweroff         1
 ttyskeepawake        1
 displaysleep         20
 highstandbythreshold 50
 standbydelaylow      0

I had ⅔ of your suggested settings - I've implemented the other and will retry 0.6.7.

Thanks,

Sean

 

[JUANESVELEZ]

Hi all. Anybody knows why a Mac doesn't restart or shutdown? I have a MacbookPro 8.1 with Ventura and OPLC 0.6.7 and until yesterday everything worked flawlessly. Today I couldn't restarted or shutting down.

 

[ronton3]

Imac 27, late 2012, 3802

I made a stupid mistake in software update, and now have Sonoma beta 2 avaiable which I am not ready to experiment with. How can I get rid of this notification.

 

[davidlv]

Imac 27, late 2012, 3802

I made a stupid mistake in software update, and now have Sonoma beta 2 avaiable which I am not ready to experiment with. How can I get rid of this notification.

From Finder, go to /Users/Shared/, press Command, Shift and dot (⌘⇧.) to show hidden files,
delete the two beta-related files.

 

[ronton3]

I believe I am at the place you described but there are no beta files.