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

[Eschers]

The sample config in the guide has been tested. Note that as a minimal baseline, the sample config does not have SurPlus included, so you'll of course need to include it before booting macOS >11.2.3.

Thanks for your quick reply!

What could it be then? Downloaded the files and built 0.7.5 myself, extracted the zip and followed the guide. The screen just stays black

Trying to install the OC to a WD Black m.2 name drive from a HDD Mojave install, so no booting to anything higher than Mojave.

ps: maybe something wrong with the OC 0.7.5 build?

 

[cdf]

Trying to install the OC to a WD Black m.2 name drive from a HDD Mojave install, so no booting to anything higher than Mojave.

If only Mojave is present, then it should boot, provided that OC is blessed. Perhaps try an NVRAM reset, boot Mojave natively, and then bless OC.

ps: maybe something wrong with the OC 0.7.5 build?

Maybe, the binaries still haven't appeared on the release page for some reason. My tests have been done with a self-compiled version from yesterday...

 

[Eschers]

If only Mojave is present, then it should boot, provided that OC is blessed. Perhaps try an NVRAM reset, boot Mojave natively, and then bless OC.


Maybe, the binaries still haven't appeared on the release page for some reason. My tests have been done with a self-compiled version from yesterday...

Just did that a couple of times, no success!

I have built the version just 2 hours ago with the instructions.

 

[h9826790]

I am using Martin’s package 0.7.4 but am hitting a firmware issue after the reboot. “A required firmware update could not be installed.” See screenshot.
I am running Big Sur just fine on this MacPro 5,1.

View attachment 1899826.

Turn on VMM

 

[cdf]

Just did that a couple of times, no success!

I have built the version just 2 hours ago with the instructions.

The OC binaries are now available on the release page (an issue with Github actions), though even with this release, I can't seem to replicate the issue on my end. Just to confirm, you've tried starting OC with the sample config as is, that is, following just the Basic setup part up to the First boot section?

 

[roobarb!]

The guide has been updated to OpenCore version 0.7.5.

Have I missed something regarding the Linux installation instructions? They seem to be gone in the new guide; is there an improved method on its way or is there a problem with the previous method in new versions?

 

[EETagent]

Managed to upgrade from BigSur to Monterey using OpenCore 0.7.4 SIP + SSDT + Sidecar & Nighshift + Serial Macpro 2019 + Airport Bradcom https://forums.macrumors.com/thread...-youve-been-waiting-for.2313858/post-30515405. Upgrade went smoothly except for BT and WiFi that stopped working. Can you please guide me in applying the above mentioned patches to restore BT and WiFi? BT chipset reported: BCM_4350C2

Just paste those two entries after your other kernel extensions in config.plist files. You will find those kexts on mentioned GitHub repository. That's for Bluetooth only, like mentioned, Wi-Fi would not work without replacing WifiAgent.app on system volume.

 

[cdf]

Have I missed something regarding the Linux installation instructions? They seem to be gone in the new guide; is there an improved method on its way or is there a problem with the previous method in new versions?

Given the new OpenLinuxBoot driver (thanks to @Bmju), those instructions had become outdated. An improved method will be included in due time.

 

[chrisrm9208]

FWIW, Monterey has been noticed by El Reg for its troublesome nature (https://www.theregister.com/2021/11/01/macos_monterey_update/) so many of the supposedly off-topic comments and problems may have a real-world cause other than OC.

 

[Eschers]

The OC binaries are now available on the release page (an issue with Github actions), though even with this release, I can't seem to replicate the issue on my end. Just to confirm, you've tried starting OC with the sample config as is, that is, following just the Basic setup part up to the First boot section?

Thanks for your reply!

I downloaded it from giithub today and everything seems to work except PCI-drives are still not seen internal, despite having everything configured as you said. is maybe innie-kext missing?

 

[cdf]

Thanks for your reply!

I downloaded it from giithub today and everything seems to work except PCI-drives are still not seen internal, despite having everything configured as you said. is maybe innie-kext missing?

Great! In most cases, Innie shouldn't be necessary if you've added the built-in property. Are you sure you have the right paths?

 

[Eschers]

Great! In most cases, Innie shouldn't be necessary if you've added the built-in property. Are you sure you have the right paths?

Thanks for the quick reply!

Nevermind, did the BoardProduct ID entry in the wrong place!

Thank you anyway!

 

[Belifant]

Once more, thank you and all involved for keeping my Mac Pro alive for this long.

 

[DrFuzzy]

Just paste those two entries after your other kernel extensions in config.plist files. You will find those kexts on mentioned GitHub repository. That's for Bluetooth only, like mentioned, Wi-Fi would not work without replacing WifiAgent.app on system volume.

Can you please provide the link for BlueToolFixup and Bluetooth-Spoof kexts? The link at the original post seems broken.
Found it https://github.com/dortania/OpenCore-Legacy-Patcher/tree/main/payloads/Kexts, BT is back again hooray!!!
Next, need to figure out how to bring WiFi back.
My WiFi is back by patching the volume using OCLP v0.3.1, pretty easily I should admit!

One more question, at the moment my SIP status, which admittedly is somewhat scary, is reported as:

Bell:~ delk$ csrutil status
System Integrity Protection status: unknown (Custom Configuration).

Configuration:
Apple Internal: disabled
Kext Signing: disabled
Filesystem Protections: disabled
Debugging Restrictions: enabled
DTrace Restrictions: enabled
NVRAM Protections: enabled
BaseSystem Verification: enabled

This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.

Do I need to enable SIP (build OC again with SIP enabled) or leave it as is?

 

[HuRR]

On OC .7.5 using @h9826790 pre-compiled package. Just as a heads up, if Nightshift doesn't work, check your config. I think the config.plist has NightshiftEnabler in the .plist in rather than FeatureUnlock. Once I changed that, all good to go.

 

[abaxworld]

Just paste those two entries after your other kernel extensions in config.plist files. You will find those kexts on mentioned GitHub repository. That's for Bluetooth only, like mentioned, Wi-Fi would not work without replacing WifiAgent.app on system volume.

<key>Arch</key>
<string>x86_64</string>
<key>BundlePath</key>
<string>BlueToolFixup.kext</string>
<key>Comment</key>
<string></string>
<key>Enabled</key>
<true/>
<key>ExecutablePath</key>
<string>Contents/MacOS/BlueToolFixup</string>
<key>MaxKernel</key>
<string>21.99.99</string>
<key>MinKernel</key>
<string>21.0.0</string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
</dict>
<dict>
<key>Arch</key>
<string>x86_64</string>
<key>BundlePath</key>
<string>Bluetooth-Spoof.kext</string>
<key>Comment</key>
<string></string>
<key>Enabled</key>
<true/>
<key>ExecutablePath</key>
<string></string>
<key>MaxKernel</key>
<string>21.99.99</string>
<key>MinKernel</key>
<string>21.0.0</string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
</dict>

"Support was dropped, but you can restore it using a modified BlueToolFixup from the OCLP GitHub repository and extend the life of the original Bluetooth card for a little longer."

Hi. I just tried what you suggest, added latest BlueToolFixup.kext and Bluetooth-Spoof.kext to the Kexts folder, added the lines described here at the end of all kext lines in config.plist but I'm afraid that doesn't work for my original Bluetooth card in a MacPro 4,1->5,1. Am I missing something or it's just because there is no fix for the original Bluetooth on these MacPros? Thanks.

 

[decasta]

Hi everyone!

I could use some help figuring out some issues I'm having...

I have a pretty textbook setup with my cMP 4,1 -> 5,1.

All this, plus...
NVME boot drive with Mojave 10.14.6
OC 0.7.5

Problem 1) With every OC version, when I try to enable HWAccel, whether manually or through Martin Lo's package, it boots up and gets stuck at the apple logo, with no progress bar.

In order to solve it, I have to pull the SSD that has OC on it, boot into mojave normally, and then manually delete all the HWAccel related stuff in the config.plist.

Problem 2) I installed Catalina on another drive, and while it runs smoothly, I've noticed that my Das Keyboard (plugged into the USB hub of my LG Monitor, plugged into the USB 3.0 PCIe card), stops working properly. Namely, whenever I press the caps lock key, it no longer responds. Meanwhile, the usb hub of the keyboard itself is still working, because my mouse is plugged into that.

The only way to get past it would be to plug another keyboard into a built-in usb port and keep typing, OR to unplug the keyboard and plug it back in. But then, sometimes, the strange behaviour comes back.

Obviously, before I load the edited list back in, I verify it every time, and it always says "OK".

Any insight as to what could be causing this?

 

[AngelThMan]

If you have an available PCIe slot, the Fenvi T919 is pretty inexpensive for a BCM94360 card and will solve the Wi-Fi connectivity without any kexts and having to mess with the U.FL connectors of the Mac Pro antennas, just install the card on a PCIe slot and forget, since it's fully supported and will work fine with the first post implementation.

Also, the Fenvi card have excellent Wi-Fi and Bluetooth reception, but for BT you to connect the USB data header of the Fenvi card to one of the Mac Pro USB ports or to the Molex PicoBlade JST USB data connector on the backplane that is used for the original bluetooth module - the black cable.

I have a Fenvi T919 installed in one of my Mac Pros, works fine.

Hi tsialex, I have a Mac Pro. That says Hackintosh, which are PC hardware. Would Fenvi T919 work on a Mac Pro 2009 5,1?

 

[TECK]

Would Fenvi T919 work on a Mac Pro 2009 5,1?

Yes.

 

[tsialex]

Hi tsialex, I have a Mac Pro. That says Hackintosh, which are PC hardware. Would Fenvi T919 work on a Mac Pro 2009 5,1?

This is a weird question since I even wrote on my post that I have a Fenvi T919 installed on one of my Mac Pros and the post I was answering was clearly about a MacPro5,1.

Perhaps next time a question like that arises I'll write that works fine with early-2009 to mid-2012 Mac Pros, just to be crystal clear - but then someone will ask about older Mac Pros.

I have a Fenvi T919 installed in one of my Mac Pros, works fine.

 

[AngelThMan]

This is a weird question since I even wrote on my post that I have a Fenvi T919 installed on one of my Mac Pros and the post I was answering was clearly about a MacPro5,1.

Perhaps next time a question like that arises I'll write that works fine with early-2009 to mid-2012 Mac Pros, just to be crystal clear - but then someone will ask about older Mac Pros.

Thanks. You're right, sorry, I missed what you said about your Mac. Your info has helped me before and I appreciate it.

 

[h9826790]

Hi everyone!

I could use some help figuring out some issues I'm having...

I have a pretty textbook setup with my cMP 4,1 -> 5,1.

View attachment 1901085

All this, plus...
NVME boot drive with Mojave 10.14.6
OC 0.7.5

Problem 1) With every OC version, when I try to enable HWAccel, whether manually or through Martin Lo's package, it boots up and gets stuck at the apple logo, with no progress bar.

In order to solve it, I have to pull the SSD that has OC on it, boot into mojave normally, and then manually delete all the HWAccel related stuff in the config.plist.

Problem 2) I installed Catalina on another drive, and while it runs smoothly, I've noticed that my Das Keyboard (plugged into the USB hub of my LG Monitor, plugged into the USB 3.0 PCIe card), stops working properly. Namely, whenever I press the caps lock key, it no longer responds. Meanwhile, the usb hub of the keyboard itself is still working, because my mouse is plugged into that.

The only way to get past it would be to plug another keyboard into a built-in usb port and keep typing, OR to unplug the keyboard and plug it back in. But then, sometimes, the strange behaviour comes back.

Obviously, before I load the edited list back in, I verify it every time, and it always says "OK".

Any insight as to what could be causing this?

Please turn on verbose mode, and if possible, turn on OC debug mode as well. And see what's showed on the screen when it hangs.

 

[SJerc]

<key>Arch</key>
<string>x86_64</string>
<key>BundlePath</key>
<string>BlueToolFixup.kext</string>
<key>Comment</key>
<string></string>
<key>Enabled</key>
<true/>
<key>ExecutablePath</key>
<string>Contents/MacOS/BlueToolFixup</string>
<key>MaxKernel</key>
<string>21.99.99</string>
<key>MinKernel</key>
<string>21.0.0</string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
</dict>
<dict>
<key>Arch</key>
<string>x86_64</string>
<key>BundlePath</key>
<string>Bluetooth-Spoof.kext</string>
<key>Comment</key>
<string></string>
<key>Enabled</key>
<true/>
<key>ExecutablePath</key>
<string></string>
<key>MaxKernel</key>
<string>21.99.99</string>
<key>MinKernel</key>
<string>21.0.0</string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
</dict>

"Support was dropped, but you can restore it using a modified BlueToolFixup from the OCLP GitHub repository and extend the life of the original Bluetooth card for a little longer."

Hi. I just tried what you suggest, added latest BlueToolFixup.kext and Bluetooth-Spoof.kext to the Kexts folder, added the lines described here at the end of all kext lines in config.plist but I'm afraid that doesn't work for my original Bluetooth card in a MacPro 4,1->5,1. Am I missing something or it's just because there is no fix for the original Bluetooth on these MacPros? Thanks.

Hi. It worked for me. I wanted a fresh Monterey install on my Mac Pro 4,1->5,1 w/original bluetooth card today and followed the steps in post #1. The only thing I can note in my installation is that I set LauncherOption to Full, DirectGopRendering to false, left the VMM disabled, skipped the Clean NVRAM step, then added the BlueToolFixup and Bluetooth-Spoof kext files to the kext directory, and finally added the exact config.plist snippet you have in your message right after my AppleMCEReporterDisabler.kext section. After a reboot, I was happy to have BlueTooth again. I've attached my config.plist in case you want to compare.

 

[SJerc]

Once more, thank you and all involved for keeping my Mac Pro alive for this long.

Ditto, kudos to all of you for keeping this bad boy alive on the latest OS. I've been following this post forever and am forever grateful for it for giving my system new life once again.

 

[abaxworld]

Hi. It worked for me. I wanted a fresh Monterey install on my Mac Pro 4,1->5,1 w/original bluetooth card today and followed the steps in post #1. The only thing I can note in my installation is that I set LauncherOption to Full, DirectGopRendering to false, left the VMM disabled, skipped the Clean NVRAM step, then added the BlueToolFixup and Bluetooth-Spoof kext files to the kext directory, and finally added the exact config.plist snippet you have in your message right after my AppleMCEReporterDisabler.kext section. After a reboot, I was happy to have BlueTooth again. I've attached my config.plist in case you want to compare.

Thank you for your answer. I have mostly the same ( I've got some extra kext lines for GPU acceleration ) but I don't get if you are installing Monterey starting again from Mojave or if it's just a Mojave installation. I'm in Monterey 12.0.1. I have modified LauncherOption and DirectGopRendering as you suggest ( had VMM disabled previously ) but the bluetooth keeps missing ( no activation is possible both in the System Preferences or the top bar icon ). Still looking for a solution. Thanks anyway. ;-)