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

[MrScratchHook]

MrScratchHook:, I got some down time and I'm ready to move from Mojave to perhaps Big Sur or Ventura. it appears I have the same 5,1 as you do. May I ask what OS you running with Pro Tools?

I'm currently running 2023.6, can't upgrade to the newest PT version on Mojave. THANKS

Hey man, soooo if you want to stay on mojave your are stuck with pt 2023.6,(2023.9 isnt compatible, supposedly) and its a really good version, but im currently on sonoma and pt 2023.6 its works with a couple of quirks( work-arounds) and surprisingly 99 percent of my plugins work. I WAS SHOCKED LOL

 

[kkinto]

If you can still boot.

I finally Got through the update but then twice the Mac just froze and silently restarted. Then it worked fine rest of day and evening. This morning it froze again but will now no longer boot. Just a loop of restarting without reaching the picker. I did Nvram reset and removed on drive all but mac is in restart loop now. I posted another thread about this but I think I have some kind of hardware issue. Unable to enter recovery or boot mojave.


EDIT -SOLVED OK finally seem to have solved the problem. Somehow the boot (sata) SSD got corrupted and became a mac killer. I pulled all drives out to take it to service technician and realised that it started just fine without them! No more restart loop. I couldnt see video but it was probably flashing the ? folder. Anyway. The moment I put the system SSD in I was back to restart loop. I put all other drives back, no problem. Got OC running again via Mojave and now on my backup Moneterey on NVMe its all good again. Tried putting the SSD in a dock to see if I could diagnose it with drive-dx but aas soon as I powered up the dock it killed the Mac - screen lost power and had to hard restart. Even though dock is via USB3 card it will kill the Mac anytime Ihave that ssd in there and create a reboot loop if its there on startup. So the SSD is a mac killer and I guess it needs to be replaced. Never had a problem like this before where an HD being connected would not allow Mac to startup! Anyway, I had thought I had mac board/ram/CPU/PSU type hardware issues but fortunately something easily replaced.

 

[joevt]

Tried putting the SSD in a dock to see if I could diagnose it with drive-dx but aas soon as I powered up the dock it killed the Mac - screen lost power and had to hard restart. Even though dock is via USB3 card it will kill the Mac anytime Ihave that ssd in there and create a reboot loop if its there on startup. So the SSD is a mac killer and I guess it needs to be replaced. Never had a problem like this before where an HD being connected would not allow Mac to startup! Anyway, I had thought I had mac board/ram/CPU/PSU type hardware issues but fortunately something easily replaced.

What kind of dock? Did you try hot plugging the dock while macOS was running instead of having the dock connected before boot?

 

[w1z]

@cdf I believe something has changed in 12.7.1 - Clean installation or reinstallation with hybridization enabled is not possible as the firmware update prompt keeps popping up with no way to bypass except with VMM flag enabled.

I only noticed this after successfully updating from 12.7 to 12.7.1 with hybridization enabled but after shutting down the mac, I was not able to boot into macOS as I kept getting a kernel panic after entering the password (something about a Global pointer being null or something).

Can you confirm this?

Forgot to add - I never had any issue installing, reinstalling or updating with hybridization enabled with releases up to 12.7

 

[kkinto]

What kind of dock? Did you try hot plugging the dock while macOS was running instead of having the dock connected before boot?

Actually used 3 different docks - a double one that is powered and standard Macpro USB connector (front) - tried hot power up and again on at startup. On at startup causes reboot loop same as when ssd was in bay 1, hot plug in and power up, or plug in while powered up would immediately kill video and then mac would restart. Next tried USB3 (mini adapater - like a little tray) bus powered and connect via USB3 sonnet card. Same thing exactly. Then tried another bus powered but USB2 adapter and exactly same result. Plugged USB 2 and 3 adapters into macbook 2017 and mac mini 2010 (hot) and killed video same way and made them reboot. This drive had Monetrey 12.7.1 system but not the OC EFI.

I did all that because I was hoping to see it in DiskUtil and erase/reformat it and try and recover the drive somehow. But no such luck.

Spoiler: kernel panic report from plugging in ssd "mac killer"

panic(cpu 6 caller 0xffffff801f5caf19): "kind == NEW && refcnt = -1\n" @jobj.c:4068
Panicked task 0xffffff8b96ce8670: 304 threads: pid 0: kernel_task
Backtrace (CPU 6), panicked thread: 0xffffff8b978c6540, Frame : Return Address
0xffffffcb695db740 : 0xffffff801c279a3d
0xffffffcb695db790 : 0xffffff801c3dca16
0xffffffcb695db7d0 : 0xffffff801c3cbd83
0xffffffcb695db820 : 0xffffff801c219a90
0xffffffcb695db840 : 0xffffff801c279e0d
0xffffffcb695db960 : 0xffffff801c2795c6
0xffffffcb695db9c0 : 0xffffff801cb14a83
0xffffffcb695dbab0 : 0xffffff801f5caf19
0xffffffcb695dbb20 : 0xffffff801f5ca39e
0xffffffcb695dbcd0 : 0xffffff801f59c1f8
0xffffffcb695dbf70 : 0xffffff801f59ab38
0xffffffcb695dbfa0 : 0xffffff801c21919e
Kernel Extensions in backtrace:
com.apple.filesystems.apfs(1934.141.2)[721020CF-BF5F-3DEF-9F3A-AFE4205CD53E]@0xffffff801f50d000->0xffffff801f68bfff
dependency: com.apple.driver.AppleEFINVRAM(2.1)[6E6AB947-75F7-344F-97FE-F1A9A803D2F2]@0xffffff801d7b2000->0xffffff801d7bbfff
dependency: com.apple.driver.AppleEffaceableStorage(1.0)[DCCE5AA9-462A-34BB-A905-A4CEB8DF45E2]@0xffffff801d7c8000->0xffffff801d7cdfff
dependency: com.apple.iokit.CoreAnalyticsFamily(1)[0BBEF1B6-3879-3835-9993-30FB5B22F3A7]@0xffffff801dcd4000->0xffffff801dcdbfff
dependency: com.apple.iokit.IOStorageFamily(2.1)[63189A2A-E19C-3F1E-96EF-95B7DB154785]@0xffffff801ef7c000->0xffffff801ef92fff
dependency: com.apple.kec.corecrypto(12.0)[5C997179-2E95-341F-A88B-07977BCCB606]@0xffffff801f6c5000->0xffffff801f745fff
dependency: com.apple.security.AppleImage4(4.2.0)[8E7BE283-81FC-3565-A114-F692370A8969]@0xffffff801d84f000->0xffffff801d867fff

Process name corresponding to current thread (0xffffff8b978c6540): kernel_task
Boot args: -no_compat_check agdpmod=pikera chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
21G920

Kernel version:
Darwin Kernel Version 21.6.0: Wed Oct 4 23:55:28 PDT 2023; root:xnu-8020.240.18.704.15~1/RELEASE_X86_64
Kernel UUID: CA525A92-20FF-38D2-AB16-E64095531D5A
KernelCache slide: 0x000000001c000000
KernelCache base: 0xffffff801c200000
Kernel slide: 0x000000001c010000
Kernel text base: 0xffffff801c210000
__HIB text base: 0xffffff801c100000
System model name: MacPro5,1 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 1737227425487
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000027d4f77f0bf
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x0000001f991c7436 0x0000000000000000
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
Zone map: 0xffffff805e728000 - 0xffffffa05e728000
. PGZ : 0xffffff805e728000 - 0xffffff8066729000
. VM : 0xffffff8066729000 - 0xffffff85320c2000
. RO : 0xffffff85320c2000 - 0xffffff86cb3f5000
. GEN0 : 0xffffff86cb3f5000 - 0xffffff8b96d8e000
. GEN1 : 0xffffff8b96d8e000 - 0xffffff9062727000
. GEN2 : 0xffffff9062727000 - 0xffffff952e0c0000
. GEN3 : 0xffffff952e0c0000 - 0xffffff99f9a5a000
. DATA : 0xffffff99f9a5a000 - 0xffffffa05e728000
Metadata: 0xffffffcb74a7b000 - 0xffffffcb94a7b000
Bitmaps : 0xffffffcb94a7b000 - 0xffffffcbaca7b000

 

[sfalatko]

@cdf I believe something has changed in 12.7.1 - Clean installation or reinstallation with hybridization enabled is not possible as the firmware update prompt keeps popping up with no way to bypass except with VMM flag enabled.

I only noticed this after successfully updating from 12.7 to 12.7.1 with hybridization enabled but after shutting down the mac, I was not able to boot into macOS as I kept getting a kernel panic after entering the password (something about a Global pointer being null or something).

Can you confirm this?

Forgot to add - I never had any issue installing, reinstalling or updating with hybridization enabled with releases up to 12.7

My update to 12.7.1 went fine with hybridization. Are you saying you couldn't OTA update with hybridization or that you couldn't reinstall with hybridization?

 

[w1z]

Are you saying you couldn't OTA update with hybridization or that you couldn't reinstall with hybridization?

I couldn't reinstall via recovery or clean install 12.7.1 using a bootable installer with hybridization. I also had no issues updating from 12.7 to 12.7.1 with hybridization. I rarely shutdown the mac and hadn't since updating (use sleep mode mostly) so I didn't notice the kernel panic until yesterday.

I'm going to try installing 12.7 with the same opencore setup/config (hybridization) and will confirm shortly.

 

[w1z]

Yeah, something definitely changed in 12.7.1 as 12.7 installed correctly with hybridization enabled (using the same opencore setup/config).

Perhaps it's related to one of the many CVE patches it addresses.

Another thing that stopped working with 12.7.1 is volume personalization (doesn't return "personalization succeeded"). Works fine under 12.7

 

[joevt]

Actually used 3 different docks - a double one that is powered and standard Macpro USB connector (front) - tried hot power up and again on at startup. On at startup causes reboot loop same as when ssd was in bay 1, hot plug in and power up, or plug in while powered up would immediately kill video and then mac would restart. Next tried USB3 (mini adapater - like a little tray) bus powered and connect via USB3 sonnet card. Same thing exactly. Then tried another bus powered but USB2 adapter and exactly same result. Plugged USB 2 and 3 adapters into macbook 2017 and mac mini 2010 (hot) and killed video same way and made them reboot. This drive had Monetrey 12.7.1 system but not the OC EFI.

I did all that because I was hoping to see it in DiskUtil and erase/reformat it and try and recover the drive somehow. But no such luck.

Spoiler: kernel panic report from plugging in ssd "mac killer"

panic(cpu 6 caller 0xffffff801f5caf19): "kind == NEW && refcnt = -1\n" @jobj.c:4068

I think the kernel panic would be easier to read if boot-args contains keepsyms=1

Since the drive causes a kernel panic in macOS, I would try connecting it in Windows or Linux and repartition it there. Then you can connect it to macOS and repartition it again so that it contains an Apple sized EFI partition. Another option is an older version of macOS that doesn't support APFS or whatever type of partition (encryption?) is causing the panic.

You could run the other OS in a virtual machine if the virtual machine has an option to let you select whether the VM or the macOS should handle a newly connected USB device.

 

[cdf]

@cdf I believe something has changed in 12.7.1 - Clean installation or reinstallation with hybridization enabled is not possible as the firmware update prompt keeps popping up with no way to bypass except with VMM flag enabled.

I only noticed this after successfully updating from 12.7 to 12.7.1 with hybridization enabled but after shutting down the mac, I was not able to boot into macOS as I kept getting a kernel panic after entering the password (something about a Global pointer being null or something).

Can you confirm this?

Forgot to add - I never had any issue installing, reinstalling or updating with hybridization enabled with releases up to 12.7

I just did a clean install of macOS 12.7.1 with hybridization (method 2 in the guide), and I cannot confirm what you are experiencing. Everything went fine.

If you want post your config and I’ll take look.

 

[w1z]

I just did a clean install of macOS 12.7.1 with hybridization (method 2 in the guide), and I cannot confirm what you are experiencing. Everything went fine.

If you want post your config and I’ll take look.

Hmm.. I also attempted method 2 in the guide as fallback after a full wipe and was always greeted with the EFI firmware updater page after the first reboot. What's strange is that the same opencore config, which I've attached, works fine for 12.7 but not 12.7.1 ... same goes for volume personalization when enabling SecureBootModel (Default or j160 with ApECID set) ... no amount of blessing would succeed under 12.7.1

Thanks for having a look.

Forgot to mention - using latest OC and kexts.

 

[cdf]

@w1z your config looks good. Some notes:

• "run-efi-updater" is deprecated since Big Sur
• Try disabling nonessential kexts (FeatureUnlock, RadeonSensor and perhaps NVMeFix)
• For volume personalization, make sure to have internet in Recovery mode (personalization succeeded in my case with macOS 12.7.1)

 

[w1z]

@w1z your config looks good. Some notes:

• "run-efi-updater" is deprecated since Big Sur
• Try disabling nonessential kexts (FeatureUnlock, RadeonSensor and perhaps NVMeFix)
• For volume personalization, make sure to have internet in Recovery mode (personalization succeeded in my case with macOS 12.7.1)

I'll remove run-efi-updater and disable some kexts over the weekend and retest again. The mac had internet and was connected so that's probably not it. Good to know though.

Thanks again.

 

[PeterHolbrook]

I just did a clean install of macOS 12.7.1 with hybridization (method 2 in the guide), and I cannot confirm what you are experiencing. Everything went fine.

Same here. I updated the day 12.7.1 was released. No issues.

 

[resonate]

MrScratchHook:, I got some down time and I'm ready to move from Mojave to perhaps Big Sur or Ventura. it appears I have the same 5,1 as you do. May I ask what OS you running with Pro Tools?

I'm currently running 2023.6, can't upgrade to the newest PT version on Mojave. THANKS

Go to Monterey with Opencore (Martin Lo package) , it's stable and good for PT. As for Mojave, you can run 2023.9 as long as you remove the Pro Tools Sketch plugin from the application bundle. (Show contents/Plugins/System Plug-Ins)

 

[MacNB2]

I just did a clean install of macOS 12.7.1 with hybridization (method 2 in the guide), and I cannot confirm what you are experiencing. Everything went fine.

If you want post your config and I’ll take look.

I have Option 2 configured (Hybridisation of board-id) and was offered:

Clicked on More Info... and was offered incremental update of 12.7.1 :



Installed without any issues.

 

[basslik]

Please forgive me,

I downloaded martin's package 9.5 and it's missing the Clover configurator.

Needing Monterey. Am I do something wrong ?

A couple of years ago I just followed his video, but missing Clover ?

 

[h9826790]

Please forgive me,

I downloaded martin's package 9.5 and it's missing the Clover configurator.

Needing Monterey. Am I do something wrong ?

A couple of years ago I just followed his video, but missing Clover ?

View attachment 2305330

Clover configurator is removed, and you can now use Mount EFI Partition (by Macschrauber) to mount the EFI partition

 

[polanskiman]

Please forgive me,

I downloaded martin's package 9.5 and it's missing the Clover configurator.

Needing Monterey. Am I do something wrong ?

A couple of years ago I just followed his video, but missing Clover ?

View attachment 2305330

As stated in the Readme.txt file in the OC v0.9.5 package:

 

[basslik]

Okay I GOT the drive blessed, WOW. I made it seem harder that it was.

shows Sonoma for update. I need Monterey, went to advance and didn't see an option. Apple store?

 

[kkinto]

shows Sonoma for update. I need Monterey, went to advance and didn't see an option. Apple store?

You need to read Martin's instructions for updating OS - temp change to the CPUID and UpdateSMBIOS entries in the config file. Then after reboot you should see Monterey under the "other updates" twirler if you don't see it now. Change back when done and reboot again.

 

[polanskiman]

Okay I GOT the drive blessed, WOW. I made it seem harder that it was.

shows Sonoma for update. I need Monterey, went to advance and didn't see an option. Apple store?

One way of downloading macOS installers is through OCLP. Download their app and through it you'll be able to download Sonoma, Monterey, Big Sure. Be sure you edit the config.plist as prescribed by Martin before launching the macOS Monterey installer though, and reverting those edits after Monterey and other macOS updates have been installed.

 

[borgo1971]

Hi. I'm using my MacPro 5,1 with latest BigSur build, but I want to go back to macOS 11.7.7, because some older software didn't work well with latests BigSur and I'm pretty sure it worked well until macOS 11.7.7. So I created a new APFS container on my main drive (nvme Samsung 970EVO plus) and tried to boot from USB stick with macOS 11.7.7. installer, but it didn't appear in OpenCore boot picker. The stick is surly bootable because it appears in Apple boot picker holding option key, but unsurprising, if selected there, prohibition signal appears on the screen. I tried even to insert the stick before powering up the Mac, or insert it only after OpenCore boot picker appears... I tried to modify OC config disabling SecureBootModel and enabling AppleBootPolicy, but it seems irrelevant. What other can I try? Is there a command/key to force OpenCore boot picker to rescan boot device (or scan USB ports)?
P.S. As this older software are the main reason I didn't upgrade to Monterey (where they didn't work at all), I thought to hold a container with BigSur 11.7.7 and this softwares, and when I'm sure I got a "working backup", upgrade my main container to Monterey... which build do you suggest? Reading the last posts, seems 12.7.1 has some troubles on our MacPro's...

 

[JMP]

I am using a Mac Pro 5,1 with a XFX ATI 580 8GB. As per the instructions from the OP, I went through the procedure and flash the firmware (ROM). RomTool completed with "...was completed successfully". However, still no boot screen.
Should I run this again? What is the solution?
Has that happened to anyone?

Thanks

 

[h9826790]

I am using a Mac Pro 5,1 with a XFX ATI 580 8GB. As per the instructions from the OP, I went through the procedure and flash the firmware (ROM). RomTool completed with "...was completed successfully". However, still no boot screen.
Should I run this again? What is the solution?
Has that happened to anyone?

Thanks

You may first use Macschrauber's ROM dump tool to check if EnableGOP is correctly flashed into the cMP.

If yes, then the XFX card is known to have firmware compatible issue on the 5,1. You may need to flash the graphic card as well in order to have a working GOP.