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

[joevt]

Well, as described in the guide, OpenCore exposes the EFI partition to which it's installed. You can mount the EFI
by entering u=$(nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:boot-path | sed 's/.*GPT,\([^,]*\),.*/\1/'); if [ "$u" != "" ]; then sudo diskutil mount $u && open /Volumes/EFI/ ; fi in Terminal.

This assumes the new mount will be at /Volumes/EFI/ which is only true if you don't have another EFI already mounted.

I usually use my script at https://gist.github.com/joevt/6d7a0ede45106345a39bdfa0ac10ffd6 to mount all EFI partitions.
In each EFI partition, I put a folder with a name describing the partition. Then I can go to a specific EFI partition by including the name of the folder:
open /Volumes/EFI*/*bay2*/.. This example opens the root folder of the EFI partition of the disk in bay 2 of my MacPro3,1.

The command to open the Open Core boot path partition can be changed like this:

source "~/Downloads/DiskUtil.sh"
u=$(nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:boot-path | sed 's/.*GPT,\([^,]*\).*/\1/'); [[ -n $u ]] && sudo diskutil mount $u && getdiskinfo $u OC_ && open "$OC_MountPoint"

but in that case I would just make a new command and add it to DiskUtil.sh:

openopencore () {
	local u=$(nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:boot-path | sed 's/.*GPT,\([^,]*\).*/\1/'); [[ -n $u ]] && sudo diskutil mount $u && getdiskinfo $u OC_ && open "$OC_MountPoint"
}

 

[kkinto]

Hi - I have had to restore my boot drive from a CCC copy and the names are identical in opencore bootpicker even though they appear correct as renamed in various places like desktop. How do I edit the drive names so that those new names (not the old ones) actually appear in the OC bootpicker? Thanks

 

[joevt]

Hi - I have had to restore my boot drive from a CCC copy and the names are identical in opencore bootpicker even though they appear correct as renamed in various places like desktop. How do I edit the drive names so that those new names (not the old ones) actually appear in the OC bootpicker? Thanks

You need to update the .disk_label or .disk_label_2x or .disk_label.contentDetails files?

 

[kkinto]

You need to update the .disk_label or .disk_label_2x or .disk_label.contentDetails files?

Thanks but I can't see any of those on any of my drives' root. Where are they located (invisibles are showing I assume as they start wit a period)? Also, how do you update them - do you need an app or are they text files?

*edit: oh I found them (.disk_label, .disk_label_2x on my Time Machine disk root). I tried to open them with text edit but obviously they are encoded or something as they are unintelligible

 

[jhmtx66]

I searched for a solution to this problem, but could not find any information. Hoping someone knows how to resolve this issue. Mac Pro 5,1 with OpenCore 0.70. Upgraded to Big Sur 11.2.3 and SATA drives in Bay 3 and 4 are not showing up (not in disk utility or finder) following any reboot. SSD drives in Bay 1 and 2 show up fine. I have to do a shutdown, then power up for them to be visible. Boot off my Catalina drive and all drives are showing up fine after both a reboot or a shutdown and power up. Any help is appreciated.

 

[austinhealey175]

I have the same configuration as you do and have the same situation. I’m only seeing all of my sata drives from a cold boot (off to power on). If I do a warm boot/restart all of them often won’t show up. They do however work normally during sleep/wake cycles.

 

[joevt]

Thanks but I can't see any of those on any of my drives' root. Where are they located (invisibles are showing I assume as they start wit a period)? Also, how do you update them - do you need an app or are they text files?

*edit: oh I found them (.disk_label, .disk_label_2x on my Time Machine disk root). I tried to open them with text edit but obviously they are encoded or something as they are unintelligible

They are not in the root. They are in the same folder as the efi file that gets booted for that partition.
The bless command can create new disk labels. Open Core has a command to do that. I have a script I use to make all my labels.
https://gist.github.com/joevt/6d7a0ede45106345a39bdfa0ac10ffd6
https://forums.macrumors.com/threads/mac-pro-3-1-cooling.2257855/post-28972512

 

[Mindgap]

Just "Open Cored" my 5,1 (super excited!) and ready for the Big Sure update. Now, it seems Big Sure is only supported till 11.3 but the Apple software update screen shows 11.5.1

Is there any chance to install 11.3 only?

 

[Macschrauber]

Till 11.2.3, the glitches start with 11.3

 

[panjandrum]

I'm having excellent luck *so far* (I realize this might change) with a series of Mac Pros (4,1 -> 5,1s). I'm using OCLP and Latebloom and at this point have 4 machines reliably booting and working seemingly without issue on 11.5.1. Been restarting them, both warm and cold booting, all week. I'll report something in the Latebloom thread sometime next week, once I've done more rigorous testing and get it installed on a couple more configurations.

I've got a mix of 580, 570, and 560 video cards, plus a lone Zotac Geforce 710. The 580s, 570s, and Geforce 710 all work (the 710 produces no video over ARD).

However, the 560 cards are "Biostar" brand, and are giving me problems. I have yet to try swapping one into an already functional system running 11.5.1, I'll give that a whirl next week this weekend, but they have garbaged video at the boot screen bad enough to prevent me from even attempting to install directly to a system with this card. These are, admittedly the cheapest 560 cards I could find at the time (now worth $899) and even their build quality is crap, so this should not surprise me. Still, they are rock-solid under Mojave, so maybe there is hope.

Anyone else get a "Biostar" branded Radeon RX 560 working? If I'm unable to resolve these issues I would be happy to send one of these to the team or individual most responsible for working on OC GPU support, if that would be of any help (probably not since this has pretty much got to be at the GPU BIOS level I imagine.)

EDIT & UPDATE: Biostar RX 560 cards are working for me after the drivers load seemingly without issue. Only a couple hours of testing, but as soon as the drivers load everything is fine. I'll need to keep swapping a 570 or 580 into each system that has a 560, just for the install process, but other than that I *think* things are good.

 

[Mindgap]

Got 11.2.3 on my machine. Now, my WIFI doesn't work at all anymore. Is there something I missed doing?

Software Versions:
CoreWLAN: 16.0 (1657)
CoreWLANKit: 16.0 (1657)
Menu Extra: 17.0 (1728)
System Information: 15.0 (1502)
IO80211 Family: 12.0 (1200.12.2b1)
Diagnostics: 11.0 (1163)
AirPort Utility: 6.3.9 (639.15)

 

[MacRumors3590]

Got 11.2.3 on my machine. Now, my WIFI doesn't work at all anymore. Is there something I missed doing?

Software Versions:
CoreWLAN: 16.0 (1657)
CoreWLANKit: 16.0 (1657)
Menu Extra: 17.0 (1728)
System Information: 15.0 (1502)
IO80211 Family: 12.0 (1200.12.2b1)
Diagnostics: 11.0 (1163)
AirPort Utility: 6.3.9 (639.15)

I use OCLP 0.2.4 to bring wifi back and it works perfect everytime even after an update on BS.
Mac Pro 5,1 w/Stock 802.11n

GitHub - dortania/OpenCore-Legacy-Patcher: Experience macOS just like before

Experience macOS just like before. Contribute to dortania/OpenCore-Legacy-Patcher development by creating an account on GitHub.

github.com

 

[TECK]

@cdf, if I want to go back to Catalina because the Big Sur 11.3+ issues, can I use the current config.plist? I remember the config was slightly different when we used Catalina.

What is the cleanest way to install Catalina from scratch, boot in Mojave and perform the install?

 

[0134168]

@cdf, if I want to go back to Catalina because the Big Sur 11.3+ issues, can I use the current config.plist? I remember the config was slightly different when we used Catalina.

What is the cleanest way to install Catalina from scratch, boot in Mojave and perform the install?

That´s what I did. Installed a clean Mojave, added OC and then updated to Catalina.

 

[TECK]

Thanks @*******, quick question about Monterey public beta, did anyone tried to install it with current config.plist provided by @cdf?

 

[0134168]

Thanks @*******, quick question about Monterey public beta, did anyone tried to install it with current config.plist provided by @cdf?

My pleasure.
Not me, stucked in Catalina. And my external SSD for test in Big Sur. If you try, please let us know how it goes.

 

[PeterHolbrook]

@cdf, if I want to go back to Catalina because the Big Sur 11.3+ issues, can I use the current config.plist? I remember the config was slightly different when we used Catalina.

I'm not @cdf, but I think it is imperative that you set the OC virtual machine flag for Catalina, or you won't receive any possible updates. See post #1.

 

[cdf]

if I want to go back to Catalina because the Big Sur 11.3+ issues, can I use the current config.plist? I remember the config was slightly different when we used Catalina.

Yes, the config is perfectly compatible with Catalina. If minimality is your thing, you won't need unfairgva for DRM, but it doesn't hurt to keep it. As mentioned in the guide and pointed out by @PeterHolbrook, you'll have to turn on the VMM flag when you want to receive updates, but Catalina updates are of course rarer now. You will also need to turn on the flag when installing Catalina from Mojave.

What is the cleanest way to install Catalina from scratch, boot in Mojave and perform the install?

Correct. A clean install from Mojave booted through OpenCore will work well.

For those that want to continue with Big Sur, I would not recommend installing 11.3+ through Mojave. It seems that the race condition is exacerbated by installing macOS to an APFS volume formatted in earlier versions of the OS. To install the current version of macOS, I would recommend using a bootable installer to reformat the physical disk as APFS (Disk Utility select View > Show All Devices) and then install from there. In fact, my testing suggests that the presence of any volumes formatted in earlier versions are triggers for the hanging, so I would recommend using the installer to reformat all disks after backing up your data.

@TECK, I would not give up on Big Sur just yet. With a complete reformatting of all my disks, Latebloom has completely suppressed the race condition on my system. I would even say that 11.5.1 has been the most stable version of Big Sur so far—although perhaps that's just an impression after having experienced the pain of 11.3, 11.3.1, and 11.4.

Remark: With a complete reformatting, you'll lose your natively bootable Mojave lifeline, so unless you have a flashed graphics card, a different strategy has to be in place for future maintenance like reblessing OC. The idea is to at least be able to get into a preboot environment on demand. I've found that an emergency OpenCore CD is very effective for this: holding C at boot will unfailingly make your machine boot from the CD. Apparently C also works for USB drives, but I haven't found this to be the case.

 

[ber404]

Hi, is this method still good to update opencore ?

I'm on 0.6.3 and want to update to 0.7 ..

 

[PeterHolbrook]

Hi, is this method still good to update opencore ?

This thread advocates a very advanced and customizable method to install/update OpenCore. Why exactly do you feel somebody here should take the time to analyze an alternative method? If you aren't happy with the method advocated here, you should be the one who takes the time to study and apply the alternative method, don't you think?

 

[paalb]

I searched for a solution to this problem, but could not find any information. Hoping someone knows how to resolve this issue. Mac Pro 5,1 with OpenCore 0.70. Upgraded to Big Sur 11.2.3 and SATA drives in Bay 3 and 4 are not showing up (not in disk utility or finder) following any reboot. SSD drives in Bay 1 and 2 show up fine. I have to do a shutdown, then power up for them to be visible. Boot off my Catalina drive and all drives are showing up fine after both a reboot or a shutdown and power up. Any help is appreciated.

This is not an OpenCore issue. I have had the same problem without OpenCore and several different OS’es on MacPro 5,1. Read this: https://discussions.apple.com/thread/7132585

 

[ber404]

This thread advocates a very advanced and customizable method to install/update OpenCore. Why exactly do you feel somebody here should take to time to analyze an alternative method? If you aren't happy with the method advocated here, you should be the one who takes the time to study and apply the alternative method, don't you think?

It's not really an alternative .. it's Martin Lo youtube channel. And I asked because it's not the same explanation on this forum. I'm not too bad at IT, but I'm lost ..

 

[mode11]

Remark: With a complete reformatting, you'll lose your natively bootable Mojave lifeline, so unless you have a flashed graphics card, a different strategy has to be in place for future maintenance like reblessing OC.

Surely this doesn't apply when you keep the Mojave disk outside the MP, and only reinsert it when you need to do maintenance? In that situation, you'll be booting into Mojave rather than Big Sur, so there shouldn't be any hanging?

 

[0134168]

Surely this doesn't apply when you keep the Mojave disk outside the MP, and only reinsert it when you need to do maintenance? In that situation, you'll be booting into Mojave rather than Big Sur, so there shouldn't be any hanging?

Correct. Just in my case, never had to boot from Mojave for fixing yet.

 

[cdf]

It's not really an alternative .. it's Martin Lo youtube channel. And I asked because it's not the same explanation on this forum. I'm not too bad at IT, but I'm lost ..

The procedure described here is for updating your own custom configuration that you would have created step by step by following parts 1 and 2 of the guide. If you have opted for Martin's universal solution instead, you should follow the procedure that applies to it. Take a look at

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 0.7.9] 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

Regarding the validity of that procedure, you might have more luck asking over there. Good luck!