Sidebar Sidebar
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

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.
h9826790 said:
Thanks for this info. I haven't test this yet.

But if this is true, then we need to test at least

1) Update from 11.1 to 11.2 by using OTA
2) Install 11.2 via full installer in 11.1
3) Install 11.2 via full installer from Catalina (the OS that just before Big Sur)
4) Install 11.2 via full installer from Mojave (the OS that last support on 5,1)
5) install 11.2 from Big Sur recovery partition

And found out which exact situation need the Firmware Feature injection.

e.g. In case 4, in general, VMM flag should be off. Which means, without the Firmware Feature, the installer should reject the 5,1 to install 11.2.
Click to expand...
Case 1 tested: iMac Pro board ID, BIOSVersion protection, no firmware features, VMM flag off. Update went smoothly.
 
  • Like
Reactions: Norbert Mikołajczyk and h9826790
Dewdman42 said:
CDF, I see that you removed the following from your provided base config.plist:

XML: 
<key>run-efi-updater</key>
    <string>No</string>


You didn't mention anything in your update section of the guide for 0.6.6, So just wondering what that was, why its gone, etc. I am guessing that this is because we have BIOSVersion to prevent firmware update, so don't need that now?
Click to expand...
You can keep this variable if you want, but it has no effect in Big Sur, and with BIOSVersion set, in addition to BlacklistAppleUpdate, you should be more than covered in both Catalina and Big Sur.
 
Last edited:
startergo said:
No it will install the default keys (empty strings or int 0) so OC validator does not complain about them.
Click to expand...
I added all the missing keys, except for PlatformInfo Memory keys, which IMO cannot be standardized and be safely omitted. The only way to grab these keys is with dmidecode and they unique to every Mac. I believe they can be safely skipped.

I also added an automated validation step, see PR #65 (@cdf, you should add these missing keys into your config.plist also):
Code: 
* Miscellaneous
  - fixing file permissions... OK
  - validating config.plist...
OCS: Missing key DataWidth, context <Memory>!
OCS: Missing key Devices, context <Memory>!
OCS: Missing key ErrorCorrection, context <Memory>!
OCS: Missing key FormFactor, context <Memory>!
OCS: Missing key MaxCapacity, context <Memory>!
OCS: Missing key TotalWidth, context <Memory>!
OCS: Missing key Type, context <Memory>!
OCS: Missing key TypeDetail, context <Memory>!

Done checking Volumes/EFI/EFI/OC/config.plist in 0 ms

I added a new PR #67 and filtered these keys, for now. If you know what default values I should add, please let me know. For example ErrorCorrection should be 3? if the failsafe 8bit int is 0x03?
 
Last edited:
Thank you all for your hard work and energy invested in this project.
Upgrade to Big Sur from Catalina on my Mac Pro 5.1 worked like a charm.

My procedure was as follows:
-Upgraded Opencore to 0.66 and left it as basic configuration with VMM turned on
-Booted into Catalina and clicked "Upgrade to Big Sur"
-Upgrade to Big Sur progressed smoothly.
-I then turned off VMM and performed the advanced configuration measures to enable OpenCanopy and hardware acceleration.

DRM content now plays in the TV app and I am a very happy camper. Wifi and Bluetooth works as expected with my upgraded card. Handoff also works between my iPhone and Mac Pro.
The only thing that appears to have been broken is "Unlock with Apple Watch". It is turned on in my Mac Pro system settings but doesn't appear as an option in the Lock Screen or at login. Any thoughts?
I had previously needed to apply a command in Terminal in order to get it to work in Catalina/Mojave.
 
Actually, unlock and handoff with Apple Watch now works. Needed to turn handoff setting to off, turn off watch. Reboot watch and turn setting on. I'm stoked that this machine is still kicking @ss after 12 years :)
 
  • Like
Reactions: Dewdman42 and JedNZ
startergo said:
Code: 
/Users/g5/Downloads/OpenCore-0/Utilities/ocvalidate/ocvalidate /Users/g5/Downloads/config.plist
OCS: Missing key AllowRelocationBlock, context <Quirks>!
OCS: Missing key Patch, context <Booter>!
OCS: No schema for Enable Night Shift at 2 index, context <Add>!
OCS: Missing key Comment, context <Add>!
OCS: Missing key SetApfsTrimTimeout, context <Quirks>!
OCS: Missing key PickerVariant, context <Boot>!
OCS: Missing key BlacklistAppleUpdate, context <Security>!
OCS: Missing key ARTFrequency, context <DataHub>!
OCS: Missing key BoardProduct, context <DataHub>!
OCS: Missing key BoardRevision, context <DataHub>!
OCS: Missing key DevicePathsSupported, context <DataHub>!
OCS: Missing key FSBFrequency, context <DataHub>!
OCS: Missing key InitialTSC, context <DataHub>!
OCS: Missing key PlatformName, context <DataHub>!
OCS: Missing key SmcBranch, context <DataHub>!
OCS: Missing key SmcPlatform, context <DataHub>!
OCS: Missing key SmcRevision, context <DataHub>!
OCS: Missing key StartupPowerEvents, context <DataHub>!
OCS: Missing key SystemProductName, context <DataHub>!
OCS: Missing key SystemSerialNumber, context <DataHub>!
OCS: Missing key SystemUUID, context <DataHub>!
OCS: Missing key AdviseWindows, context <Generic>!
OCS: Missing key MLB, context <Generic>!
OCS: Missing key MaxBIOSVersion, context <Generic>!
OCS: Missing key ProcessorType, context <Generic>!
OCS: Missing key ROM, context <Generic>!
OCS: Missing key SpoofVendor, context <Generic>!
OCS: Missing key SystemMemoryStatus, context <Generic>!
OCS: Missing key SystemProductName, context <Generic>!
OCS: Missing key SystemSerialNumber, context <Generic>!
OCS: Missing key SystemUUID, context <Generic>!
OCS: Missing key DataWidth, context <Memory>!
OCS: Missing key Devices, context <Memory>!
OCS: Missing key ErrorCorrection, context <Memory>!
OCS: Missing key FormFactor, context <Memory>!
OCS: Missing key MaxCapacity, context <Memory>!
OCS: Missing key TotalWidth, context <Memory>!
OCS: Missing key Type, context <Memory>!
OCS: Missing key TypeDetail, context <Memory>!
OCS: Missing key BID, context <PlatformNVRAM>!
OCS: Missing key FirmwareFeatures, context <PlatformNVRAM>!
OCS: Missing key FirmwareFeaturesMask, context <PlatformNVRAM>!
OCS: Missing key MLB, context <PlatformNVRAM>!
OCS: Missing key ROM, context <PlatformNVRAM>!
OCS: Missing key SystemUUID, context <PlatformNVRAM>!
OCS: Missing key BIOSReleaseDate, context <SMBIOS>!
OCS: Missing key BIOSVendor, context <SMBIOS>!
OCS: Missing key BoardAssetTag, context <SMBIOS>!
OCS: Missing key BoardLocationInChassis, context <SMBIOS>!
OCS: Missing key BoardManufacturer, context <SMBIOS>!
OCS: Missing key BoardSerialNumber, context <SMBIOS>!
OCS: Missing key BoardType, context <SMBIOS>!
OCS: Missing key BoardVersion, context <SMBIOS>!
OCS: Missing key ChassisAssetTag, context <SMBIOS>!
OCS: Missing key ChassisManufacturer, context <SMBIOS>!
OCS: Missing key ChassisSerialNumber, context <SMBIOS>!
OCS: Missing key ChassisType, context <SMBIOS>!
OCS: Missing key ChassisVersion, context <SMBIOS>!
OCS: Missing key PlatformFeature, context <SMBIOS>!
OCS: Missing key ProcessorType, context <SMBIOS>!
OCS: Missing key SmcVersion, context <SMBIOS>!
OCS: Missing key SystemFamily, context <SMBIOS>!
OCS: Missing key SystemManufacturer, context <SMBIOS>!
OCS: Missing key SystemProductName, context <SMBIOS>!
OCS: Missing key SystemSKUNumber, context <SMBIOS>!
OCS: Missing key SystemSerialNumber, context <SMBIOS>!
OCS: Missing key SystemUUID, context <SMBIOS>!
OCS: Missing key SystemVersion, context <SMBIOS>!
OCS: Failed to calculate size of false field containing <empty> as type integer, context <PlayChime>!
OCS: Missing key SetupDelay, context <Audio>!
OCS: No schema for SetApfsTrimTimeout at 17 index, context <ProtocolOverrides>!
OCS: No schema for DeduplicateBootOrder at 0 index, context <Quirks>!

Lilu.kext is loaded at Kernel->Add[0], but DisableLinkeditJettison is not enabled at Kernel->Quirks!
CheckKernel returns 1 error!

UEFI->Input->KeySupportMode is illegal (Can only be Auto, V1, V2, AMI)!
CheckUEFI returns 1 error!

Done checking /Users/g5/Downloads/config.plist in 1 ms, but it has 2 errors to be fixed

Once you correct the errors use the ocvalidate to inspect it.
Click to expand...

Thanks, I'll work on getting these errors fixed.

h9826790 said:
Change the iMac Pro board ID to Mac Pro 7,1 board ID
Click to expand...

That did it. Thanks!
 
Sorry, this is probably off topic,
but from my OC 0.65 5,1 Catalina I can select my NAS volumes, but then not mount them!
Mounting works fine from the Mojave disk and also from a MBP with Catalina.
the Console says: NetAuthSysAgent ERROR: AFP_Mount - theEnumerator->Mount failed 6
Obvious reasons like Firewall / hosts are tested... Can this be an OpenCore problem?
 
zzzachi said:
Sorry, this is probably off topic,
but from my OC 0.65 5,1 Catalina I can select my NAS volumes, but then not mount them!
Mounting works fine from the Mojave disk and also from a MBP with Catalina.
the Console says: NetAuthSysAgent ERROR: AFP_Mount - theEnumerator->Mount failed 6
Obvious reasons like Firewall / hosts are tested... Can this be an OpenCore problem?
Click to expand...
absoloutly not. Opencore is just the boot loader, this error is from the OS.
This error looks like an afp (netatalk) error, what kind of NAS are you running?
Maybe you have an invalid credentials stored in your Keychain ?
 
TECK said:
I added all the missing keys, except for PlatformInfo Memory keys, which IMO cannot be standardized and be safely omitted.
Click to expand...
Not sure why are they even coming up. If Custom Memory is disabled OC validator does not complain. See the corrected config file
 

Attachments

  • config.plist.zip
    3.6 KB · Views: 86
  • Like
Reactions: TECK
OpenCanopy doesn't show up

I'm sure I've done something wrong, but can't figure out what. After updating to OC 0.6.6, everything works great, except OpenCanopy doesn't show up. Everything is the way it's supposed to be in /EFI/OC/Resources (as a matter of fact, that was inherited form 0.6.5 and previous iterations). Naturally, config.plist lists the PickerMode as "External", and "OpenCanopy.efi" is listed as the first driver under UEFI. OpenCanopy.efi is located in /EFI/OC/Drivers. It was created on February 2 at 6:12pm (I live in Western Europe). Its length is 73,732 bytes. When I boot from "EFI Boot", all I get is the text list of bootable disks. What am I missing?

EDIT: I've followed all the relevant recommendations for 0.6.6, but I've added the relevant parameters for the Orinoco frame buffer:
<key>@0,name</key>
<data>
QVRZLE9yaW5vY28=
</data>
Is this somehow incompatible?
 
Last edited:
LFO8 said:
Idk, but the reason I use 0.6.3 is I use Martin Lo’s package for 0.6.3 that includes the Wifi patch. Otherwise my Wifi doesn’t work in Big Sur.
Click to expand...
Is there a way to integrate the WiFi patch from Martin Lo's 0.6.3 OC package into 0.6.6?
 
Hi I update on my Mac Pro 4.1 Catalina > Big Sure normally with Cpu Flag OC 0.6.6 all is running fine only my 10 GB Networkcard not functional
1612451290666.png

can do this with OC ? The Networkcard is a Asus XG-C100C with Mojave and Catalina no Problem on Big Sure now no driver installed.

on Mojave or Catalina the Card works
see
1612469048349.png




THX for help
 
Last edited:
PeterHolbrook said:
OpenCanopy doesn't show up

I'm sure I've done something wrong, but can't figure out what. After updating to OC 0.6.6, everything works great, except OpenCanopy doesn't show up. Everything is the way it's supposed to be in /EFI/OC/Resources (as a matter of fact, that was inherited form 0.6.5 and previous iterations). Naturally, config.plist lists the PickerMode as "External", and "OpenCanopy.efi" is listed as the first driver under UEFI. OpenCanopy.efi is located in /EFI/OC/Drivers. It was created on February 2 at 6:12pm (I live in Western Europe). Its length is 73,732 bytes. When I boot from "EFI Boot", all I get is the text list of bootable disks. What am I missing?

EDIT: I've followed all the relevant recommendations for 0.6.6, but I've added the relevant parameters for the Orinoco frame buffer:
<key>@0,name</key>
<data>
QVRZLE9yaW5vY28=
</data>
Is this somehow incompatible?
Click to expand...
Do you have :

Misc -> Boot -> PickerMode : External
Misc -> Boot -> PickerAttributes : 17
Misc -> Boot -> PickerVariant : Auto or Modern
 
TECK said:
What are the FirmwareFeatures and FirmwareFeaturesMask properties you added? I also see you set the BlacklistAppleUpdate to False.
Click to expand...
No that file was just a conversion of the previous OC version Steve_Jones shared and complained that it was not working with the new version. Nothing was added or deleted to/from the configuration except for the obsolete and the new parameters.
 
  • Like
Reactions: TECK
PeterHolbrook said:
In my case, PickerAttributes=1.
Click to expand...
oks. in my case, on a cmp5,1 I use "0" . But the OpenCore guide suggest "17" for mouse/trackpad support with custom .VolumeIcon.icns reading from the drive.

But, you should defiantly get the OpenCanoby to show as you have "External" as PickerMode and hopefully "auto" or "Modern" in PickerVariant (which is a new config in OC 0.6.6) .
 
cdf said:
The guide has been updated to OpenCore version 0.6.6.

There are also a few changes and additions to the guide. These include
  • simplifications to the instructions
  • details for Big Sur
  • directions for easier updates
Click to expand...
Thanks cdf! Its nice to have nightshift back. I appreciate all you do for this community. I'm not a developer, but if you need testers, I'd be happy to help.
 
  • Like
Reactions: cdf
h9826790 said:
You have to completely "rename" the GPU, but not just "add" the AMD prefix.

e.g. I add this code under DeviceProperties section to rename my Radeon VII to AMD Radeon VII
Code: 
                <key>model</key>
                <string>AMD Radeon VII</string>
View attachment 1703871
Click to expand...
How can I ident my Vega 64 in OC v0.6.6 without SoftPowerPlayTable being injected? I just need to properly identify my GPU for VideoProc. My config.plist looks like this presently:
1612463959377.png
 
Cleaned up the errors with the exception of the missing keys, changed my spoofing to Mac Pro 7,1 and everything looks good. This should look much better.

Thanks for everyone's help.
 

Attachments

  • config.plist.zip
    3.3 KB · Views: 100
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back