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

[startergo]

Great! I think I'm making headway. I can see now the two hidden files inside the boot folder. So, if I think I labelled them incorrectly, I should be able to just delete them and re-label, correct?

It should overwrite them too. @joevt has more comprehensive utility:

macOS disk labels, mounting partitions

macOS disk labels, mounting partitions. GitHub Gist: instantly share code, notes, and snippets.

gist.github.com

 

[dmcnaugh15]

Very good. I'll try "macOS disk labels" out! I do have [hopefully] one last question about the disklabel tool.

When I enter "disklabel" in the terminal line, I see the usage options, like "-status <diskname>", etc. But, when I try to enter any of those terminal commands, I get responses like the following: "zsh: command not found: -status". I also tried using variations with sudo at the beginning. See screenshot for other commands I tried.

 

[tsialex]

Very good. I'll try "macOS disk labels" out! I do have [hopefully] one last question about the disklabel tool.

When I enter "disklabel" in the terminal line, I see the usage options, like "-status <diskname>", etc. But, when I try to enter any of those terminal commands, I get responses like the following: "zsh: command not found: -status". I also tried using variations with sudo at the beginning. See screenshot for other commands I tried.

For most commands, you use the following syntax: name_of_command command_options origin destiny

You should use:

disklabel -status diskXX

 

[EddieK420]

@cdf Post #1 is the best. Thank you so much for all the hard work you put into doing this for us!. Some of us do not have as much free time as @hwojtek to read through 250 pages of forums postings.

 

[dmcnaugh15]

For most commands, you use the following syntax: name_of_command command_options origin destiny

You should use:

disklabel -status diskXX

Thanks tsialex. Using that syntax, I still get the following message (also see screenshot):

• cannot open disk2: No such file or directory

 

[tsialex]

Thanks tsialex. Using that syntax, I still get the following message (also see screenshot):

• cannot open disk2: No such file or directory

Use OC own version of disklabel, not the macOS one:

OpenCore on the Mac Pro

For disk labeling OC provides its own program called disklabel: Copy and paste that to your Bootx64.efi folder: cd to the folder in terminal and run: g5@G5s-Mac-Pro-2 BOOT % /Volumes/EFI/EFI/BOOT/disklabel Usage: disklabel -d .disk_label image.ppm! disklabel -e "Label" .disk_label...

forums.macrumors.com

 

[dmcnaugh15]

I think I was using the OC version. I just entered the mac diskutil list command in the screenshot to demonstrate that the disk I'm interested in checking exists.

 

[cdf]

The guide now includes some instructions for installing Linux.

 

[redbandit0]

After a bit of work and troubleshooting through these wonderful forums to get OC 0.6.4 and my cMP 5,1 working with both Mojave and High Sierra, I am stuck with the csrutil in disabled status. I can't get it to turn back on! I boot into recovery (I have tried the recovery on both those two OSes) and it just will not stay turned on after the reboot. I would really like to get that last step worked out. Anyone run into this before? Thanks!

 

[sL1pKn07]

Hi ppl

today start migrate from clover to opencore 0.6.4

all seems ok... but when login or stay un the loggin screen some time, the machine freeze :S

i saw in redit this,

https://www.reddit.com/r/hackintosh/comments/gefagu

but change the machine type in my case is a no go. because my hardware is too old (bios based) (Xeon x5650 + Gigabyte GA-EX58-UD5)

anyone with the same issue like me solve the problem?

greetings

 

[dmcnaugh15]

Hi ppl

today start migrate from clover to opencore 0.6.4

all seems ok... but when login or stay un the loggin screen some time, the machine freeze :S

i saw in redit this,

https://www.reddit.com/r/hackintosh/comments/gefagu

but change the machine type in my case is a no go. because my hardware is too old (bios based) (Xeon x5650 + Gigabyte GA-EX58-UD5)

anyone with the same issue like me solve the problem?

greetings

Did you try pressing the clear cmos button on the back of the motherboard, and re-entering the BIOS parameters? After my transition from Clover to OC, I had mouse freezing problems, and pressing the clear cmos fixed that.

 

[nobullone1964]

Hi ppl

today start migrate from clover to opencore 0.6.4

all seems ok... but when login or stay un the loggin screen some time, the machine freeze :S

i saw in redit this,

https://www.reddit.com/r/hackintosh/comments/gefagu

but change the machine type in my case is a no go. because my hardware is too old (bios based) (Xeon x5650 + Gigabyte GA-EX58-UD5)

anyone with the same issue like me solve the problem?

greetings

This is not a Hackintosh thread. It's for Mac Pro only. There are other places to look for help with PCs.

 

[sL1pKn07]

Hi

iep. dozen of times. also when reboot/shutdown, i have "resets" is the bios wich i need to restore by hand (AHCI, logo screen, enable things)

not works

i also try to restore my clover backup (from linux, installing the bootloader), but now i get kernel panics :S

i'm not sure what i touch. maybe EFI file permissions? :S

EDIT: ok. clover fixed. seems some kext with symlinks do problems. remove it solve the issue

greetings

 

[h9826790]

After a bit of work and troubleshooting through these wonderful forums to get OC 0.6.4 and my cMP 5,1 working with both Mojave and High Sierra, I am stuck with the csrutil in disabled status. I can't get it to turn back on! I boot into recovery (I have tried the recovery on both those two OSes) and it just will not stay turned on after the reboot. I would really like to get that last step worked out. Anyone run into this before? Thanks!

 

[joevt]

For most commands, you use the following syntax: name_of_command command_options origin destiny

You should use:

disklabel -status diskXX

That's the macOS disk label command.

whereis disklabel
result:
/sbin/disklabel

whatis disklabel
result:
disklabel(8) - manipulate and query an Apple Label disk label


Kind of unfortunate that OpenCore decided to use the same name as the command included in macOS.
See man disklabel for more info about the macOS command.
I'm not sure what an Apple Label disk label is, but it has nothing to do with the .disk_label files that you want to create.

The OpenCore command should probably be executed using it's path or make an alias:

disklabel=/Volumes/Storage/Downloads/OpenCore\ 0.6.4\ Release/Utilities/disklabel/disklabel
alias disklabel="'$disklabel'"
disklabel

result:

Usage:
disklabel -d .disk_label image.ppm!
disklabel -e "Label" .disk_label .disk_label_2x
disklabel -bgra "Label" .disk_label .disk_label_2x

My script at https://gist.github.com/joevt/6d7a0ede45106345a39bdfa0ac10ffd6 has some disk label related commands:

• dump_label shows what a disk label looks like (sort of - the result is two hex digits per pixel, with white pixels replaced with .. - but the result is good enough to be able to read, especially for the 2x labels)
• dumpAllDiskLabels shows disk labels that are located in certain locations on all disks:
  • 1) in the folder containing the blessed file on an APFS or HFS+ volume
  • 2) in the folder containing a boot.efi file at the second level of a volume
  • 3) in the /System/Library/CoreServices folder at the root or second level of a volume
  • 4) in the /EFI/BOOT folder
  • You should use the mountEFIpartitions, mountRecoveryHDpartitions, mountRecoveryPartitions, mountPrebootPartitions commands beforehand so that it can check all the partitions.
• makemultilinedisklabel to make a multi-line disk label.
• makeLabelCommands makes sample multi-lined disk label creation commands for HFS+ macOS volumes. Edit the result before executing the same command.

 

[donchan]

Hello,

I installed Catalina on my 4,1 -> 5,1 following the guide in this thread.
Thanks for this.
If I would install Big Sure which steps I have to do?
Thank you so much.

 

[paalb]

Hello,

I installed Catalina on my 4,1 -> 5,1 following the guide in this thread.
Thanks for this.
If I would install Big Sure which steps I have to do?
Thank you so much.

Read this and decide if you wan't to do that now. I am waiting for missing things to resolve first. https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/post-29417580

 

[javieralvarez]

Hey Friends - any info on the safety of these updates? I'm currently 10.14.6 (Mojave) with Opencore 0.6.4 on a 5,1. Thanks!

 

[nobullone1964]

Hey Friends - any info on the safety of these updates? I'm currently 10.14.6 (Mojave) with Opencore 0.6.4 on a 5,1. Thanks!

They are fine. If you're a fan of Topsites don't update Safari.

 

[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	Catalina supported GPU**, EFI (flashed) or a standard UEFI card (PC GPU)

* Need to upgrade? See the upgrade instructions.
** Several GPUs that are supported with High Sierra had support removed from Mojave and Catalina, like any non-Kepler generation NVIDIA GPUs or AMD GPUs earlier than HD 7950. Several HD 78xx GPUs (Pitcairn) were rebadged as R9 2xx and are not supported anymore by Mojave/Catalina drivers. All Mac Pro factory GPUs had support removed with Mojave.

PART I
Basic Installation




PART II
Advanced Configuration




PART III
Maintenance




APPENDIX
Third Party OS Installation
​

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!

In the guide to step "3 First Boot" is reported:
bless --mount /Volumes/EFI --setBoot
but unfortunately it never works! Why?
I tried also to follow the spoiler to reset the SMC but nothing happens!
In a previous version of the guide the following command was suggested:
bless --mount /Volumes/EFI --setBoot --file /Volumes/EFI/EFI/BOOT/BOOTx64.efi --verbose.
In fact only through this extended command I can perform the Bless.
Why?
Thank you!

 

[Caesar_091]

Is there a way to restore the original EFI/bootloader (i.e.: unistall OpenCore) if something goes wrong?

I've just backup-ed my primary OS boot drive (Mojave) on the MacPro in my signature: I would only go for OpenCore for H264/HVEC hardware encoding/decoding (right now I'm not interested in Catalina or BigSur) and, why not, boot picker screen. Can I install it just on the right disk and EFI partition (Mojave disk with its EFI partition) without a Disk A and Disk B configuration as per this tutorial's 1st post?

TIA

 

[h9826790]

Is there a way to restore the original EFI/bootloader (i.e.: unistall OpenCore) if something goes wrong?

I've just backup-ed my primary OS boot drive (Mojave) on the MacPro in my signature: I would only go for OpenCore for H264/HVEC hardware encoding/decoding (right now I'm not interested in Catalina or BigSur) and, why not, boot picker screen. Can I install it just on the right disk and EFI partition (Mojave disk with its EFI partition) without a Disk A and Disk B configuration as per this tutorial's 1st post?

TIA

You better simply install my OC package if your primary aim is to enable HWAccel.

Activate AMD hardware acceleration

I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package updated to 1.0.0] For those who only need HWAccel, post #594 has everything you need. This new package mainly offer HWAccel + boot screen. Also, this package should work in...

forums.macrumors.com

My package is developed for that purpose.

And as long as you have backup the content in your EFI partition (usually, nothing useful at there), you can always revert the changes.

 

[IceHouse]

Hey Friends - any info on the safety of these updates? I'm currently 10.14.6 (Mojave) with Opencore 0.6.4 on a 5,1. Thanks!

I use the OC 0.6.4 Package from h9826790 and I try to install the Security Update 2020-007 - no sucess - it works on the update but after a second boot it shows a Protokoll Screen Windows and only tells me that there was an error - not which. I can save the protokoll, send it to Apple or reboot.

I try it 2 times without sucess then I give up.

Mea Culpa - mea maxima culpa... it was the 2020-005 Update I try and got the Eroor. Now I had boot into 10.14.6 and check the Updates - see the 2020-007 Update and give it a try - it works 1A without any Error. Sorry for confusion... go ahead 🤪 🖖

 

[cdf]

In the guide to step "3 First Boot" is reported:
bless --mount /Volumes/EFI --setBoot
but unfortunately it never works! Why?
I tried also to follow the spoiler to reset the SMC but nothing happens!
In a previous version of the guide the following command was suggested:
bless --mount /Volumes/EFI --setBoot --file /Volumes/EFI/EFI/BOOT/BOOTx64.efi --verbose.
In fact only through this extended command I can perform the Bless.
Why?
Thank you!

Although this is a very well known issue, why it happens is not clear... Have you tried the first command with other disks in your Mac?

 

[GunStrauss]

Hmm, I'm happily running both macOS Big Sur and Windows 10 on my 5.1 Mac Pro, but I have an issue:

After installing Windows 10, I got the very nice boot screen where I could select between Windows 10 and macOS, however; now I don't get the boot screen any more when the Windows 10 disk is connected, it starts directly in Windows.

Weird issue? Can it have something to do with Windows update?