MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

[PeterHolbrook]

Good that you made it! Looked over your config again and I see e.g you misplaced <key>MmioWhitelist</key>. You should put it below 'Patch':

<key>Patch</key>
<array/>
<key>MmioWhitelist</key>
<array/>

Thanks for the pointer. However, since both seem to be at the same level within the Root/Booter structure, isn't their relative order indifferent?

EDIT: I've changed it as you suggested, but PlistEdit Pro restores the alphabetical sorting as soon as I try to save config.plist. From that I conclude that the order is irrelevant.

 

[Dewdman42]

If your MaxKernel lines are set for 21.5.0, that should mean the AVX patches aren't being loaded on your system after the 12.5 update. Can anyone verify that AVX patches are no longer relevant for our old machines under Monterey 12.5?

I have already updated them to 21.6.0. I did the above test with MaxKernel increased to 21.6.0. So as I said, either the AVXpel patch continues to work with final released 12.5 (most likely conclusion), or the other possibility is that the binaries changed enough that even with the MaxKernal value set to 21.6.0, if the bytes don't match the patch won't actually happen...and if that were the case, and it didn't panic, then THAT would mean Apple removed the dependency on AVX, at least for the voice control that I tested. That is a mouthful, but really the bottom line is that unless/until Syncretic or someone else actually verifies the final released 12.5 binaries to make sure that the patch is still correct and relevant, there is no way to know for sure the answer of that question. I suppose if you turn on OC debug logging you might be able to find out if the patch was applied successfully or not(?). Anyway, the most likely conclusion is that the patch is still working and in fact worked, with MaxKernal updated to 21.6.0. However I also want to say that I was able to upgrade and boot to 12.5 before I updated MaxKernal (patch not applied). However I did not test Voice Control under that scenario, and don't plan to.

 

[mktchin]

I have already updated them to 21.6.0. I did the above test with MaxKernel increased to 21.6.0. So as I said, either the AVXpel patch continues to work with final released 12.5 (most likely conclusion), or the other possibility is that the binaries changed enough that even with the MaxKernal value set to 21.6.0, if the bytes don't match the patch won't actually happen...and if that were the case, and it didn't panic, then THAT would mean Apple removed the dependency on AVX, at least for the voice control that I tested. That is a mouthful, but really the bottom line is that unless/until Syncretic or someone else actually verifies the final released 12.5 binaries to make sure that the patch is still correct and relevant, there is no way to know for sure the answer of that question. I suppose if you turn on OC debug logging you might be able to find out if the patch was applied successfully or not(?). Anyway, the most likely conclusion is that the patch is still working and in fact worked, with MaxKernal updated to 21.6.0. However I also want to say that I was able to upgrade and boot to 12.5 before I updated MaxKernal (patch not applied). However I did not test Voice Control under that scenario, and don't plan to.

Hi
I’m using Martin Lo’s V3 config with OC 080. 12.5 works and Voice Control working well. No panics.

 

[Dewdman42]

That's outside the scope of this thread.

 

[TECK]

Can anyone verify that AVX patches are no longer relevant for our old machines under Monterey 12.5?

I never installed any AVX patches or kexts on my Mac Pro 5,1. Never got kernel panics.

 

[cdf]

I never installed any AVX patches or kexts on my Mac Pro 5,1. Never got kernel panics.

It depends on your workflow. In fact, I have also never got any AVX-related panics that weren't intentionally triggered. As a quick test, try enabling Voice Control (System Preferences > Accessibility > Voice Control).

 

[MacHosehead]

As a quick test, try enabling Voice Control

Voice Control will do first command after being enabled but then has to be turned off and on again for anything else. I haven't seen a panic yet.

MP4,1->5,1 X5680, 16GB, RX 470, Monterey 12.5, OCLP 4.7

 

[cdf]

Voice Control will do first command after being enabled but then has to be turned off and on again for anything else. I haven't seen a panic yet.

MP4,1->5,1 X5680, 16GB, RX 470, Monterey 12.5, OCLP 4.7

So the panic issue was resolved months ago with the NoAVXFSCompressionTypeZlib kext (which is included in OCLP) or the AVXpel patch. Of course, anybody using these fixes now won't see a panic (and if your workflow didn't actually make use of AVX before, then you're unlikely to have ever experienced an AVX-related panic). The point of the Voice Control test here is simply to confirm that a panic will occur without these fixes.

 

[Riot Nrrrd]

The last time I checked in on this thread, I was told by people that if I were to install dosdude1's Catalina patcher (or OpenCore Legacy Patcher) on my Mid-2010 MacPro5,1 (6-core 3.33 GHz model), my iSight FireWire camera (that I use for WebEx and Zoom) would stop working and my Apple RAID Utility would cease functioning, and I couldn't manage my 4x2 TB internal Apple RAID Card RAID5 anymore. That pretty much put me off of trying it (it still runs Mojave 10.14.6 perfectly).

Has anything changed in the interim? If not, I guess I could replace it with a Mac Studio or a MacBook Pro M1 Max and then that would free it up to remove the iSight, dismantle the RAID and turn it into a play toy. But not while it's still my primary computer.

 

[Tomabe]

Hello.
I have two Mac Pro 5.1 (2010). One is an 8 core and the other is a 12 core and both have an NVIDIA GTX780. Using Martin Lo’s opencore video instructions I updated both from 10.14 to 11.6.8 and things went well. I then wanted to further update the 12 core to 12.3, so I downloaded the DMG file and left if downloading overnight. In the morning the screen was black and nothing I have done can get video to the BenQ monitor. I have tried:

1. replacing the GTX 780 with an AMD Radeon 7950
2. swapping boot drives between the two Mac Pro
3. switching PCI slots
4. externally powering the NVIDIA and AMD GPUs
5. booting to a USB drive
6. booting to recovery mode
7. switching cables from Display Port to HDMI

The 12 core Mac Pro has a black screen in all these scenarios with the monitor reporting ’no signal’. When I swap the 12 core Mac Pro SSD boot drive in the 8 core Mac Pro (using a Samsung 52inch TV for a display and also has an SSD boot drive), it boots perfectly into Big Sur 11.6.8 ... so there is nothing 'wrong' with the 12 core Mac Pro boot drive.

So all this seems to point to the PCI in the Mac Pro 12 core not working properly? And even though the screen is black and says it’s not receiving data, the Mac Pro 12 core is actually booting and going through all the proper boot sequence - you just can’t see it. I really don’t know what to try next!

 

[novaman_on_da_beat]

I neep some help with installing Big Sur and Monterey. Without spending a lot of time with typing please view my video and help me out. Please; what am I doing wrong!

20220728_222931.mp4

drive.google.com

MacPro 5,1
Mojave 11.6.8
OCLP 0.4.9

I've also tried installing using OC 0.8.2, same results as described above. Hope to hear from the community.

 

[PeterHolbrook]

I've also tried installing using OC 0.8.2, same results as described above. Hope to hear from the community.

There may be exceptions, but this "community" is not generally knowledgeable about OCLP, so perhaps you should address your questions to a forum where OCLP may be actively promoted. Have you studied post #1 of this thread?

Mojave was macOS 10.14, but you mention 11.6.8, which is the latest iteration of Big Sur.

 

[novaman_on_da_beat]

There may be exceptions, but this "community" is not generally knowledgeable about OCLP, so perhaps you should address your questions to a forum where OCLP may be actively promoted. Have you studied post #1 of this thread?

Mojave was macOS 10.14, but you mention 11.6.8, which is the latest iteration of Big Sur.

I've actually tried using both platforms/ processes. OCLP and Martin Lo's OC. You're correct, Mojave is 10.14.6 to be exact and Big Sur, 11.6.8. SMH, I'm so silly, and was very tired trying to post on my phone. Here's my link again: https://drive.google.com/file/d/1FQCEiZMm9sRqgJG8kjoNQASWWPrcguv-/view?usp=sharing

Attached are my system details, etc.

I've gone through the steps in the first post of this thread; I've read up on every relevant scenario and posts as well. Some have been helpful in the sense that I'm able to discover new things about other systems, but none dive in to specific detail about their installation and experiences. So, question; if I'm using OC 0.8.2, what do I do to install? Some say, create a Bootable Installer; done that. Hold Option and go through the install process. Doesn't seem to work for me.

Next question: Do I need to disable SIP before I install OC? I feel like I've tried installing OC and then tried disabling SIP and blessing at the same time. The jumping back and forth out of recovery seems a bit much... LOL!

Lastly, I have looked yet on the platform for a specific thread that addresses OCLP but will do so.

 

[cdf]

if I'm using OC 0.8.2, what do I do to install?

Since it looks like you're already running Mojave, the easiest approach is to install a newer version of macOS from there. As described in the first post of this thread, you'll want to keep Mojave around as a fall back, so when you start the installer from Mojave, make sure to select another disk as the installation location. The first post describes two possible configuration settings for a successful installation (see the macOS section).

Next question: Do I need to disable SIP before I install OC? I feel like I've tried installing OC and then tried disabling SIP and blessing at the same time. The jumping back and forth out of recovery seems a bit much... LOL!

Because the initial blessing process can be done in Recovery, there is no need to disable SIP (follow the steps in the Basic setup section). The important point here is that before blessing your ESP, you must be booted natively and not through a prior OC instance (see the Maintenance section if you need to start from scratch).

Good luck!

 

[William4673]

Hi all,

Experimental question for you all more well versed with the workings of open core.
Say I have an install of macOS Catalina on an APPLE model m.2 ssd (the custom ones in the MacBooks from 2013-2016?) that I would like to take out of my laptop and use as a fast storage device in my Mac Pro. This drive already has Catalina installed and configured on it. Am I able to use the Catalina patched installer to overwright this previous installation ( repair and reinstall macOS option in recovery mode ) , so as to keep my data intact, but make it compatible with the mac Pro? ( 5,1 ) by the way.

Just curious, because money is short rn and saving that bit on another SSD would be helpful. For more info I have open core configured, macOS Mojave open core as my main drive, a highsierra vanilla drive I use for NVRAM cleaning, and an open core windows 10 EUFI install. I have a metal compatible gpu.

thanks, i would love to h if this is possible.

-will

 

[cdf]

Am I able to use the Catalina patched installer to overwright this previous installation ( repair and reinstall macOS option in recovery mode ) , so as to keep my data intact, but make it compatible with the mac Pro? ( 5,1 ) by the way.

Since you already have OC setup, just install the SSD and select it from the OC boot picker. No need to do anything with a patched installer. To get the most out of Catalina, make sure to add any missing configuration settings (see Settings for macOS 12.0.1 or earlier in the Complete your setup section of the first post).

 

[streak8047]

Monterey 12.5 MacPro 5,1 has installed usbmouse not working ,three times nvram reset mouse working stop working once remove or restart .Graphics acceleration & DRM working .

 

[NC12]

—Deleted—

 

[Mike Richardson]

I recently installed a new wifi ac + bluetooth 4.0 card (Broadcom BCM94360CD) from osxwifi and have not been able to get universal control working (airplay to Mac, handoff and other bluetooth connections work). I am on the latest version of opencore 0.8.2 and have featureunlock loaded. Is there anything else I have to do to get it to work?

I have the same question. I am using the card that came with my 5,1 though. It seems to work in normal operation but I can't enable Handoff/Continuity.

On some older OS I remember using a tool and being able to enable Handoff. Having recently installed Mexico Monterey though, that tool seems to be super outdated.

 

[trifero]

I recently installed a new wifi ac + bluetooth 4.0 card (Broadcom BCM94360CD) from osxwifi and have not been able to get universal control working (airplay to Mac, handoff and other bluetooth connections work). I am on the latest version of opencore 0.8.2 and have featureunlock loaded. Is there anything else I have to do to get it to work?

Mine works perfect. Is it similar to this?

 

[NC12]

I have the same question. I am using the card that came with my 5,1 though. It seems to work in normal operation but I can't enable Handoff/Continuity.

On some older OS I remember using a tool and being able to enable Handoff. Having recently installed Mexico Monterey though, that tool seems to be super outdated.

The card that came with your mac pro wouldn’t include a newer bluetooth module like mine though so it won’t support most features. As such I am not having problems with handoff and continuity. You would need to use OCLP in order to restore it to a working condition.

 

[NC12]

Mine works perfect. Is it similar to this?

Mines almost identical except my chipset says BCM_20702B0 instead

 

[trifero]

That "almost" is a word. What it´s extrange to me if that you bought it in Osxwifi. Should work like a charm.
What do you mean in "and other bluetooth connections do work"?

 

[NC12]

That "almost" is a word. What it´s extrange to me if that you bought it in Osxwifi. Should work like a charm.
What do you mean in "and other bluetooth connections do work"?

Everything works except universal control

 

[racer]

I've been running the vanilla OC from message 1 with the config.plist and Big Sur for over a year now with no problems whatsoever. Updated OC and Big Sur as updates became available all smooth sailing.

Until a couple of weeks ago I routinely updated to 11.6.8. On reboot I got the black screen with the "Your computer restarted because of a problem..." in 5 languages.

Booted my backup Mojave drive, all good.

Reinstalled OC on a usb drive, installed BS 11.6.1 on the internal SSD, installation went fine, first boot "Your computer restarted blah blah..."

Booted Mojave from new usb drive OC, fine.
Tried reinstalling different BS version (11.6.7). Same, installation runs fine, first reboot "Your computer restarted blah blah..."

Disconnected everything on the Mac, reinstalled to different drive and from different sources (usb,sdd) same result.
Tried installing Montery 12.4, installation runs fine, first reboot bang.

In my desperation even tried OCLP 0.4.9 with new installer from usb drive, again installation ran fine, first reboot crash.

I've cleared NVRAM 3 times on most reinstalls, I've tried multiple hw drives, Mojave runs perfectly with or without OC, but for the life of me I can get BS or Monterey to boot.

Totally baffled.