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

[Grumply]

Hi everyone,

After some considerable pain and faffing about last night. I did eventually succeed in getting Catalina up and going on 0.6.1

And I currently have Bootpicker giving me access to a working copy Catalina, a 10.15.6 Recovery Partition, my Windows drive and a 10.14.6 Recovery Partition. There's also a "ghost" icon for OSX (which I'm assuming is the ghost of Mojave?).

I'm wondering if there's a way to strip out the ghost volume of Mojave and the Mojave Recovery Partition from the bookpicker?

When I go into disk utility, I am seeing this curious situation, where there's the correct number of volumes listed on the left, but in the top corner it says my Catalina drive is "SHARED BY 5 VOLUMES":

Is that what's causing the "ghost" volumes to show up in the Boot Picker? And if so, how do I ghost bust them?

When I ask Terminal to list the volumes, this is what I get (what's actually plugged into the machine are two 1tb SATA SSDs, one for Catalina, one for Windows):

 

[startergo]

Hi everyone,

After some considerable pain and faffing about last night. I did eventually succeed in getting Catalina up and going on 0.6.1

And I currently have Bootpicker giving me access to a working copy Catalina, a 10.15.6 Recovery Partition, my Windows drive and a 10.14.6 Recovery Partition. There's also a "ghost" icon for OSX (which I'm assuming is the ghost of Mojave?).

View attachment 956075

I'm wondering if there's a way to strip out the ghost volume of Mojave and the Mojave Recovery Partition from the bookpicker?

When I go into disk utility, I am seeing this curious situation, where there's the correct number of volumes listed on the left, but in the top corner it says my Catalina drive is "SHARED BY 5 VOLUMES":

View attachment 956076

Is that what's causing the "ghost" volumes to show up in the Boot Picker? And if so, how do I ghost bust them?

When I ask Terminal to list the volumes, this is what I get (what's actually plugged into the machine are two 1tb SATA SSDs, one for Catalina, one for Windows):

View attachment 956079

Why don't you enable all devices in disk utility? It looks like disk1s2 is not mounted for some reason.

 

[roobarb!]

Enthusiasm returned and I manually updated my config file to match 0.6.1's requirements. No beans. Wouldn't boot, just fell back to the simple boot picker in the same way the config file from post 1 does for me. Only thing that worked was my chain-boot to Windows through rEFInd.

Checked the plist file differences back to 0.5.8 and didn't see anything that would make the older version too unhappy with a newer plist file, so swapped out the guts of OpenCore and rebooted. Boots fine, acceleration working. Also fixes Catalina not updating for me with 0.5.6, so I guess I’m happy.

I also now remember that I am not booting the OS from NVME (I said it had been a while). I'm using the internal bays for Mojave and Catalina while having all my user areas on NVME.

Attached is my current config.plist which works fine on 0.5.8 and not on 0.6.1. I'll trace what's changed another day, too late now. Clues appreciated.

 

[h9826790]

This is like making a Hackintosh out of Mac Pro, am I right?

Quite different fundamentally.

Mac Pro 5,1 can boot any macOS without boot loader. We just make the process easier and more native (for those non supported macOS). Or use OpenCore to activate some missing functions.

 

[texem]

Does anyone have success with MacPro 4,1-5,1 and OpenCore with macOS Big Sur and have working firewire? I have it working in macOS Catalina however Big Sur in system profile sees I have a firewire card but my audio device will only Lock and sync but not activate?

+1

Can please someone on a cMP 5,1 try this :
connect a Firewire (H)DV-CAM and import a video via iMovie and or FinalCutPro ?
No success here with latest beta of BigSur .. System-profiler shows the CAM connected to the FW-bus and thats all.

Worked with Catalina.

 

[Grumply]

Well after another full day of fiddling, I've had some success and now have Catalina up and running seamlessly, with bootpicker giving me just the options for:

- Catalina
- Recovery Partition
- Windows

Which is where I was with Mojave on 0.6.0, and where I wanted to be. I am noticing though with Catalina and 0.6.1 that my initial boot up into the bootpicker has become significantly slower. Before it was maybe 15-20 seconds, now it's closer to a minute before the bootpicker shows up (boot times once a partition has been selected appear to be normal).

Is this common? Or might something have gone awry?

 

[PeterHolbrook]

I know the tutorial on page 1 is very thorough, and I have no doubt that, if I were to install OpenCore 0.6.1 from scratch, using the model config.plist provided and adding to it one new parameter or set of parameters at a time (like OpenCanopy configurations), and checking that it works, I might eventually end up with an optimal setup, like the one I now have for 0.6.0. The problem is that such a process is quite time-consuming. I've tried twice already to adapt my current config.plist to the new parameters of 0.6.1, by comparing my config.plist and the model one provided on page 1, but both times ended up with an OpenCore Boot Picker loop. I've also tried using the "maintenance" script provided, but, perhaps because I'm not sure where to place it or where to run it from, I get errors such as these:

python tree.py
* OpenCore 0.6.1
- downloading component... <urlopen error [SSL: TLSV1_ALERT_PROTOCOL_VERSION] tlsv1 alert protocol version (_ssl.c:590)>
OK
- building files structure...
Traceback (most recent call last):
File "tree.py", line 150, in <module>
main(root_directory())
File "tree.py", line 13, in main
install_opencore('0.6.1', directory)
File "tree.py", line 91, in install_opencore
extract_files(file, directory)
File "tree.py", line 45, in extract_files
zipfile = ZipFile(BytesIO(response.read()))
UnboundLocalError: local variable 'response' referenced before assignment

Because of the above, I'm somewhat lost. Perhaps the OpenCanopy files I'm using are incompatible with OpenCore 0.6.1? Or there's something really absurd in my config.plist? Just in case someone with more experience (almost anyone, really) can have a look at the enclosed file and detect one or more stupid errors, will you give me the heads-up? Many thanks!

 

[Itconnects]

It boots but just without a boot screen - correct. Power up and hold Alt+Com+P+R and hang on through at least two boot chimes then let go.

same issue after PRAM reset. No boot screen

Sorry guys, it was my DP cable. I switched to HDMI and it’s now working.

 

[Grumply]

If it's of any use to anyone (and I suspect it is) here are the two 0.6.1 config files I needed to get my installation to work. The first is Martin's personal config but with his own recommended pre-install adjustments to get around the "drive requires firmware update required" roadblock, and the second is his post-install config (which you need to switch to once Catalina is up and running).

You'll want to bless these onto both your configuration drive, and the drive you're installing Catalina onto:

 

[Steve_Jones]

Is there an easy way to tell if Hardware Acceleration is enabled? I've downloaded VideoProc but Hardware Acceleration is greyed out and it's not detecting my video card.

My RX580 8 GB video card is at

/PCI0@0/IOU0@3/GFX0@0 = PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)

and I've edited my config.plist to:

<key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)</key>

Using kextstat, I can see Lilu and WhateverGreen loaded.

TIA.

 

[h9826790]

Is there an easy way to tell if Hardware Acceleration is enabled? I've downloaded VideoProc but Hardware Acceleration is greyed out and it's not detecting my video card.

My RX580 8 GB video card is at

/PCI0@0/IOU0@3/GFX0@0 = PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)

and I've edited my config.plist to:

<key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)</key>

Using kextstat, I can see Lilu and WhateverGreen loaded.

TIA.

Post #1 Q29 and Q27

Activate AMD hardware acceleration

[For existing OpenCore users, you can always download my latest OpenCore package at post #1314 for update] Full HWAccel achieved now! Everything is covered in the OpenCore thread. The step by step tutorial to enable AMD hardware acceleration is now at here, but I strongly recommend you go...

forums.macrumors.com

 

[startergo]

I know the tutorial on page 1 is very thorough, and I have no doubt that, if I were to install OpenCore 0.6.1 from scratch, using the model config.plist provided and adding to it one new parameter or set of parameters at a time (like OpenCanopy configurations), and checking that it works, I might eventually end up with an optimal setup, like the one I now have for 0.6.0. The problem is that such a process is quite time-consuming. I've tried twice already to adapt my current config.plist to the new parameters of 0.6.1, by comparing my config.plist and the model one provided on page 1, but both times ended up with an OpenCore Boot Picker loop. I've also tried using the "maintenance" script provided, but, perhaps because I'm not sure where to place it or where to run it from, I get errors such as these:

python tree.py
* OpenCore 0.6.1
- downloading component... <urlopen error [SSL: TLSV1_ALERT_PROTOCOL_VERSION] tlsv1 alert protocol version (_ssl.c:590)>
OK
- building files structure...
Traceback (most recent call last):
File "tree.py", line 150, in <module>
main(root_directory())
File "tree.py", line 13, in main
install_opencore('0.6.1', directory)
File "tree.py", line 91, in install_opencore
extract_files(file, directory)
File "tree.py", line 45, in extract_files
zipfile = ZipFile(BytesIO(response.read()))
UnboundLocalError: local variable 'response' referenced before assignment

Because of the above, I'm somewhat lost. Perhaps the OpenCanopy files I'm using are incompatible with OpenCore 0.6.1? Or there's something really absurd in my config.plist? Just in case someone with more experience (almost anyone, really) can have a look at the enclosed file and detect one or more stupid errors, will you give me the heads-up? Many thanks!

\OpenCore-0.6.1-RELEASE\Utilities\ocvalidate>ocvalidate.exe config.plist
OCS: No schema for New item at 5 index, context <Tools>!
OCS: Missing key ARTFrequency, context <DataHub>!
OCS: Missing key BoardProduct, context <DataHub>!
OCS: Missing key BoardRevision, context <DataHub>!
OCS: Missing key DevicePathsSupported, context <DataHub>!
OCS: Missing key FSBFrequency, context <DataHub>!
OCS: Missing key InitialTSC, context <DataHub>!
OCS: Missing key PlatformName, context <DataHub>!
OCS: Missing key SmcBranch, context <DataHub>!
OCS: Missing key SmcPlatform, context <DataHub>!
OCS: Missing key SmcRevision, context <DataHub>!
OCS: Missing key StartupPowerEvents, context <DataHub>!
OCS: Missing key SystemProductName, context <DataHub>!
OCS: Missing key SystemSerialNumber, context <DataHub>!
OCS: Missing key SystemUUID, context <DataHub>!
OCS: Missing key AdviseWindows, context <Generic>!
OCS: Missing key MLB, context <Generic>!
OCS: Missing key ROM, context <Generic>!
OCS: Missing key SpoofVendor, context <Generic>!
OCS: Missing key SystemProductName, context <Generic>!
OCS: Missing key SystemSerialNumber, context <Generic>!
OCS: Missing key SystemUUID, context <Generic>!
OCS: Missing key BID, context <PlatformNVRAM>!
OCS: Missing key FirmwareFeatures, context <PlatformNVRAM>!
OCS: Missing key FirmwareFeaturesMask, context <PlatformNVRAM>!
OCS: Missing key MLB, context <PlatformNVRAM>!
OCS: Missing key ROM, context <PlatformNVRAM>!
OCS: Missing key BIOSReleaseDate, context <SMBIOS>!
OCS: Missing key BIOSVendor, context <SMBIOS>!
OCS: Missing key BIOSVersion, context <SMBIOS>!
OCS: Missing key BoardAssetTag, context <SMBIOS>!
OCS: Missing key BoardLocationInChassis, context <SMBIOS>!
OCS: Missing key BoardManufacturer, context <SMBIOS>!
OCS: Missing key BoardSerialNumber, context <SMBIOS>!
OCS: Missing key BoardType, context <SMBIOS>!
OCS: Missing key BoardVersion, context <SMBIOS>!
OCS: Missing key ChassisAssetTag, context <SMBIOS>!
OCS: Missing key ChassisManufacturer, context <SMBIOS>!
OCS: Missing key ChassisSerialNumber, context <SMBIOS>!
OCS: Missing key ChassisType, context <SMBIOS>!
OCS: Missing key ChassisVersion, context <SMBIOS>!
OCS: Missing key FirmwareFeatures, context <SMBIOS>!
OCS: Missing key FirmwareFeaturesMask, context <SMBIOS>!
OCS: Missing key MemoryFormFactor, context <SMBIOS>!
OCS: Missing key PlatformFeature, context <SMBIOS>!
OCS: Missing key ProcessorType, context <SMBIOS>!
OCS: Missing key SmcVersion, context <SMBIOS>!
OCS: Missing key SystemFamily, context <SMBIOS>!
OCS: Missing key SystemManufacturer, context <SMBIOS>!
OCS: Missing key SystemProductName, context <SMBIOS>!
OCS: Missing key SystemSKUNumber, context <SMBIOS>!
OCS: Missing key SystemSerialNumber, context <SMBIOS>!
OCS: Missing key SystemUUID, context <SMBIOS>!
OCS: Missing key SystemVersion, context <SMBIOS>!
OCS: No schema for DirectGopCacheMode at 2 index, context <Output>!
Done checking config.plist in 146 ms

You can check your config file with the ocvalidate even in Windows from here:

Builds

OCS: No schema for DirectGopCacheMode at 2 index, context <Output>! is no longer a valid option.
OCS: No schema for New item at 5 index, context <Tools>! this code looks screwed up in your config:

 

[i.am.not.a.hipster]

I had the same issue (3) with catalina when i upgraded to 0.6.1. I didn't do it step by step - ie I didn't reboot every time it said to but did check the config with plutil. I had a backup of the 0.6.0 EFI so simply went back to that and it worked fine. I then redid the entire 0.6.1 update but rebooting at each step indicated. It worked the second time. While doing it the second time I felt I had made an error the first time. One possibility was when enabling nightshift I copied the lilu entry a second time. Possible too that the kexts were not properly all copied (I think). Suggest you redo step by step.
Also rerun the PCI path as I think the PCIRoot string indicates the slot number.

Thanks much -- your suggestion at the end about rerunning the PCI path script when swapping slots worked -- I can now place the devices in the slots I want -- just need to update the paths if referred to in config.plist like you thought.

I also tried redoing the OpenCore 0.61 installation step by step with a new installation of Catalina on Disk A per the guide on page 1 of this thread, but again, same thing happens -- OC boot picker menu keeps coming up....if the volume is selected, keeps dropping back to the OC boot picker menu. If left to time-out, it goes into a loop.

 

[Steve_Jones]

Post #1 Q29 and Q27

Activate AMD hardware acceleration

[For existing OpenCore users, you can always download my latest OpenCore package at post #1314 for update] Full HWAccel achieved now! Everything is covered in the OpenCore thread. The step by step tutorial to enable AMD hardware acceleration is now at here, but I strongly recommend you go...

forums.macrumors.com

Thanks.

Used the Refresh button on the Option page and now it shows Hardware Acceleration.

Great writeup BTW.

 

[PeterHolbrook]

\OpenCore-0.6.1-RELEASE\Utilities\ocvalidate>ocvalidate.exe config.plist
OCS: No schema for New item at 5 index, context <Tools>!
[...]
OCS: No schema for DirectGopCacheMode at 2 index, context <Output>!
Done checking config.plist in 146 ms

You can check your config file with the ocvalidate even in Windows from here:

Builds

OCS: No schema for DirectGopCacheMode at 2 index, context <Output>! is no longer a valid option.
OCS: No schema for New item at 5 index, context <Tools>! this code looks screwed up in your config:
View attachment 956343

Many thanks for the heads up. Actually, most of the ocvalidate warnings refer to options directly inherited from my currently working 0.6.0 setup, which one of the members of this forum was kind enough to provide. That also applies to the "New item" oddity you mention. I'll study that section in particular using known valid config.plists of others. I've already removed the invalid DirectGopChacheMode parameter.

 

[6DecadesLater]

Thanks much -- your suggestion at the end about rerunning the PCI path script when swapping slots worked -- I can now place the devices in the slots I want -- just need to update the paths if referred to in config.plist like you thought.

I also tried redoing the OpenCore 0.61 installation step by step with a new installation of Catalina on Disk A per the guide on page 1 of this thread, but again, same thing happens -- OC boot picker menu keeps coming up....if the volume is selected, keeps dropping back to the OC boot picker menu. If left to time-out, it goes into a loop.

Odd. Starting over from scratch on installing 0.6.1 (just the EFI setup, kexts and config edits, not the whole install of Catalina) got rid of the endless boot loop. Have you downloaded the latest versions of all kexts? When you did the reinstall, did it go into a loop on the first reboot? I did all the changes straight through to the end without booting at the various intervals the first time which is why I couldn't pinpoint any exact step I screwed up.

 

[6DecadesLater]

Well after another full day of fiddling, I've had some success and now have Catalina up and running seamlessly, with bootpicker giving me just the options for:

- Catalina
- Recovery Partition
- Windows

Which is where I was with Mojave on 0.6.0, and where I wanted to be. I am noticing though with Catalina and 0.6.1 that my initial boot up into the bootpicker has become significantly slower. Before it was maybe 15-20 seconds, now it's closer to a minute before the bootpicker shows up (boot times once a partition has been selected appear to be normal).

Is this common? Or might something have gone awry?

Blessing the EFI volume again sped up the bootpicker showing. Need to do that if you do a NVRAM reset.

 

[mrkapqa]

Am i right in assuming that if i could install OpenCore on a MacPro 2.1 (upgraded firmware) with a MacBranded 5870 Radeon the only advantage (but big one) would be that VideoProc or similar software would recognize the VideoCard correctly for Hardware Acceleration?

Would there be any downsides? I have seen someone mentioning no longer being able to boot into Bootcamp partition?

 

[6DecadesLater]

Do you know what is blacklisted related to MacPro 5,1 in Big Sur?

I may not understand your question but isn't everything? Big Sur is not officially supported at all on Mac Pro pre late 2013

 

[paulogilmour]

Hello everyone. I reinstalled Windows 10 following the exFat method described here. It worked perfect. Until after an update, for a reason I don't know, it no longer displays the opencore boot piker. I can't get into Catalina, unless I remove the hard drive that contains Windows. Looking at the Windows EFI partition, I noticed that the BOOT folder was created. I deleted it, but Windows still automatically booted. And I can't access Catalina.

 

[h9826790]

Am i right in assuming that if i could install OpenCore on a MacPro 2.1 (upgraded firmware) with a MacBranded 5870 Radeon the only advantage (but big one) would be that VideoProc or similar software would recognize the VideoCard correctly for Hardware Acceleration?

No, it won't. macOS provide zero HWAccel support for HD5000 series GPU. There is nothing to hactivate.

 

[xb12]

hi

With an unsupported processor Intel Xeon 3500,
I can boot screen, thanks, with an iMac i3 processor recognized I don't know if I have to.
No work, no $.

is there a way to have the bootscreen without all the other modifications ?

I have the Dosdude1 utility for legacy drivers.
Shoud I keep it running please ?

 

[xb12]

Is there an easy way to tell if Hardware Acceleration is enabled? I've downloaded VideoProc but Hardware Acceleration is greyed out and it's not detecting my video card.

My RX580 8 GB video card is at

/PCI0@0/IOU0@3/GFX0@0 = PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)

and I've edited my config.plist to:

<key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)</key>

Using kextstat, I can see Lilu and WhateverGreen loaded.

TIA.

Hi. Same append to me.
I checked post #1 and my processor version is unsupported.

 

[Ludacrisvp]

hi

With an unsupported processor Intel Xeon 3500,
I can boot screen, thanks, with an iMac i3 processor recognized I don't know if I have to.
No work, no $.

is there a way to have the bootscreen without all the other modifications ?

I have the Dosdude1 utility for legacy drivers.
Shoud I keep it running please ?

The display of the core i3 processor means nothing. It’s 100% cosmetic and fixable with opencore settings.

you could probably try using The copy of refind by @Dayo To boot with a boot screen.

 

[TECK]

I know the tutorial on page 1 is very thorough, and I have no doubt that, if I were to install OpenCore 0.6.1 from scratch, using the model config.plist provided and adding to it one new parameter or set of parameters at a time (like OpenCanopy configurations), and checking that it works, I might eventually end up with an optimal setup, like the one I now have for 0.6.0. The problem is that such a process is quite time-consuming. I've tried twice already to adapt my current config.plist to the new parameters of 0.6.1, by comparing my config.plist and the model one provided on page 1, but both times ended up with an OpenCore Boot Picker loop. I've also tried using the "maintenance" script provided, but, perhaps because I'm not sure where to place it or where to run it from, I get errors such as these:

python tree.py
* OpenCore 0.6.1
- downloading component... <urlopen error [SSL: TLSV1_ALERT_PROTOCOL_VERSION] tlsv1 alert protocol version (_ssl.c:590)>
OK
- building files structure...
Traceback (most recent call last):
File "tree.py", line 150, in <module>
main(root_directory())
File "tree.py", line 13, in main
install_opencore('0.6.1', directory)
File "tree.py", line 91, in install_opencore
extract_files(file, directory)
File "tree.py", line 45, in extract_files
zipfile = ZipFile(BytesIO(response.read()))
UnboundLocalError: local variable 'response' referenced before assignment

Because of the above, I'm somewhat lost. Perhaps the OpenCanopy files I'm using are incompatible with OpenCore 0.6.1? Or there's something really absurd in my config.plist? Just in case someone with more experience (almost anyone, really) can have a look at the enclosed file and detect one or more stupid errors, will you give me the heads-up? Many thanks!

I created the OC maintenance tool, open a terminal and run these commands:

git clone https://github.com/axivo/opencore.git
cd opencore
python tree.py

For your config, take a look at this example:

axivo/opencore

OpenCore components and preference list generator for Mac Pro 4,1 - 5,1 - axivo/opencore

github.com

If you have any questions, please start a separate thread and I will answer them all there, so we don't hijack this thread. Once you understand the functionality, you can simplify the upgrades by a lot. Also, if you think there are certain improvements to documentation, either ask into the new thread or create a repo issue.