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.
Dayo said:
Do you think this will not work then ... or only on non-cMP:
Click to expand...
Note that "MaxBIOSVersion" only applies to a generic (automatic, full-spoofing) platform information configuration, which we don't tend to use here.

As a precaution, I've set BIOSVersion to 9999.0.0.0.0 for use with a manual (iMac Pro board-ID hybridization) configuration.
 
  • Like
Reactions: Eschers and h9826790
cdf said:
Note that "MaxBIOSVersion" only applies to a generic (automatic, full-spoofing) platform information configuration, which we don't tend to use here.

As a precaution, I've set BIOSVersion to 9999.0.0.0.0 for use with a manual (iMac Pro board-ID hybridization) configuration.
Click to expand...
Yes about the auto. Was just curious in general whether it would work given the observation. Presumably you think it would from your setting.
 
Dayo said:
Presumably you think it would from your setting.
Click to expand...
Correct.

I believe this idea is due to h9826790 and it makes sense that it should work. Right now, it's the best thing we have to prevent unwanted firmware updates in Big Sur.
 
  • Like
Reactions: Dayo
I think it depends what you are spoofing. The bios version will match the board ID's ROM settings. So for cMP it will adjust to a 3 digit (first) and for the iMacPro1,1 and the MacPro7,1 will be different.
 
Last edited:
Don't use Generic section even with only MaxBIOSVersion set to yes, because this is the result:
Code: 
Hardware Overview:

  Model Name:    Mac Pro
  Model Identifier:    MacPro6,1
  Processor Name:    6-Core Intel Xeon
  Processor Speed:    3.5 GHz
  Number of Processors:    2
  Total Number of Cores:    12
  L2 Cache (per Core):    256 KB
  L3 Cache (per Processor):    12 MB
  Hyper-Threading Technology:    Enabled
  Memory:    128 GB
  System Firmware Version:    9999.999.999.999.999
  SMC Version (system):    1.39f11
  SMC Version (processor tray):    1.39f11
  Serial Number (system):    OPENCORE_SN1
  Hardware UUID:    137698FB-2630-5450-867C-0A70D9731D5B
  Provisioning UDID:    137698FB-2630-5450-867C-0A70D9731D5B

Code: 
<key>PlatformInfo</key>
    <dict>
        <key>Automatic</key>
        <true/>
        <key>CustomMemory</key>
        <false/>
        <key>Generic</key>
        <dict>
            <key>MaxBIOSVersion</key>
            <true/>
        </dict>
        <key>SMBIOS</key>
        <dict>
            <key>BIOSReleaseDate</key>
            <string></string>
            <key>BIOSVendor</key>
            <string></string>
            <key>BIOSVersion</key>
            <string></string>
            <key>BoardAssetTag</key>
            <string></string>
            <key>BoardLocationInChassis</key>
            <string></string>
            <key>BoardManufacturer</key>
            <string></string>
            <key>BoardProduct</key>
            <string>Mac-7BA5B2D9E42DDD94</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>
            </data>
            <key>FirmwareFeaturesMask</key>
            <data>
            </data>
            <key>PlatformFeature</key>
            <integer>0</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>
        <key>UpdateDataHub</key>
        <false/>
        <key>UpdateNVRAM</key>
        <false/>
        <key>UpdateSMBIOS</key>
        <true/>
        <key>UpdateSMBIOSMode</key>
        <string>Create</string>
    </dict>
 
This works fine:
Code: 
<key>PlatformInfo</key>
    <dict>
        <key>Automatic</key>
        <false/>
        <key>CustomMemory</key>
        <false/>
        <key>SMBIOS</key>
        <dict>
            <key>BIOSReleaseDate</key>
            <string></string>
            <key>BIOSVendor</key>
            <string></string>
            <key>BIOSVersion</key>
            <string>9999.0.0.0.0</string>
            <key>BoardAssetTag</key>
            <string></string>
            <key>BoardLocationInChassis</key>
            <string></string>
            <key>BoardManufacturer</key>
            <string></string>
            <key>BoardProduct</key>
            <string>Mac-7BA5B2D9E42DDD94</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>
            </data>
            <key>FirmwareFeaturesMask</key>
            <data>
            </data>
            <key>PlatformFeature</key>
            <integer>0</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>
        <key>UpdateDataHub</key>
        <false/>
        <key>UpdateNVRAM</key>
        <false/>
        <key>UpdateSMBIOS</key>
        <true/>
        <key>UpdateSMBIOSMode</key>
        <string>Create</string>
    </dict>
Code: 
Hardware Overview:

  Model Name:    Mac Pro
  Model Identifier:    MacPro5,1
  Processor Name:    6-Core Intel Xeon
  Processor Speed:    3.5 GHz
  Number of Processors:    2
  Total Number of Cores:    12
  L2 Cache (per Core):    256 KB
  L3 Cache (per Processor):    12 MB
  Hyper-Threading Technology:    Enabled
  Memory:    128 GB
  System Firmware Version:    9999.0.0.0.0
But I am not sure if it has any effect on the updates.
 
I'm reading this post as I'm trying to run Windows on my Mac Pro5.1. It says

The sample configuration includes the required setting to protect the Mac Pro from potential damage caused by UEFI Windows.
Click to expand...

As I already have an OpenCore configuration I want to know which setting this is so I can apply it to my current config.

Any suggestions?
 
Svenv1 said:
I'm reading this post as I'm trying to run Windows on my Mac Pro5.1. It says



As I already have an OpenCore configuration I want to know which setting this is so I can apply it to my current config.

Any suggestions?
Click to expand...
  1. ProtectSecureBoot
    Type: plist boolean
    Failsafe: false
    Description: Protect UEFI Secure Boot variables from being written.
    Reports security violation during attempts to write to db, dbx, PK, and KEK variables from the operating system.
    Note: This quirk mainly attempts to avoid issues with NVRAM implementations with problematic defragmentation, such as select Insyde or MacPro5,1.
Click to expand...
 
KevinClark said:
hello tell me please how to get the name of the OS under each volume with open core boot ?

Thanks
Click to expand...
Download the OpenCore package:
1. Open terminal and type:
Code: 
disklabel
disklabel: usage: One of
    -status <diskname>
    -create <diskname> [-msize=<size>] [owner-uid=<uid>] [owner-gid=<gid>] [dev-name=<name>] [owner-mode=<mode>] [other-property=<value>]
    -destroy <diskname>
    [-properties] <diskname> [owner-uid[=<uid>]] [owner-gid[=<gid>]] [dev-name[=<name>]] [owner-mode[=<mode>]] [other-property[=<value>]]

Hit Enter. You should get the result as above. That is the default Mac disk label.
2. Back in terminal type cp and drag the OpenCore disklabel, which you just downloaded inside the terminal:

1610460013768.png


after that type /usr/local/bin :
Code: 
cp /Volumes/EFI/Utilities/disklabel/disklabel  /usr/local/bin

and hit Enter.
3. Open new terminal and type disklabel
you should get:
Code: 
disklabel
Usage:
disklabel -d .disk_label image.ppm!
disklabel -e "Label" .disk_label .disk_label_2x
disklabel -bgra "Label" .disk_label .disk_label_2x
That is the OpenCore disklabel. Usage: disklabel -e "Label" .disk_label .disk_label_2x
Where "Label" is the desired new Volume name.
4. Run disklabel -e "Label" .disk_label .disk_label_2x after you navigated to /System/Library/CoreServices or wherever the boot files reside (if it is BOOTx64.efi or something else) inside terminal.
 
Last edited:
  • Like
Reactions: thenightflyer, h9826790 and JedNZ
startergo said:
Download the OpenCore package:
1. Open terminal and type:
Code: 
disklabel
disklabel: usage: One of
    -status <diskname>
    -create <diskname> [-msize=<size>] [owner-uid=<uid>] [owner-gid=<gid>] [dev-name=<name>] [owner-mode=<mode>] [other-property=<value>]
    -destroy <diskname>
    [-properties] <diskname> [owner-uid[=<uid>]] [owner-gid[=<gid>]] [dev-name[=<name>]] [owner-mode[=<mode>]] [other-property[=<value>]]

Hit Enter. You should get the result as above. That is the default Mac disk label.
2. Back in terminal type cp and drag the OpenCore disklabel, which you just downloaded inside the terminal:

View attachment 1711425

after that type /usr/local/bin :
Code: 
cp /Volumes/EFI/Utilities/disklabel/disklabel  /usr/local/bin

and hit Enter.
3. Open new terminal and type disklabel
you should get:
Code: 
disklabel
Usage:
disklabel -d .disk_label image.ppm!
disklabel -e "Label" .disk_label .disk_label_2x
disklabel -bgra "Label" .disk_label .disk_label_2x
That is the OpenCore disklabel. Usage: disklabel -e "Label" .disk_label .disk_label_2x
Where "Label" is the desired new Volume name.
4. Run disklabel -e "Label" .disk_label .disk_label_2x after you navigated to /System/Library/CoreServices or wherever the boot files reside (if it is BOOTx64.efi or something else) inside terminal.
Click to expand...
Thanks a lot
 
I have a 5,1 Pro running Mojave. Using the guide, I successfully mounted the EFI volume and put the opencode EFI folder into it. then I needed to reboot into recovery to bless it, using
Code: 
sudo nvram "recovery-boot-mode=unused" && sudo reboot recovery
– but this didn't work as expected. During the recovery mode boot it displays fullscreen scrolling text output showing various systems starting up, and then goes blank. I left it for 45 mins and nothing else happened.

IMG_3346.jpeg


After this I needed to zap PRAM before it would boot back into the normal system. Anyone know what's going astray here, and how I can fix it?
 
Hi all,

has anyone else lost airplay support when updating to Big Sur? for me it works perfectly in catalina (I use Airplay audio), but not in Big Sur
on a Mac Pro 5,1 (native) with single cpu Intel(R) Xeon(R) CPU X5690 @ 3.47GHz and opencore 0.63

thanks in advance!
 
I just "messed up" my 2012 MacPro 5,1 with OpenCore 0.65 and Catalina,
maybe somebody has some tips...

I had it working but then the Mac booted back into Mojave.
I then set the boot partition by System Preferences / Startup Disk to the Catalina Disk
and now it shuts down a few seconds after the boot chime.
I tried to change the volume by pressing alt at boot time, but failed to do so until now.
(have to do it blind because I have a 580 inside)
--> Is using System Preferences / Startup Disk a no-go with OpenCore ?
--> I need to go to recovery to bless a disk but System Preferences / Startup Disk can mess it up?

Second problem is the boot picker showed the EFI volume itself...
Booting it didnt work as i recall, i had to select the Catalina volume.
Is that normal?

Third problem is, my Catalina Volume was not fresh, it was cloned with CCC.
I then changed the Volume name on the desktop,
but the boot picker still shows the old volume name.

ps. I have an EFI / APPLE folder on this Disk... (some stuff inside, not just empty folders)
thought maybe that is the problem, but #1 states to just leave it.

inputs highly appreciated :)
 
zzzachi said:
Is using System Preferences / Startup Disk a no-go with OpenCore ?
Click to expand...
OpenCore obey what you select in Startup Disk, if you config it correctly.

zzzachi said:
I need to go to recovery to bless a disk but System Preferences / Startup Disk can mess it up?
Click to expand...
Every time you manually bless something, you may disable OpenCore

zzzachi said:
I had it working but then the Mac booted back into Mojave.
Click to expand...
You select to boot to Mojave?

What do you mean "THEN the Mac booted BACK into Mojave"? It did that by itself?

zzzachi said:
I then set the boot partition by System Preferences / Startup Disk to the Catalina Disk
and now it shuts down a few seconds after the boot chime.
Click to expand...
Typical symptoms if you default the cMP to boot to a macOS that isn't supported (without any boot loader, or the not compat check boot argument...)

zzzachi said:
I tried to change the volume by pressing alt at boot time, but failed to do so until now.
(have to do it blind because I have a 580 inside)
Click to expand...
100% won't work, not even in blind.

zzzachi said:
Second problem is the boot picker showed the EFI volume itself...
Booting it didnt work as i recall, i had to select the Catalina volume.
Is that normal?
Click to expand...
In fact, the simple trick to remove that EFI entry is by selecting the default boot drive you want in startup disk

zzzachi said:
Third problem is, my Catalina Volume was not fresh, it was cloned with CCC.
I then changed the Volume name on the desktop,
but the boot picker still shows the old volume name.
Click to expand...
forums.macrumors.com

OpenCore on the Mac Pro

Download the OpenCore package: https://dortania.github.io/builds/?product=OpenCorePkg&viewall=true 1. Open terminal and type: disklabel disklabel: usage: One of -status -create [-msize=] [owner-uid=] [owner-gid=] [dev-name=] [owner-mode=] [other-property=] -destroy...
forums.macrumors.com forums.macrumors.com

zzzachi said:
I have an EFI / APPLE folder on this Disk... (some stuff inside, not just empty folders)
thought maybe that is the problem, but #1 states to just leave it.
Click to expand...
99.99% not related.
 
  • Like
Reactions: octoviaa and cdf
zzzachi said:
--> Is using System Preferences / Startup Disk a no-go with OpenCore ?
--> I need to go to recovery to bless a disk but System Preferences / Startup Disk can mess it up?

Second problem is the boot picker showed the EFI volume itself...
Booting it didnt work as i recall, i had to select the Catalina volume.
Is that normal?

Third problem is, my Catalina Volume was not fresh, it was cloned with CCC.
I then changed the Volume name on the desktop,
but the boot picker still shows the old volume name.

ps. I have an EFI / APPLE folder on this Disk... (some stuff inside, not just empty folders)
thought maybe that is the problem, but #1 states to just leave it.

inputs highly appreciated :)
Click to expand...
It is recommended using System Preferences / Startup Disk that is not your problem.
It is normal to have to select Catalina volume. It is normal that Catalina volume is selected by OpenCore if you have selected it in System Preferences / Startup Disk.

It is normal that your old name is what shows. Look here

Try to use the sudo nvram "recovery-boot-mode=unused" && sudo reboot recovery
And then bless again.
 
  • Like
Reactions: cdf
paalb said:
It is recommended using System Preferences / Startup Disk that is not your problem.
It is normal to have to select Catalina volume. It is normal that Catalina volume is selected by OpenCore if you have selected it in System Preferences / Startup Disk.

It is normal that your old name is what shows. Look here

Try to use the sudo nvram "recovery-boot-mode=unused" && sudo reboot recovery
And then bless again.
Click to expand...

thanks for clarifying this ... I wonder what i did...
right now the machine shuts down after the chime, so first i need to be able to boot again!
tomorrow i try to remove the catalina ssd and see if i can get into mojave again.

about disklabel...
i saw it, but how the heck does the boot picker get the old volume name?
if i rename the disk on the desktop, even diskutil info /dev/diskXsX gives me the new name
 
Last edited:
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