macOS 13 Ventura on Unsupported Macs Thread

[Dilli]

Hello!!
I installed Ventura in my mac mini 5.1 and all works EXCEPT the "Settings". When I open the "OS Settings" all is "black-blinded". I applied patch succesfullly 3 times or more and I've tried some different options and the result is the same. All working and fast EXCEPT os setting, so, I can't manage my system properly. The chipset is INTEL SANDY BRIDGE HD3000 (and with OpenCore 6.1, theorically is supported)

Under your settings & display : Some how use tab+spacebar to select right corner of 3rd black bar or use your mouse and then change the display setting from "color display" to "unknown display" . This will bring back the settings & toggles.
Scroll back few pages to see my earlier post with screenshots

 

[tejljr]

I just installed macOS 13.2.1 on my MacBookPro 7,1 and I get this message when trying to install the root patches. I’m connected to Ethernet. I looked for the KDKs but only KDK 13.2 and 13.3 are there. Which one should I use?

 

[Dilli]

View attachment 2163070

I just installed macOS 13.2.1 on my MacBookPro 7,1 and I get this message when trying to install the root patches. I’m connected to Ethernet. I looked for the KDKs but only KDK 13.2 and 13.3 are there. Which one should I use?

use the 13.2

 

[Dilli]

A strange bug is discovered. When the macbook air is put to sleep overnight and awake from sleep next morning I see Safari dock icon showing the small indication dot of running in background. I have always shut my apps before putting the mac book to sleep. I even checked the startup login items and nothing is there. I am on 13.2.1🥺 Just thought to point it out. cheers

 

[tejljr]

use the 13.2

It’s still saying it cannot find the KDK even though it’s installed locally.

 

[davidlv]

It’s still saying it cannot find the KDK even though it’s installed locally.

Delete the /Library/Developers/KDKs folder, reinstall OCLP to disk, and reboot,
Run the root patch again
If that doesn't work, you may need to use the MountEFI utility available on Github
to delete everything in the EFI partition, and reinstall OCLP

GitHub - corpnewt/MountEFI: An even more robust edition of my previous MountEFI scripts

An even more robust edition of my previous MountEFI scripts - corpnewt/MountEFI

github.com

 

[tejljr]

Delete the /Library/Developers/KDKs folder, reinstall OCLP to disk, and reboot,
Run the root patch again
If that doesn't work, you may need to use the MountEFI utility available on Github
to delete everything in the EFI partition, and reinstall OCLP

GitHub - corpnewt/MountEFI: An even more robust edition of my previous MountEFI scripts

An even more robust edition of my previous MountEFI scripts - corpnewt/MountEFI

github.com

Failed.

 

[davidlv]

Failed.

You haven't said which version of OCLP you are using, can you download the latest 0.6.2 nightly and try that?
I had problems running Monterey on a MBP 8,2 from late 2011. It was just too slow, but it did run Big Sur well enough.
Might give that a try. While it is possible to get it running, Ventura may be too much for that old hardware. Just a suggestion.

 

[nastiliano]

Everything works that I can tell. There is just a lag with everything else.

SOLVED, thanks:

Working Around Non-Metal Issues | OpenCore Legacy Patcher

 

[nastiliano]

Hello everyone!!
I installed Ventura in my mac mini 5.1 and all works EXCEPT the "Settings". When I open the "OS Settings" all is "black-blinded". I applied patch succesfullly 3 times or more and I've tried some different options and the result is the same. All working and fast EXCEPT os setting, so, I can't manage my system properly. . Thechipset is INTEL SANDY BRIDGE HD3000 (and with OpenCore 6.1, theorically is supported)

SOLVED:

Working Around Non-Metal Issues | OpenCore Legacy Patcher

 

[rbart]

Hi all. I have a particular question with running Ventura on a 2015 iMac 27, iMac 17,1
I have successfully installed Ventura 13.2.1 on the aforementioned iMac using OCLP 0.6.1. MacOS Ventura, OCLP and all apps were "freshly" downloaded directly from the developers' websites and freshly installed. No other applications other than Chrome, Brave and Opera were installed.The installation was uneventful and everything is running well except for Google Chrome and its "derivative" browsers. (By derivative browsers I mean those that seem to have been derived from Chrome... specifically, I mean Brave and Opera. All three of these browsers are extremely slow to launch. When I launch either of these browsers, a white window opens up with no menu bar. The window remains white for pretty well exactly 50 seconds. After this prolonged wait, the browsers function and all is well. Other browsers (I have tried Firefox and Safari) run fine. My iMac is the 3.3GHz version running the Intel i5-6600 and the AMD R9 M395 GPU with 2GB VRAM. The computer is running 16GB of RAM (4x4GB). I have divided the 2.12GB Fusion Drive into its component drives (128GB Apple SSD and 2TB Hard Drive). I have tried installing the OS separately on the SSD and on the HD. Both installations result in the same lag time. It is interesting to note that I have installed the same OS with the same version of OCLP on a 2013 iMac 27 and the problem has not occurred there. Does anyone have any insights or solutions?

It's a know issue of OCLP with Mac that use AMD GPU.
It doesn't support hardware HEVC decoder.
So you have such issues with some apps (Chrome, VMWare fusion, Photos ...)
It's very annoying, I am not sure OCLP developers will be able to fix this as they used old AMD drivers that are not fully compatible with Ventura.
I have rolled back to Monterey until we have good news on these problems.

 

[hyperions]

Temperature is not your problem, but I think you have to replace or reconnect that temperature sensor or your CPU will remain as slow as it currently runs.
You could try Intel Power Gadget in order to monitor your actual CPU clock speed - although I don't know whether that will still work in Ventura. In case that tool always shows the same low CPU frequency for all cores, you know that the missing temperature sensor might be the reason.

hi... I probably found another method to understand the frequency of the processor at which it works ... with the "sudo powermetrics" command in the terminal ... below the screen ... that value of 1600mhz and at 59.26% has to do possibly with limited CPU workload? i have imac21 2011 i5 2.7ghz...

 

[chris1111]

On Kepler GT 710 black screen after update to latest Beta Ventura
only way to boot is nv_diable=1

I also try removing the GT 710 then using Internal HD 3000 graphics but Root patched is blank, I cannot click on?
Dell Optiplex 790, i5 2500k

@khronokernel​

please add a future which allows to know if it is a Hackintosh so that the root patch is selectable because I see on other site that this problem happens and no solution is possible
thanks

 

[Dastane]

Hello evry one
I have imac 2011 27" ( 12.2) i7 with nvidia Kepler 1100m montrey os
When trying to install ventura i getter this

 

[Dastane]

 

[deeveedee]

please add a future which allows to know if it is a Hackintosh so that the root patch is selectable because I see on other site that this problem happens and no solution is possible
thanks

Maybe I'm oversimplifying this problem, but have you tried selecting OCLP Settings, changing the SMBIOS Model and returning to the main menu?

Spoiler: Select OCLP Settings

Spoiler: Change SMBIOS Model

Spoiler: Return to Main Menu

@chris1111 Correct me if I'm wrong, but this forum is typically for real Macs. Over at InsanelyMac, we're using OCLP for hacks. You can view this thread and my thread for some ideas. The OCLP developers have made it very clear that they are only supporting OCLP on real Macs, so we're on our own for hack solutions.

 

[tejljr]

You haven't said which version of OCLP you are using, can you download the latest 0.6.2 nightly and try that?
I had problems running Monterey on a MBP 8,2 from late 2011. It was just too slow, but it did run Big Sur well enough.
Might give that a try. While it is possible to get it running, Ventura may be too much for that old hardware. Just a suggestion.

OCLP 0.6.1 on MBP 7,1

 

[tejljr]

View attachment 2163185

I got that same error when upgrading. A SMC/NVRAM reset helped for me. If that doesn’t work, it could be either a bad USB installer or you may have to format your drive to macOS Extended Journaled

 

[perez987]

BTW, as for OCLP 0.6.2, it has been stationary for two weeks, now (while previously there were continuous, almost daily updates):
Hopefully, the project is still alive and well…

Of course it’s alive. We are talking of 2 weeks without updates in Github. Not too long. Developers sometimes are busy (work, school, etc.).

 

[Dilli]

F

View attachment 2163185

Format your ssd drive as macOS extended journled and try again

 

[cantaloop]

View attachment 2163070

I just installed macOS 13.2.1 on my MacBookPro 7,1 and I get this message when trying to install the root patches. I’m connected to Ethernet. I looked for the KDKs but only KDK 13.2 and 13.3 are there. Which one should I use?

Had the same thing with mine.
Just use OCLP 0.6.2 nightly with KDBK integrated. Solved it for me.

 

[davidlv]

F


Format your ssd drive as macOS extended journled and try again

I think that should be "format your USB drive to macOS HFS+ GUID" and try again. The target SSD should be APFS.
Correct?

 

[webg3]

View attachment 2163070

I just installed macOS 13.2.1 on my MacBookPro 7,1 and I get this message when trying to install the root patches. I’m connected to Ethernet. I looked for the KDKs but only KDK 13.2 and 13.3 are there. Which one should I use?

KDK Is it only necessary in the pre-metal models?

in Air 2012 did not download this pack

only MBP 2010

 

[Dastane]

I got that same error when upgrading. A SMC/NVRAM reset helped for me. If that doesn’t work, it could be either a bad USB installer or you may have to format your drive to macOS Extended Journaled

i do them all but same think....

F


Format your ssd drive as macOS extended journled and try again

as davidlv says, the ssd should be APFS

I think that should be "format your USB drive to macOS HFS+ GUID" and try again. The target SSD should be APFS.
Correct?

the usb key is recognized by the mac


....the problem is still present

 

[hvds]

KDK Is it only necessary in the pre-metal models?

in Air 2012 did not download this pack

only MBP 2010

KDK loading is done to obtain the kmutil functionality which is no longer contained in the system. kmutil is used to make new kernel caches.
OCLP tries to avoid KDK loading where possible and also has some „KDK-less“ functioning implemented for that.
So normally KDK should be necessary when kexts are replaced on the root volume, but with exceptions - and these I don‘t know but should be in the sys-patch.py etc sources. Apart from non-metal, also changed wlan (and more) could need KDK.
I‘m sure others can improve my amateur knowlede written down here.

With macOS Ventura, you will also need to install the KDK onto root if you plan to use kmutil
	# This is because Apple removed on-disk binaries (ref: https://github.com/dortania/OpenCore-Legacy-Patcher/issues/998)
	# 'sudo ditto /Library/Developer/KDKs/<KDK Version>/System /System/Volumes/Update/mnt1/System'