I just put Ventura on my 2012 Mac Mini and so far it seems to be running fine. I have 16 GB RAM, and wanted to mention that that is an easy and cheap upgrade - 16 GB cost me $18 on Amazon.
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
Another 2012 Mac-Mini with Ventura, with 'only' 8Gb of Ram. The performance is more related to the speed of a good SSD (Toshiba in my case) than the amount of memory. I have also a Macbook Pro 13" from 2012 with a little more capable cpu (i7 vs i5), but a slower SSD, and the performance of the Mini is far better in response time.
EDITED
Wake On Command utility (uses "Magic Packet"): Unable to get this little utility working at all. Wondering if anyone is able to use this with success?
Wake On Command utility (uses "Magic Packet"): Unable to get this little utility working at all. Wondering if anyone is able to use this with success?
WakeOnCommand
A simple utility that can send “magic packets” to wake up sleeping computers supporting Wake-on-LAN (also called Wake for network access in macOS). All you have to do is enter the IP address and MAC address of a computer, and then click the Wake button. WakeOnCommand will remember the...
apps.apple.com
Last edited:
I can’t say that I’ve noticed it on my 7,1 Mini, but as it’s shoved in the garage as a headless Plex server, it doesn’t get rebooted unless there’s a software update.I see exactly the same on the Mini7,1, 13.6.3, OCLP 1.3.0. Reinstalling the root patch fixes until the next reboot, tried a safe boot uninstall and re-install, NVRAM resets, you are not alone.
I decided to try using my OCLP Ventura USB installer, re-installing the Mac OS in that partition, and that fixed the problem! So at least I know I have a solution just in case that happens again, and it helps I have that smaller APSF volume with Monterey on the same SSD for such emergencies, like when the time comes where Ventura and OCLP get an update, I can format and update the USB installer with them.
I am having the same graphics issue. I noticed the whole laptop was so slugging and lagging. I thought it was an issue with failing SSD.
My Ventura was installed 2 months ago and it was working fine until I upgraded to OCLP 1.3.0. One day I noticed that my MacBook no longer shows the resolution of 1680 x 1050 (I recalled it worked)
Chanced upon this thread while trying to google for solutions and I tried to re-installed the root patches again and it is working better.
My Ventura was installed 2 months ago and it was working fine until I upgraded to OCLP 1.3.0. One day I noticed that my MacBook no longer shows the resolution of 1680 x 1050 (I recalled it worked)
Chanced upon this thread while trying to google for solutions and I tried to re-installed the root patches again and it is working better.
I've the same problem. The Motu audio interface is correctly see in system pref in the usb port but in sound system it's not seen. This happens after OCLP usb 1.1 patch.
Any solutions?
App Store and many apps not working after OCLP update.
I have OCLP for a long time in my Macbook Pro mid 2012. Today I did update it to 1.3.0 in my macOS Ventura 13.6. After that, App Store is failing in update my apps, and even worst, when trying to install the newer app version, will delete the previous one and I have no app no more! The little progress circle goes near closing before error message, so my guess App Store can't copy new files to Applications folder anymore, but I have no clue of how to fix it. Also Preview is crashing when opening, MAMP is not starting servers, don't know how those apps are related.
Thinking about revert macOS Ventura using an old Carbon Copy Cloner backup, but not sure if it will fix it...
I have OCLP for a long time in my Macbook Pro mid 2012. Today I did update it to 1.3.0 in my macOS Ventura 13.6. After that, App Store is failing in update my apps, and even worst, when trying to install the newer app version, will delete the previous one and I have no app no more! The little progress circle goes near closing before error message, so my guess App Store can't copy new files to Applications folder anymore, but I have no clue of how to fix it. Also Preview is crashing when opening, MAMP is not starting servers, don't know how those apps are related.
Thinking about revert macOS Ventura using an old Carbon Copy Cloner backup, but not sure if it will fix it...
On a early 2011 MacBook Pro 8,1 with a Kingston A400 480GB SSD drive. I was able to install Monterey 12.6.3 and OLPC 0.6.1 on it last year. It became sluggish. Applying OLPC 1.3.0 root patch did not help.
I tried upgrading to the latest Monterey 12.7.2, OCLP 1.3.0 and get the "A require firmware update cannot be installed".
I wipe the drive and reinstalled High Sierra 10.12.6 (last version supported). This was successful. I try upgrading to Ventura 13.6.3, OCLP 1.3.0 again and get the same message of "A require firmware update cannot be installed". I tried doing the same process with Monterey 12.7.2 OLPC 1.3.0 and again with the same message of "A require firmware update cannot be installed".
Any ideas?
Note I was successful installing and running Ventura 13.6.3, OCLP 1.3.0 on a early 2009 iMac 9,1 with same type of Kingston A400 480GB SSD drive.
I tried upgrading to the latest Monterey 12.7.2, OCLP 1.3.0 and get the "A require firmware update cannot be installed".
I wipe the drive and reinstalled High Sierra 10.12.6 (last version supported). This was successful. I try upgrading to Ventura 13.6.3, OCLP 1.3.0 again and get the same message of "A require firmware update cannot be installed". I tried doing the same process with Monterey 12.7.2 OLPC 1.3.0 and again with the same message of "A require firmware update cannot be installed".
Any ideas?
Note I was successful installing and running Ventura 13.6.3, OCLP 1.3.0 on a early 2009 iMac 9,1 with same type of Kingston A400 480GB SSD drive.
Destiny has solved the problem for me. I realize my backup disk was attached so CCC overwrite the previous backup for the current problematic one. Not being able to move back, I decided to move forward and let the macOS update itself to Sonoma. And... voilá, everything back to normal!
Probably there is no reason to keep with Ventura if Sonoma is available now, time will tell...
Having High Sierra and OCLP on the same disk has never been recommended. This is an old issue primarily in the domain of non-Metal Macs and why OCLP support begins with Big Sur as OCLP disrupts SIP to function. A better and safer solution if actually neccessary is to keep High Sierra and OCLP on separate disks.
Having High Sierra and OCLP on the same disk has never been recommended. This is an old issue primarily in the domain of non-Metal Macs and why OCLP support begins with Big Sur as OCLP disrupts SIP to function. A better and safer solution if actually neccessary is to keep High Sierra and OCLP on separate disks.
The problem I posted about was not with having High Sierra on the same disk. Also High Sierra was booted natively.
Suggest you post this to the Paradise on Discord to receive proper attention. https://discord.gg/rqdPgH8xSN, here.
I was trying to get into this Discord thing a while ago, tbh that was way over my head and I have given up understanding how Discord works.
Feel free to post it there, linking to the thread I made.
The problem, the OS suddenly gets indicated by OC as High Sierra, getting the HS icon exists for quite a while, lets say years.
As it seems OC reads the
SystemConfig.plist of the OS' Preboot Volumes to indicate it.Where this is just cosmetical (I dont know if other settings are touched by this) the consequences for the booted OS are worse.
We discussed this here a year ago, and I posted details, providing a few lines of AppleScript to fix it.
Manually Configured OpenCore on the Mac Pro
observed a mad behaviour of High Sierra: it has overwritten SystemVersion.plist and PlatformSupport.plist in both my /Preboot volumes in Ventura and Monterey (being in the same container of another drive) (Noticed it by icons of Ventura and Monterey changed to High Sierra icons in OpenCore...
forums.macrumors.com
This is a confusing statement (for me). I think there are multiple things being confused in this statement:
- OCLP is not Open Core. OCLP installs Open Core in the EFI of a disk that is formatted with GUID partition map. OCLP is an app that runs in macOS.
- There is no problem with Open Core and High Sierra being installed on the same disk. The "old issue" is a potential conflict between High Sierra and macOS versions starting with Big Sur and newer.
Thanks to the developers. Finally worked up the courage to move from Monterey to Ventura on iMac 14,1 with OCLP 1.3.0. All is well.
So, OCLP is based on OpenCore, installs OpenCore, runs on OpenCore, to separate the two in this context is indeed mysterious. APFS corruptions between High Sierra APFS versions and later versions is a well-documented fact, as you point out. OCLP merely enables it to happen. 🧐
It may be that we are simply using different terminology. OCLP is not based on OpenCore - it is a python app. OCLP does not run on OpenCore, it is an app that runs in macOS. The hackintosh community has been using Open Core without OCLP for longer than most in this unsupported thread have known about OCLP, so separating the two is normal for most who use Open Core. OCLP is an Open Core configurator and a root patcher for macOS. Many in the hackintosh community use OCLP only to apply root patches while they build their own custom Open Core EFI (without using OCLP). Many use OCAT (another Open Core configurator) to build their Open Core EFI while they use OCLP to apply root patches, so they use two utilities to configure their hacks, neither of which is "based on OpenCore" and neither of which "runs on OpenCore." If "based on OpenCore" means that the utility configures OpenCore, then I agree.
My point was that your original statement "High Sierra and OCLP on the same disk has never been recommended" is incorrect. In my hackintosh, I have High Sierra and Open Core and OCLP on the same disk without problems, while Big Sur, Monterey, Ventura and Sonoma are on another disk - no problems.
Last edited:
Need more info. Mac model, versions of macOS and OCLP installed?? 🤷♂️I am having sluggish performance and frequent freezes for 1-2 seconds before it resumes.... no idea what is wrong
@5354 I, too, am amazed by the mind-reading skills of the experts in this forum, but even they may have difficulty with a diagnosis given the level of detail that you provided. If you don't get a solution from someone, you may want to provide some basic info like
- Your Mac Model identifier (e.g., MP5,1)
- The exact version of macOS (e.g. Ventura 13.6.3)
- The version of OCLP that you used to "Build and Install Open Core" and to apply post-install patches
- What was the last version of macOS that you ran without these symptoms?
- Did you perform an upgrade from a previous macOS (if so, which previous version) or a clean install of macOS?
Good morning,
I'm experiencing a strange situation with OCLP 0.68 and Ventura 13.6.3. if I try to print any document with the Epson ET-2711 printer each page takes about 10/15 minutes (when it finishes). So far nothing to worry about, apparently it can be overcome by reinstalling the drivers and with other various tests. The thing I really don't understand is that by launching printing from Windows 11 (run with WMware) which uses the built-in drivers (not downloaded ad hoc from the Epson website) the printer works divinely. At this point I assumed that there might be some problems with managing the print spool. Have any of you ever had similar experiences using OCLP?
Thanks for the attention
Warm regards
Alessandro
I'm experiencing a strange situation with OCLP 0.68 and Ventura 13.6.3. if I try to print any document with the Epson ET-2711 printer each page takes about 10/15 minutes (when it finishes). So far nothing to worry about, apparently it can be overcome by reinstalling the drivers and with other various tests. The thing I really don't understand is that by launching printing from Windows 11 (run with WMware) which uses the built-in drivers (not downloaded ad hoc from the Epson website) the printer works divinely. At this point I assumed that there might be some problems with managing the print spool. Have any of you ever had similar experiences using OCLP?
Thanks for the attention
Warm regards
Alessandro