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

0488568 · Mar 8, 2022

OVERKILL338LM said:
I edited my post, see update. Things changed with Monterey, it's covered in the link I provided.

Darn, too late for me I just erased the drive.

Im gonna go with Big Sur, since everything installed right and I feel its faster than Monterey on my system.

Thanks for the help.

TECK · Mar 8, 2022

cdf said:
Actually, you don’t need to remove the no_compat_check boot arg to enable hardware acceleration... If you want hardware acceleration in Mojave, then take a look at the spoiler at the end of the section Complete you setup.

I edited my initial post, you're too fast to respond.

After I add the NVRAM code into configuration, when I select to boot into Mojave, I end with a boot loop and a black screen. All I want is to be able to boot into Mojave and I believe adding just the following code should let me do that:

Code:

    <key>NVRAM</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
            <dict>
                <key>boot-args</key>
                <string>-no_compat_check</string>
            </dict>
        </dict>
        <key>Delete</key>
        <dict>
            <key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
            <array>
                <string>boot-args</string>
            </array>
        </dict>

We both use the same config, can you please test on your side the boot loop? For me it reboots twice with a black screen on Mojave. I did not added pikera and other settings except the no_compat_check, since you told me to remove them with the new configuration.

To me, it makes sense to have a working config for both drives, not just Monterey.

cdf · Mar 8, 2022

TECK said:
We both use the same config, can you please test on your side the boot loop? For me it reboots twice with a black screen on Mojave. I did not added pikera and other settings except the no_compat_check, since you told me to remove them with the new configuration.

To me, it makes sense to have a working config for both drives, not just Monterey.

For my current setup, I only ever boot Mojave natively, so I haven’t tested this recently, and because I’m away from my Mac Pro for the next few weeks, I won’t be able to do any testing for a while.

You might be able to solve your issue by setting SecureBootModel to Disabled (in addition to using no_compat_check). Alternatively, if you plan on booting Mojave through OC regularly, you might want to adopt the legacy settings (iMac Pro board ID) described in the spoiler I mentioned in my last post.

TECK · Mar 9, 2022

cdf said:
For my current setup, I only ever boot Mojave natively, so I haven’t tested this recently, and because I’m away from my Mac Pro for the next few weeks, I won’t be able to do any testing for a while.

Thanks, I'll wait for you to be available, curious to see the results. For now, I removed the legacy OS boot settings. I never boot into Mojave, unless I need to refresh the BootROM and is done natively, not through OC bootloader. The only beef I have is when I accidentally select the Mojave disk and I get the forbidden circle.

OVERKILL338LM · Mar 9, 2022

fabriciom said:
Darn, too late for me I just erased the drive.

Im gonna go with Big Sur, since everything installed right and I feel its faster than Monterey on my system.

Thanks for the help.

You are quite welcome!

I had the opposite experience, so that's interesting! I found Monterey to be MUCH faster than Big Sur.

z521 · Mar 12, 2022

Not sure if this is the correct place to post this as not to familiar with the forum. Attempted to install Monterey on my 5,1 and get this "firmware required to upgrade". I searched here and internet but nothing about it only you have to have an apple ssd. I have an apple ssd with Monterey on it but how do I upgrade the firmware on my 5,1 with it or is that even possible? Do I have to have one with Mojave on it? Really don't want to erase it so is there a solution to this? If this isn't the correct location for this, let me know please.
Thanks

tsialex · Mar 12, 2022

z521 said:
Not sure if this is the correct place to post this as not to familiar with the forum. Attempted to install Monterey on my 5,1 and get this "firmware required to upgrade". I searched here and internet but nothing about it only you have to have an apple ssd. I have an apple ssd with Monterey on it but how do I upgrade the firmware on my 5,1 with it or is that even possible? Do I have to have one with Mojave on it? Really don't want to erase it so is there a solution to this? If this isn't the correct location for this, let me know please.
Thanks

Configure the correct FIRMWARE FEATURES on your OC config, use the search for details on how to do it.

trifero · Mar 12, 2022

People is lazy.

z521 · Mar 12, 2022

I don't really think I am lazy just not familiar with this firmware thing. I use Martin lo's that is 7.8 I believe. Is that the secure boot loader?

tsialex · Mar 12, 2022

z521 said:
Is that the secure boot loader?

No. This is explained on the first post of this thread, read "Complete your setup / Spoofing and enabling missing features".

You have to edit at least SMBIOS, or PlatformNVRAM and SMBIOS, to something like the example below:

Code:

  <key>PlatformNVRAM</key>
        <dict>
            <key>BID</key>
            <string></string>
            <key>FirmwareFeatures</key>
            <data>A1QMwAgAAAA=</data>
            <key>FirmwareFeaturesMask</key>
            <data>P/8f/wgAAAA=</data>
            <key>MLB</key>
            <string></string>
            <key>ROM</key>
            <data></data>
            <key>SystemSerialNumber</key>
            <string></string>
            <key>SystemUUID</key>
            <string></string>
        </dict>

<key>SMBIOS</key>
        <dict>
            <key>BIOSReleaseDate</key>
            <string></string>
            <key>BIOSVendor</key>
            <string></string>
            <key>BIOSVersion</key>
            <string>9144.0.7.8.0</string>
            <key>BoardAssetTag</key>
            <string></string>
            <key>BoardLocationInChassis</key>
            <string></string>
            <key>BoardManufacturer</key>
            <string></string>
            <key>BoardProduct</key>
            <string>Mac-27AD2F918AE68F61</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>AxQMwAgAAAA=</data>
            <key>FirmwareFeaturesMask</key>
            <data>P/8f/wgAAAA=</data>
            <key>PlatformFeature</key>
            <integer>-1</integer>
            <key>ProcessorType</key>
            <integer>0</integer>
            <key>SmcVersion</key>
            <data></data>
            <key>SystemFamily</key>
            <string></string>
            <key>SystemManufacturer</key>
            <string></string>
            <key>SystemProductName</key>
            <string></string>
            <key>SystemSKUNumber</key>
            <string></string>
            <key>SystemSerialNumber</key>
            <string></string>
            <key>SystemUUID</key>
            <string></string>
            <key>SystemVersion</key>
            <string></string>
        </dict>

References:

Activate AMD hardware acceleration

The best reference for this is directly at the OC source: https://github.com/acidanthera/OpenCorePkg/commit/1cb8490fd60f6b5f983d42e5bbf08e3d2d43d8f6 Explicitly: bit 35 (FW_FEATURE_SUPPORTS_LARGE_BASESYSTEM) of FirmwareFeatures is required for the update. The minimal approach is to preserve the...

forums.macrumors.com

Activate AMD hardware acceleration

Happy to help! If you're curious about the FirmwareFeatures, you can obtain the original values by booting Mojave natively (without OpenCore) and running dmidecode (for the SMBIOS values) and also entering the following Terminal commands (for the NVRAM values): nvram -x...

forums.macrumors.com

0488568 · Mar 12, 2022

OVERKILL338LM said:
You are quite welcome!

I had the opposite experience, so that's interesting! I found Monterey to be MUCH faster than Big Sur.

Hi,

So I've made a backup of my big sur installed and I'm going through the open core legacy patcher route to try out Monterey.

So far so good, I do like that it builds an OC config specific for your machine and it installs it automatically. What I didn't like was that it installs an older version of OC (0.7.7 I think).

It did detect my bluetooth stuff during the setup.

Hopefully its as quick as you say.

Thanks for the tips.

OVERKILL338LM · Mar 12, 2022

fabriciom said:
Hi,

So I've made a backup of my big sur installed and I'm going through the open core legacy patcher route to try out Monterey.

So far so good, I do like that it builds an OC config specific for your machine and it installs it automatically. What I didn't like was that it installs an older version of OC (0.7.7 I think).

It did detect my bluetooth stuff during the setup.

Hopefully its as quick as you say.

Thanks for the tips.

No problem!

0488568 · Mar 12, 2022

OVERKILL338LM said:
No problem!

So far so good.

I did the post install for the patcher and it found my wifi which I had lost a while ago.

It does feels snapier than Big Sur.

I'm having to re-authorize all my AUs again but no biggie.

I feel that the OCLP route right now is the best solution. Don't need to get your hands dirty. Just a couple of clicks and things are done.

Thanks!

toomanyairmiles · Mar 12, 2022

toomanyairmiles said:
I'm experiencing some weird mouse behavior, dropping windows while dragging, for example.

Anyone have any thoughts on what might be behind it? Opencore on Big Sur and Opencore on Catalina both have the same behavior.

Mac Pro 5,1 with RX580 and two 4k displays.

So I finally got to the bottom of this and the solution is setting AppleEvent to OEM.

Opencore contains a reimplementation of the OEM Apple Event protocol which, on (I guess) multi monitor 4k display systems like mine, has too short of a timeout and this leads to a 'senile cursor' that forgets what you're dragging. You can alter the timeout using PointerPollMin, I haven't had time to try this, but the OEM setting has finally resolved this issue for me.

More info: https://dortania.github.io/docs/latest/Configuration.html and see 11.10 AppleInput Properties

719c6 · Mar 12, 2022

1st - After getting Mojave going with the -no_compat_check, I have since moved on to Monterey... working great BTW. I have not removed the arg in the config.plist since moving to Monterey. Question is, do I need to delete it or leave it?

2nd - 8 sticks of 2GB 10600 ECC or 8 sticks of 4GB 10600 non-ECC?

Thanks!

cdf · Mar 12, 2022

719c6 said:
1st - After getting Mojave going with the -no_compat_check, I have since moved on to Monterey... working great BTW. I have not removed the arg in the config.plist since moving to Monterey. Question is, do I need to delete it or leave it?

It doesn’t hurt to keep it, but it serves no purpose if you are booting only Catalina and later through OC. Besides, you can always boot Mojave natively if need be.

Scubaman · Mar 13, 2022

fabriciom said:
I've got Monterey 12.2.1 working but no bluetooth.

Do I need to get a new bluetooth card? If so which one?

Thanks

Hi, I have a Mac Pro 5,1 and been having issues with Bluetooth for a while. I finally bit the bullet and bought the kit from OSX Wifi (US$214.98):

Mac Pro 2009 (4,1) and Mac Pro 2010-2012 (5,1) - Apple Broadcom BCM943602CDP - 802.11 a/b/g/n/ac with Bluetooth 4.2 Upgrade Kit - Limited Edition

802.11ac, BT 4.2 and Continuity & Handoff for HACKINTOSH, Mac Pro, iMac with Native Support for Apple Broadcom BCM943602CDP for PC, HACKINTOSH, Mac Pro, iMac

www.osxwifi.com

It's not cheap but Monterey 12.2.1 is working fine on my system. Do buy the Antenna Kit as it makes sure your bluetooth connections are optimised.

PS: any idea where to get a copy of OC 0.7.9 - I've got 0.7.8 but it seems this is out of date.

PeterHolbrook · Mar 13, 2022

Scubaman said:
any idea where to get a copy of OC 0.7.9 - I've got 0.7.8 but it seems this is out of date.

Try post #1.

0488568 · Mar 13, 2022

Scubaman said:
Hi, I have a Mac Pro 5,1 and been having issues with Bluetooth for a while. I finally bit the bullet and bought the kit from OSX Wifi (US$214.98):

Mac Pro 2009 (4,1) and Mac Pro 2010-2012 (5,1) - Apple Broadcom BCM943602CDP - 802.11 a/b/g/n/ac with Bluetooth 4.2 Upgrade Kit - Limited Edition

802.11ac, BT 4.2 and Continuity & Handoff for HACKINTOSH, Mac Pro, iMac with Native Support for Apple Broadcom BCM943602CDP for PC, HACKINTOSH, Mac Pro, iMac

www.osxwifi.com

It's not cheap but Monterey 12.2.1 is working fine on my system. Do buy the Antenna Kit as it makes sure your bluetooth connections are optimised.

PS: any idea where to get a copy of OC 0.7.9 - I've got 0.7.8 but it seems this is out of date.

I solved all my problems by using OCLP.

trifero · Mar 13, 2022

Scubaman said:
Hi, I have a Mac Pro 5,1 and been having issues with Bluetooth for a while. I finally bit the bullet and bought the kit from OSX Wifi (US$214.98):

Mac Pro 2009 (4,1) and Mac Pro 2010-2012 (5,1) - Apple Broadcom BCM943602CDP - 802.11 a/b/g/n/ac with Bluetooth 4.2 Upgrade Kit - Limited Edition

802.11ac, BT 4.2 and Continuity & Handoff for HACKINTOSH, Mac Pro, iMac with Native Support for Apple Broadcom BCM943602CDP for PC, HACKINTOSH, Mac Pro, iMac

www.osxwifi.com

It's not cheap but Monterey 12.2.1 is working fine on my system. Do buy the Antenna Kit as it makes sure your bluetooth connections are optimised.

PS: any idea where to get a copy of OC 0.7.9 - I've got 0.7.8 but it seems this is out of date.

Really, no need to spend that money. Just an adapter and proper BT/WiFI module

719c6 · Mar 14, 2022

Most of the macOS have their respective icon in the bootpicker... any way to designate the different Windows versions, ie. Windows 10 vs. 11?

Bmju · Mar 14, 2022

https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/Flavours.md - forward search for Windows; you need to create .contentFlavour file next to each bootable Windows file \EFI\Microsoft\Boot\bootmgfw.efi:

Windows is automatically detected by OpenCore, so the basic Windows flavour will be applied automatically. Unlike macOS, Windows versions are not detected automatically, so per-version icons will require manual specification by the user (e.g. in .contentFlavour) as follows, in order to be found and used.

Windows icon is recommended, all others are optional.

Windows - Microsoft Windows (auto-detected by OC; fallback: HardDrive)

Windows11:Windows - Microsoft Windows 11 (Windows11.icns)

Windows10:Windows - Microsoft Windows 10 (Windows10.icns)

Windows8_1:Windows - Microsoft Windows 8.1 (Windows8_1.icns, etc.)

Windows8:Windows - Microsoft Windows 8

Windows7:Windows - Microsoft Windows 7

719c6 · Mar 14, 2022

Bmju said:
https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/Flavours.md - forward search for Windows; you need to create .contentFlavour file next to each bootable Windows file \EFI\Microsoft\Boot\bootmgfw.efi:

Anyone have "premade" Windows icons 10 & 11 that fit the default OCLP style? I found a Windows10.icns and renamed to .VolumeIcon.icns in the EFI folder. Works but can't find a 11.

Wifinomad · Mar 14, 2022

sfalatko said:
Here is the relevant part from the first post - you need to put these lines back into your config.plist in the NVRAM key -

⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀
<key>NVRAM</key>
<dict>
<key>Add</key>
<dict>
<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<dict>
<key>boot-args</key>
<string>-no_compat_check</string>
</dict>
⋮
</dict>
<key>Delete</key>
<dict>
<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<array>
<string>boot-args</string>
</array>
</dict>

Sorry for the noob question but does that mean adding these two sections directly under <key>NVRAM</key> or replacing lines that are already there. I updated to 0.7.7 via OCLP 0.4.2 and I have the same issue of old OS's no longer being permissible. They loaded with OC 0.7.3. I attached my config.plist as it currently is for a cMP with Radeon 580. Grateful for advice as system works perfectly otherwise with MacOS 12.2 and 11.6.4 but I have need of an old Mojave install for a Drobo NAS.

sfalatko · Mar 14, 2022

Wifinomad said:
Sorry for the noob question but does that mean adding these two sections directly under <key>NVRAM</key> or replacing lines that are already there. I updated to 0.7.7 via OCLP 0.4.2 and I have the same issue of old OS's no longer being permissible. They loaded with OC 0.7.3. I attached my config.plist as it currently is for a cMP with Radeon 580. Grateful for advice as system works perfectly otherwise with MacOS 12.2 and 11.6.4 but I have need of an old Mojave install for a Drobo NAS.

Add "-no_compat_check" to the line with "keepsyms=1 debug=0x100" so it reads "-no_compat_check keepsyms=1 debug=0x100" (separated by spaces). No other changes needed.

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

Cancelled

macrumors 65816

macrumors 68020

macrumors 65816

macrumors member

macrumors newbie

Contributor

macrumors 68030

macrumors newbie

Contributor

Cancelled

macrumors member

Cancelled

macrumors newbie

macrumors member

macrumors 68020

macrumors member

macrumors 68000

Cancelled

macrumors 68030

macrumors member

macrumors 6502a

macrumors member

macrumors newbie

Attachments

macrumors 6502a

Our Staff