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.
Hi all,
I've got a Mac Pro 5,1, Vega 56 graphic card that drive 3 4k monitors.

On this configuration the post install patches for OCLP only work if I use 0.6.1; 0.6.2 to 0.6.4 don't seem to install the post patches correctly for the graphic card; I get the solid background dock, very sluggish behaviour and only two of the 3 monitors fire up - all signs the graphic card drivers are not as they should be.

I'm keen to get to a newer version of OCLP for video playback issues etc.

Has anyone else had this issue?
 
MBP11,3 + macOS Ventura 13.3.1 + OCLP 0.6.5n = Parallels 18 now starts VMs with the Parallels hypervisor normally, while those with the Apple hypervisor still refuse to start (probably due to AMFI still being disabled, in this early nightly build); while VMware Fusion 13 and VirtualBox 7, which can use only the Apple hypervisor, still won’t start any VM…
 
I just succesfully installed Ventura on my iMac (see spec in signature, with standard graphics, wifi & bluetooth). There is no Airplay option within the Sound Settings menu on my iMac although it is present and working very well on various speakers via my MacBook Pro. Is there a known issue specific to mid-2011 iMacs?

To add, I can select Airplay as the output in Apple Music and have the iMac Airplay successfully via that method. But I would prefer the global option to send all sound output to Airplay for other sources (i.e. other apps such as browser, Audacity, rekordbox, etc).

I also found that there are no Airplay devices in the Airplay picker in YouTube on Safari. And in Apple Podcasts app there is no sound output picker from which I can switch to any Airplay devices (unlike in the same app on my MacBook Pro).

Here's my Sound Setting on MacBook Pro where all is well:
View attachment 2189963
And here's the problematic iMac's Sound Settings:
View attachment 2189969

Just confirming: devs have confirmed that as will call it "full" Airplay (globally, from the sound output picker) is enabled by upgrading the wifi card. Note that this is applicable to my iMac model (see signature) and may be different for other models. Airplay from Apple Music does work without an upgrade. And note that I do not know about video Airplay capabilities with/without wifi upgrade.

I see that wifi upgrade is entirely possible and is covered in this thread. I'll switch over to that thread in order to have an exploration of current options for folks who do not do soldering!
 
  • Like
Reactions: Lgga74
I messed with the files in my EFI volume and deleted everything, for copying files from OCLP EFI on a USB. I was able to copy the relevant files but now my bootcamp Windows doesn’t show up as an option in the OCLP boot picker. The windows partition is not bootable.

Any idea how I can make the windows partition bootable again? Can I borrow the relevant EFI files (like bootx64.efi etc) from somewhere?
 
Can I safely update my iMac 14,2 (Late 2013) to 13.3 or am I better waiting for the next release of OCLP 0.6.5?
If you have a recoverable backup and you install to a new volume, you're safe. On my production rig, I never upgrade to a new minor or major version without having a recoverable backup - and that's when the new version is an official release.
 
Hello, with Ventura we lost the panel to schedule the start, wake and shutdown on our Mac but the technical function is always present. It is possible to use PMSET. I write a little software to control PMSET with a graphic interface like before. It is free and you can download it (French or English) at http://bmaillard.free.fr/programmer/. Enjoy.

Capture d’écran 2023-04-18 à 19.16.41.png
 
Just updated my OpenCore to 0.6.4 on my iMac 14,2 (27” - Late 2013) I installed OpenCore to my EFI rebooted an everything was fine. Installed the new root patches and rebooted and now my iMac is hanging on the boot screen.

Haven’t installed the 13.3.1 update yet.

Any ideas on how I can fix this?
 
Just updated my OpenCore to 0.6.4 on my iMac 14,2 (27” - Late 2013) I installed OpenCore to my EFI rebooted an everything was fine. Installed the new root patches and rebooted and now my iMac is hanging on the boot screen.

Haven’t installed the 13.3.1 update yet.

Any ideas on how I can fix this?
Hello, try to Boot on an Usb disk with an OPCL 0.6.3 or less install on it.
 
  • Like
Reactions: TimmuJapan
Just tried booting from my original opencore ventura usb installer and same thing.

It was a much older/lower version of OpenCore
Not good. On my Mac , I have always 3 partitions, 2 for os, one to work one to test the new install and 1 for applications and documents. I think you have to re-install your OS. Apply my organisation for the next time.
 
  • Like
Reactions: luckyduke23
Not good. On my Mac , I have always 3 partitions, 2 I for os, one to work one to test the new install and 1 for applications and documents. I think you have to re-install your OS. Apply my organisation for the next time.
That was my thought as well. Looks like that’s the job for tomorrow then
 
I messed with the files in my EFI volume and deleted everything, for copying files from OCLP EFI on a USB. I was able to copy the relevant files but now my bootcamp Windows doesn’t show up as an option in the OCLP boot picker. The windows partition is not bootable.

Any idea how I can make the windows partition bootable again? Can I borrow the relevant EFI files (like bootx64.efi etc) from somewhere?
 
  • Like
Reactions: cybazaar
Is it true that whenever a process such as ControlCenter.app crashes relevant information about the crash is sent to developers? I'm completely ok with this since that is the only way debugging on dozens of different hardware configurations can be done efficiently. But I would like to know when this happens and what is sent.
 
Is it true that whenever a process such as ControlCenter.app crashes relevant information about the crash is sent to developers? I'm completely ok with this since that is the only way debugging on dozens of different hardware configurations can be done efficiently. But I would like to know when this happens and what is sent.
Crash reports are not collected by OCLP, though this may be implemented in the future (don't quote me on this), potentially by opting in.
 
Probably that would be useful to developers. If so, I would opt in. I have posted here several crash reports for apps like ControlCenter.app. Is that a good idea or just wasting space here?
 
If you have a recoverable backup and you install to a new volume, you're safe. On my production rig, I never upgrade to a new minor or major version without having a recoverable backup - and that's when the new version is an official release.
Or install 2 OS on 2 partitions one to work one to test the new install. I have 3 partitions, 2 for OS and ons for app and document. On Mac it 's work very fine. Backup of document is on cloud. And I have always a clean instal.

Image.png
 
  • Like
Reactions: luckyduke23
Hmmm… my Parallels macOS VMs won’t start, even if the hypervisor is changed from Apple to Parallels: so, the fact that AMFI is disabled outright prevents those VMs from starting. So, we’ll just have to wait for the AMFI fix…

Edit (see below): Bluestacks is for running Android apps (as in WSA on Windows 11); I tried it some time ago, but haven’t used it recently.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.