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

[joevt]

On modern Macs, the background is "syrah black." For legacy Macs, it was "light gray." Both colors can be set in OC. However, because no Macs with the gray background are supported in Big Sur, the gray option may lead to unexpected results during the second-stage screen, like the apple turning white. Thus it is recommended to use black. It will also make the normal blackout period between the first and second screens less noticeable.

Black is not good for legacy Macs because then you can't see the labels of icons in the Startup Manager (if you are bypassing OC). Maybe OC should have a second background color variable which it can use when it loads.

 

[startergo]

Black is not good for legacy Macs because then you can't see the labels of icons in the Startup Manager (if you are bypassing OC). Maybe OC should have a second background color variable which it can use when it loads.

I enforce gray in OC.

 

[cdf]

Black is not good for legacy Macs because then you can't see the labels of icons in the Startup Manager (if you are bypassing OC). Maybe OC should have a second background color variable which it can use when it loads.

Right. But the settings only apply when booting through OpenCore (if applied to the sample config in the guide). Of course, there is also the matter of accessing the Apple boot picker through OC. However, with standard graphics cards, there are currently technical issues that prevent the Startup Manager from starting at all even with GOP working.

 

[joevt]

Right. But the settings only apply when booting through OpenCore (if applied to the sample config in the guide). Of course, there is also the matter of accessing the Apple boot picker through OC. However, with standard graphics cards, there are currently technical issues that prevent the Startup Manager from starting at all even with GOP working.

OpenCore modifies an NVRAM variable DefaultBackgroundColor which affects the Startup Manager even if OpenCore is not booted (as long as OpenCore is booted once to make the change). 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14 is an Apple UUID - not specific to OpenCore.

I guess the Startup Manager requires UGA so it won't work with GOP but OpenCore has UGAonGOP? So maybe there's other stuff that needs setup before it will work? I haven't tried it yet. I use a UGA graphics card with my MacPro3,1 so I have no problem with Startup Manager. I do have GOP cards to test.

 

[Dayo]

OpenCore modifies an NVRAM variable DefaultBackgroundColor which affects the Startup Manager even if OpenCore is not booted (as long as OpenCore is booted once to make the change). 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14 is an Apple UUID - not specific to OpenCore.

If you set the "WriteFlash" key to "false", NVRAM modification should be temporary (in RAM only) and only have effect when booting OpenCore but yes, persistent NVRAM modification can happen indeed (depending on config).

There is some chart explaining how WriteFlash impacts persistence of changes somewhere on the OpenCore Repo. Need to try to find this.

 

[Dayo]

This one: https://github.com/acidanthera/bugtracker/issues/1212#issuecomment-706561979

 

[Dayo]

@Bmju ... with the passage of time and your mucking about in OC code, is there really no way to have a situation where you have oc_value in the first column and os_value in the second on the above?

 

[cdf]

OpenCore modifies an NVRAM variable DefaultBackgroundColor which affects the Startup Manager even if OpenCore is not booted (as long as OpenCore is booted once to make the change). 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14 is an Apple UUID - not specific to OpenCore.

As I said "if applied to the sample config in the guide." See WriteFlash as @Dayo mentioned.

So maybe there's other stuff that needs setup before it will work?

Correct. Although UgaPassThrough is not enough (on the Mac Pro 5,1), perhaps loading UGAonGOP.efi explicitly would work.

 

[startergo]

As I said "if applied to the sample config in the guide." See WriteFlash as @Dayo mentioned.


Correct. Although UgaPassThrough is not enough (on the Mac Pro 5,1), perhaps loading UGAonGOP.efi explicitly would work.

UGAonGOP.efi does not help.

 

[woefi]

So I booted BigSur (already installed, known-good Installation) on my MacPro5,1 using OpenCore Legacy Patcher (OCLP) and since version 0.0.21 all went fine.

The problem I have is my Geekbench metal score is only half as usual (Sapphire Pulse RX580).

My Hackintosh has the same card and reaches about 51000 (metal)
My MacPro in Mojave has always only had 46000 (metal)
And now with BigSur and OCLP I get mere 26000 (metal)

I read there was a kext called RadeonBoost, but as I understand this should only give me the difference between the 46000 and 51000 back, right?

So there has to be some other problem. Any Ideas, how I can check my acceleration status? VDADecoderchecker says all is fine.

 

[hutzi20]

The problem I have is my Geekbench metal score is only half as usual (Sapphire Pulse RX580).

Put your Mac into sleep mode. After wake it up again you should see a doubled performance in your geekbench results.

 

[woefi]

Put your Mac into sleep mode.

Thanks, I read that some time ago and yes it works, but I was hoping there was already a solution.

Also: does the macpro really max out at 46000 with this card (maybe because of pcie2.0?)

 

[chrisrm9208]

Apologies for asking something obvious but I've not found this in this thread; is there any way to hide the various 'Update' volumes from Finder, something within config.plist?

 

[Stex]

Thanks, I read that some time ago and yes it works, but I was hoping there was already a solution.

Also: does the macpro really max out at 46000 with this card (maybe because of pcie2.0?)

I have the same GPU and experience a similar issue. I found out that I get about 60% GB5 metal compute results (approx 31k) if I only connect one monitor via DisplayPort. When i connect my 2 monitors, I get the normal result (approx 51k).

I did not know about the sleep work around, will try that to see if it applies in my case.

With Big Sur my cMP maxes out around 51k for the GB5 metal compute result.

 

[Ausdauersportler]

I have the same GPU and experience a similar issue. I found out that I get about 60% GB5 metal compute results (approx 31k) if I only connect one monitor via DisplayPort. When i connect my 2 monitors, I get the normal result (approx 51k).

I did not know about the sleep work around, will try that to see if it applies in my case.

With Big Sur my cMP maxes out around 51k for the GB5 metal compute result.

Depending on the Mac system the dGPU will switch to max. memory frequency as soon as you connect a second display to the system. This gives better benchmark results because in this particular test a series of single micro benchmarks start and stop and the kext performance management throttles down after each micro test. You can have extreme performance and extreme power draw if you switch on both max. core and memory frequency all the time.

Now we know why most of such benchmarks (and this in particular) are really stupid tests.

 

[jlbillman]

Help! I have a Mac Pro 5,1, 64 GB RAM, AMD Radeon 7950, OC 0.6.8, Bug Sur 11.2.3 installed along with two Apple 27" LED cinema Displays. After upgrading to Big Sur Only one of my monitors works. Has anyone else run into this? I have been searching for a few days for a solution but haven't found any clues yet.

 

[0134168]

Help! I have a Mac Pro 5,1, 64 GB RAM, AMD Radeon 7950, OC 0.6.8, Bug Sur 11.2.3 installed along with two Apple 27" LED cinema Displays. After upgrading to Big Sur Only one of my monitors works. Has anyone else run into this? I have been searching for a few days for a solution but haven't found any clues yet.

Same config here. Mac pro 5,1, two 27 Led Cinema Display, Radeon 7950. Running catalina but last time i tried BS all was smotth and fine. If you want, I can try running updated BS.

 

[Ausdauersportler]

Same config here. Mac pro 5,1, two 27 Led Cinema Display, Radeon 7950. Running catalina but last time i tried BS all was smotth and fine. If you want, I can try running updated BS.

Has one of you tried OCLP instead of this particular version of OpenCore described and maintained here? If the problem exists there too you may open a GitHub issue - I am quite sure the developers might have an idea. But you have to test it on your system first.

 

[0134168]

Has one of you tried OCLP instead of this particular version of OpenCore described and maintained here? If the problem exists there too you may open a GitHub issue - I am quite sure the developers might have an idea. But you have to test it on your system first.

Nop, I use another configuration, initially for Catalina but runs fine with BS. This one. Never had an isuue with it. Runs perfect.

Blog - MacFinder - Certified Refurbished Apple Systems

Stay informed with MacFinder: explore news, in-depth roundups, expert buying advice and more from the UK's no.1 independent Apple reseller.

create.pro

 

[0134168]

As I told you, running 11.0.1 smooth. Now downloading 11.2.3. I will tell later how it goes.

 

[0134168]

Help! I have a Mac Pro 5,1, 64 GB RAM, AMD Radeon 7950, OC 0.6.8, Bug Sur 11.2.3 installed along with two Apple 27" LED cinema Displays. After upgrading to Big Sur Only one of my monitors works. Has anyone else run into this? I have been searching for a few days for a solution but haven't found any clues yet.

I confirm. 11.2.3 running in both Apple Led Cinema Display nicely.

 

[laxamar]

I'm sorry if this was answered, I missed it:
Do we en up with 2 disks ALWAYS (one external, one internal) or is there a way to have the internal drive boot OC and continue with BigSur?

 

[eVasilis]

I'm sorry if this was answered, I missed it:
Do we en up with 2 disks ALWAYS (one external, one internal) or is there a way to have the internal drive boot OC and continue with BigSur?

OC and big sur in my case are on an sata ssd on bay one. Everything works like a charm.

 

[0134168]

OC and big sur in my case are on an sata ssd on bay one. Everything works like a charm.

Same here.

 

[cdf]

I'm sorry if this was answered, I missed it:
Do we en up with 2 disks ALWAYS (one external, one internal) or is there a way to have the internal drive boot OC and continue with BigSur?

Take a look at the guide. There is no requirement for an external disk. OpenCore can be installed on the EFI partition of the Big Sur disk. A second disk (internal or external) with Mojave is recommended to help with the initial installation and to use in case of a misconfiguration.