MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

startergo · Dec 7, 2020

haralds said:
Isn't AFFS the Amiga File System?

It is a typo. I meant APFS.efi

haralds · Dec 7, 2020

startergo said:
Installation of what exactly the APFS.efi driver? You just put it inside the drivers folder and select it in the OC configuration file. You can generate it following this instructions:
RefindPlus/BUILDING.md at GOPFix · dakanji/RefindPlus (github.com)
After you compile RefindPlus you will find the driver in the same folder as the generated refind.efi file.

You mentioned an AFFS.efi - no typo. Was that a mistake? I built and installed RefindPlus.efi including config and it did not change the issue.

startergo · Dec 7, 2020

haralds said:
You mentioned an AFFS.efi - no typo. Was that a mistake? I built and installed RefindPlus.efi including config and it did not change the issue.

I said it was a typo on my side. Also APFS.efi is not in the RefindPlus package. Clickhere for the actual driver.

haralds · Dec 7, 2020

startergo said:
I said it was a typo on my side. Also APFS.efi is not in the RefindPlus package. Clickhere for the actual driver.

Thank you kindly, Sir. THAT did the trick.

haralds · Dec 7, 2020

Just some background info: are drivers loaded by OpenCore replaced by the running system? I am thinking about preloaded drivers like APFS.efi.

KevinClark · Dec 8, 2020

I tried to enable SIP on my open core USB key via recovery open core it doesn't want to work

mangombia · Dec 8, 2020

KevinClark said:
I tried to enable SIP on my open core USB key via recovery open core it doesn't want to work

Check your config.plist>NVRAM>7C436110-AB2A-4BBB-A880-FE41995C9F82>csr-active-config -- that entry and data will override your Recovery setting.

startergo · Dec 8, 2020

haralds said:
Just some background info: are drivers loaded by OpenCore replaced by the running system? I am thinking about preloaded drivers like APFS.efi.

You can use Catalina's own apfs.efi:

LucMac · Dec 8, 2020

Quick Question:

Decided to finally upgrade from Mojave to Big Sur using OpenCore 0.6.3.
Mounting the EFI partition of my APFS bootvolume didn't worked.


Volume on diskXs1 failed to mount
If the volume is damaged, try the "readOnly" option

disk5s1 because I got 5 more HDDs installed.
That's why the APFS bootdrive is disk5

So I decidid to bless OpenCore on a flashdrive. Worked, I'm now on 11.0.1.
Now I want to put OpenCore on the EFI partition of my bootdrive.

I thought maybe after updating to Big Sur the problem is gone, but I still can't mount the EFI partition.
sudo diskutil and Clover both don't work.

What could be the problem and how can I permanently fix this?

haralds · Dec 8, 2020

LucMac said:
Quick Question:

Decided to finally upgrade from Mojave to Big Sur using OpenCore 0.6.3.
Mounting the EFI partition of my APFS bootvolume didn't worked.

Volume on diskXs1 failed to mount If the volume is damaged, try the "readOnly" option
disk5s1 because I got 5 more HDDs installed.
That's why the APFS bootdrive is disk5

So I decidid to bless OpenCore on a flashdrive. Worked, I'm now on 11.0.1.
Now I want to put OpenCore on the EFI partition of my bootdrive.

I thought maybe after updating to Big Sur the problem is gone, but I still can't mount the EFI partition.
sudo diskutil and Clover both don't work.

What could be the problem and how can I permanently fix this?

Is you boot drive a standard disk or NVMe on PCiE?

haralds · Dec 8, 2020

haralds said:
What I see is that the USB polling is not even as required by the USB spec. Devices define a polling interval and the OS is supposed to follow that. There seem to be large gaps on unsupported configurations.

I should not that this was much less of an issue during earlier 11.0 betas until fairly late into the process.

I tried the OpenCore drivers UsbMouseDxe.efi and XhciDxe.efi, but they resulted in the system not booting.

LucMac · Dec 8, 2020

It's a Samsung SSD on a sonnet tempo ssd 6gb/s sata pcie 2.0 card.

mangombia · Dec 8, 2020

LucMac said:
Quick Question:

Decided to finally upgrade from Mojave to Big Sur using OpenCore 0.6.3.
Mounting the EFI partition of my APFS bootvolume didn't worked.

Volume on diskXs1 failed to mount If the volume is damaged, try the "readOnly" option
disk5s1 because I got 5 more HDDs installed.
That's why the APFS bootdrive is disk5

So I decidid to bless OpenCore on a flashdrive. Worked, I'm now on 11.0.1.
Now I want to put OpenCore on the EFI partition of my bootdrive.

I thought maybe after updating to Big Sur the problem is gone, but I still can't mount the EFI partition.
sudo diskutil and Clover both don't work.

What could be the problem and how can I permanently fix this?

I was never able to get OC to successfully work on the EFI of any NVMe. One of my 5,1s is a media server w/4x8tb HDDs in RAID5 on the SATA ports and I didn't want to disturb the EFI of any of the RAID drives so I put OC on the EFI of a USB. It works just fine and makes it very easy to take OC out of the mix if I need to test. So easy in fact that I did the same for my 5,1 workstation. One word of caution: make sure you've got a working version of Mojave that is first in your boot order. If you have Catalina/Big Sur or Win10 ahead of Mojave and you have to take OC out it is going to try and boot from one of those. In the case of Catalina/Big Sur it will fail, in the case of Win10 it will write security certificates to your BootROM which will at least hasten its corruption, if not outright corrupt it.

haralds · Dec 8, 2020

startergo said:
You can use Catalina's own apfs.efi:
View attachment 1689284

Would Big Sur's also work?

haralds · Dec 8, 2020

haralds said:
I tried the OpenCore drivers UsbMouseDxe.efi and XhciDxe.efi, but they resulted in the system not booting.

SOLVED! It looks like one of the USB3 hubs was trouble for Big Sur but not the older versions of macOS. Go figure. With some judicious reassignment of plugs I removed it.
Lesson: with USB trouble try the "plug, try, and die" approach (just made that up.) Reminds of Windows plug and pray.
Man, the hours wasted on this.

haralds · Dec 8, 2020

haralds said:
Is you boot drive a standard disk or NVMe on PCiE?

Tried it with Big Sur and that works. Still have to see Catalina.

haralds · Dec 8, 2020

haralds said:
Would Big Sur's also work?

Works on both Big Sur and Catalina.

Fwi Haxx · Dec 8, 2020

anyone have updated to 0.6.4 ? does we have to add some arg in config.plist ?
i m running on Mac Pro 5.1, Radeon VII, 2X3,46Ghz XEON

does anyone have a working config.plist for this Mac with 0.6.4 ?
thank you

PeterHolbrook · Dec 9, 2020

Fwi Haxx said:
anyone have updated to 0.6.4 ? does we have to add some arg in config.plist ?
i m running on Mac Pro 5.1, Radeon VII, 2X3,46Ghz XEON

does anyone have a working config.plist for this Mac with 0.6.4 ?
thank you

I re-used my 0.6.3 config.plist for 0.6.4 without any issues. After reading some advice, I simply added

<key>BlacklistAppleUpdate</key>
<true/>

to the /Misc/Security section.

h9826790 · Dec 9, 2020

PeterHolbrook said:
I re-used my 0.6.3 config.plist for 0.6.4 without any issues.

Do NOT do this.

You are just lucky, the 0.6.3 config isn't NOT compatible to OC 0.6.4.

h9826790 · Dec 9, 2020

Fwi Haxx said:
anyone have updated to 0.6.4 ? does we have to add some arg in config.plist ?
i m running on Mac Pro 5.1, Radeon VII, 2X3,46Ghz XEON

does anyone have a working config.plist for this Mac with 0.6.4 ?
thank you

cdf updated post #1 for 0.6.4 already.

I also posted my 0.6.4 package at 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

startergo · Dec 9, 2020

cdf said:
Assuming that you've completed Part II of the guide: simply replace

XML:

<dict> <key>BoardProduct</key> <string>Mac-7BA5B2D9E42DDD94</string> </dict>

by

XML:

<dict> <key>BoardProduct</key> <string>Mac-7BA5B2D9E42DDD94</string> <key>FirmwareFeatures</key> <data>A1QM4A==</data> <key>FirmwareFeaturesMask</key> <data>P/8f/w==</data> </dict>

In my preliminary testing, this was the only change necessary to install Big Sur 11.0.1 with the full installer in Catalina 10.15.7. The change is still considered experimental. But in theory, it should be safe: you shouldn't need to sign in and out of Apple services; you can also keep the change afterwards.

I just realized this only affects the variable in that NVRAM GUID, but it does not apply globally:

Code:

sudo bless --setBoot --folder /Volumes/CAT1/System/Library/CoreServices --file /Volumes/CAT1/System/Library/CoreServices/boot.efi --verbose
Password:
EFI found at IODeviceTree:/efi
Mount point for /Volumes/CAT1/System/Library/CoreServices is /
Common mount point of '/Volumes/CAT1/System/Library/CoreServices' and '' is /
No BootX creation requested
Non-Data-role volume, so not considered Data-Given-Pre-SSV-to-SSV case
This is not an APFS Data-Volume-Parameter-Driven Pre-SSV to SSV case
No boot.efi creation requested
No auxiliary booter partition required
System partition found
Preferred system partition found: disk0s1
Preferred system partition found: disk1s1
Preferred system partition found: disk2s1
Preferred system partition found: disk3s1
Preferred system partition found: disk4s1
Preferred system partition found: disk5s1
Preferred system partition found: disk6s1
Preferred system partition found: disk7s1
Preferred system partition found: disk11s1
Preferred system partition found: disk12s1
Preferred system partition found: disk13s1
Preferred system partition found: disk15s1
Returning booter information dictionary:
{
    "Auxiliary Partitions" =     (
    );
    "Data Partitions" =     (
        disk10s2
    );
    "Preboot Volumes" =     (
        disk10s3
    );
    "System Partitions" =     (
        disk4s1,
        disk15s1,
        disk13s1,
        disk12s1,
        disk11s1,
        disk7s1,
        disk6s1,
        disk5s1,
        disk3s1,
        disk2s1,
        disk1s1,
        disk0s1
    );
}
Mounting at /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/Tbless.Mcw3
Executing "/sbin/mount"
Returned 0
Found system volume UUID path in preboot for disk10s2
Executing "/sbin/umount"
Returned 0
found ioreg "FirmwareFeaturesMask"; featureMaskValue=0xFF1FFF3F
found ioreg "FirmwareFeatures"; featureFlagsValue=0xC00C5403
isPreBootEnvironmentUEFIWindowsBootCapable=0
preboot environment is not UEFI boot capable
isDVDWithElToritoWithUEFIBootableOS=0
Checking if disk is complex (if it is associated with booter partitions)
No auxiliary booter partition required
System partition found
Preferred system partition found: disk0s1
Preferred system partition found: disk1s1
Preferred system partition found: disk2s1
Preferred system partition found: disk3s1
Preferred system partition found: disk4s1
Preferred system partition found: disk5s1
Preferred system partition found: disk6s1
Preferred system partition found: disk7s1
Preferred system partition found: disk11s1
Preferred system partition found: disk12s1
Preferred system partition found: disk13s1
Preferred system partition found: disk15s1
Returning booter information dictionary:
{
    "Auxiliary Partitions" =     (
    );
    "Data Partitions" =     (
        disk10s2
    );
    "Preboot Volumes" =     (
        disk10s3
    );
    "System Partitions" =     (
        disk4s1,
        disk15s1,
        disk13s1,
        disk12s1,
        disk11s1,
        disk7s1,
        disk6s1,
        disk5s1,
        disk3s1,
        disk2s1,
        disk1s1,
        disk0s1
    );
}
Mounting at /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/Tbless.f4Ox
Executing "/sbin/mount"
Returned 0
Found system volume UUID path in preboot for disk10s2
Executing "/sbin/umount"
Returned 0
Substituting preboot volume disk10s3
IOMedia disk10s3 has UUID FC925876-5E70-4C45-BDCC-672A92085E1D
Setting EFI NVRAM:
    efi-boot-device='<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>FC925876-5E70-4C45-BDCC-672A92085E1D</string></dict></dict><key>BLLastBSDName</key><string>disk10s3</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\B582A3CE-F466-43C2-A2DF-6428D56470CC\System\Library\CoreServices\boot.efi</string></dict></array>'
Setting EFI NVRAM:
    IONVRAM-DELETE-PROPERTY='efi-boot-file'
Setting EFI NVRAM:
    IONVRAM-DELETE-PROPERTY='efi-boot-mkext'
Setting EFI NVRAM:
    IONVRAM-DELETE-PROPERTY='efi-boot-kernelcache'
Old boot-args: -v -no_compat_check keepsyms=1 debug=144
    Got token: -v
    Preserving: -v
    Got token: -no_compat_check
    Preserving: -no_compat_check
    Got token: keepsyms=1
    Preserving: keepsyms=1
    Got token: debug=144
    Preserving: debug=144
New boot-args unchanged, skipping update.

Code:

nvram -x 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures</key>
    <data>
    A1QMwA==
    </data>
</dict>
</plist>

As you can see the bless command reveals:
featureFlagsValue=0xC00C5403, which is equal to A1QMwA==

Now if you set those parameters in the NVRAM section:

Code:

<key>NVRAM</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
            <dict>
                <key>DefaultBackgroundColor</key>
                <data>
                v7+/AA==
                </data>
                <key>FirmwareFeatures</key>
                <data>
                A1QM4A==
                </data>
                <key>FirmwareFeaturesMask</key>
                <data>
                P/8f/w==
                </data>
                <key>UIScale</key>
                <data>
                AQ==
                </data>
            </dict>
            <key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
            <dict>
                <key>boot-args</key>
                <string>-v -no_compat_check keepsyms=1 debug=0x144</string>
                <key>csr-active-config</key>
                <data>
                /w8AAA==
                </data>
                <key>run-efi-updater</key>
                <string>No</string>
            </dict>
        </dict>
        <key>Delete</key>
        <dict>
            <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
            <array>
                <string>UIScale</string>
                <string>DefaultBackgroundColor</string>
                <string>FirmwareFeatures</string>
                <string>FirmwareFeaturesMask</string>
            </array>
            <key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
            <array>
                <string></string>
                <string>run-efi-updater</string>
                <string>csr-active-config</string>
            </array>
        </dict>

you get this:

Code:

 sudo bless --setBoot --folder /Volumes/CAT1/System/Library/CoreServices --file /Volumes/CAT1/System/Library/CoreServices/boot.efi --verbose
Password:
EFI found at IODeviceTree:/efi
Mount point for /Volumes/CAT1/System/Library/CoreServices is /
Common mount point of '/Volumes/CAT1/System/Library/CoreServices' and '' is /
No BootX creation requested
Non-Data-role volume, so not considered Data-Given-Pre-SSV-to-SSV case
This is not an APFS Data-Volume-Parameter-Driven Pre-SSV to SSV case
No boot.efi creation requested
No auxiliary booter partition required
System partition found
Preferred system partition found: disk0s1
Preferred system partition found: disk1s1
Preferred system partition found: disk2s1
Preferred system partition found: disk3s1
Preferred system partition found: disk4s1
Preferred system partition found: disk5s1
Preferred system partition found: disk6s1
Preferred system partition found: disk11s1
Preferred system partition found: disk12s1
Preferred system partition found: disk13s1
Preferred system partition found: disk14s1
Preferred system partition found: disk15s1
Returning booter information dictionary:
{
    "Auxiliary Partitions" =     (
    );
    "Data Partitions" =     (
        disk7s2
    );
    "Preboot Volumes" =     (
        disk7s3
    );
    "System Partitions" =     (
        disk1s1,
        disk15s1,
        disk14s1,
        disk13s1,
        disk12s1,
        disk11s1,
        disk6s1,
        disk5s1,
        disk4s1,
        disk3s1,
        disk2s1,
        disk0s1
    );
}
Mounting at /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/Tbless.M0KU
Executing "/sbin/mount"
Returned 0
Found system volume UUID path in preboot for disk7s2
Executing "/sbin/umount"
Returned 0
found ioreg "FirmwareFeaturesMask"; featureMaskValue=0xFF1FFF3F
found ioreg "FirmwareFeatures"; featureFlagsValue=0xE00C5403
isPreBootEnvironmentUEFIWindowsBootCapable=1
given BSD is not a DVD disc medium
isDVDWithElToritoWithUEFIBootableOS=0
Checking if disk is complex (if it is associated with booter partitions)
No auxiliary booter partition required
System partition found
Preferred system partition found: disk0s1
Preferred system partition found: disk1s1
Preferred system partition found: disk2s1
Preferred system partition found: disk3s1
Preferred system partition found: disk4s1
Preferred system partition found: disk5s1
Preferred system partition found: disk6s1
Preferred system partition found: disk11s1
Preferred system partition found: disk12s1
Preferred system partition found: disk13s1
Preferred system partition found: disk14s1
Preferred system partition found: disk15s1
Returning booter information dictionary:
{
    "Auxiliary Partitions" =     (
    );
    "Data Partitions" =     (
        disk7s2
    );
    "Preboot Volumes" =     (
        disk7s3
    );
    "System Partitions" =     (
        disk1s1,
        disk15s1,
        disk14s1,
        disk13s1,
        disk12s1,
        disk11s1,
        disk6s1,
        disk5s1,
        disk4s1,
        disk3s1,
        disk2s1,
        disk0s1
    );
}
Mounting at /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/Tbless.Ur77
Executing "/sbin/mount"
Returned 0
Found system volume UUID path in preboot for disk7s2
Executing "/sbin/umount"
Returned 0
Substituting preboot volume disk7s3
IOMedia disk7s3 has UUID FC925876-5E70-4C45-BDCC-672A92085E1D
Setting EFI NVRAM:
    efi-boot-device='<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>FC925876-5E70-4C45-BDCC-672A92085E1D</string></dict></dict><key>BLLastBSDName</key><string>disk7s3</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\B582A3CE-F466-43C2-A2DF-6428D56470CC\System\Library\CoreServices\boot.efi</string></dict></array>'
Setting EFI NVRAM:
    IONVRAM-DELETE-PROPERTY='efi-boot-file'
Setting EFI NVRAM:
    IONVRAM-DELETE-PROPERTY='efi-boot-mkext'
Setting EFI NVRAM:
    IONVRAM-DELETE-PROPERTY='efi-boot-kernelcache'
Old boot-args: -v -no_compat_check keepsyms=1 debug=144
    Got token: -v
    Preserving: -v
    Got token: -no_compat_check
    Preserving: -no_compat_check
    Got token: keepsyms=1
    Preserving: keepsyms=1
    Got token: debug=144
    Preserving: debug=144
New boot-args unchanged, skipping update.

Note this: isPreBootEnvironmentUEFIWindowsBootCapable=1
And this is still the same:

Code:

nvram -x 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures</key>
    <data>
    A1QM4A==
    </data>
</dict>
</plist>

racer · Dec 9, 2020

h9826790 said:
cdf updated post #1 for 0.6.4 already.

I also posted my 0.6.4 package at 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

So in #1 there is a "PART I Basic Installation" with a "4 Install Catalina" which works like a charm.

I was hopping for a "5 Install Big Sur" now that OC 0.6.4 is out, or is it not that simple?

Much appreciate all the work everyone has put into this 🙏

cdf · Dec 9, 2020

racer said:
So in #1 there is a "PART I Basic Installation" with a "4 Install Catalina" which works like a charm.

I was hopping for a "5 Install Big Sur" now that OC 0.6.4 is out, or is it not that simple?

Much appreciate all the work everyone has put into this 🙏

It's not that simple: DRM, Night Shift and USB still need work. I will be investigating alternative configurations for Big Sur soon.

racer · Dec 9, 2020

cdf said:
It's not that simple: DRM, Night Shift and USB still need work. I will be investigating alternative configurations for Big Sur soon.

Thanks for the update.

MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

macrumors 603

macrumors 68040

macrumors 603

macrumors 68040

macrumors 68040

macrumors 6502

macrumors member

macrumors 603

macrumors member

macrumors 68040

macrumors 68040

macrumors member

macrumors member

macrumors 68040

macrumors 68040

macrumors 68040

macrumors 68040

macrumors newbie

macrumors 68000

macrumors P6

macrumors P6

macrumors 603

macrumors member

macrumors 68020

macrumors member

Our Staff