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.
The guide has been updated to OpenCore version 0.6.7.

Please note that in order to more strictly follow OpenCore's specification, the sample configuration for 0.6.7 has undergone exceptionally considerable changes. If your configuration is based on the sample, it is advised to recreate it from the new file.
 
  • Like
Reactions: innovaTutor, h9826790 and PeterHolbrook
RicheeThree said:
The EFI volume on the Mojave disk contains EFI\EFI\APPLE\EXTENSIONS and \FIRMWARE. I don't know what the Windows disk has in its EFI, because as soon as I insert it, it boots to it, and there's no way to boot to macOS (Mojave or Big Sur).
Click to expand...
Those folders are fine. As for the Windows drive, perhaps try inspecting the contents of its EFI volume by using another machine. Continuing to boot UEFI Windows without OpenCore can be destructive to your firmware chip, and the inability to properly bless may be an indication of a failing chip, so before continuing, you should boot natively into Mojave and use ROMTool to make a backup of your BootROM (take a look at post #6,990 and make sure to read post #7,003.)
 
cdf said:
Those folders are fine. As for the Windows drive, perhaps try inspecting the contents of its EFI volume by using another machine. Continuing to boot UEFI Windows without OpenCore can be destructive to your firmware chip, and the inability to properly bless may be an indication of a failing chip, so before continuing, you should boot natively into Mojave and use ROMTool to make a backup of your BootROM (take a look at post #6,990 and make sure to read post #7,003.)
Click to expand...
Ok. I worked with the great @tsialex to rebuild my BootROM. I received it recently and flashed it anew. After flashing, still having the same issue. So I assume I should just nuke my Windows drive using another machine and install Windows again.
 
  • Like
Reactions: innovaTutor
RicheeThree said:
Ok. I worked with the great @tsialex to rebuild my BootROM. I received it recently and flashed it anew. After flashing, still having the same issue. So I assume I should just nuke my Windows drive using another machine and install Windows again.
Click to expand...
This is weird.

Your Windows disk is a PCIe AHCI/NVMe, SATA connected to a SATA3 card or SATA connected to a south bridge SATA port?
 
Ausdauersportler said:
You will not get around this error. Mojave and older versions on macOS have not been updated to understand the changes Apple introduced with Big Sur APFS.

Never touch an APFS partition for Big Sur with older versions of disk utility.
Click to expand...

Hmm, this is interesting point. I routinely use Mojave for updating OC. What will be the best way to manage the APFS volumes on BigSur volume...without booting to BigSur? Will the BigSur installation media boot up on 5,1 without OC?
 
tsialex said:
This is weird.

Your Windows disk is a PCIe AHCI/NVMe, SATA connected to a SATA3 card or SATA connected to a south bridge SATA port?
Click to expand...
It is an OWC Mercury Extreme Pro 6G SSD connected to a PCIe card in the x4/RAID PCIe slot. Should I slide the drive into one of the standard SATA drive bays?
 
Last edited:
I've been comparing the 0.6.7 sample config.plist with the 0.6.6 I have right now. I have certain doubts as to the implications of some changes. Can anyone explain the scope of the "dict" sections of the following keys?

DataHub
Generic
PlatformNVRAM
SMBIOS

My doubts derive from the contents of some of the subkeys. For instance, if I'm not mistaken, it appears that the DataHub dictionary is supposed to specify, among other things, the speed of my processor, but the speed is presented as being 0. Am I supposed to enter something different, like 3.1 GHz? If I leave 0, will OpenCore identify the processor correctly, or will it crash? If I don't enter the DataHub dictionary at all, will anything fail? Similar considerations apply to the other keys.
 
After booting using 0.6.7,

Code: 
nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version
generates this response:

Code: 
nvram: Error getting variable - '4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version': (iokit/common) data was not found

The same thing happens if entered with sudo.
 
Dewdman42 said:
Hmm, this is interesting point. I routinely use Mojave for updating OC. What will be the best way to manage the APFS volumes on BigSur volume...without booting to BigSur? Will the BigSur installation media boot up on 5,1 without OC?
Click to expand...
You can't, otherwise you risk drive corruption.

I've tried booting into non-OC BS on my 5,1 just to see what would happen. It'll start the 1st stage boot screen with Apple logo and then hard reset after about 10 seconds. Same applies to BS installer volumes.
 
Last edited:
PeterHolbrook said:
Am I supposed to enter something different
Click to expand...
Edit what the guide asks you to edit and leave what it doesn't ask you to edit alone.
Those are presumably failsafe values that now explicitly specified.
Some of these are now explicitly permitted to be absent.

Ultimately, you need to read the manual if you want to fully understand what's happening.

PeterHolbrook said:
After booting using 0.6.7...
Click to expand...
I get this (different setup but to show it is working as expected):
Screen Shot 2021-03-02 at 12.09.16.jpg



amstel78 said:
I've tried booting into non-OC BS on my 5,1 just to see what would happen. It'll start the 1st stage boot screen with Apple logo and then hard reset after about 10 seconds.
Click to expand...
You can't boot directly into BS with SIP enabled (leads to a kernel panic ... hard reboot).
You either have to disable SIP (fully, as when done via RP) or use the PreBoot partition (as OC does).

RefindPlus now also sorts this out behind the scenes if you switch the "reinforce_apfs' flag on (as MyBootMgr does).
 
Last edited:
Dayo said:
I get this (different setup but to show it is working as expected):
View attachment 1737455
Click to expand...
My issue was caused by some kind of corruption in the NVRAM. Resetting it solved the problem immediately.

Dayo said:
Edit what the guide asks you to edit and leave what it doesn't ask you to edit alone.
Click to expand...
I don't usually like patronizing from anyone, nor do I normally let others think for me, no matter what their expertise. You see, I'm currently booted to 0.6.7 WITHOUT entering ANY of the recommended (?) "dictionaries" of the following keys.

DataHub
Generic
PlatformNVRAM
SMBIOS

Before deciding NOT to enter any of that, I read the manual, but, since I didn't fully understand the usefulness of such entries, I refrained from doing so for the time being. That's why I asked. Now, are you telling me that I need to enter all that mindlessly? Just why? Because you say so? I think not.
 
Last edited:
PeterHolbrook said:
I've been comparing the 0.6.7 sample config.plist with the 0.6.6 I have right now. I have certain doubts as to the implications of some changes. Can anyone explain the scope of the "dict" sections of the following keys?

DataHub
Generic
PlatformNVRAM
SMBIOS
Click to expand...
Instead of omitting properties as a way of applying failsafes, the sample configuration now explicitly sets those values. The reason is to satisfy the specification (the configuration now passes ocvalidate). Still, many of the properties are never actually applied.

Because we use manual mode (automatic is false), nothing in Generic is applied. Also, because UpdateDataHub is false and UpdateNVRAM is false, nothing in DataHub or PlatformNVRAM is applied. The only thing that matters here is SMBIOS. Because UpdateSMBIOS is true, a new SMBIOS is generated. However, because most of the values are empty or zero (corresponding to failsafes), most OEM values are automatically preserved.

In fact, 0.6.7 saw nice improvements in regard to OEM preservation. In particular, FirmwareFeatures and FirmwareFeaturesMask are now automatically set from the original values, and you may notice that your CPU frequency appears properly rounded in About This Mac.
 
  • Like
Reactions: h9826790, Dewdman42, paalb and 3 others
Need some help...
I have a 5.1 with GTX680 and 144.000. With OC 0.5.7 it was running Mojave and Catalina with iSight and WLAN. After updating to OC 0.6.6 iSight and WLAN are gone.

I tried a lot and now I am lost. Meanwhile it shows:
Modell-Identifizierung: MacPro6,1
Seriennummer (Prozessormodul): OPENCORE_MLB_SN11
Boot-ROM-Version: 137.0.0.0.0
 
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