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.
I erased my main NVMe drive, installed a fresh Mojave using a USB stick on my NVme - Mojave works fine - then I took the plunge with the usual 0.7.4 OC steps EFI files, blessing etc ; still good with Mojave. But the next step to go to BigSur 11.6 looked good - ie the install went well - but after the reboot failed i end up (starting of my backup drive) to see a new Volume called Update sitting on the desktop and a non-working NVMe-BigSur11.6-0.7.4. - maybe i should just go back to BigSur 11.2 if i can find it somewhere?

@abaxworld - are you saying you swapped the 0.7.4 config.plist (for yours) and it's all good?
 
Last edited:
I finally have been able to update from Beta 9 to RC2. The description of what I did is in the OpenCore on the MacPro forum, starting at post #9230 ( https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/page-370 ). Here it is my own config.plist modified as explained there. Hope it can help you to update your system too.
I've downloaded your config.txt renamed it to config.plist replaced mine and it will not boot with said config
any thoughts I have Martin lo's package also
 
I've downloaded your config.txt renamed it to config.plist replaced mine and it will not boot with said config
any thoughts I have Martin lo's package also
Try to use a fresh ( download the Martin's package again if needed ) one and modify the VMM flags to "OFF", the SecureBootModel to "Default" and add only PlatformInfo>PlatformNVRAM between PlatformInfo>Generic and PlatformInfo>SMBIOS. Put my file side by side with the original and modify as needed using BBEdit or other similar application. This config.plist is for OpenCore latest release ( 0.7.4 ), not for other previous versions.

EDITED: Also erase the files inside the folder /Library/Updates. I add my config.plist again in .zip format. May be, when you changed from .txt to .plist it kept the original extension.
 

Attachments

  • config.plist.zip
    5 KB · Views: 103
Last edited:
I erased my main NVMe drive, installed a fresh Mojave using a USB stick on my NVme - Mojave works fine - then I took the plunge with the usual 0.7.4 OC steps EFI files, blessing etc ; still good with Mojave. But the next step to go to BigSur 11.6 looked good - ie the install went well - but after the reboot failed i end up (starting of my backup drive) to see a new Volume called Update sitting on the desktop and a non-working NVMe-BigSur11.6-0.7.4. - maybe i should just go back to BigSur 11.2 if i can find it somewhere?

@abaxworld - are you saying you swapped the 0.7.4 config.plist (for yours) and it's all good?
I modified the original Martin Lo's config.plist using the instructions by @cdf and it worked perfectly ( yes, OC 0.7.4 ). I don't have a NVMe drive, just a regular SSD to the HD slot.
 
  • Like
Reactions: Cracticus
@abaxworld - thanks. but above my paygrade - work pending, editing in FCP so for now I have stable HardwareAcc in FCP 10.5.4 with 5,1 Catalina 10.15.7 (Catalina-patcher used to install to the NVMe from a Mojave boot) ; OC 0.6.8 ; EFI blessed. All good.
Screen Shot 2021-10-24 at 11.24.34 am.png


I will try BigSur(Plus) 11.6 in a few weeks time with the next stable OC build.
 
Last edited:
  • Like
Reactions: h9826790
I started the Mac OS 12 update, get all the way through the first part of the install and it reboots. Takes me to a screen saying it’s unable to install some firmware thing then forces me to reboot back to 10.14 (my other install drive) I can’t for the life of me get it past this firmware updater.

I have tried redownloading, starting over, a different drive.

I’m using martins .74 package and it worked great for 11.6

Can anyone help? I just at my wits end now
 
I started the Mac OS 12 update, get all the way through the first part of the install and it reboots. Takes me to a screen saying it’s unable to install some firmware thing then forces me to reboot back to 10.14 (my other install drive) I can’t for the life of me get it past this firmware updater.

I have tried redownloading, starting over, a different drive.

I’m using martins .74 package and it worked great for 11.6

Can anyone help? I just at my wits end now
Enable the VM flag always before doing updates.
 
  • Like
Reactions: r6novak
Enable the VM flag always before doing updates.
Thank you, honestly im really new to this and trying to learn. I tried looking up what that mean but I don’t get it. Where and how and where do I enable the VM flag? I hate sounding stupid but I really appreciate the help
 
Thank you for this custom pack. I have just upgraded from Catalina to Big Suf (10.15.7 to 11.6.1) overnight!
One year without any upgrades. I saw Monterey was released on yesterday and I think now is a right time for me to proceed a Major upgrade from Catalina to Big Surf. I need stablity so I couldn't play around uncertain upgrades.
 
Last edited:
I started the Mac OS 12 update, get all the way through the first part of the install and it reboots. Takes me to a screen saying it’s unable to install some firmware thing then forces me to reboot back to 10.14 (my other install drive) I can’t for the life of me get it past this firmware updater.

I have tried redownloading, starting over, a different drive.

I’m using martins .74 package and it worked great for 11.6

Can anyone help? I just at my wits end now
My package does not support Monterey yet.

Most likely I can include that in the upcoming 0.7.5 package. However, more tests need to be done.
 
Last edited:
Public Service Announcement:

GiveAwayOfTheDay has VideoProc 4.4 for Mac and Windows free today (Tuesday, 26oct21). Click that link, give an email address, they'll email you a download link. The downloaded file contains both the Windows installer and the Mac DMG. Once you install it, visit this link and click "Get License Code" to download the license keys. Enter the appropriate key the first time you run the software.

Notes:
  • I have no affiliation with GiveAwayOfTheDay, Digiarty, or any related entities. I receive no benefit from anyone downloading or using this. This is strictly a PSA, since VideoProc seems to be popular around here (and I personally like it).
  • The GAOTD license does not expire; however, it does not include any updates, so be careful to never update the software or your license will revert to the "trial version". (This happened to me more than once. :mad:)
  • If you're running multiple versions of MacOS on your system, you'll want to do separate installs on each MacOS version, since the license seems to be bound to where it's installed. The same license key will work for multiple installations (I verified this just now on my systems).
  • They seem to have renamed the product "VideoProc Converter" and introduced some companion products; at first glance, it appears that VideoProc Converter is more or less just an update of the old VideoProc product. I know nothing about the newer products.
  • What you're reading in this message is what I know. If you need help downloading, installing, registering, etc., you'll need to ask on the GiveAwayOfTheDay site or at VideoProc.com - I can't really help you with that.
  • GiveAwayOfTheDay offers like this one are only good for 24 hours. If I've done the math correctly, this offer is good until 08:00 GMT tomorrow (that's 03:00 EDT, midnight PDT).
Enjoy!
 
  • Like
Reactions: h9826790
There are a few users asked about how to stop Big Sur update to go beyond 11.2.3. For those who are using my OpenCore package (0.6.6 or older), and already running 11.2.3, here is the method.

Once you update the system to 11.2.3.
1) Mount the EFI partition
2) Open config.plist with a text editor
3) Search
Code:
<key>FirmwareFeatures</key>
<data>A1QM4A==</data>
<key>FirmwareFeaturesMask</key>
<data>P/8f/w==</data>
4) Remove them, save changes, and reboot.

N.B. This is not just to stop Big Sur update to go beyond 11.2.3. But completely disable the ability to install / update ANY versions of Big Sur. e.g. You can't even re-install 11.2.3 until you add these code back in. Therefore, please only do this if you know what you are doing. If you screw up your OS, and want to make a clean Big Sur installation. You will need to add these code back in by using another OS / boot drive / computer / etc.
I'm still on the hunt for the reason, why my system says 11.2.3 is the last version and there are no updates available. If I boot from my Mojave-install in the OC boot-picker, software update shows 11.6, if I boot from my BigSur 11.2.3 install software update shows Monterey. So the reason isn't OC or my cMP5.1, I think it must have to do with stopping the BigSur system-updates following 11.2.3. But I can't remember if how or I did it. Found the post above and noticed that these two entries "A1QM4A==" and "P/8f/w==" are missing in the 0.7.4 sample config file, that contains 2 entries for"FirmwareFeatures". Is this ok? But I think my problem is related to something else that prevents BigSur updates
 

Attachments

  • Bildschirmfoto 2021-10-26 um 18.04.04.png
    Bildschirmfoto 2021-10-26 um 18.04.04.png
    134.5 KB · Views: 91
  • Bildschirmfoto 2021-10-26 um 18.03.43.png
    Bildschirmfoto 2021-10-26 um 18.03.43.png
    141.7 KB · Views: 87
  • Bildschirmfoto 2021-10-26 um 18.57.14.png
    Bildschirmfoto 2021-10-26 um 18.57.14.png
    117.1 KB · Views: 87
I'm still on the hunt for the reason, why my system says 11.2.3 is the last version and there are no updates available. If I boot from my Mojave-install in the OC boot-picker, software update shows 11.6, if I boot from my BigSur 11.2.3 install software update shows Monterey. So the reason isn't OC or my cMP5.1, I think it must have to do with stopping the BigSur system-updates following 11.2.3. But I can't remember if how or I did it. Found the post above and noticed that these two entries "A1QM4A==" and "P/8f/w==" are missing in the 0.7.4 sample config file, that contains 2 entries for"FirmwareFeatures". Is this ok? But I think my problem is related to something else that prevents BigSur updates

Since Monterey was released on yesterday. The official update from Software Update pulls only Monterey. You have to download Big Surf 11.6 directly from Opencore thread. They have an utility allowing you to choose which build to download selectively which is awesome. It works for me. Run the following in your terminal. That's all.

 
Since I've upgraded to Big Surf 11.6.1 today. A big jump from Catalina 10.15.7 overnight. Then I installed the latest FCPX 10.6. The performance is suuuuuper fast!!! During the encoding phase to an output movie. The Mac now can make use 100% (465W) of GPU power (Vega 56) no matter the output format either a h264 or h265 (HEVC) mov file.

See the cap. It is amazing. In the previous build of FCPX. It could only make used of about 50% of GPU power. This new FCPX is totally rewritten and when it works on Big Surf. It works total differently. I've been waiting for this version of FCPX for years and finally it has come! Now, encoding a project movie which has 10 mins long is only a task of several minutes job!!! Cheers!!!
 

Attachments

  • Screen Shot 2021-10-27 at 02.47.02.png
    Screen Shot 2021-10-27 at 02.47.02.png
    62.7 KB · Views: 96
  • Screen Shot 2021-10-27 at 02.46.48.png
    Screen Shot 2021-10-27 at 02.46.48.png
    66.6 KB · Views: 93
Last edited:
Since Monterey was released on yesterday. The official update from Software Update pulls only Monterey. You have to download Big Surf 11.6 directly from Opencore thread. They have an utility allowing you to choose which build to download selectively which is awesome. It works for me. Run the following in your terminal. That's all.
Yeah, that did the trick. Downloaded the appropriate OS installer, worked without problems. Additionally to the updated system, softwareupdate list now all the remaining installs for BigSur. I think it has really been some kind of update-blocker I have applied to prevent automatic update as long as it has been advised not to go further than 11.2.3. Stupid me, I can't remember the way I did it. But problem solved, thanks for your help
 

Attachments

  • Bildschirmfoto 2021-10-26 um 22.35.04.png
    Bildschirmfoto 2021-10-26 um 22.35.04.png
    133.3 KB · Views: 95
  • Bildschirmfoto 2021-10-26 um 22.35.09.png
    Bildschirmfoto 2021-10-26 um 22.35.09.png
    158.8 KB · Views: 91
  • Like
Reactions: solaris8x86
My package does not support Monterey yet.

Most likely I can include that in the upcoming 0.7.5 package. However, more tests need to be do.
My package does not support Monterey yet.

Most likely I can include that in the upcoming 0.7.5 package. However, more tests need to be done.
I would love to see that on Monday! I am currently struggling to implement the appropriate changes myself. Maybe any insights on the missing PlatformNVRAM section?
 
I would love to see that on Monday! I am currently struggling to implement the appropriate changes myself. Maybe any insights on the missing PlatformNVRAM section?

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.
 

Attachments

  • config.plist.zip
    5 KB · Views: 99
Hey guys, I successfully installed Big Sur using Martin Los 0.7.4 on my Mac Pro 5,1. System drive is a NVME on PCI and running an XFX RX580.

The issue I'm facing is that after an hour or so Finder crashes. I try to relaunch it and it won't load. If I try to load any other app they won't load. Only solution is a restart. What should I do?
 
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
 
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?
 

Attachments

  • Screen Shot 2021-10-28 at 19.48.00.png
    Screen Shot 2021-10-28 at 19.48.00.png
    254.4 KB · Views: 70
  • Screen Shot 2021-10-28 at 19.47.54.png
    Screen Shot 2021-10-28 at 19.47.54.png
    505.4 KB · Views: 71
  • Screen Shot 2021-10-28 at 19.48.29.png
    Screen Shot 2021-10-28 at 19.48.29.png
    228.3 KB · Views: 74
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.