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

[Dewdman42]

Yes, I followed post #1 exactly, including advanced config. Nothing else.

 

[startergo]

Yes, I followed post #1 exactly, including advanced config. Nothing else.

There is a thread here:

System preferences software update badge

I’d like to vote again for what I think is the safest simplest solution to clearing the sys pref notification badge. 1) QUIT System Preferences 2) in terminal run: sudo softwareupdate --ignore "macOS Catalina" 3) in terminal run: defaults delete com.apple.preferences.softwareupdate...

forums.macrumors.com

Which is for Catalina, but you can adapt the commands for Big Sur, but honestly this is not related to OC and may need a topic on its own.
Edit:
This method is for Big Sur:

macOS 10.14 Mojave on Unsupported Macs Thread

Hi @RK78 The SSD in my MBP5,3 is in HFS + so yes no problem to install it in HFS+ I was also surprised not to find any distribution file and you are right, we have to be careful with this .pkg like if we had modified the distibution file because it is then possible to install it on any disk /...

forums.macrumors.com

 

[Dayo]

You are really confusing me now. I already did check online for workarounds, which is what I tried to do that doesn't work.

Do you know another work around that will work with OpenCore MP5,1 running Catalina?

That's what I'm trying to tell you.
Telling Software Updates to ignore an update is not a workaround but a standard feature. This feature was removed in the Catalina 10.15.5 update. To get it back, you need to roll back your installation to one before you installed the update that removed this capability from Software Update which is not really a viable option.

What I have done on my Mojave installation is that before installing the equivalent security update, I saved the Software Update Utility. Then after installing the security update, I put the old version of the Software Update Utility back in and been repeating the procedure for every update since then.

I now ignore both Big Sur and Catalina.
Read more here: https://www.macrumors.com/2020/05/28/macos-ignore-software-updates/

They are removing the ability to ignore updates in Big Sur, it is supposedly just a warning in Catalina, but people can still do it...IF...their machine is eligible, which mine is apparently not.

It is not related to your machine but to the version of Catalina you have in place as explained. Once you went past Catalina 10.5.4, this capability was disabled.

So again... how can I remove that notification from my OC Catalina MP5,1? It appears to not be possible unless there is some OC hackery around it.

Not OpenCore related obviously and if you do not have the old Software Update Utility (before it was amended) saved somewhere, you can no longer ignore such major updates. You might be able to grab a copy from time machine.

I followed this process at the time: https://forums.macrumors.com/posts/28519784. Maybe best to post in that thread.

 

[Dewdman42]

The updater also just popped up a notification that I need to update GarageBand...but when I open up App Store, it says I can't update it because its only for BigSur,.

So clearly there is something broken about this OpenCore configuration with regards to Software update.

I am not sure what you mean about Catalina version, this is my first try at installing Catalina at all, I went directly to 10.15.7, using OpenCore as described in post#1.

Rolling back to older Catalina is not an option.

Are you saying that all Mac users everywhere....running Catalina...with or without OC...are having these same problems...notifications about Big Sur that won't go away and also notifications to update to apps that can't be installed without Big Sur first? if so that is really lame on Apple's part...

 

[Dewdman42]

There is a thread here:

System preferences software update badge

I’d like to vote again for what I think is the safest simplest solution to clearing the sys pref notification badge. 1) QUIT System Preferences 2) in terminal run: sudo softwareupdate --ignore "macOS Catalina" 3) in terminal run: defaults delete com.apple.preferences.softwareupdate...

forums.macrumors.com

Which is for Catalina, but you can adapt the commands for Big Sur, but honestly this is not related to OC and may need a topic on its own.
Edit:
This method is for Big Sur:

macOS 10.14 Mojave on Unsupported Macs Thread

Hi @RK78 The SSD in my MBP5,3 is in HFS + so yes no problem to install it in HFS+ I was also surprised not to find any distribution file and you are right, we have to be careful with this .pkg like if we had modified the distibution file because it is then possible to install it on any disk /...

forums.macrumors.com

I'll check those threads out. thanks

 

[Dayo]

So clearly there is something broken about this OpenCore configuration with regards to Software update.

I am lost as to how to restate that this has nothing to do with OpenCore or your machine but the version of Catalina that you are running. It doesn't matter whether you installed Catalina natively, via OpenCore, via DosDude patch, or by any other means.

You have v10.15.7 and I told you that the capability to ignore major updates was removed as from v10.15.5 onward and provided a link for you to read on this as well as how this issue can be bypassed if desired.

As mentioned, this subject is off-topic on an OpenCore thread and best to either start a new thread or post to a thread dealing with the subject such as the example I posted.

 

[Dewdman42]

peace Dayo, you're being way too aggressive man. I'm just ask questions... I just installed OC for the first time, so I started here. No need to get so angry and rude. The garage band thing seems more suspect to me...as I should not be getting any notification about apps that need to be updated for BigSur when I am actually running Catalina. Again, if that turns out to be a general problem for all Catalina users, than I will find that out now that you have yelled at me to go away, I will go find out. Peace man.

 

[bookemdano]

The thing with Garageband has nothing to do with OpenCore either. I still have Catalina on my 16" MBP and was just offered an update to Garageband that won't install because I'm not on Big Sur.

In fairness to Dayo, I don't think he was being angry or rude--I think he was just getting frustrated that you weren't understanding what he was saying after multiple posts. Remember that you asked for help and he was spending time trying to help you.

 

[Dewdman42]

and likewise I didn't feel like he was understanding me or my question.

 

[Dewdman42]

The thing with Garageband has nothing to do with OpenCore either. I still have Catalina on my 16" MBP and was just offered an update to Garageband that won't install because I'm not on Big Sur.

Thanks for this info.

 

[bookemdano]

and likewise I didn't feel like he was understanding me

Yes but in this instance the burden is on you because you're the one who asked for help. As they say, "beggars can't be choosers". Understand that even if you didn't like his tone, he was attempting to help you understand and solve your problem.

 

[Dayo]

peace Dayo, you're being way too aggressive man. I'm just ask questions... I just installed OC for the first time, so I started here. No need to get so angry and rude. The garage band thing seems more suspect to me...as I should not be getting any notification about apps that need to be updated for BigSur when I am actually running Catalina. Again, if that turns out to be a general problem for all Catalina users, than I will find that out now that you have yelled at me to go away, I will go find out. Peace man.

Sorry ... I raised my voice as it seemed you weren't hearing me despite repeating the same thing a number of times. Particularly after taking time to search the forum to give you info which your "Clearly, there is something wrong with ..." response indicated you hadn't read.

Anyway, summary is that the feature was disabled in 10.15.5 and you are on 10.15.7. You need to either live with it as Apple wants or hack your installation as I described. Ultimately not OpenCore related and best discussed in a relevant thread if desired.

 

[TECK]

I updated my thread, related to Bluetooth issues, might help others.

I wrote back the reconstructed ROM, I had to reboot Big Sur twice and Bluetooth was visible. I will wait few days and report back to see if the issue makes surface again. Thank you @tsialex for your help!

@cdf @h9826790 I think we should keep a close eye on this. I will report back if I lose again Bluetooth, if this happens, this is clearly an issue with OC and/or Big Sur, we cannot blame it on ROM fragmentation.

 

[GSXB]

OK, so I added the needed lines

In the Kernel Key.

I've added the lines just after

<dict>
<key>Arch</key>
<string>x86_64</string>
<key>BundlePath</key>
<string>RadeonBoost.kext</string>
<key>Comment</key>
<string></string>
<key>Enabled</key>
<false/>
<key>ExecutablePath</key>
<string></string>
<key>MaxKernel</key>
<string></string>
<key>MinKernel</key>
<string></string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
</dict>


So look for the Kernel key, under <dict> you have the <key>Add</key> in which you have the <array> in which you are adding the 2 dict éléments from the original post.

Of course you have to add the kext in the right folder

No joy, it panics every time I amend the plist to try to get WiFi. As for the kext I would assume it goes in the kext folder

 

[GSXB]

Hi folks. I can confirm that works as expected on my 5,1 with stock wifi on Big Sur 11.0.1.
We are always more near to a perfect "vanilla" machine....
Thank you for keeping this thread updated with such great news

Post you config.plist I’ve tried all sorts can’t get it working

 

[w1z]

A quick update on the non-bootable Big Sur USB installer issue -

It was a flash drive issue 🤦‍♂️

Attempting Big Sur clean install with SecureBoot temporarily disabled by setting it to j160.

Update 1: First attempt failed around the 15 minute mark due to drive read error. So I unplugged the USB flash drive from the USB 3 hub it was connected to and plugged it in the cMP's front USB port and rebooted. Erased destination drive, restarted the installation and it completed without errors. cMP rebooted at least 3 times during the installation so that's normal.

Update 2: SSV - Seal is broken when SecureBootModel is set to j160, Default or Disabled and ApECID is set to 0. Attempting another installation with ApECID value populated using a 64-bit integer and SecureBootModel set to j160. Looking at OpenCore Big Sur page, you can generate one by executing:

python3 -c 'import secrets; print(secrets.randbits(64))'

I am using Big Sur's recovery volume to reinstall with SecureBootModel, aka Apple Secure Boot, fully enabled - let's see.

Update 3: Big Sur successfully installed with SecureBootModel fully enabled but the volume's seal is still showing as broken. Snapshot seal on the other hand is sealed/ok.

 

[csxlab]

Another huge step in getting BCM4322 to work in Catalina and Big Sur

GitHub - khronokernel/IO80211-Patches: Repo for patched IO80211Family Kexts

Repo for patched IO80211Family Kexts. Contribute to khronokernel/IO80211-Patches development by creating an account on GitHub.

github.com

Stock IO80211Family kext from Mojave already works in Catalina, but there were kernel panics when entering recovery because of collission with Catalina's version. Big Sur did not even boot as Big Sur's version is already preloaded in prelinked kernel and trying to inject Mojave version results in kernel panic too.

Patched IO80211Family kext above does not collide with system versions so original Broadcom card now works in Catalina's recovery and even in Big Sur without any system partition modifications!

            <dict>
                <key>Comment</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
                <key>Enabled</key>
                <true/>
                <key>MaxKernel</key>
                <string>20.99.99</string>
                <key>MinKernel</key>
                <string>19.0.0</string>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/IO80211Mojave</string>
                <key>Arch</key>
                <string>Any</string>
                <key>BundlePath</key>
                <string>IO80211Mojave.kext</string>
            </dict>
            <dict>
                <key>Comment</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
                <key>Enabled</key>
                <true/>
                <key>MaxKernel</key>
                <string>20.99.99</string>
                <key>MinKernel</key>
                <string>19.0.0</string>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/AirPortBrcm4331</string>
                <key>Arch</key>
                <string>Any</string>
                <key>BundlePath</key>
                <string>IO80211Mojave.kext/Contents/PlugIns/AirPortBrcm4331.kext</string>
            </dict>

@cdf It might be a good idea to add this into the wiki post after more testing is done

hi there, I have this card and I just installed Big Sur with Open Core 0.6.3. Can I ask how do I do this?
I am trying to find a tutorial for dummies, as I tried this a few days ago, and broke my open core (off course I did something wrong) .. and now I am a bit afraid to do something to update the wi-fi kexts.

 

[tsialex]

I updated my thread, related to Bluetooth issues, might help others.

One thing to comment here, while the BT problem seems much more common than I initially thought from the dumps I've checked since I added the bluetoothActiveControllerInfo scan, several people on the OC thread like @cdf @h9826790 @startergo and others already have the reconstructed BootROMs and probably won't have the problem at all.

Yesterday, I checked my two Mac Pros and even being used as testbeds, with the NVRAM being hit hard with frequent updates from changes of hardware, and the main offender DIMMs, I didn't find the duplication of bluetoothActiveControllerInfo, besides the usual backup on the second store.

So for me, and probably several others that have reconstructed BootROM images already, this duplication is not happening by the fact that we flash the reconstructed one whenever needed - I usually flash the cleaned one every three months or so.

 

[Enricote]

One thing to comment here, while the BT problem seems much more common than I initially thought from the dumps I've checked since I added the bluetoothActiveControllerInfo scan, several people on the OC thread like @cdf @h9826790 @startergo and others already have the reconstructed BootROMs and probably won't have the problem at all.

Yesterday, I checked my two Mac Pros and even being used as testbeds, with the NVRAM being hit hard with frequent updates from changes of hardware, and the main offender DIMMs, I didn't find the duplication of bluetoothActiveControllerInfo, besides the usual backup on the second store.

So for me, and probably several others that have reconstructed BootROM images already, this duplication is not happening by the fact that we flash the reconstructed one whenever needed - I usually flash the cleaned one every three months or so.

I have My BootROM reconstructed by Tsialex yesterday. It gives peace of mind to know you can clean your very attacked BootROM after so many changes and trials and you can do it again from time to time. Procedure from Tsialex is very straight forward even for simple users, like me. Very cost-effective in my humble opinion.

 

[AndreeOnline]

Has anyone confirmed to have a Vega Frontier Edition HW accelerated in Catalina or Big Sur? It has always been my feeling it should be possible, but it doesn't seem to be a very common card (but has been of great use to me with its 16GB of RAM in Resolve).

For the longest time I let my Mac Pro sit happy with Mojave, but I'm spending some time now to see what can be done with Big Sur (which is up and running).

While most things seem smooth, Resolve 17 won't start. I'll look into that when I feel MacOS and the Mac Pro work in harmony.

I was quickly up and running mostly thanks to @h9826790 — so a shout out/thanks to him! And a followup question: after installing your package, to get HWaccel working, do I only need to edit the address of the gfx card?

Thanks to everyone for all the great work, even if I don't quite find the time to stay up to date at every turn. Still nice to browse the threads and gain insight into various things. 👍🏻

 

[Stefano85]

Post you config.plist I’ve tried all sorts can’t get it working

I’m out for work at the moment, tonight I’ll upload it in this post.
Cheers

@GSXB @csxlab

here attached my config.plist and the patched kext to put in the OC/Kexts folder
Clearly pay attention if you think to use my config.plist... I think the best is to only use it about how to insert the strings into your one.

 

[TECK]

Yesterday, I checked my two Mac Pros

I think something is different in Big Sur, I’ll report back if the Bluetooth issue makes surface. I plan to reboot every day, last time it took 2 days to lose Bluetooth after an NVRAM reset.

 

[h9826790]

Has anyone confirmed to have a Vega Frontier Edition HW accelerated in Catalina or Big Sur? It has always been my feeling it should be possible, but it doesn't seem to be a very common card (but has been of great use to me with its 16GB of RAM in Resolve).

For the longest time I let my Mac Pro sit happy with Mojave, but I'm spending some time now to see what can be done with Big Sur (which is up and running).

While most things seem smooth, Resolve 17 won't start. I'll look into that when I feel MacOS and the Mac Pro work in harmony.

I was quickly up and running mostly thanks to @h9826790 — so a shout out/thanks to him! And a followup question: after installing your package, to get HWaccel working, do I only need to edit the address of the gfx card?

Thanks to everyone for all the great work, even if I don't quite find the time to stay up to date at every turn. Still nice to browse the threads and gain insight into various things. 👍🏻

Vega FE should have HWAccel in Big Sur as long as you inject the iMac Pro / Mac Pro 7,1 board ID via OpenCore (my package injected the iMac Pro board ID by default). Nothing else is required.

But in Big Sur, if you need multi monitors support, you have to change the board ID to the 7,1's board ID.

OpenCore on the Mac Pro

Known issue, as discussed before. OC developer team fully aware this issue, and looking for solution. On my cMP, SSD on TempoSSD has highest priority (e.g. boot to that drive first after NVRAM reset). You should able to keep the Mojave drive on the TempoSSD as fail safe. Doesn't make sense...

forums.macrumors.com

 

[EETagent]

hi there, I have this card and I just installed Big Sur with Open Core 0.6.3. Can I ask how do I do this?
I am trying to find a tutorial for dummies, as I tried this a few days ago, and broke my open core (off course I did something wrong) .. and now I am a bit afraid to do something to update the wi-fi kexts.

How did you broke your OpenCore? What error OC displayed?

1) Add IO80211Mojave.kext into the OC/Kexts folder
2) Make ProperTree snapshot or add that XML after other kext entries in config.plist

 

[TECK]

It was a flash drive issue

Can you please let me know why do you use a flash drive instead of performing the clean install from Mojave? Curios to see the usability for you.