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.
Hello there,

i have like in the first wiki post typed into a terminal

sudo nvram "recovery-boot-mode=unused" && sudo reboot recovery

After typing my password into the terminal the Mac restarts, but not into the recovery mode rather into normal Mac OS. Now, if i normal shut off the Mac and start the Mac with hold CMD+R the Mac started every time into MacOS instead the recovery mode. What can i do now?

Best regards
Chris
 
Last edited:
Chrisf1977 said:
Hello there,

i have like in the first wiki post typed into a terminal

sudo nvram "recovery-boot-mode=unused" && sudo reboot recovery

After typing my password into the terminal the Mac restarts, but not into the recovery mode rather into normal Mac OS. Now, if i normal shut off the Mac and start the Mac with hold CMD+R the Mac started every time into MacOS instead the recovery mode. What can i do now?

Best regards
Chris
Click to expand...
Try Command + R, but not Command + P

Update: just saw your post is corrected to Command + R

In that case, please make sure the recovery partition is there.

What's the return if you enter diskutil list in terminal?
 
Chrisf1977 said:
Hello there,

i have like in the first wiki post typed into a terminal

sudo nvram "recovery-boot-mode=unused" && sudo reboot recovery

After typing my password into the terminal the Mac restarts, but not into the recovery mode rather into normal Mac OS. Now, if i normal shut off the Mac and start the Mac with hold CMD+P the Mac started every time into MacOS instead the recovery mode. What can i do now?

Best regards
Chris
Click to expand...
First - just to be sure - the keystroke for entering into recovery mode on boot is Command + R.

If you are doing that and not booting into recovery mode make sure you still have a recovery partition. In terminal use
Code: 
diskutil list
You should see a list of all your disks - each one with macOS installed on it should show something like this:
Code: 
/dev/disk9 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +500.0 GB   disk9
                                 Physical Store disk7s3
   1:                APFS Volume ⁨Big Sur - Data⁩          369.3 GB   disk9s1
   2:                APFS Volume ⁨Preboot⁩                 240.9 MB   disk9s2
   3:                APFS Volume ⁨Recovery⁩                610.8 MB   disk9s3
   4:                APFS Volume ⁨VM⁩                      1.1 MB     disk9s4
   5:                APFS Volume ⁨Big Sur⁩                 15.1 GB    disk9s5
   6:              APFS Snapshot ⁨com.apple.os.update-...⁩ 15.1 GB    disk9s5s1

If you don't have recovery partition you can generally rebuild it
 
Hey there,

i am running OC on my cMP5,1 - everything working flawlessly
  • Sapphire RX 580 Pulse 8GB (got the Ati Radeon HD 5770 laying around)
  • SM951 NVMe M.2
I am planning to reinstall Mac OS Big Sur from scratch (clean install bc I will pass the cMP to another person)

How would you proceed?
- Could I just reinstall via Recovery Mode?
- Should I reinstall the HD 5770 to do so?
- Would you rather install an officially supported OSX and then re-OpenCore the machine?

Cheers, Heblon
 
Sorry, I have corrected it to CMD-R :)

diskutility says I have a Recovery Partition. Bevor I wanted to boot into the recovery partition I have copied the MacOS System from a other Disk via Super Duper to a second Disk. The copied System is also startable , but without the Recovery Mode.

Code: 
Christians-Mac-Pro:Recovery chris$ diskutil list


/dev/disk0 (external):


   #:                       TYPE NAME                    SIZE       IDENTIFIER


   0:      GUID_partition_scheme                         1.0 TB     disk0


   1:                        EFI EFI                     209.7 MB   disk0s1


   2:                 Apple_APFS Container disk2         1000.0 GB  disk0s2





/dev/disk1 (external):


   #:                       TYPE NAME                    SIZE       IDENTIFIER


   0:      GUID_partition_scheme                         500.1 GB   disk1


   1:                        EFI EFI                     209.7 MB   disk1s1


   2:       Microsoft Basic Data Win10                   499.9 GB   disk1s2





/dev/disk2 (synthesized):


   #:                       TYPE NAME                    SIZE       IDENTIFIER


   0:      APFS Container Scheme -                      +1000.0 GB  disk2


                                 Physical Store disk0s2


   1:                APFS Volume MacOS_Mojave            400.0 GB   disk2s1


   2:                APFS Volume Data                    599.0 GB   disk2s2


   3:                APFS Volume Preboot                 24.9 MB    disk2s3


   4:                APFS Volume Recovery                507.4 MB   disk2s4


   5:                APFS Volume VM                      20.5 KB    disk2s5





/dev/disk3 (internal, physical):


   #:                       TYPE NAME                    SIZE       IDENTIFIER


   0:      GUID_partition_scheme                        *1.0 TB     disk3


   1:                        EFI EFI                     209.7 MB   disk3s1


   2:                  Apple_HFS TimeMachineBackup_in... 999.9 GB   disk3s2





/dev/disk4 (external, physical):


   #:                       TYPE NAME                    SIZE       IDENTIFIER


   0:      GUID_partition_scheme                        *4.0 GB     disk4


   1:                        EFI EFI                     209.7 MB   disk4s1


   2:       Microsoft Basic Data OpenCore                3.8 GB     disk4s2





/dev/disk5 (disk image):


   #:                       TYPE NAME                    SIZE       IDENTIFIER


   0:      GUID_partition_scheme                        +7.7 GB     disk5


   1:                        EFI EFI                     209.7 MB   disk5s1


   2:                  Apple_HFS InstallESD              7.4 GB     disk5s2





Christians-Mac-Pro:Recovery chris$

The I have mounted the recovery partition. In there is a Directory with some files:

Code: 
Christians-Mac-Pro:Recovery chris$ ls


9D4491D8-F164-4B22-9AB3-26DA8BA287F0


Christians-Mac-Pro:Recovery chris$ cd 9D4491D8-F164-4B22-9AB3-26DA8BA287F0/


Christians-Mac-Pro:9D4491D8-F164-4B22-9AB3-26DA8BA287F0 chris$ ls


BaseSystem.chunklist    boot.efi.j140kap.im4m    com.apple.Boot.plist    immutablekernel.j680ap.im4m


BaseSystem.dmg    boot.efi.j174ap.im4m    immutablekernel    immutablekernel.j780ap.im4m


PlatformSupport.plist    boot.efi.j213ap.im4m    immutablekernel.j132ap.im4m    immutablekernel.x589amludev.im4m


SystemVersion.plist    boot.efi.j680ap.im4m    immutablekernel.j137ap.im4m    immutablekernel.x589icludev.im4m


boot.efi    boot.efi.j780ap.im4m    immutablekernel.j140aap.im4m    immutablekernel.x589iclydev.im4m


boot.efi.j132ap.im4m    boot.efi.x589amludev.im4m    immutablekernel.j140kap.im4m    prelinkedkernel


boot.efi.j137ap.im4m    boot.efi.x589icludev.im4m    immutablekernel.j174ap.im4m


boot.efi.j140aap.im4m    boot.efi.x589iclydev.im4m    immutablekernel.j213ap.im4m


Christians-Mac-Pro:9D4491D8-F164-4B22-9AB3-26DA8BA287F0 chris$
 
TECK said:
To make sure your config.plist is proper, validate it with ocvalidate tool. You could also use the OC Plistlib Generator or OC Configurator to make sure your config is correct.
Click to expand...

For users whose configurations are based on the sample here in the guide, your suggestion is a set-up-for-failure. Before making such a suggestion and then providing "solutions," you should have clarified what will happen and why it is not significant:

ocvalidate will complain about missing properties for DataHub, Generic, Memory, PlatformNVRAM, and SMBIOS. These warning can be ignored for the basic configuration because none of the properties get applied. Populating the properties with empty or default values will silence the warnings. For an advanced configuration (in manual mode with UpdateSMBIOS true), the SMBIOS properties do get applied, but if properties are missing or have empty values, the values already provided by the machine are used, an effective failsafe for real Macs.

When the sample configuration in the guide was first designed, ocvalidate had not yet been released. But now that more users adopt ocvalidate, and to more strictly adhere to OpenCore design guidelines, it might be worth it in the next update to add those entries to the sample configuration.
 
Thanks for update the guide. Next week I try to install Big Sur on the Mac Pro. I just have some doubts about the post install, what changes exactly should I consider?
My Mac Pro is a 4.1 with 5.1 firmware
2x 2.26GHz Intel Xeon CPU
16 GB Ram
AMD Radeon HD 7950 3GB with modified firmware
Kingston SATA SSD 500GB
Samsung 970 EVO SSD 1TB on PCIe Adapter
USB 3.0 on PCIe Card by Sonnet Technologies

Thanks in advance for your help.
 
Heblon said:
Hey there,

i am running OC on my cMP5,1 - everything working flawlessly
  • Sapphire RX 580 Pulse 8GB (got the Ati Radeon HD 5770 laying around)
  • SM951 NVMe M.2
I am planning to reinstall Mac OS Big Sur from scratch (clean install bc I will pass the cMP to another person)

How would you proceed?
- Could I just reinstall via Recovery Mode?
- Should I reinstall the HD 5770 to do so?
- Would you rather install an officially supported OSX and then re-OpenCore the machine?

Cheers, Heblon
Click to expand...
There are different ways to go about this. For a clean install, I would recommend booting from Mojave natively from another disk (see "Disabling OpenCore" in Part 3 of the guide), back up your OC EFI files (particularly if you have an advanced custom configuration), prepare your disk for installation (APFS), install OC (updated with a basic configuration) and boot Mojave through it, then install Big Sur to your disk (from Mojave), and finally restore any custom settings to OC.
 
  • Like
Reactions: karsten and Heblon
syncom said:
Thanks for update the guide. Next week I try to install Big Sur on the Mac Pro. I just have some doubts about the post install, what changes exactly should I consider?
My Mac Pro is a 4.1 with 5.1 firmware
2x 2.26GHz Intel Xeon CPU
16 GB Ram
AMD Radeon HD 7950 3GB with modified firmware
Kingston SATA SSD 500GB
Samsung 970 EVO SSD 1TB on PCIe Adapter
USB 3.0 on PCIe Card by Sonnet Technologies

Thanks in advance for your help.
Click to expand...
Familiarize yourself with the VMM flag. Leaving it on to install Big Sur will ensure a smooth installation. Afterwards, you'll want to disable it (and it can remained disabled for Big Sur if you go for an advanced configuration with hybridization). You can disable DirectGopRendering if your graphics card is flashed, and depending on your monitor, you might want to change UIScale. After these minor post-install changes, look into an advanced configuration to fully reap the benefits of OpenCore. Good luck!
 
  • Like
Reactions: syncom
TECK said:
This is proper, is an empty dictionary:
Click to expand...
What he meant was that it was not the proper way to CLOSE a tag.
That is, when you have opened a tag with "<dict>", using "<dict/>" in an attempt to close this is not proper.
 
Last edited:
  • Like
Reactions: TECK
Next Problem. I have followed all Steps to the step blend: bless --mount /Volumes/EFI --setBoot --file /Volumes/EFI/EFI/BOOT/BOOTx64.efi --verbose. After rebooting i have no text-based boot picker, the Mac booted directly into MacOs. Is this happened while i have only one bootable system or must the boot picker always shown?

This is the output from the terminal in recovery mode after the bless command:
IMG_2650.jpg


Why says bless "Preferred System Partition found disk3s1"? The OC Partition is disk5s1. Disk3s1 is my MacOS Mojave Installation.
 
Last edited:
Continuity in Big Sur? -

Any advice on how to enable continuity in Big Sur? I have successfully implemented manual patches in Mojave and Catalina but have not found anything on enabling it in Big Sur. Bluetooth and WiFi are working fine in Big Sur as I have upgraded my Airport card.

I did try the "ExtendBTFeatureFlags"setting as TRUE in my config.plist but that didn't work for me. Any help would be appreciated.

I have a 2010 MacPro5,1.

Regards,
SMF
 
I have now played with some parameters in the config.plist, like Resolution, TakeOffDelay and Timeout. I have increased the Takeoffdelay to 5000 and the Timeout to 60(sec). Now I can see if the Mac is booting, the LED on the USB Stick where OC is installed is blinking, the LED of my mouse is going on, after about 60 seconds the LED of my Mouse goes off for a short time (1 or 2 seconds) and MacOS is loaded. This says me that the Boot Picker is loaded, but I cannot see it on my screen.

In the Terminal I can also see that the Mac is booted with OC:

Code: 
Christians-Mac-Pro:OpenCore 0.6.6 chris$ nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version


4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version    REL-066-2021-02-02


Christians-Mac-Pro:OpenCore 0.6.6 chris$

Has anyone an idea why I cannot see the Text Bootpicker or the Graphical Bootpicker?
 
cdf said:
the values already provided by the machine are used, an effective failsafe for real Macs
Click to expand...
I opened https://github.com/acidanthera/bugtracker/issues/1477, do you know where is documented that the values already provided by the machine are used? Thank you for letting me know.

Edit: Vitaly replied, they are improving the documentation. I asked him to confirm if we should define into config.plist all properties with their default failsafe values, in order to to avoid OC guessing/interpreting if a failsafe value or OEM system value should be used.

For now, I implemented all missing properties into OC Plistlib Generator and also have an automated validation of generated config.plist.
 
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