You are right @johnwillsey, I just timed mines and it took 20 seconds from chime to OpenCanopy selector. I never really noticed this, as I never reboot my Mac.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
There is no need to install Catalina if you want Big Sur.
Or you want to dual boot these two OS?
I figured I get everything setup as per the first page than do Big Sur.
What do I need to do to install Big Sur now?
Turn off VMM, make sure SMBIOS spoofing turned on with the required firmware feature mask.
Can I just clarify one thing about moving to Big Sur.
I'm currently on latest Catalina and have upgraded my OC to 0.63 last night.
If I upgrade Catalina to Big Sur using the above method, I will lose DRM content playback?
Yeah, my cMP at home with the Nano. If I take that it works fine - but I assume that eliminates any chance of HWA. But it seems like it wasn't supported with the Nano anyway. I refreshed and checked VideoProc with it in there and it still said unsupported. I can live without it - not doing anything that really requires it anyway, and if I do I'll just swap out to a card that's supported.
Thanks for all the help!
Yeah.. red boxes for video in safari, but OK in chrome for Netflix and Amazon. (just clarifying since it's not completely lost)
Chrome etc don't use DRM.
Anyway, the cMP will only lost DRM streaming ability. For fully downloaded video (e.g. in TV apps), the cMP should still able to play the movie
Hi,
I've got exactly what the first page says. I believe is the iMac Pro string.
What do I need to have in SMBIOS?
Thanks
You can simply download my pre-configured OpenCore package here.
Activate AMD hardware acceleration
I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package updated to 1.0.0] For those who only need HWAccel, post #594 has everything you need. This new package mainly offer HWAccel + boot screen. Also, this package should work in...
forums.macrumors.com
The 0.6.3 version support Big Sur by default.
You can simply download my pre-configured OpenCore package here.
Activate AMD hardware acceleration
I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package updated to 1.0.0] For those who only need HWAccel, post #594 has everything you need. This new package mainly offer HWAccel + boot screen. Also, this package should work in...
The 0.6.3 version support Big Sur by default.
Uff install all that scares the life out of me.
Did get it from your config thanks.
<key>SMBIOS</key>
<dict>
<key>BoardProduct</key>
<string>Mac-7BA5B2D9E42DDD94</string>
<key>ProcessorType</key>
<integer>1281</integer>
<key>FirmwareFeatures</key>
<data>A1QM4A==</data>
<key>FirmwareFeaturesMask</key>
<data>P/8f/w==</data>
</dict>
With Big Sur and SMBIOS Mac Pro 7.1, I need Lilu, WhateverGreen and graphic card PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)?You can simply download my pre-configured OpenCore package here.
Activate AMD hardware acceleration
I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package updated to 1.0.0] For those who only need HWAccel, post #594 has everything you need. This new package mainly offer HWAccel + boot screen. Also, this package should work in...
The 0.6.3 version support Big Sur by default.
Catalina has been working well for me, but I had some problems with getting Big Sur to boot without the MVV flag on. I did apply the new SMBIOS as well. It booted fine, but every time I rebooted, it went into the Opencore progress bar, but never finished. I rebooted into Catalina, and the Big Sur boot volume was grayed out (the -data volume was fine).
After the next install, I went directly to Disk Utility, and saw that the boot drive was the snapshot. I tried a few things without success. After the first boot, it never booted into Big Sur again. I even downloaded the install a couple times, and made a new APFS volume each time.
I was hoping to see someone else with the same problem on this thread, but haven't as yet.
I have the Catalina volume on a 970 on the 12-core, a 960 on the 6-core, and the Big Sur volume is on a SATA SSD connected to a powered SATA cable. That setup has worked fine in the past. Only one volume per physical disk. I didn't even have the Mojave volume connected for the 6-core.
Any help would be greatly appreciated.
After the next install, I went directly to Disk Utility, and saw that the boot drive was the snapshot. I tried a few things without success. After the first boot, it never booted into Big Sur again. I even downloaded the install a couple times, and made a new APFS volume each time.
I was hoping to see someone else with the same problem on this thread, but haven't as yet.
I have the Catalina volume on a 970 on the 12-core, a 960 on the 6-core, and the Big Sur volume is on a SATA SSD connected to a powered SATA cable. That setup has worked fine in the past. Only one volume per physical disk. I didn't even have the Mojave volume connected for the 6-core.
Any help would be greatly appreciated.
Do you have multiple drives with multiple EFIs? if so, perhaps an EFI is loading that does not support Big Sur and it's being loaded? (That where I'd start looking)...
I am writing just to thank you for all your work.
I had Catalina (everything ok), now I have Big Sur (everything ok).
THANK YOU VERY MUCH.
- 4.1 ~ 5.1 (12 Cores, 2 x X5690)
- Graphic EVGA GTX 680 4Gb flash Mac edition
- SSD 1Tb macOS + M2 1T Data
- Wifi BCM94360CD BT4.0
I had Catalina (everything ok), now I have Big Sur (everything ok).
THANK YOU VERY MUCH.
- 4.1 ~ 5.1 (12 Cores, 2 x X5690)
- Graphic EVGA GTX 680 4Gb flash Mac edition
- SSD 1Tb macOS + M2 1T Data
- Wifi BCM94360CD BT4.0
@cdf I applied @h9826790's patch for external NVMe and removed all Kernel dictionary keys who are marked as failsafe, see PR.
@h9826790 you can safely remove the failsafe keys, for example:
Will translate into a nice compact patch:
@h9826790 you can safely remove the failsafe keys, for example:
Code:
Kernel = {
'Patch': [
{
'Comment': 'Set external NVMe drive as internal',
'Enabled': True,
'Find': unhexlify_data('45 78 74 65 72 6E 61 6C'),
'Identifier': 'com.apple.iokit.IONVMeFamily',
'Replace': unhexlify_data('49 6E 74 65 72 6E 61 6C')
}
]
}Will translate into a nice compact patch:
Code:
<key>Kernel</key>
<dict>
<key>Patch</key>
<array>
<dict>
<key>Comment</key>
<string>Set external NVMe drive as internal</string>
<key>Enabled</key>
<true/>
<key>Find</key>
<data>
RXh0ZXJuYWw=
</data>
<key>Identifier</key>
<string>com.apple.iokit.IONVMeFamily</string>
<key>Replace</key>
<data>
SW50ZXJuYWw=
</data>
</dict>
</array>
</dict>
Last edited:
As a purist, I would argue that the patch is a hack: it simply replaces the string "External" by "Internal" in the kext. Cosmetically, it works, but technically, adding the device property is better: it's how Apple does it.
What steps did you take going from Catalina to Big Sur? The path there is not clear yet from yet from all these posts.
Hi. I'm using RefindPlus/OpenCore, and previously I was told to refer to the OpenCore thread for instructions on installing Catalina (which I did), and now I want to try out BigSur, so I assume I follow all the instructions and guidance here as well (and that this also all applies to those of us who use the RefindPlus/OpenCore method).
Just a couple of things I'm not sure on (yes, I've read OpenCore post #1 plus RefindPlus/Open post #1 all over again):
I want to install BigSur on a separate SSD (SATA Bay).
1. Should I use the
2. I saw in a video here that I have to change
3. When changing the SMBIOS info, do I copy this section below (i.e append it), or replace the entire section?
This is what I currently have – it has quite a few more
4. And do I need to Turn off boot selection routing by finding
And do I then have to do anything else once BigSur is installed to reverse or change anything back?
Just a couple of things I'm not sure on (yes, I've read OpenCore post #1 plus RefindPlus/Open post #1 all over again):
I want to install BigSur on a separate SSD (SATA Bay).
1. Should I use the
OC or OC_ALT boot option and make any changes to that config.plist option only? The reason I ask is that I read here lately that VMM needs to be toggled off, which is the default setting for RefindPlus/OpenCore OC (as opposed to RefindPlus's alternative OC_ALT which has VMM turned on by default).2. I saw in a video here that I have to change
UpdateSMBIOS from <true> to <false>. Does that also apply to the RefindPlus/OpenCore method?3. When changing the SMBIOS info, do I copy this section below (i.e append it), or replace the entire section?
Code:
<key>SMBIOS</key>
<dict>
<key>BoardProduct</key>
<string>Mac-7BA5B2D9E42DDD94</string>
<key>ProcessorType</key>
<integer>1281</integer>
<key>FirmwareFeatures</key>
<data>A1QM4A==</data>
<key>FirmwareFeaturesMask</key>
<data>P/8f/w==</data>
</dict>This is what I currently have – it has quite a few more
key s and strings additional to what's above:
Code:
<key>SMBIOS</key>
<dict>
<key>BIOSReleaseDate</key>
<string></string>
<key>BIOSVendor</key>
<string></string>
<key>BIOSVersion</key>
<string></string>
<key>BoardAssetTag</key>
<string></string>
<key>BoardLocationInChassis</key>
<string></string>
<key>BoardManufacturer</key>
<string></string>
<key>BoardProduct</key>
<string>Mac-F221BEC8</string>
<key>BoardSerialNumber</key>
<string></string>
<key>BoardType</key>
<integer>0</integer>
<key>BoardVersion</key>
<string></string>
<key>ChassisAssetTag</key>
<string></string>
<key>ChassisManufacturer</key>
<string></string>
<key>ChassisSerialNumber</key>
<string></string>
<key>ChassisType</key>
<integer>0</integer>
<key>ChassisVersion</key>
<string></string>
<key>FirmwareFeatures</key>
<data></data>
<key>FirmwareFeaturesMask</key>
<data></data>
<key>PlatformFeature</key>
<integer>0</integer>
<key>ProcessorType</key>
<integer>1281</integer>
<key>SmcVersion</key>
<data></data>
<key>SystemFamily</key>
<string>Mac Pro</string>
<key>SystemManufacturer</key>
<string></string>
<key>SystemProductName</key>
<string>MacPro5,1</string>
<key>SystemSKUNumber</key>
<string></string>
<key>SystemSerialNumber</key>
<string></string>
<key>SystemUUID</key>
<string></string>
<key>SystemVersion</key>
<string></string>
</dict>4. And do I need to Turn off boot selection routing by finding
RequestBootVarRouting and changing true to false ?And do I then have to do anything else once BigSur is installed to reverse or change anything back?
Your extra keys are all failsafe keys, you are repeating what is already set as default value by OC.
Just to point out that RefindPlus and OpenCore are two totally different applications and how you set up your OpenCore config has no relation to the fact that you chainload it via RefindPlus. That is, your questions can be simply asked in terms of setting up OpenCore as if you installed OpenCore by itself. That's why that thread recommends asking here for guidance if wanting to vary the defaults that comes with.
OC or OC_ALT have no specific significance and are just two instances of OpenCore. They can be set up exactly the same and the config file from one moved to the other. That one has something on and the other off, does not have any special relevance and you can have the setting both off or both on in the ConfigFactory Tool if you wish.To your query, the answer is that you decide which of the two instances you want to use for a purpose and set up the config file as you want.
As per above ... "RefindPlus/OpenCore method" is not a thing in terms of setting up OpenCore. OpenCore remains OpenCore. RefindPlus is just like Finder where you are presented with items you want to run. That's all there is to it and it doesn't change what you are running in the same way that using Finder to start a program as opposed to using the Dock does not change the program.
NB: No idea about the video just saying RefindPlus/OpenCore is no different to any other OpenCore.
The above is a subset of the full OpenCore config item (Refer to the Docs). You don't need to reproduce the full set as ConfigFactory does and you can either:
- Just use the subset
- Set the relevant keys that you currently have to match these. EDIT: Will need to ensure nothing else is in conflict.
- You could also just grab a config file such as that by @h9826790 and use it
The extra keys are put in by ConfigFactory in advance of where the OpenCore devs have hinted they are going with the setup but not yet needed to be explicitly specified.
It seems the config from @h9826790 is set to go for BigSur so I would just adopt that in your shoes and overwrite the config file of one of the two OpenCore Instances provided in MyBootMgr with this.
Having said all that, you may want to wait about two weeks for OpenCore 0.6.4 as there are gaps in OpenCore 0.6.3 relating to BigSur (the protection in OpenCore against undesirable firmware updates does not work in v0.6.3). MyBootMgr 064 will come with OpenCore 0.6.4 and have BigSur setup items but if you can't wait for OpenCore 0.6.4, you can build a copy from the code on GitHub and use the suggested Config file.
Last edited:
Currently works that way but the OpenCore devs have pointed out a few times that they actually do not have defaults and the behaviour on encountering such missing/unspecified fields is not defined.
Basically, while it currently uses the failsafe in such instances, it might fail on the next release, or, perhaps worse still, work as if you had input an undesirable entry. If you explicitly specify it as done in MyBootMgr however, you will get the failsafe.
See this comment and the others: https://github.com/acidanthera/bugtracker/issues/1122#issuecomment-680938158
Last edited: