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.
Unbelievable! Using Martin's 0.7.3 and 0.7.4, I was booted back to Big Sur after attempting Monterey Install. Search for @cdf configuration that everyone was talking about... I was about to give up and wait for Martin's update. But on page 120 there are two config.txt files for 0.7.4 OC: @Stex and @abaxworld. One last try and they both works! The differences are:

Big-Sur-MP-2:Downloads xmaster$ diff -b config.plist-abaxworld config.plist-stex
513c513
< <data>fwgAAA==</data>
---
> <data>AAAAAA==</data>
595c595
< <data>AxQMwAgAAAA=</data>
---
> <data></data>
597c597
< <data>P/8f/wgAAAA=</data>
---
> <data></data>

Stex's have System Integrity Protection enabled. abaxworld's was Martin's 0.74 original configuration.
Both good!

Differences between abaxworld's and Martin's
Big-Sur-MP-2:Downloads xmaster$ diff -b config.plist-abaxworld OpenCore/0.7.4/EFI/OC/config.plist
249c249
< <data>AAAAAAAAAAAAAAAAAAAAAA==</data>
---
> <data>AAAAAAAAAAAAAACAAAAAAA==</data>
490c490
< <string>Default</string>
---
> <string>Disabled</string>
571,587d570
< <key>PlatformNVRAM</key>
< <dict>
< <key>BID</key>
< <string></string>
< <key>FirmwareFeatures</key>
< <data>A1QMwAgAAAA=</data>
< <key>FirmwareFeaturesMask</key>
< <data>P/8f/wgAAAA=</data>
< <key>MLB</key>
< <string></string>
< <key>ROM</key>
< <data></data>
< <key>SystemSerialNumber</key>
< <string></string>
< <key>SystemUUID</key>
< <string></string>
< </dict>
595c578
< <data>AxQMwAgAAAA=</data>
---
> <data>A1QM4A==</data>
597c580
< <data>P/8f/wgAAAA=</data>
---
> <data>P/8f/w==</data>
840c823
< <true/>
---
> <false/>


@Stex @abaxworld @cdf @h9826790
 
So far so good. But...

I'm getting some strange artifacts when editing 4k in Final Cut Pro X 10.6. Does this have to do with the Patcher?
If that's H264 / HEVC, then it's a known issue that the hardware decoder may shows artifacts in the timeline under some situation. It's relatively rare, but happens.


 
  • Like
Reactions: Danielgbr
Hey guys, so with some digging and a few coffee cups with some friends over on discord, some friends believe that the problem's with Feature Unlock. So I loaded up the config.plist and did a search and found that by default its active (for NightShift). Deactivated it (changed YES > NO). Let's see if things will work better
Please let me know if disable Feature Unlock fixed that issue. If yes, then I will keep Feature Unlock in the package, but make that disabled by default.
 
  • Like
Reactions: Danielgbr
Safest option would be to wait for @h9826790 to update the package, which he does regularly when OC updates are released. But if you would like to give it another try before then, you can try my attached config that worked for my system. Note that I had the same problem (installer reverting back to macOS 11.6.1) when using the original @h9826790 OC package (both 0.7.3 and 0.7.4) without any modifications. I then revisited step by step the @cdf comprehensive OC guide in the main OC thread to map any changes/additions that I needed to make, and also followed the various recent suggestions shared by @cdf and others in that thread over the past few days. I realize this is similar to what you did, but you might have missed one or two changes in the config. The config here attached is by no means a long term solution, and even if it works for you (and others), you should still update to the latest @h9826790 OC package whenever it is posted in this thread. Also FYI, hardware acceleration is working on my system running macOS 12.0.1, and so does BT and WIFI (with updated internal BT/WIFI card connected to an external USB 2.0 port) . Everything else works for that matter, as it did previously when running macOS Big Sur 11.x.x.
thank you very much. I will try that config!
 
Safest option would be to wait for @h9826790 to update the package, which he does regularly when OC updates are released. But if you would like to give it another try before then, you can try my attached config that worked for my system. Note that I had the same problem (installer reverting back to macOS 11.6.1) when using the original @h9826790 OC package (both 0.7.3 and 0.7.4) without any modifications. I then revisited step by step the @cdf comprehensive OC guide in the main OC thread to map any changes/additions that I needed to make, and also followed the various recent suggestions shared by @cdf and others in that thread over the past few days. I realize this is similar to what you did, but you might have missed one or two changes in the config. The config here attached is by no means a long term solution, and even if it works for you (and others), you should still update to the latest @h9826790 OC package whenever it is posted in this thread. Also FYI, hardware acceleration is working on my system running macOS 12.0.1, and so does BT and WIFI (with updated internal BT/WIFI card connected to an external USB 2.0 port) . Everything else works for that matter, as it did previously when running macOS Big Sur 11.x.x.
Thanks, Stex, this worked for me! At first I tried to just continue with the existing Monterey installation attempt, but this was just resulting in the same reboot as before and I could only get back to 11.6.1. I restarted the Monterey installation from there and it went through without a problem.
 
Hi everybody, hope this doesn't interrupt this thread. If so please move to elsewhere. I have had a superficial look for similar issues and again sorry if it is dealt with elsewhere in this thread.

I've been happily using this excellent and easy to understand OpenCore patcher for a while now. First with Catalina and now for a couple of months trouble free with Big Sur installed on a PCIE NVME SSD.

However last night I began to run into issues with sleep. I have installed nothing new and run no updates on any software for a few weeks prior. In the middle of the day the computer started experiencing the racing fans when it tried to enter sleep mode having been sleeping perfectly fine up until this point.

I performed a 3 chime NVRAM reset to see if that would maybe help with this issue.

Having done that it is now not possible to boot back into BigSur with any other bootable drives installed in the machine (There is a legacy version of High Sierra on a HDD and Mojave on another PCIE SSD that I keep around for the occasional file and 32bit compatibility). If either of these drives are installed in the Mac it defaults to booting into one of these whatever order the drives are installed in bays or PCI slots. It is then not possible to boot back into BigSur due to the 'incompatible drive' warning that has been noted before and these OS' not recognising the Big Sur drive as a boot volume (It shows up as two drives BigSur_Data and Update). The only way to boot into BigSur is to make sure that all the other boot drives are removed.

Additionally upon boot without other drives installed the HDMI port stops working when the machine gets to the log in screen. It displays the boot picker and loading screen until login and then becomes non responsive until the cable is unplugged and plugged back in again. The main Apple DVI monitor continues to function fine.

Without the other drives installed the machine seems to be functioning correctly and sleep is working as normal again.

Have updated from 0.7.3 to 0.7.4 and the behaviour remains.

Any advice?

Mac Pro Late 2009 5,1 (Flashed 4,1)
Big Sur 11.6 PCIE SSD
OpenCore 0.7.4
2x 3.46Ghz
64GB Ram (8x8GB)
Saphire Radeon RX470 8GB
 
Hi everybody, hope this doesn't interrupt this thread. If so please move to elsewhere. I have had a superficial look for similar issues and again sorry if it is dealt with elsewhere in this thread.

I've been happily using this excellent and easy to understand OpenCore patcher for a while now. First with Catalina and now for a couple of months trouble free with Big Sur installed on a PCIE NVME SSD.

However last night I began to run into issues with sleep. I have installed nothing new and run no updates on any software for a few weeks prior. In the middle of the day the computer started experiencing the racing fans when it tried to enter sleep mode having been sleeping perfectly fine up until this point.

I performed a 3 chime NVRAM reset to see if that would maybe help with this issue.

Having done that it is now not possible to boot back into BigSur with any other bootable drives installed in the machine (There is a legacy version of High Sierra on a HDD and Mojave on another PCIE SSD that I keep around for the occasional file and 32bit compatibility). If either of these drives are installed in the Mac it defaults to booting into one of these whatever order the drives are installed in bays or PCI slots. It is then not possible to boot back into BigSur due to the 'incompatible drive' warning that has been noted before and these OS' not recognising the Big Sur drive as a boot volume (It shows up as two drives BigSur_Data and Update). The only way to boot into BigSur is to make sure that all the other boot drives are removed.

Additionally upon boot without other drives installed the HDMI port stops working when the machine gets to the log in screen. It displays the boot picker and loading screen until login and then becomes non responsive until the cable is unplugged and plugged back in again. The main Apple DVI monitor continues to function fine.

Without the other drives installed the machine seems to be functioning correctly and sleep is working as normal again.

Have updated from 0.7.3 to 0.7.4 and the behaviour remains.

Any advice?

Mac Pro Late 2009 5,1 (Flashed 4,1)
Big Sur 11.6 PCIE SSD
OpenCore 0.7.4
2x 3.46Ghz
64GB Ram (8x8GB)
Saphire Radeon RX470 8GB
Boot to any drive, re-install OC 0.7.4, including run the bless tool (make sure SIP still disabled). This should makes your cMP default boot to OC 0.7.4 again, which allows you to select the OS you want.
 
  • Like
Reactions: Jackdown_101
Boot to any drive, re-install OC 0.7.4, including run the bless tool (make sure SIP still disabled). This should makes your cMP default boot to OC 0.7.4 again, which allows you to select the OS you want.
Thanks for this.... tried this but have the same result.


I noticed that the drive was displaying with an odd file name when I blessed the EFI and I think something else is going on here with my install as the drive structure is looking very wrong....

Screenshot 2021-10-29 at 14.08.24.png



Screenshot 2021-10-29 at 14.04.33.png


Everything appears to be working, apart from at boot, but there have clearly been issues somewhere. Catalina_Opencore was the name of the drive before the Big Sur update. I changed in to OpenCore Boot following the install.

EDIT
Just caught up with this secure volume thing from apple. Sorry if not relevant.
 
Last edited:
Please let me know if disable Feature Unlock fixed that issue. If yes, then I will keep Feature Unlock in the package, but make that disabled by default.
So far no issues. Today I have a long work day on that computer and I'll be able to see if it worked.
 
  • Like
Reactions: h9826790
It's h264 4k hlg (hdr format). Today I'll be editing in premiere and I'll see if this is limited to FCPX or if it's a hardware issue. Keep you guys posted
If that's H264 / HEVC, then it's a known issue that the hardware decoder may shows artifacts in the timeline under some situation. It's relatively rare, but happens.


 
Can a kind soul lead me to the right direction?!?

Scenario
I am using Martin Lo's package 0.7.4 to boot with OpenCore on a MacPro 5,1.
It sits on a removable USB Stick and works perfectly.

Sometimes I want to boot without OpenCore.
I remove the stick and restart. Selected the SSD with BigSur 11.6.1 before in the SystemPreferences as boot device.
The boot-args has -no_compat_check AND SIP is always diabled.
But it ends up in shutting down the machine as it would do without the nvram boot-args parameter.

When I used the OCLP before I could do the above scenario with no problems at all.

So my guess is the Martin Lo packages changes somthing to either the boot-args or SIP or both.

My question: Is that true and if so how can I stop it from doing this?

Cheers. Thanks for any hint.
 
Thanks for this.... tried this but have the same result.


I noticed that the drive was displaying with an odd file name when I blessed the EFI and I think something else is going on here with my install as the drive structure is looking very wrong....

View attachment 1883139


View attachment 1883136

Everything appears to be working, apart from at boot, but there have clearly been issues somewhere. Catalina_Opencore was the name of the drive before the Big Sur update. I changed in to OpenCore Boot following the install.

EDIT
Just caught up with this secure volume thing from apple. Sorry if not relevant.
I had issues when trying to use OpenCore coming from Catalina (using dosdude). I have a NVME via PCI and when I formated the drive, installed Mojave and Opencore, I had issues. Had to format the NVME drive a few times to complete removing everything, because previously there was an extra Data partition and Recovery drive. Those leftovers caused problems. Don't know if this could be your issue.
 
Safest option would be to wait for @h9826790 to update the package, which he does regularly when OC updates are released. But if you would like to give it another try before then, you can try my attached config that worked for my system. Note that I had the same problem (installer reverting back to macOS 11.6.1) when using the original @h9826790 OC package (both 0.7.3 and 0.7.4) without any modifications. I then revisited step by step the @cdf comprehensive OC guide in the main OC thread to map any changes/additions that I needed to make, and also followed the various recent suggestions shared by @cdf and others in that thread over the past few days. I realize this is similar to what you did, but you might have missed one or two changes in the config. The config here attached is by no means a long term solution, and even if it works for you (and others), you should still update to the latest @h9826790 OC package whenever it is posted in this thread. Also FYI, hardware acceleration is working on my system running macOS 12.0.1, and so does BT and WIFI (with updated internal BT/WIFI card connected to an external USB 2.0 port) . Everything else works for that matter, as it did previously when running macOS Big Sur 11.x.x.
Thank you very much for your post. I really don't know what's wrong with my Mac (or me haha) but that config does not boot....
 
So far no issues. Today I have a long work day on that computer and I'll be able to see if it worked.

Please let me know if disable Feature Unlock fixed that issue. If yes, then I will keep Feature Unlock in the package, but make that disabled by default.
So I spent the day working normally on my Mac Pro and had no issues after disabling FeatureUnlock. I believe this was the solutions to the problem
 
Is there a guide to installing Big Sur with OC on a 5,1? Or is it as simple as making a bootable USB?

Also can't seem to find the initial release or can I just use v11.6.1 Build 20G224 which seems to still be available.
 
Is there a guide to installing Big Sur with OC on a 5,1? Or is it as simple as making a bootable USB?

Also can't seem to find the initial release or can I just use v11.6.1 Build 20G224 which seems to still be available.
I suggest you use the EFI file from @h9826790 , in #1,314

You can use any release you like.
 
I suggest you use the EFI file from @h9826790 , in #1,314

You can use any release you like.
Thanks man.

No that's not what I'm asking. I have the current OC installed in my Mojave EFI partition.

Is there a guide to installing Big Sur with OC already on a 5,1? Or is it as simple as making a bootable Big Sur USB?

Is the Big Sur installation process able to be done from a bootable Big Sur install USB? I'm asking because I thought perhaps the 'upgrade' path from system preferences was the only option for OC users.

***Also can't seem to find the initial release or can I just use v11.6.1 Build 20G224 which seems to still be available.



Screen Shot 2021-11-01 at 3.35.32 pm.png


Screen Shot 2021-11-01 at 3.32.23 pm.png
 
Last edited:
Thanks man.

No that's not what I'm asking. I have the current OC installed in my Mojave EFI partition.

Is there a guide to installing Big Sur with OC already on a 5,1? Or is it as simple as making a bootable Big Sur USB?

Is the Big Sur installation process able to be done from a bootable Big Sur install USB? I'm asking because I thought perhaps the 'upgrade' path from system preferences was the only option for OC users.

***Also can't seem to find the initial release or can I just use v11.6.1 Build 20G224 which seems to still be available.



View attachment 1899265

View attachment 1899266
Hey! This guy on YouTube does an update to Martin Lo's OC package to the new version to get Big Sur. Pretty straight forward:
 
  • Like
Reactions: offdwall
Hey guys, so my artifacting with HWACCEL is pretty bad. Can't get any work done. So I've spent most of the day goin through the forum. I can't figure out what in the config.plist on EFI I have to deactivate to turn off HWACCEL. Can anyone point this out?

Thanks!
 
Got a bit of a really out on a limb unsupported question here. I'm running a MacPro 5,1, macOS 11.6.1, Martin's OC 0.7.4. I just put in a mac flashed Titan Ridge TB3 card and am attempting to run a UAD Octo PCIe card in a Sonnet Echo Express SE 1 PCIe to TB 3 chassis.

I've got two scenarios that happen, neither of which is great:

1)With ThunderBolt 3 enabled (true) in OpenCore config,, the system kernel panics on a cold boot. After a warm restart, all functions fine, the UAD card is recognized and works. TB hot swapping of drives works as well. Issue is the kernel panic on cold start. Log dump shows the Universal Audio drivers crashing.

2) With ThunderBolt 3 disabled (false) in OpenCore config, no kernel panic on a cold boot but the UAD card is not recognized. After a warm restart, all functions fine, the UAD card is recognized and works. The issue with this configuration is there is no hot swapping of other TB devices.

The UAD card works fine in a PCI slot in the 5,1 but I'm out of slots and want to add TB3 USBC. The chassis/UAD PCIe card combo also works fine on a supported MBP in Big Sur, so it's definitely something with the Titan Ridge and or OpenCore on the 5,1.

Any suggestions? thx.
 
  • Like
Reactions: kings79
Why is Big Sur crossed out on Martin's guide #1314 @h9826790

Additional option 3: If you want to enable the ability to install / update Catalina, Big Sur and Monterey, please follow the steps in this video. [N.B. you should revert the changes after macOS installation completed. This special setting is not designed for daily use]

Can you not upgrade from Mojave to Big Sur anymore?
I Have 11.5.2 20G95 App in my App folder.
 
Why is Big Sur crossed out on Martin's guide #1314 @h9826790

Additional option 3: If you want to enable the ability to install / update Catalina, Big Sur and Monterey, please follow the steps in this video. [N.B. you should revert the changes after macOS installation completed. This special setting is not designed for daily use]

Can you not upgrade from Mojave to Big Sur anymore?
I Have 11.5.2 20G95 App in my App folder.
I believe it just means you don't have to mess with the VMM flag for Big Sur and you do for Catalina and now apparently Monterey.
 
  • Like
Reactions: h9826790
I believe it just means you don't have to mess with the VMM flag for Big Sur and you do for Catalina and now apparently Monterey.
Yer sweet.

So does that mean I just DL the installer app and launch it from the app folder?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.