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.
Hi, I am currently running Catalina 10.15.7 and everything works great. Because I do not have upgraded Wi-Fi card, I am injecting using OpenCore IO80211Family.kext extracted from Mojave ( Was anyone successful with only Brcm4331.kext? I do not think it's compatible with other Catalina's kexts in IO80211Family ) and it's stable so far ( Can't boot recovery/installer with IO80211Family enabled though ). Can anyone here confirm that IO80211Family from Mojave is still compatible with Big Sur? Thanks
 
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.
Click to expand...

Hello,

I tried this change in the config plist but big sur is still asking for a firmware update before installing on APFS (it is proposing me to use the last SATA drive I have which is still HFS+)

Did I miss something ?

Thanks
 
  • Like
Reactions: PowerPaw
shadow_999 said:
Hello,

I tried this change in the config plist but big sur is still asking for a firmware update before installing on APFS (it is proposing me to use the last SATA drive I have which is still HFS+)

Did I miss something ?

Thanks
Click to expand...
I'll recheck the part II to be sure to have everything done. Are all the steps mandatory ?

Thanks
 
Thanks for the contributions from everyone so far and especially Martin - I finally have this to working with Big Sur Beta :)

Plenty more to do with figuring out how to tweak this monster but hopefully getting somewhere with this at last.
 

Attachments

  • Screenshot 2020-11-01 at 14.55.35.png
    Screenshot 2020-11-01 at 14.55.35.png
    144.1 KB · Views: 245
cdf said:
Unfortunately, it seems that users have had mixed results with XFX cards. Some have a bootscreen, some no bootscreen, and others weird colors. Hopefully somebody with the same card can chime in.
Click to expand...
Ok, so I got farther along on the issue, it turns out my XFX card does in fact have OpenCore boot screens and I have returned it to the default vbios.

The problem is it only wants to output on a different monitor of mine, and doesn’t wait to draw on my LG Ultrafine 4K (w/ vr2 cable). I am going to mess around with the output settings in my config.plist and see if I can get anywhere.

Or is there a way to reliably boot between UEFI Windows 10 & MacOS (Big Sur) with open core without boot screens, rather than just trying to get the arrow keys right in the dark? A way to use the boot picker in MacOS and a specific version of BootCamp to allow going back the other way?
 
Last edited:
The OpenCore software allows me to choose between Mojave and Catalina, which I would not be able to do from preferences, since Mojave is dimmed out.

My only irritation is that the boot choice screen is basically a typed two lines with the preferred boot (Catalina) being listed as 1 and the other boot (Mojave) being listed as 2.

The name of the operating system is not provided, just the name of the drive: Drive 1 and Mac HD.

The boot coice screen is available for about 1 to maybe 1-1/2 seconds.

If I type 2, the computer boots to Mojave on the Mac HD and if 1, the computer boots to Catalina on Drive 1.

If I do not type in a number (which there is barely time to do) the computer defaults to Catalina.

In the Wiki on installing OpenCore it shows a boot choice screen with images of three drives. I would assume that that screen remains either for a fairly long time, or until the choice is made.

What do I need to do to get that same sort of boot choice screen?

Thanks for the help. Making progress.
 
wnlewis said:
The OpenCore software allows me to choose between Mojave and Catalina, which I would not be able to do from preferences, since Mojave is dimmed out.

My only irritation is that the boot choice screen is basically a typed two lines with the preferred boot (Catalina) being listed as 1 and the other boot (Mojave) being listed as 2.

The name of the operating system is not provided, just the name of the drive: Drive 1 and Mac HD.

The boot coice screen is available for about 1 to maybe 1-1/2 seconds.

If I type 2, the computer boots to Mojave on the Mac HD and if 1, the computer boots to Catalina on Drive 1.

If I do not type in a number (which there is barely time to do) the computer defaults to Catalina.

In the Wiki on installing OpenCore it shows a boot choice screen with images of three drives. I would assume that that screen remains either for a fairly long time, or until the choice is made.

What do I need to do to get that same sort of boot choice screen?

Thanks for the help. Making progress.
Click to expand...
It's covered in #1 part 2, may be you missed that part
 
Anyone tried the new CustomMemory function in 0.6.3 beta with 32GB DIMM?

I wonder if this allow the 5,1 to run 8x32GB RAM in macOS.
 
Dayo said:
Can anyone help translate this response on spoofing SSE4.2 support into plain English?
Click to expand...
Use the VMM flag as an example.

forums.macrumors.com

Understanding the OpenCore Data variable settings

I'll answer the easier question first. You want to convert the hex value: printf "\x02" | base64. For the other question, try printf "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x80\x00\x00\x00\x00" | base64. Taking endianness into account, the 00 00 00 80 part corresponds to the ECX register...
forums.macrumors.com forums.macrumors.com
 
h9826790 said:
Anyone tried the new CustomMemory function in 0.6.3 beta with 32GB DIMM?

I wonder if this allow the 5,1 to run 8x32GB RAM in macOS.
Click to expand...
Nope but I will try since I was last time the one who asked for it. So I am gonna try and report back. Do you have a link where I can download 0.6.3 beta? Thank you.
 
Last edited:
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.
Click to expand...
I tried with these:
Code: 
<key>BoardProduct</key>
            <string>Mac-7BA5B2D9E42DDD94</string>
<key>FirmwareFeatures</key>
            <data>PvWP/QAAAAA=</data>
            <key>FirmwareFeaturesMask</key>
            <data>P/+f/wAAAAA=</data>
Which are the regular iMacPro1,1 features generated by OpenCore Configurator and it is doing the same.
Code: 
machdep.cpu.feature_bits: 1053530050427354111
machdep.cpu.extfeature_bits: 5034215680
 
205Maxi said:
Alright tried and it did not work, I am pretty sure I am doing something wrong in the config.

I do not know if the first part memory is correct ...


</dict>
<key>Memory</key>
<dict>
<key>DataWidth</key>
<integer>64</integer>
<key>ErrorCorrection</key>
<integer>3</integer>
<key>FormFactor</key>
<integer>9</integer>
<key>MaxCapacity</key>
<integer>68719476736</integer>
<key>TotalWidth</key>
<integer>64</integer>
<key>Type</key>
<integer>26</integer>
<key>TypeDetail</key>
<integer>128</integer>
<key>Devices</key>
<array>
<dict>
<key>AssetTag</key>
<string></string>
<key>BankLocator</key>
<string>BANK 0</string>
<key>DeviceLocator</key>
<string>ChannelA-DIMM0</string>
<key>Manufacturer</key>
<string>Kynix</string>
<key>PartNumber</key>
<string>HMT84GR7AMR4C-H9</string>
<key>SerialNumber</key>
<string>80AD011432304F4FE6</string>
<key>Size</key>
<integer>32768</integer>
<key>Speed</key>
<integer>1333</integer>
</dict>
<dict>
<key>AssetTag</key>
<string></string>
<key>BankLocator</key>
<string>BANK 1</string>
<key>DeviceLocator</key>
<string>ChannelA-DIMM1</string>
<key>Manufacturer</key>
<string>Kynix</string>
<key>PartNumber</key>
<string>HMT84GR7AMR4C-H9</string>
<key>SerialNumber</key>
<string>80AD011432304F4FE6</string>
<key>Size</key>
<integer>32768</integer>
<key>Speed</key>
<integer>1333</integer>
</dict>
<dict>
<key>AssetTag</key>
<string></string>
<key>BankLocator</key>
<string>BANK 2</string>
<key>DeviceLocator</key>
<string>ChannelB-DIMM0</string>
<key>Manufacturer</key>
<string>Kynix</string>
<key>PartNumber</key>
<string>HMT84GR7AMR4C-H9</string>
<key>SerialNumber</key>
<string>80AD011432304F4FE6</string>
<key>Size</key>
<integer>32768</integer>
<key>Speed</key>
<integer>1333</integer>
</dict>
<dict>
<key>AssetTag</key>
<string></string>
<key>BankLocator</key>
<string>BANK 3</string>
<key>DeviceLocator</key>
<string>ChannelB-DIMM1</string>
<key>Manufacturer</key>
<string>Kynix</string>
<key>PartNumber</key>
<string>HMT84GR7AMR4C-H9</string>
<key>SerialNumber</key>
<string>80AD011432304F4FE6</string>
<key>Size</key>
<integer>32768</integer>
<key>Speed</key>
<integer>1333</integer>
</dict>
</array>
</dict>
<key>PlatformNVRAM</key>
Click to expand...
use ProperTree to check the config file:

config.plist Setup | OpenCore Install Guide

dortania.github.io
You can copy/paste the code directly in an empty sheet. If it is valid it will accept it.
 
  • Like
Reactions: paalb
205Maxi said:
Alright tried and it did not work, I am pretty sure I am doing something wrong in the config


</dict>
<key>Memory</key>
<dict>
<key>DataWidth</key>
<integer>64</integer>
<key>ErrorCorrection</key>
<integer>3</integer>
<key>FormFactor</key>
<integer>9</integer>
<key>MaxCapacity</key>
<integer>68719476736</integer>
<key>TotalWidth</key>
<integer>64</integer>
<key>Type</key>
<integer>26</integer>
<key>TypeDetail</key>
<integer>128</integer>
<key>Devices</key>
<array>
<dict>
<key>AssetTag</key>
<string></string>
<key>BankLocator</key>
<string>BANK 0</string>
<key>DeviceLocator</key>
<string>ChannelA-DIMM0</string>
<key>Manufacturer</key>
<string>Kynix</string>
<key>PartNumber</key>
<string>HMT84GR7AMR4C-H9</string>
<key>SerialNumber</key>
<string>80AD011432304F4FE6</string>
<key>Size</key>
<integer>32768</integer>
<key>Speed</key>
<integer>1333</integer>
</dict>
<dict>
<key>AssetTag</key>
<string></string>
<key>BankLocator</key>
<string>BANK 1</string>
<key>DeviceLocator</key>
<string>ChannelA-DIMM1</string>
<key>Manufacturer</key>
<string>Kynix</string>
<key>PartNumber</key>
<string>HMT84GR7AMR4C-H9</string>
<key>SerialNumber</key>
<string>80AD011432304F4FE6</string>
<key>Size</key>
<integer>32768</integer>
<key>Speed</key>
<integer>1333</integer>
</dict>
<dict>
<key>AssetTag</key>
<string></string>
<key>BankLocator</key>
<string>BANK 2</string>
<key>DeviceLocator</key>
<string>ChannelB-DIMM0</string>
<key>Manufacturer</key>
<string>Kynix</string>
<key>PartNumber</key>
<string>HMT84GR7AMR4C-H9</string>
<key>SerialNumber</key>
<string>80AD011432304F4FE6</string>
<key>Size</key>
<integer>32768</integer>
<key>Speed</key>
<integer>1333</integer>
</dict>
<dict>
<key>AssetTag</key>
<string></string>
<key>BankLocator</key>
<string>BANK 3</string>
<key>DeviceLocator</key>
<string>ChannelB-DIMM1</string>
<key>Manufacturer</key>
<string>Kynix</string>
<key>PartNumber</key>
<string>HMT84GR7AMR4C-H9</string>
<key>SerialNumber</key>
<string>80AD011432304F4FE6</string>
<key>Size</key>
<integer>32768</integer>
<key>Speed</key>
<integer>1333</integer>
</dict>
</array>
</dict>
<key>PlatformNVRAM</key>
Click to expand...
Apart from checking the code.

You may need to spoof the memory config as well. Insert the memory config that's same as your real memory config most likely won't help.

e.g. Rather than set memory as 4x32GB DIMM, you may try to spoof it to 8x16GB DIMM.

If you purely want to make sure your memory config code works. Please use 16GB DIMM to test that first. Since 32GB DIMM can't boot macOS by default. You will have no way to know which part doesn't work if you swap DIMM and add memory config at the same time.
 
  • Like
Reactions: eksu
h9826790 said:
Apart from checking the code.

You may need to spoof the memory config as well. Insert the memory config that's same as your real memory config most likely won't help.

e.g. Rather than set memory as 4x32GB DIMM, you may try to spoof it to 8x16GB DIMM.
Click to expand...
When I put 0.6.3 in it does not boot, as soon I put 0.6.2 without changing anything she it works.

I am gonna review the config plist with the memory config and see if it works the way you are describing it.

Let's see, finger crossed...

Thank you for your help
 
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