Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.

user853

macrumors newbie
Aug 8, 2024
8
5
Paravirtualization is 3D acceleration for macOS guests, so while you may not want it for third party operating systems, you're still dealing with it. My situation may, or may not be the same as yours though. For me, VMs were a way to deal with macOS dropping 32-bit support in terms of games. So, I would either need to run a windows VM, or Linux and 3D acceleration was necessary for graphics to work correctly. With open core, that's no longer possible, and future versions of VMware start with Ventura or newer for support now. So the only work around I was able to find in this situation was to install Linux on an external drive and run steam and use Proton for the windows games I want to play. Sonoma works well on this iMac with Open core, and the pro apps seem to work. I did test a macOS VM on this iMac a while back under Sonoma / OCLP, and paravirtualization worked. However third party 3D acceleration didn't. the machine would boot and then go to a black screen. If you check out the Sequoia thread, there was talk there about paravirtualization working in Paralells, so that might be worth you looking into to see if that will work for you.
Thx MacinMan!
"Paravirtualization is 3D acceleration for macOS guests" - is not true, sorry.

In general terms, very simplistically, this is a technology that provides an API for the hardware of guest virtual machines. (https://en.wikipedia.org/wiki/Virtualization#Paravirtualization)

The OCLP team clarified in their comment ( https://github.com/dortania/OpenCore-Legacy-Patcher/issues/1008 ) that this technology does not work in Sonoma and a rollback to Ventura is required. This was the reason for my initial question about the prospects.

1726316310218.png
 

MacinMan

macrumors 65816
Jan 27, 2011
1,379
787
Denham Springs, LA
Thx MacinMan!
"Paravirtualization is 3D acceleration for macOS guests" - is not true, sorry.

In general terms, very simplistically, this is a technology that provides an API for the hardware of guest virtual machines. (https://en.wikipedia.org/wiki/Virtualization#Paravirtualization)

The OCLP team clarified in their comment ( https://github.com/dortania/OpenCore-Legacy-Patcher/issues/1008 ) that this technology does not work in Sonoma and a rollback to Ventura is required. This was the reason for my initial question about the prospects.

View attachment 2417762
I forgot to include in my above post that. It works in Sonoma with an AMD GPU, but not on the Haswell machines. I have one of each. So, basically in my situation the two macs are reversed when running open core. Para works on the iMaac for macOS guests, while 3D acceleration for guests such as windows, Linux, etc does not. On the MBP Para doesn't work, but 3D for other guests does.

My above statement about parvirtualization is partially true, Without it enabled, macOS guests aren't 3D accelerated.

Anyway, I just tested the latest version of VMWare Fusion (13.6.0) on Sonoma, and it doesn't fix the issue with audio and latest Ubuntu/based Linux Distros.
 

MacinMan

macrumors 65816
Jan 27, 2011
1,379
787
Denham Springs, LA
FWIW I am running Parallels on my 2 Mac's
I've considered just doing away with virtual machines as a whole as my main need for them is gone since I got my dual boot set up. I did keep VMWare around though just in case i needed to set up quick test machine. I did read sometime back that Parallels works better than Fusion for certain things. I'm keeping my eye on the Sequoia thread as well, because things look good for macOS 15. Just waiting for things to be out of beta before trying it.
 

edweb

macrumors newbie
Aug 29, 2021
7
1
Greetings to you, Mac Gurus

iMac 18,3 running 13.6.9

Back in June I installed OCLP 1.5 and upgraded to 14.5; running well, no installation or running / configuration issues.

Turns out some programs no longer worked correctly thereafter (don't know why, either), so eventually decided to revert back to 13.6.9.

I thought I followed the uninstall process, also for OCLP. Now whenever I try to clear NVRAM I end up with "Initialization failed. Unable to run diagnostics. DEC 500" (see screenshot).

But running diagnostics reveals no issue / no problem to solve.

When rebooting with "Option" key it brings me to 2 boot options: EFIBoot (OCLP logo) and Macintosh HD.

Re-installing 13.6.9 doesn't do anything.

Looks like some OCLP files are still stuck somewhere on my system - can somebody please advise how to find them / get rid of them ?

Many thanks
 

Attachments

  • IMG_1332.jpg
    IMG_1332.jpg
    117.6 KB · Views: 25
  • IMG_1337.jpg
    IMG_1337.jpg
    229.5 KB · Views: 21
  • IMG_1338.jpg
    IMG_1338.jpg
    286.2 KB · Views: 21
  • IMG_1339.png
    IMG_1339.png
    1.5 MB · Views: 22
Last edited:

ponta pon pon

macrumors member
Oct 22, 2018
30
29
Hi,
(1) As First of all I did update my Mac (MBP 15'retina late 2013 with Kepler 11,3 , macOS 14.6.1, OCLP 1.5.0) to 15.0(24A335)RC via OTA under new OCLP 2.0.1.
(2) I did reboot and did post-root-patch. After that, MBP reboot. It could get back WiFi then MBP reboot.
(3) Then again I installed post-root-patch by a lot of downloaded packages with WiFi in few minutes and reboot once more. And then it shows a beautifully Login window and a normal a desktop!!

New wall papers , bluetooth , FaceTime with iPhone Continuity Camera seems all OK !

Thanks to OCLP Developers !!
 
Last edited:

OKonnel

macrumors 6502
Apr 16, 2009
360
655
Italy
God Sunday to everyone!
To celebrate the official release of OCLP 2.0.0 I would like to suggest that we send a little or great volunteer support to the amazing OCLP Team thanks to which our Macs are living a new life.

My invitation is ABSOLUTELY spontaneous and I felt moved to donate something what @khronokernel has continued to work hard despite having to undergo surgery.
[note: khronokernel himself broke the news, discreetly, so there is no violation of privacy. After all, the good Mykola Grymalyuk, aka khronokernel, published his resume himself and also has a transparent profile on LinkedIn].

I consider Mykola aka khronokernel equal or superior (in generosity) to the great dreamer Steve Jobs and wish him much good and happiness; to him and to all members of Team OCLP.

It would be a beautiful dream if Apple would come to realize that its value, human, scientific and consequently also economic, would increase a lot if Apple, for once, would refuse to cultivate in its heart only profit reasoning.
Apple owns billions of billions of dollars and could have do not excluded a great many Macs (certainly those from 2013 onward), from Big Sur to Sequoia. Perhaps Apple could have excluded all support and could have disclaimed any liability for unintentional damage caused to users with old Macs who accepted the terms; but it could have kept the drivers there and authorized their support for macOS, even after Catalina.

Steve Jobs, perhaps, would have realized that allowing this would enhance Apple's value… ESPECIALLY vis-à-vis Windows! Since so many people would switch to Macs upon seeing how powerful they are to run, after a decade, even better than when they were created. Exactly the opposite of all PCs and Windows.

So even if Apple closes its, we do not close our hearts.

Now come on guys, everyone donate!

IMG_4820.png
 

Dr Harkaput

macrumors newbie
Sep 11, 2024
4
7
I searched the thread for this issue but couldn't see if a solution exists. I have a Mac Mini 2012 with intel i7, 6 gb ram, and the Intel HD graphics 400 (that is supposed to have support for "Metal 2"). I have Sonoma installed and the Photos app crashes when clicking the "memories" album. I see people with dual gpus have solved it by choosing the "non-intel" gpu or unchecking automatic gpu-switch. Since my mac mini only has an intel gpu I can't find a solution. Any idea? Thanks.
This issue was resolved by updating to OCLP 2.0.
 

trickbox

macrumors newbie
Feb 24, 2008
22
7
Updated to OCP 2.0 this morning (2013 iMac running Sonoma 14.6.1) with no issue. With 2.0.1 and Sonoma 14.7, my attached Apple Cinema Display no longer connects and when plugged in the screen on the iMac goes black for a couple of seconds before coming back for about 5 seconds. This happens continuously in a loop. I think the system is trying to connect to the display, failing and restoring th iMac screen. Same thing is happening to the USB from the connected monitor. Trying to charge from this screen lasts a second before dropping. Only way to get the iMac to work is disconnect the monitor completely. I've tried resetting the PRAM and reinstalling OCP and the Root Patches to no avail. Not sure if the problem is with OCP 2.0.1 or Sonoma 14.7. Anyone else having this issue?
 

georgeimac

macrumors member
Jun 13, 2021
57
20
Updated to OCP 2.0 this morning (2013 iMac running Sonoma 14.6.1) with no issue. With 2.0.1 and Sonoma 14.7, my attached Apple Cinema Display no longer connects and when plugged in the screen on the iMac goes black for a couple of seconds before coming back for about 5 seconds. This happens continuously in a loop. I think the system is trying to connect to the display, failing and restoring th iMac screen. Same thing is happening to the USB from the connected monitor. Trying to charge from this screen lasts a second before dropping. Only way to get the iMac to work is disconnect the monitor completely. I've tried resetting the PRAM and reinstalling OCP and the Root Patches to no avail. Not sure if the problem is with OCP 2.0.1 or Sonoma 14.7. Anyone else having this issue?
I have not updated to 14.7, reluctant to do so at this time
 
Last edited:

Eriamjh1138@DAN

macrumors 6502a
Sep 16, 2007
941
1,027
BFE, MI
Updated to OCP 2.0 this morning (2013 iMac running Sonoma 14.6.1) with no issue. With 2.0.1 and Sonoma 14.7, my attached Apple Cinema Display no longer connects and when plugged in the screen on the iMac goes black for a couple of seconds before coming back for about 5 seconds. This happens continuously in a loop. I think the system is trying to connect to the display, failing and restoring th iMac screen. Same thing is happening to the USB from the connected monitor. Trying to charge from this screen lasts a second before dropping. Only way to get the iMac to work is disconnect the monitor completely. I've tried resetting the PRAM and reinstalling OCP and the Root Patches to no avail. Not sure if the problem is with OCP 2.0.1 or Sonoma 14.7. Anyone else having this issue?
Which iMac 2013? The late 2013 21.5 or the 27”?

i have a 27” iMac late 2013 14,2 model and use 1 or 2 30” cinema displays Via the thunderbolt ports and various adapters. if the CDs don’t work, I won’t update.
 

roysterdoyster

macrumors 6502
Jul 3, 2017
402
430
OTA update 14.6 -> 14.7 via OCLP 2.1.0n successful for MBP4,1 17-inch Early 2008, then successful update 14.7 -> 15.0. Fantastic ingenious software engineering by the devs. Kudos to them.
 
  • Like
Reactions: deeveedee

xboxbml

macrumors 6502a
Sep 15, 2015
539
177
Well, after spending 4 hours redownloading all my movies last saturday after reloading Monterey on this 15" 2015 MBP I went ahead and "upgraded" to Sequoia/OCLP 2.0.1 tonight. It works, just like Sonoma, but the same stupid issue exists with not being able to play Apple purchased movies on or with an external monitor connected, either on the OWC TB2 dock or directly to the HDMI port. What a PITA. I mean it's great and all and I know the devs are doing great work on this, but this really is a deal breaker for me. I have to be able to use the attached big monitor so I can use the built in for work/web etc. and the big one for movies or TV. Not even Xfinity Stream is working right. Thinks I'm not on my home wifi.. Worked fine on Monterey. I was really hoping Sequoia/OCLP 2.0.1 would fix it. Guess not. Back to Monterey I go...unfortunately..
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.