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

[erll]

after the introduction of the SurPlus patch, i upgraded from 11.2.3 to 11.6 without incident. then on Monday i upgraded too 11.6.1 before installing 12.0.1. again, this went smoothly... with just one exception: i appear to have lost bluetooth functionality. i only mention this because my card is an Apple Broadcom BCM943602CD card (purchased from OSXWiFi in Feb of 2019) which is supposed to be supported in Monterey...

 

[splifingate]

I have an OSXWIFI BCM94360CDAX (full-kit) in my MP 5,1 . . . everything works, incl. Apple Watch Unlock on BS 11.6.1

Not ready to move to Monty, just yet

Regards, splifingate

 

[tsialex]

after the introduction of the SurPlus patch, i upgraded from 11.2.3 to 11.6 without incident. then on Monday i upgraded too 11.6.1 before installing 12.0.1. again, this went smoothly... with just one exception: i appear to have lost bluetooth functionality. i only mention this because my card is an Apple Broadcom BCM943602CD card (purchased from OSXWiFi in Feb of 2019) which is supposed to be supported in Monterey...

Reset the SMC, then boot Mojave and confirm that BT is working there. Do the basic diagnostic steps.

You also could have a NVRAM corruption problem, with multiplication of BT entries bluetoothActiveControllerInfo and bluetoothInternalControllerInfo.

 

[erll]

Reset the SMC, then boot Mojave and confirm that BT is working there. Do the basic diagnostic steps.

You also could have a NVRAM corruption problem, with multiplication of BT entries bluetoothActiveControllerInfo and bluetoothInternalControllerInfo.

thank you so much for your input! i will try to do this during the week. in the event that my NVRAM is corrupted, how would i go about fixing that?

 

[tsialex]

thank you so much for your input! i will try to do this during the week. in the event that my NVRAM is corrupted, how would i go about fixing that?

I'll send you a PM.

 

[erll]

Send me a PM later.

thank you. i will contact you once i have completed the suggested steps...

 

[Eweie]

While I am not sure if removing it will fix your bt dongle you could always make an automator app that would run that script on login

I use an apple bluetooth keyboard so I can't log in. I guess I'll try removing it and report back if it worked.

 

[Eweie]

I removed the stock wifi and bluetooth cards and my usb bluetooth 4 dongle doesn't initialize automatically but also sudo kill -9 $(pgrep bluetoothd) doesn't make it work anymore.

 

[Nekapsule]

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.

I use these Fenvi cards in both my X56xx Hackintoshes and they work great (I have both the HB1200 and the T919).

You also get Airdrop/Handoff out of the box when running a MacPro6,1 SMBios, but that also requires some CPU Power Management changes as this model never came with the CPUs you had in the previous Mac Pros.
You can use https://github.com/vin047/MacPro41-PowerProfile to achieve that without the need of CPUFriend (but CPUFriend would achieve the same results once you extract the MacPro4,1 or 5,1 PowerManagement profiles).

In saying that, wouldn't you be able to remove the RF shield on the Fenvi and extract the Wifi/BT module in there? As far as know, these cards are just an m.2 to PCIe adapter and ship with a pre-installed native Apple module. Unless the modules they use are from Macbooks and not the same form factor as the ones in a MacPro?

 

[donvito4ever]

I removed the stock wifi and bluetooth cards and my usb bluetooth 4 dongle doesn't initialize automatically but also sudo kill -9 $(pgrep bluetoothd) doesn't make it work anymore.

I have 2 Mac Pro 5.1... one of them, all resolved and worked as expected (not all times, I'll explain later) BT working fine with BCM943602CD. But the other MacPro no... with or without BT dongle and don't recognise fine the BCM943602CD (I think that will be a false chinesse copy)... I'll buy other to try to fix it.

My Mac Pro that works as expected not all time: I have an issue with the read/write files in finder or one docs in, for example, Pages. Generally all works perfect but, ramdomly, I have to reboto to open documents in Pages/Word/etc... always waiting to open... same thing with, for example move a file to trashcan, like you can see in the attached video...

What can I do to solve it???

 

[tsialex]

In saying that, wouldn't you be able to remove the RF shield on the Fenvi and extract the Wifi/BT module in there? As far as know, these cards are just an m.2 to PCIe adapter and ship with a pre-installed native Apple module.

Most people want to use the Fenvi as is and not to a source for the module, you probably can score modules cheaper on AliExpress, since MacPro5,1 BT reception/reach with the original antennas is extremely problematic when you install it below desks.

 

[TECK]

OC 0.7.5 is released but they are missing the built packages on Lilu, WG and OC. Can anyone get in touch directly with the devs?

Edit: never mind, it looks like they are working on it, Lilu and WG packages are there now.

 

[tsialex]

OC 0.5.7 is released but they are missing the built packages on Lilu, WG and OC. Can anyone get in touch directly with the devs?

0.5.7 was back in April 2020.

0.7.5​

Repository: acidanthera/OpenCorePkg · Tag: 0.7.5 · Commit: eab5149 · Released by: vandroiy2013

v0.7.5​

• Revised OpenLinuxBoot documentation
• Supported Linux ostree boot layout
• Fixed external drive icons for Boot Entry Protocol
• Added GPU Resize BAR quirks to reduce BARs on per-OS basis
• Fixed OpenLinuxBoot hang bug after correct detection of some distros
• Added DMG signature check during download, thx @jspraul and @zhangyoufu
• Updated builtin firmware versions for SMBIOS and the rest
• Updated recovery downloading commands to include macOS 11 and 12

—
This release has 2 assets:

• Source code (zip)
• Source code (tar.gz)

Visit the release page to download them.

 

[cdf]

The guide has been updated to OpenCore version 0.7.5.

New guide

With the recent release of Monterey and with OpenCore stabilizing with fewer changes, this was the opportunity to completely reformat and rewrite the guide, not only to maximize clarity, but also to make the guide easier to maintain as wiki long term.

The new guide offers improved methods and new recommendations. The changes include

• numbered steps to more easily follow the instructions
• diagrams to better visualize your ESP
• description of key settings to effectively customize your setup
• tested approaches to safely upgrade to Monterey (with VMM or SecureBootModel)
• creation of a rescue CD (especially useful for Macs without boot-screen support)
• inclusion of OpenCanopy in the sample config for a simpler initial setup
• configuration around MacPro7,1 board ID for a more minimal hardware acceleration setup on Big Sur and later
• reversion to NightShiftEnabler to minimize the performance impact of user-space patching

Happy updating!

 

[TECK]

0.5.7 was back in April 2020.

Fixed

 

[TECK]

Plistlib Generator 1.2.1 was released with support for OC 0.7.5 (see notable changes), you will need to perform several minor changes to your current setup.py file, prior executing the usual upgrade process. The new configuration is reduced and is following @cdf's guide at letter as usual, with several settings being removed, making it even easier to perform future upgrades.

Myself and @cdf collaborated on this release, to test everything properly prior.

 

[MacToby]

The guide has been updated to OpenCore version 0.7.5.

New guide

With the recent release of Monterey and with OpenCore stabilizing with fewer changes, this was the opportunity to completely reformat and rewrite the guide, not only to maximize clarity, but also to make the guide easier to maintain as wiki long term.

The new guide offers improved methods and new recommendations. The changes include

• numbered steps to more easily follow the instructions
• diagrams to better visualize your ESP
• description of key settings to effectively customize your setup
• tested approaches to safely upgrade to Monterey (with VMM or SecureBootModel)
• creation of a rescue CD (especially useful for Macs without boot-screen support)
• inclusion of OpenCanopy in the sample config for a simpler initial setup
• configuration around MacPro7,1 board ID for a more minimal hardware acceleration setup on Big Sur and later
• reversion to NightShiftEnabler to minimize the performance impact of user-space patching

Happy updating!

A question about the new guide. Will AirPlay to Mac and Universal Control (when released) in macOS Monterey still work with your new Guide or do we still need the FeatureUnlock kext for that?

 

[cdf]

A question about the new guide. Will AirPlay to Mac and Universal Control (when released) in macOS Monterey still work with your new Guide or do we still need the FeatureUnlock kext for that?

Air Play to Mac indeed needs the patch from FeatureUnlock to work, but the guide is currently not recommending FeatureUnlock because of recent reports of hangs (stability must be prioritized here). Once more is known about the problem, an informed decision will be made on the recommendation for getting AirPlay to Mac and Universal Control (when released) to work.

 

[Eweie]

I have 2 Mac Pro 5.1... one of them, all resolved and worked as expected (not all times, I'll explain later) BT working fine with BCM943602CD. But the other MacPro no... with or without BT dongle and don't recognise fine the BCM943602CD (I think that will be a false chinesse copy)... I'll buy other to try to fix it.

My Mac Pro that works as expected not all time: I have an issue with the read/write files in finder or one docs in, for example, Pages. Generally all works perfect but, ramdomly, I have to reboto to open documents in Pages/Word/etc... always waiting to open... same thing with, for example move a file to trashcan, like you can see in the attached video...

What can I do to solve it???

View attachment 1899450

I don't have this issue but also haven't been using the Mac with Monterrey for long.
I have noticed when installing apps to the apps directory sometimes they dont show up until reboot.
which had me really confused for a while why a game I was trying to install kept saying if I wanted to overwrite it.
I'm also not able to add the clone of my boot drive to the spotlight privacy exclusion list.
I'm assuming these are just Monterrey bugs in general.

 

[Eweie]

I have seen your issue before though and I think your ssd might be on its way out. im currently RMAing a aData drive that shows the same symptoms you show after 700gb of data.
you might want to try cloning your system to another drive and see if you have the same problem.

 

[zelob]

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.

.

 

[DrFuzzy]

<dict> <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.

Wi-Fi support can be restored as well by using IO80211ElCap and corecaptureElCap. You would not be able to connect to network without https://github.com/dortania/PatcherSupportPkg/tree/master/12-Monterey/CoreServices/Legacy-Wifi though, so OCLP system volume patching is needed here.

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

 

[TECK]

@cdf the OC 0.7.5 assets are still missing, I opened #1839. For these who want to built themselves, there are instructions posted into Plistlib Generator Wiki:

Configuration: Build Options

OpenCore Plistlib Generator for Mac Pro 4,1 - 5,1. Contribute to axivo/opencore development by creating an account on GitHub.

github.com

$ ls -lh Binaries
total 16896
-rw-r--r--  1 floren  staff   4.6M  1 Nov 15:02 OpenCore-0.7.5-DEBUG.zip
-rw-r--r--  1 floren  staff   3.6M  1 Nov 15:03 OpenCore-0.7.5-RELEASE.zip

Currently running on OC 0.7.5:

 

[Eschers]

did several installs following the guides (from 0.4 something to 0.7.3) but now it refuses to boot first time OC.. don't know what it could be. Maybe the config file is corrupt or something?

EDIT: tried id a fourth time, still no success. Followed the instructions as described. Don't know if something is missing.

 

[cdf]

did several installs following the guides (from 0.4 something to 0.7.3) but now it refuses to boot first time OC.. don't know what it could be. Maybe the config file is corrupt or something?

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.