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

[205Maxi]

Try the test version 😉
View attachment 931060

Well thank you very very much I screwed up tonight, when I system is back up and running I'll give this a shot, also is it open core very. 0.6 DBG? Thank you again.. Love the plist file I do not know if I can use it on the MacPro but hey thanks a bunch again ...

 

[205Maxi]

Try the test version 😉
View attachment 931060

Tried that on a fresh system installation, the driver folder misses the openruntime tough. I do not know if I am just copying the BOOT.efi and the Opencore.efi but system during the fresh install boot with and on the second half of the install it shuts down, and loop.

We are close to get 0.6 working.. Or I am missing something.

 

[sonbai]

Fantastic thread, thank you so much for this. I now have a boot screen and hardware acceleration on my old 2 x 2.4Ghz, RX560 Mac Pro. Managed to make it boot automatically into Catalina too.

Only slight annoyance left is that it signifies my processor as a Core i3 and not a Xeon, on About This Mac. The weird thing is that Cpuid1Data is AAAAAAAAAAAAAACAAAAAAA== and Cpuid1Mask is AAAAAAAAAAAAAAAAAAAAAA== so in theory Cpuid1Mask is already off. What should I do to have it show it's a Xeon?

 

[h9826790]

Fantastic thread, thank you so much for this. I now have a boot screen and hardware acceleration on my old 2 x 2.4Ghz, RX560 Mac Pro. Managed to make it boot automatically into Catalina too.

Only slight annoyance left is that it signifies my processor as a Core i3 and not a Xeon, on About This Mac. The weird thing is that Cpuid1Data is AAAAAAAAAAAAAACAAAAAAA== and Cpuid1Mask is AAAAAAAAAAAAAAAAAAAAAA== so in theory Cpuid1Mask is already off. What should I do to have it show it's a Xeon?

Study the OpenCore document, look for

<key>ProcessorType</key>

 

[sonbai]

Study the OpenCore document, look for

<key>ProcessorType</key>

Thank you. This is all way over my head, but as far as i understand, i have to override ProcessorType manually... But i can't make out how to do it. I thought about changing the Processors.strings file in Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/Resources/en.lproj under <key>Quad-Core Intel Core i3</key> and changing the string line into <string>Quad-Core Intel Xeon</string> but not sure about this. Am i off? Any help super appreciated. Thanks again!

 

[h9826790]

Thank you. This is all way over my head, but as far as i understand, i have to override ProcessorType manually... But i can't make out how to do it. I thought about changing the Processors.strings file in Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/Resources/en.lproj under <key>Quad-Core Intel Core i3</key> and changing the string line into <string>Quad-Core Intel Xeon</string> but not sure about this. Am i off? Any help super appreciated. Thanks again!

You can, but no need to touch that system file. Unless you want to show the exact CPU model like this

Otherwise, all you need is just set the processor type in OpenCore as per the table here.

OpenCorePkg/Include/Apple/IndustryStandard/AppleSmBios.h at master · acidanthera/OpenCorePkg

OpenCore bootloader. Contribute to acidanthera/OpenCorePkg development by creating an account on GitHub.

github.com

 

[jackluke]

Study the OpenCore document, look for

<key>ProcessorType</key>

Spoofing a different "ProcessorType" on opencore config.plist, changes also its ACPI Tables or DSDT settings ?

 

[sonbai]

You can, but no need to touch that system file. Unless you want to show the exact CPU model like this
View attachment 931122

Otherwise, all you need is just set the processor type in OpenCore as per the table here.

OpenCorePkg/Include/Apple/IndustryStandard/AppleSmBios.h at master · acidanthera/OpenCorePkg

OpenCore bootloader. Contribute to acidanthera/OpenCorePkg development by creating an account on GitHub.

github.com

Right, so I typed 0x0501 on Clover > Cpu > Cpu type, saved the new plist file and copied it into the EFI drive, overwriting the old plist file, rebooted and... Black screen. It chimes but the video output is black. Restored the SSD to a SuperDuper backup I did yesterday but it keeps not working... Is it possible that there's something wrong with my GPU?

 

[cdf]

Right, so I typed 0x0501 on Clover > Cpu > Cpu type, saved the new plist file and copied it into the EFI drive, overwriting the old plist file, rebooted and... Black screen.

You should not be using Clover on the Mac Pro. Remove the contents of your EFI partition (they're still there even if you restored your disk), reset the NVRAM, boot natively (in Mojave or earlier), and reinstall OpenCore.

 

[startergo]

Small terminal command to download and build latest Lilu and dependent kexts:

Spoiler: Kexts

GitHub - acidanthera/Lilu: Arbitrary kext and process patching on macOS

Arbitrary kext and process patching on macOS. Contribute to acidanthera/Lilu development by creating an account on GitHub.

github.com

GitHub - acidanthera/WhateverGreen: Various patches necessary for certain ATI/AMD/Intel/Nvidia GPUs

Various patches necessary for certain ATI/AMD/Intel/Nvidia GPUs - acidanthera/WhateverGreen

github.com

GitHub - acidanthera/IOJones: Realtime I/O Registry viewer

Realtime I/O Registry viewer. Contribute to acidanthera/IOJones development by creating an account on GitHub.

github.com

GitHub - PMheart/LiluFriend: A helper of Lilu that ensures everything loaded properly

A helper of Lilu that ensures everything loaded properly - PMheart/LiluFriend

github.com

GitHub - acidanthera/HibernationFixup: A Lilu plugin intended to fix hibernation compatibility issues

A Lilu plugin intended to fix hibernation compatibility issues - acidanthera/HibernationFixup

github.com

GitHub - cdf/Innie: Make PCIe drives appear internal

Make PCIe drives appear internal. Contribute to cdf/Innie development by creating an account on GitHub.

github.com

GitHub - cdf/NightShiftEnabler: Enable Night Shift on unsupported Mac models

Enable Night Shift on unsupported Mac models. Contribute to cdf/NightShiftEnabler development by creating an account on GitHub.

github.com

GitHub - acidanthera/CpuTscSync: It is a Lilu plugin, combining functionality of VoodooTSCSync and disabling xcpm_urgency if TSC is not in sync. It should solve kernel panics after wake.

It is a Lilu plugin, combining functionality of VoodooTSCSync and disabling xcpm_urgency if TSC is not in sync. It should solve kernel panics after wake. - acidanthera/CpuTscSync

github.com

acidanthera/DebugEnhancer

A Lilu plugin intended to enable debug output in the macOS kernel - acidanthera/DebugEnhancer

github.com

 

[sonbai]

You should not be using Clover on the Mac Pro. Remove the contents of your EFI partition (they're still there even if you restored your disk), reset the NVRAM, boot natively (in Mojave or earlier), and reinstall OpenCore.

Up until this morning it worked fine, and I’d be alright if I could just restore it to that state and then make the changes. Can I wipe that ssd clean with my MacBook Pro and restore it with a time machine backup (Or even an older SuperDuper backup) of the Mac Pro? I’m afraid it won’t let me restore a dosdude Catalina on a MacBook Pro.
Alternatively do I still have to erase the ssd fully?

 

[h9826790]

Right, so I typed 0x0501 on Clover > Cpu > Cpu type, saved the new plist file and copied it into the EFI drive, overwriting the old plist file, rebooted and... Black screen. It chimes but the video output is black. Restored the SSD to a SuperDuper backup I did yesterday but it keeps not working... Is it possible that there's something wrong with my GPU?

You make it too complicated, all you need is just this in the PlatformInfo section. You better simply use a Text Editor to do that.

    <key>PlatformInfo</key>
    <dict>
        <key>Automatic</key>
        <false/>
        <key>SMBIOS</key>
        <dict>
            <key>BoardProduct</key>
            <string>Mac-7BA5B2D9E42DDD94</string>
            <key>ProcessorType</key>
            <integer>1281</integer>
        </dict>
        <key>UpdateDataHub</key>
        <false/>
        <key>UpdateNVRAM</key>
        <false/>
        <key>UpdateSMBIOS</key>
        <true/>
        <key>UpdateSMBIOSMode</key>
        <string>Create</string>
    </dict>

N.B. my example above assume the config also activate HWAccel. If not, please ignore the

<key>BoardProduct</key>
<string>Mac-7BA5B2D9E42DDD94</string>

[automerge]1594047918[/automerge]

Spoofing a different "ProcessorType" on opencore config.plist, changes also its ACPI Tables or DSDT settings ?

No need to touch ACPI or DSST for cMP.

 

[sonbai]

You make it too complicated, all you need is just this in the PlatformInfo section. You better simply use a Text Editor to do that.

    <key>PlatformInfo</key>
    <dict>
        <key>Automatic</key>
        <false/>
        <key>SMBIOS</key>
        <dict>
            <key>BoardProduct</key>
            <string>Mac-7BA5B2D9E42DDD94</string>
            <key>ProcessorType</key>
            <integer>1281</integer>
        </dict>
        <key>UpdateDataHub</key>
        <false/>
        <key>UpdateNVRAM</key>
        <false/>
        <key>UpdateSMBIOS</key>
        <true/>
        <key>UpdateSMBIOSMode</key>
        <string>Create</string>
    </dict>

N.B. my example above assume the config also activate HWAccel. If not, please ignore the

<key>BoardProduct</key>
<string>Mac-7BA5B2D9E42DDD94</string>

[automerge]1594047918[/automerge]

No need to touch ACPI or DSST for cMP.

Are you referring to the .plist file? So should I just have something like <integer>0501</integer>, which is my processor identifier? I'm currently restoring the ssd to a SuperDuper backup I did yesterday, hoping I'll be able to boot and make that change.

 

[cdf]

Up until this morning it worked fine, and I’d be alright if I could just restore it to that state and then make the changes. Can I wipe that ssd clean with my MacBook Pro and restore it with a time machine backup (Or even an older SuperDuper backup) of the Mac Pro? I’m afraid it won’t let me restore a dosdude Catalina on a MacBook Pro.
Alternatively do I still have to erase the ssd fully?

Just use your MacBook to access the EFI partition of your SSD. You can then just replace the contents of the EFI partition. Backup and restore operations usually do not touch the EFI, and that's where your problem is.

 

[h9826790]

Are you referring to the .plist file? So should I just have something like <integer>0501</integer>, which is my processor identifier? I'm currently restoring the ssd to a SuperDuper backup I did yesterday, hoping I'll be able to boot and make that change.

Yes, just open the OpenCore config.plist file by any text editor, search PlatformInfo, and manually enter the processor type at the correct section like this

N.B. You must also turn on UpdateSMBIOS for it to work (as per the code in my previous post, or in the screen capture above)

1281 is the correct parameter for your Xeon

 

[6DecadesLater]

As @cdf mentioned, this is something related to your PCIe connection. See my request for reboot options to manage this which was then added to v0.5.8: https://github.com/acidanthera/bugtracker/issues/861#issuecomment-616344925

FWIW, I seem to have stopped having the issue after running the maintenance tasks in Onyx:
View attachment 930171

I tried several of the suggestions (including Onyx) but still had issues so I went back to first principles and reinstalled OC and redid config.plist edits. I didn't reinstall Catalina but just redid OC in the EFI. It seems to be working now. It has trouble restarting - closes all apps but doesn't power cycle. Going to run Onyx again.

Thanks for the posts.
[automerge]1594059299[/automerge]

A huge thank you to those who set up Opencore.

Yesterday, I finally took the plunge and tried the installation (basic) and it worked first time. Brilliant!
The instructions seemed a bit scary, but in retrospect they're only a few steps.
Wifi has gone (I'm guessing it's the issue with the old Broadcom airport card, but that's not a serious problem: I can either get an updated card, or connect to the network box with a cable).

During boot there are some momentary (?1 second) curious thin horizontal stripes appearing on the top 1/3 of a blank light grey screen. I'll take a pic next time.

I'll probably drop back to 10.14 until I decide about the wifi. But in the meanwhile I have a working 10.15 ssd for my cmP 5,1 ! Thanks again.

I saw the small stripes too - just for a second. They went away when I added the hardware acceleration.

 

[sonbai]

Yes, just open the OpenCore config.plist file by any text editor, search PlatformInfo, and manually enter the processor type at the correct section like this
View attachment 931164
N.B. You must also turn on UpdateSMBIOS for it to work (as per the code in my previous post, or in the screen capture above)

1281 is the correct parameter for your Xeon
View attachment 931165

Thank you very much. I just tried to boot my Mac Pro without the ssd, just with the four hard drives I use for data, thinking it would at least display some error message or the option to reinstall the latest supported OS, but the screen stays black. And my MacBook Pro is on Catalina so it can't open the Mojave installer to create a bootable Mac Pro Mojave ssd. Really struggling here, could something be wrong with my GPU?

 

[h9826790]

Thank you very much. I just tried to boot my Mac Pro without the ssd, just with the four hard drives I use for data, thinking it would at least display some error message or the option to reinstall the latest supported OS, but the screen stays black. And my MacBook Pro is on Catalina so it can't open the Mojave installer to create a bootable Mac Pro Mojave ssd. Really struggling here, could something be wrong with my GPU?

Why remove your boot drive?

That of course will cause the cMP can't boot.

And since you screwed up OpenCore, the GOP boot screen won't work as well. Black screen is expected.

I believe the easiest way is just plug the Mojave drive back in. Hold Command + R to boot to recovery, then fix OpenCore at there (if it's too hard for you to fix OpenCore in Recovery partition, you can simply remove it, then boot to Mojave, and re-install OpenCore again).

Why you need to run Mojave installer? You killed your current Mojave? I think you just screwed up OpenCore config.plist. You can plug that drive into the MBP, mount the EFI partition, remove / fix OpenCore on your MBP (if you don't know how to boot your cMP now).

You can also make a Linux LiveCD / LiveUSB on the MBP, then boot it on your cMP, and fix your OpenCore drive.

There should be lots of ways to fix it. You can even boot your cMP in target disk mode, and let your MBP fix the OpenCore drive installed on cMP.

 

[Perana]

I have run across another problem, boot screen all working fine now, installed Windows 10 OK, but cannot boot to desktop in Windows 10, seems to be an issue with the graphics driver, I can get in with Safe mode OK, I removed the device and deleted the driver so it would boot using the basic display driver, which worked, until windows automatically installed a new driver. GPU is a 7950, was working fine on my previous install prior to Open Core.

 

[overshoot]

Random question.

I have a "official" 5,1 with an NVME loaded with Mojave as my main drive. I then have Mojave in Bay 1, High Sierra in Bay 2, and Windows 10 (Legacy) in Bay 3. I made a Opencore USB bootloader (using @h9826790 package) and followed all the directions and reset SMC as well. It loaded the OC picker perfectly. When I select the NVME drive, I see the Apple boot logo and then it just hangs. If I select the Mojave SSD, it boots up perfectly. Any insight would be greatly appreciated. Planning on upgrading to Catalina but want to try it out on the SSD before I update with the NVME.

I have the exact same issue.

Is there a workaround for that or OC can't load macOS yet from an NVME?

 

[h9826790]

I have run across another problem, boot screen all working fine now, installed Windows 10 OK, but cannot boot to desktop in Windows 10, seems to be an issue with the graphics driver, I can get in with Safe mode OK, I removed the device and deleted the driver so it would boot using the basic display driver, which worked, until windows automatically installed a new driver. GPU is a 7950, was working fine on my previous install prior to Open Core.

The Mac EFI UGA on the HD7950 doesn’t work well in EFI Windows.

It can work in some cases, not 100% sure what’s the exact criteria. But in most cases, it will cause BOSD.

 

[lxmeta]

I have the exact same issue.

Is there a workaround for that or OC can't load macOS yet from an NVME?

Not sure what you mean.
I have a macPro 5.1 with a NVME blade in there.
No issue at all with Mojave, Catalina or Big Sur and OC from 5.6 to 5.9. OC is installed on the NVME blade, and can load all types of OS from the Blade as well as from other disks.

 

[overshoot]

Not sure what you mean.
I have a macPro 5.1 with a NVME blade in there.
No issue at all with Mojave, Catalina or Big Sur and OC from 5.6 to 5.9. OC is installed on the NVME blade, and can load all types of OS from the Blade as well as from other disks.

I did copy my system using CCC (Carbon Copy Cloner) and tried to boot it up.
It loaded and then crashed just before loading the Desktop.

I'll try a fresh install on it instead.

Thanks for your feedback.

 

[Perana]

The Mac EFI UGA on the HD7950 doesn’t work well in EFI Windows.

It can work in some cases, not 100% sure what’s the exact criteria. But in most cases, it will cause BOSD.

Thanks again!

Of course the stock ROM doesn't include GOP for my card, luckily adding GOP to the original ROM for the 7950 worked and all appears well now, so boot screen works, Catalina works and Windows 10 works finally!

 

[HuRR]

I have the exact same issue.

Is there a workaround for that or OC can't load macOS yet from an NVME?

I actually got this resolved. I ended up just using a base config.plist file instead of @h9826790's (not that it was the .plist file that was the issue! Thanks btw) and making any edits I wanted to use on OpenCore. Everything worked perfectly! But then I wanted to enable NightShift and followed the directions on the first page. I had the same exact problem as before. My Mojave SSD would boot but not the NVME. I mounted the EFI and deleted the NightShiftEnabler.kext. I remembered that I had installed Lilu, WhateverGreen, and AppleALC on my NVME previously. OpenCore was injecting those kexts and Catalina was also loading them as well. I made sure to delete those kexts from my Cataline NVME, grab the latest, and stick them into EFI partition. Boom. Everything worked!

Double check and see if you have the same problem.

Speaking of kexts, what's the best way to get HDMI/DP Audio? Do I inject the kext using OpenCore using AppleALC?

EDIT: OpenCore is on my SSD not on my NVME. I don't believe installing OpenCore on an NVME is recommended.