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

[205Maxi]

config.plist attached.

May be processor count make the difference. My single processor 5,1 can boot Big Sur with 7,1 SMBIOS. Just have the usual "memory config alert" after boot to desktop.

It's expected only one port work with iMac Pro SMBIOS until you patch board-id to board-ix (usually done via WhateverGreen) but you can also do that manually

<key>Patch</key>
        <array>
            <dict>
                <key>Base</key>
                <string></string>
                <key>Comment</key>
                <string>Patch AppleGraphicsDevicePolicy board-id to board-ix</string>
                <key>Count</key>
                <integer>0</integer>
                <key>Enabled</key>
                <true/>
                <key>Find</key>
                <data>Ym9hcmQtaWQ=</data>
                <key>Identifier</key>
                <string>com.apple.driver.AppleGraphicsDevicePolicy</string>
                <key>Limit</key>
                <integer>0</integer>
                <key>Mask</key>
                <data></data>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>Replace</key>
                <data>Ym9hcmQtaXg=</data>
                <key>ReplaceMask</key>
                <data></data>
                <key>Skip</key>
                <integer>0</integer>
            </dict>
        </array>

So the MacPro 7,1 spoofing works because you only have te Single Proc Tray. and You only have one gigantic screen, I run 3 ACD's and when I put the single tray in it works too... When I switch for the Dual then Panic.

Now if I spoof with iMacPro Both works Dual and Single but I only get 1 screen out of the 3 working.
[automerge]1593117372[/automerge]

So the MacPro 7,1 spoofing works because you only have te Single Proc Tray. and You only have one gigantic screen, I run 3 ACD's and when I put the single tray in it works too... When I switch for the Dual then Panic.

Now if I spoof with iMacPro Both works Dual and Single but I only get 1 screen out of the 3 working.

Also as always a big thank you to you. I think that I got the idea.. I am just wondering why spoofing the MacPro7,1 only gives me Kernel Panic with Dual, I mean we know that MacPro7,1 is single socket so that's maybe the problem, it was perfectly working fine with Catalina though.

 

[startergo]

Interesting. Boot Camp Assistant in Big Sur now works without modification. No more "This Mac does not support Boot Camp." The utility even detected my existing Windows installation and gave the option to erase it.

Hmmm. So maybe you can copy that boot camp app so we can test it under Catalina/Mojave?

 

[eksu]

I read this on the discord:
User "Veemyu#8767"

We are unable to see this post unless we have an invite link to the discord. What discord server is this / could you share a link?

Thanks.

 

[205Maxi]

config.plist attached.

May be processor count make the difference. My single processor 5,1 can boot Big Sur with 7,1 SMBIOS. Just have the usual "memory config alert" after boot to desktop.

It's expected only one port work with iMac Pro SMBIOS until you patch board-id to board-ix (usually done via WhateverGreen) but you can also do that manually

<key>Patch</key>
        <array>
            <dict>
                <key>Base</key>
                <string></string>
                <key>Comment</key>
                <string>Patch AppleGraphicsDevicePolicy board-id to board-ix</string>
                <key>Count</key>
                <integer>0</integer>
                <key>Enabled</key>
                <true/>
                <key>Find</key>
                <data>Ym9hcmQtaWQ=</data>
                <key>Identifier</key>
                <string>com.apple.driver.AppleGraphicsDevicePolicy</string>
                <key>Limit</key>
                <integer>0</integer>
                <key>Mask</key>
                <data></data>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>Replace</key>
                <data>Ym9hcmQtaXg=</data>
                <key>ReplaceMask</key>
                <data></data>
                <key>Skip</key>
                <integer>0</integer>
            </dict>
        </array>

When you say " until you patch board-id to board-ix " do I need only to declare <string>Patch AppleGraphicsDevicePolicy board-ix</string> ? No sure I understood Can I get some clarifications? Also where in the WhateverGreen you replace by the board id? there is nothing as such there...

 

[brucifer]

Hi folks,

I have a Mid 2010 cMP 5,1 dual 3.46 6core, 128GB ram, Radeon VII (Slot1), Sonnet m2 x4 NVME (1TB boot, 3x1TB in Raid0) (Slot2), Myricom 10Gb CX4 for network connection (Slot3) .TitanRidge TB3 (Slot4). Pixlas Mod has been done and is powering the Radeon VII, and I've got OpenCore running for the TitanRidge, as well as for the HW Acceleration for the Radeon VII. Im running 10.14.6.
This is all running great! Except for my Myricom 10Gb card. The card did work fine before I installed OC. I was able to get almost full wire speed at 10Gb. Almost a full 1GB per second. Since I started messing around with OC I now can only get around 400 Write but only 30MB Read! I've tried other cards, other slots. I also installed the latest Myri driver (1.3.6) that is for 10.14. I tested this in a non OC box and was getting decent speeds, so I'm thinking it must have something to do with OC, but just not sure where to start looking.

Since getting the TB3 working I've got an OWC pro doc that has the 10Gb ethernet port on it. I've tested this and I currently am getting 400MB Read and write speeds. This is another problem I'm trying to work out.. why only 400? If I can get this working at full speed then I can get rid of the Myricom and not worry about it, but I'm still curious why I'm seeing this issue.
Any suggestions?
I really appreciate any help with this.
Thanks for any ideas.
brucifer

 

[jvlfilms]

Hello everyone! I'm looking to try OpenCore as I'm getting a little tired of not having boot screens. I have a pretty simple setup which is as follows:

- PCIe drive w/ Mojave
- SATA SSD drive with Windows 10

Now if I want to use OpenCore I'd have to basically lose Win10 drive unless I convert it to UEFI mode.

IDEALLY I would boot into Windows 10 and use the converter tool MBR2GPT. Then install OC from my Mojave drive. Does that seem right?

 

[startergo]

We are unable to see this post unless we have an invite link to the discord. What discord server is this / could you share a link?

Thanks.

Discord - Group Chat That’s All Fun & Games

Discord is great for playing games and chilling with friends, or even building a worldwide community. Customize your own space to talk, play, and hang out.

discord.gg

 

[jameslmoser]

The Hide Self param was removed in OC v0 5.9

Oh that is right I remember seeing something about that...

 

[telepati]

Big Sur should be installed with Virtual machine or with supported Mac on an external drive and fully booted to Desktop then:

Open your config.plist and change:
Booter --> Quirks --> AvoidRuntimeDefrag to FALSE (NO) otherwise you can't boot at all

NVRAM --> ADD --> 7C436110-AB2A-4BBB-A880-FE41995C9F82
create a new DATA child with a value of <00>

And also

NVRAM --> Delete --> 7C436110-AB2A-4BBB-A880-FE41995C9F82

create a new String called "booter-fileset-kernel"

Could you please share your config.plist?

 

[Tiem]

That's due to the iMac Pro SMBIOS spoofing, nothing about the Navi X6000 framework issue.

Without this boot argument, most likely only one display port on the card will work.

Not so much as a result of running it headless, which both the MP7,1 and iMP1,1 do. Framebuffer isn't used because we don't run iGPUs.

And you'd notice right away if you need the argument as once the macOS loader passes it to the Framebuffer, all you'll get is a black screen.

 

[eksu]

Following some settings from the linked discord and after compiling a pre-release build of OpenCore 0.6.0 for myself, I was able to install Big Sur with the AppleRaid kext for my SAS drives as well as RadeonBoost.

 

[startergo]

Driver injection into kernel collections normally used in macOS 11, and required for macOS 11 installer, is
unsupported.
Possible workarounds:
For preinstalled versions of macOS 11 add NVRAM variable
7C436110-AB2A-4BBB-A880-FE41995C9F82:booter-fileset-kernel with 00 value; for some EfiBoot variants
it may also be required to set booter-fileset-basesystem variable
New OC 0.6 commit is posted with possible workaround for macOS 11
You need to compile it from the master branch. For simplicity you can use OCBuilder. As always check your configuration with ocvalidate (former ConfigValidity)
And review the differences:

OpenCorePkg/Docs/Differences/Differences.pdf at master · acidanthera/OpenCorePkg

OpenCore bootloader. Contribute to acidanthera/OpenCorePkg development by creating an account on GitHub.

github.com

inspect and compare your plist to the current sample.plist

 

[205Maxi]

Not so much as a result of running it headless, which both the MP7,1 and iMP1,1 do. Framebuffer isn't used because we don't run iGPUs.

And you'd notice right away if you need the argument as once the macOS loader passes it to the Framebuffer, all you'll get is a black screen.

Well I was finally able to spoof it has a MacPro7,1 on Dual CPU Tray. There is only one thing that you do not see here if you paid attention to...

 

[DigitaLife]

OpenCore on Legacy Apple Hardware

This guide explains how to use the excellent OpenCore bootloader on a classic Mac Pro to install, run and update macOS Catalina, resulting in a clean, unpatched operating system no different than on a supported Mac.

Why OpenCore?

There are several advantages to using OpenCore on a classic Mac Pro:

Boot picker screen (even with a standard graphics card)
View attachment 916024
Software Update (just like on a supported Mac)
View attachment 882160
Hardware acceleration (and DRM for Netflix on Safari) View attachment 919405
Requirements

Mac Pro model	Early 2009 with MacPro5,1 firmware,* Mid 2010 or Mid 2012
Processor architecture	Westmere (E56xx, L56xx, X56xx) / Gulftown (W36xx)
Boot ROM version	144.0.0.0.0*
Graphics	EFI (flashed) or standard UEFI card

* Need to upgrade? See the upgrade instructions.

PART I
Basic Installation




PART II
Advanced Configuration




PART III
Maintenance




APPENDIX​

Acknowledgements

A big thank you to @vit9696 and the other talented developers of Acidanthera for making all of this possible. Special gratitude goes to @h9826790 for spearheading the hardware acceleration study and @startergo for the relentless testing that led to boot screen support. And thanks to all those that have contributed to this thread!

Sorry but I don't understand the follow step for Windows installation.
What exactly should I do?

Prepare the installer

Use the actual volumes names in the following step:

• Enter: rsync -r /Volumes/CCCOMA_X64/ /Volumes/USB

Let the task complete.

Can you help me please?
Thanks in advance!

 

[cdf]

Sorry but I don't understand the follow step for Windows installation.
What exactly should I do?

Prepare the installer

Use the actual volumes names in the following step:

• Enter: rsync -r /Volumes/CCCOMA_X64/ /Volumes/USB

Let the task complete.

Can you help me please?
Thanks in advance!

You enter that command in terminal after mounting the USB drive and the Windows ISO (the actual names may be different than CCCOMA_X64 and USB). Make sure not to forget the "/" that follows the name of the ISO. The command will copy the contents of the ISO to the USB drive.

 

[jackluke]

Driver injection into kernel collections normally used in macOS 11, and required for macOS 11 installer, is
unsupported.
Possible workarounds:
For preinstalled versions of macOS 11 add NVRAM variable
7C436110-AB2A-4BBB-A880-FE41995C9F82:booter-fileset-kernel with 00 value; for some EfiBoot variants
it may also be required to set booter-fileset-basesystem variable
New OC 0.6 commit is posted with possible workaround for macOS 11
You need to compile it from the master branch. For simplicity you can use OCBuilder. As always check your configuration with ocvalidate (former ConfigValidity)
And review the differences:

OpenCorePkg/Docs/Differences/Differences.pdf at master · acidanthera/OpenCorePkg

OpenCore bootloader. Contribute to acidanthera/OpenCorePkg development by creating an account on GitHub.

github.com

inspect and compare your plist to the current sample.plist

I just discovered a way to boot BigSur using the legacy prelinkedkernel without OpenCore:

macOS 11 Big Sur on Unsupported Macs Thread

Breaking news: I discovered a way to boot BigSur without Opencore using the legacy prelinkedkernel instead of the new BootKernelExtensions.kc , here are the steps: diskutil apfs list to identify your UUID-BigSur unique Preboot Volume string. diskutil mount Preboot or mount your BigSur Preboot...

forums.macrumors.com

It implies a manual editing of Preboot BigSur com.apple.Boot.plist redirecting the kernelcache to the prelinkedkernel rather than BootKernelExtensions.kc , the advantage is that on the prelinkedkernel opencore version 0.59 can still inject dynamically the kext .

 

[DigitaLife]

You enter that command in terminal after mounting the USB drive and the Windows ISO (the actual names may be different than CCCOMA_X64 and USB). Make sure not to forget the "/" that follows the name of the ISO. The command will copy the contents of the ISO to the USB drive.

I am afraid that I will have to give up installing Windows according to the guide ... for me it is quite complicated and I am afraid to make mistakes!
I didn't think it was so complicated for me!
I think I will have to redo the installation in Legacy Mode and then convert to UEFI, even if I'm afraid of certificates ...

 

[cdf]

I am afraid that I will have to give up installing Windows according to the guide ... for me it is quite complicated and I am afraid to make mistakes!
I didn't think it was so complicated for me!
I think I will have to redo the installation in Legacy Mode and then convert to UEFI, even if I'm afraid of certificates ...

Sure. But copying the Windows ISO files to a USB drive is a pretty standard step...

 

[DigitaLife]

Sure. But copying the Windows ISO files to a USB drive is a pretty standard step...

Sorry but I'm pretty confused ...:
1) I copied the entire file, called "Win10_2004_Italian_x64" inside the USB called "Win10", but nothing happens.
2) On the other hand, if I open the Windows ISO file, the volume that appears in the finder is called "CCCOMA_X64_FRE_IT-IT_DV9".
I then copied the entire contents directly to the USB volume (Win10).
I tried to restart and in fact I see the Windows external drive!
So how should I use the rsync -r / Volumes / CCCOMA_X64 / / Volumes / USB command?
Even some subsequent steps are not quite so simple ... Too bad because all the driving is really well done !!!
Thanks so much for your patience.

 

[cdf]

I then copied the entire contents directly to the USB volume (Win10).
I tried to restart and in fact I see the Windows external drive!
So how should I use the rsync -r / Volumes / CCCOMA_X64 / / Volumes / USB command?

If you've already copied the contents to the USB drive, then you don't need that command, because that's what the command does. For the subsequent steps, the important thing is to use the actual drive letters that you get from diskpart.

 

[Alex-IN]

Well I was finally able to spoof it has a MacPro7,1 on Dual CPU Tray. There is only one thing that you do not see here if you paid attention to...

View attachment 927923

Can look at EFI?

 

[DigitaLife]

If you've already copied the contents to the USB drive, then you don't need that command, because that's what the command does. For the subsequent steps, the important thing is to use the actual drive letters that you get from diskpart.

I arrived at the last step .. everything is ok but now I wouldn't want to go wrong!
The EFI volume of the Windows drive is empty ... what exactly should I copy here?

• Copy /USB/EFI/Microsoft to /Volumes/EFI/EFI
• Delete /USB/EFI and rename efi.bak to efi

And the next step is not clear to me: what and where should I delete?

Sorry but without your help I can't do it!
Thank you very much!

 

[cdf]

I arrived at the last step .. everything is ok but now I wouldn't want to go wrong!
The EFI volume of the Windows drive is empty ... what exactly should I copy here?

• Copy /USB/EFI/Microsoft to /Volumes/EFI/EFI
• Delete /USB/EFI and rename efi.bak to efi

And the next step is not clear to me: what and where should I delete?

Sorry but without your help I can't do it!
Thank you very much!

The EFI volume of the Windows drive is empty. That's OK. In that volume, create a folder called EFI. Now look at the contents of your USB drive. You should see a folder called EFI and a folder called efi.bak. If you open the folder called EFI, you should see a folder called Microsoft. Copy that folder into the EFI folder you just created. Finally delete the EFI folder in the USB drive and rename efi.bak to efi. Don't forget to remove the USB drive before proceeding. When you reboot you should see Windows (not external) in the boot picker.

 

[DigitaLife]

The EFI volume of the Windows drive is empty. That's OK. In that volume, create a folder called EFI. Now look at the contents of your USB drive. You should see a folder called EFI and a folder called efi.bak. If you open the folder called EFI, you should see a folder called Microsoft. Copy that folder into the EFI folder you just created. Finally delete the EFI folder in the USB drive and rename efi.bak to efi. Don't forget to remove the USB drive before proceeding. When you reboot you should see Windows (not external) in the boot picker.

Perfect!
But why do I have to "finally delete the EFI folder in the USB drive and rename efi.bak to efi"?
Last question:
but when should I have entered the license key?
At the first step, the window for entering the license key and other information appeared, but as I previously carried out other operations with the Command Prompt, this no longer appeared!
Now I tried to change the license key from the system settings but it says that my key is not valid (purchased regularly) and in any case Windows seems to be activated regularly!
Really strange !!!

 

[cdf]

But why do I have to "finally delete the EFI folder in the USB drive and rename efi.bak to efi"?

The USB drive originally contained the folder called efi, which made the drive bootable. During the installation, we backed up that folder and replace it with another one that we generated for your Windows drive. This folder contained the Microsoft folder that we needed. After copying the Microsoft folder, we restore the USB drive to its original state in case we want to use it again.

but when should I have entered the license key?
At the first step, the window for entering the license key and other information appeared, but as I previously carried out other operations with the Command Prompt, this no longer appeared!
Now I tried to change the license key from the system settings but it says that my key is not valid (purchased regularly) and in any case Windows seems to be activated regularly!
Really strange !!!

Windows probably activated itself automatically when you connected to the internet. If you've ever had Windows activated on your machine, Microsoft knows it.