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

[xbomber2002]

Ok i see now.

But my card originally came with no UEFI support. I think with it's original unmodified vbios I cannot get the OC bootpicker when starting the Mac. Not sure but I'll try tomorrow...Anyway, Is it possible to force windows not checking "signatures" when installing drivers ?

 

[startergo]

Ok i see now.

But my card originally came with no UEFI support. I think with it's original unmodified vbios I cannot get the OC bootpicker when starting the Mac. Not sure but I'll try tomorrow...Anyway, Is it possible to force windows not checking "signatures" when installing drivers ?

AMD/ATI Pixel Clock Patcher

AMD/ATI Pixel Clock Patcher modifies the AMD/ATI video driver to allow higher resolutions and refresh rates by removing the 165 MHz pixel clock limit for single-link DVI and HDMI, the 330 MHz limit fo

www.monitortests.com

 

[xbomber2002]

AMD/ATI Pixel Clock Patcher

AMD/ATI Pixel Clock Patcher modifies the AMD/ATI video driver to allow higher resolutions and refresh rates by removing the 165 MHz pixel clock limit for single-link DVI and HDMI, the 330 MHz limit fo

www.monitortests.com

Ok thanks, I'll take a a closer look tomorrow and i'll let you know.

 

[haralds]

For Catalina, make sure to turn on the VMM flag before checking for updates.

Thanks for responding. The flag is set, but I still am only on 19H524. Safari was updated. It nags for Big Sur, but does not give the Security Update option.

 

[GunStrauss]

I sincerely don't think its coincidental that the final Mac Pro 5.1 compatibility breaks before AMD 6000-series drivers are introduced in macOS. For many this will probably be the final straw before jumping to more modern systems.

 

[Bmju]

I always find it slightly frustrating that you can't diff OC log files, as the timing information at the start of every line is always going to be different.

Have written these small shell scripts to remove timings from OC log file (output to stdout) and to diff two OC log files after timing info is removed: https://github.com/MikeBeaton/OcDiffLog

Example usage:

$ occleanlog opencore-2021-05-06-082342.txt
...

$ ocdifflog opencore-2021-05-06-082342.txt opencore-2021-05-06-082640.txt
...

Turns out some memory allocation details (affecting several lines) differ between runs, but little enough that remaining diffs from small changes can still be found.

 

[sfalatko]

Thanks for responding. The flag is set, but I still am only on 19H524. Safari was updated. It nags for Big Sur, but does not give the Security Update option.

Check Software update - it may be nagging about Big Sur (with VMM set) but there is a link just below the Big Sur text that says something like "more details" - click that and you should see the Security update if it is being offered to you. Click on that and it will only install the security update. After that is done you can turn VMM off and the Big Sur update won't be shown.

 

[eVasilis]

Hi all,

I hope you can enlighten me: where exactly and how do we add boot-args in the config.plist to accommodate for this:

#625

Thanks!

 

[cdf]

Hi all,

I hope you can enlighten me: where exactly and how do we add boot-args in the config.plist to accommodate for this:

#625

Thanks!

It's probably best not to add the boot args to the config. Instead, use a hybridization setup with a clean NVRAM (see part 2 of the guide), and use recovery mode to add the boot args as usual with something like

nvram boot-args="-v debug=0x100 rd=uuid boot-uuid=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"

That way, the boot args will be deleted after an NVRAM reset. Note that after an NVRAM reset, your machine may or may not boot into OC, so make sure to have a natively bootable installation of macOS. You will also need to properly rebless OC.

 

[startergo]

That way, the boot args will be deleted after an NVRAM reset

Why wouldn't they be deleted after NVRAM reset if set in the config file?

 

[cdf]

Why wouldn't they be deleted after NVRAM reset if set in the config file?

Because if the "boot-args" variable and its GUID are present in the delete dictionary, then OC would just set the variable again.

 

[eVasilis]

It's probably best not to add the boot args to the config. Instead, use a hybridization setup with a clean NVRAM (see part 2 of the guide), and use recovery mode to add the boot args as usual with something like

nvram boot-args="-v debug=0x100 rd=uuid boot-uuid=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"

That way, the boot args will be deleted after an NVRAM reset. Note that after an NVRAM reset, your machine may or may not boot into OC, so make sure to have a natively bootable installation of macOS. You will also need to properly rebless OC.

I did that and this is what I got with 11.2.3

 

[OakTone]

The fix in RefindPlus that gave bootscreen for Nvidia GPUs was ported to OpenCore v0.6.9.
It is now also available in OpenCore, with or without OCLP, as long as running v0.6.9 and the relevant settings are activated

Thanks! This is working great in a 5,1 in which I just installed a Quadro K4000. Testing out MyBootMgr and Martin's package, both RefindPlus and OC boot screens show up with slick GUIs (OC in plain text as intended when chain loaded with RP). After booting, the Quadro drives two 4K screens (DP, DVI-to-HDMI) successfully in Mojave 10.14.6, whether booted via RP, OC, or RP-OC chain. (Haven't installed Win10 yet; that's next on the agenda.) So far so good! 👍

BUT… Big Sur 11.2.3 is another story. Somehow BS + OC (at least as configured) isn't playing nice with the Quadro. After selecting it from the OC boot menu, I end up with a black screen -- not completely frozen (pointer moves, keyboard responds), but useless. Trying VNC, I can login and see the same black screen, only managing to move the pointer. (The other screen is completely dead.) Checking for services, RFB is all that shows up on the network; usually this machine also offers SMB, SSH, etc.

Is this a known issue with certain Nvidia cards and Big Sur? I had this exact setup working just a week ago (RP/OC and 11.2.3) with a GT 710. I'd suspect the K4000 is just a bad card except that it performs well in Mojave. Any thoughts from the brain trust here would be appreciated.

 

[eVasilis]

It's probably best not to add the boot args to the config. Instead, use a hybridization setup with a clean NVRAM (see part 2 of the guide), and use recovery mode to add the boot args as usual with something like

nvram boot-args="-v debug=0x100 rd=uuid boot-uuid=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"

That way, the boot args will be deleted after an NVRAM reset. Note that after an NVRAM reset, your machine may or may not boot into OC, so make sure to have a natively bootable installation of macOS. You will also need to properly rebless OC.

Thanks!

 

[Dayo]

Is this a known issue with certain Nvidia cards and Big Sur?

You are more likely to get a suitable response in GPU or Big Sur related discussion threads such as this...

GPU Compatibility List for cMP

Content: 1. Summary 2. Information on common GPUs that can be used in cMP 3. GPU power consumption 4. Color compatibility 5. Flashing nuances 6. What to choose? 7. Useful links. 1. Summary 1.1. There are 50+ GPU types that are compatible with cMP (classic MacPro = Mac Pro 1.1-5.1/...

forums.macrumors.com

or this...

macOS 11 Big Sur on Unsupported Macs Thread

This thread will be used to discuss advancements in getting macOS 11.0 Big Sur running on unsupported Macs. --- Compatibility List: --- FAQ: Q: What does unsupported mean for my old Mac? A: Three problems: Apple locks you out from running the stock installer of Big Sur and as...

forums.macrumors.com

 

[OakTone]

You are more likely to get a suitable response in GPU or Big Sur related discussion threads such as this...

GPU Compatibility List for cMP

Content: 1. Summary 2. Information on common GPUs that can be used in cMP 3. GPU power consumption 4. Color compatibility 5. Flashing nuances 6. What to choose? 7. Useful links. 1. Summary 1.1. There are 50+ GPU types that are compatible with cMP (classic MacPro = Mac Pro 1.1-5.1/...

forums.macrumors.com

or this...

macOS 11 Big Sur on Unsupported Macs Thread

This thread will be used to discuss advancements in getting macOS 11.0 Big Sur running on unsupported Macs. --- Compatibility List: --- FAQ: Q: What does unsupported mean for my old Mac? A: Three problems: Apple locks you out from running the stock installer of Big Sur and as...

forums.macrumors.com

Got it, will do. And thank you for all your hard work on the MyBootMgr package. I am sold on the RP + OC combo as the ideal way to wrangle updated cMPs.

 

[haralds]

Check Software update - it may be nagging about Big Sur (with VMM set) but there is a link just below the Big Sur text that says something like "more details" - click that and you should see the Security update if it is being offered to you. Click on that and it will only install the security update. After that is done you can turn VMM off and the Big Sur update won't be shown.

Thank you. I am well aware of that. I have other systems with partitions with older systems. This link appeared for the Safari update but is not there for the security update. I also cannot install over the current system using a 10.15.7 installer. Guess it's flash stick time.
--> just found that the flags might not have been set correctly after all! Duh!
--> confirmation: setting both flag and mask supports Catalina update with 0.6.9 - RTFM

 

[Mike Richardson]

Just woke my MacPro5,1 up from display sleep (locked screen - Not full sleep) and got this screen.

VNC worked to do a graceful reboot and then it was fine.

FileVault had finished encrypting the main drive earlier today, so that could be related.

I am running OC 0.6.8 on Mojave, does 0.6.9 fix any issues like this? Video card is Radeon RX 580 "MacVidCards" edition.

It was not a full sleep which I haven't even tried since putting OC. Before OC if I slept it, it would just wake up again right away. But it's also the file server so sleeping it kind of defeats the purpose.

 

[grouch]

Has anyone gotten CentOS working on a Mac Pro 5,1 or 4,1? Fedora seems to work fine but CentOS is just a black screen after selecting the Anaconda installer. I'm at the end of my rope.

 

[chrisrm9208]

Has anyone gotten CentOS working on a Mac Pro 5,1 or 4,1? Fedora seems to work fine but CentOS is just a black screen after selecting the Anaconda installer. I'm at the end of my rope.

I just ran up CentOS 8 on my cMP5,1 using Parallels 16; it's one of the freebies Parallels has in it.

 

[paalb]

Just woke my MacPro5,1 up from display sleep (locked screen - Not full sleep) and got this screen.

VNC worked to do a graceful reboot and then it was fine.

FileVault had finished encrypting the main drive earlier today, so that could be related.

I am running OC 0.6.8 on Mojave, does 0.6.9 fix any issues like this? Video card is Radeon RX 580 "MacVidCards" edition.

It was not a full sleep which I haven't even tried since putting OC. Before OC if I slept it, it would just wake up again right away. But it's also the file server so sleeping it kind of defeats the purpose.

Other might have an OC answer to you. My tip is to disconnct and connect your monitor the next time this happen. I am familiar with this happening on a clean install without OC.

 

[Ausdauersportler]

Thanks! This is working great in a 5,1 in which I just installed a Quadro K4000. Testing out MyBootMgr and Martin's package, both RefindPlus and OC boot screens show up with slick GUIs (OC in plain text as intended when chain loaded with RP). After booting, the Quadro drives two 4K screens (DP, DVI-to-HDMI) successfully in Mojave 10.14.6, whether booted via RP, OC, or RP-OC chain. (Haven't installed Win10 yet; that's next on the agenda.) So far so good! 👍

BUT… Big Sur 11.2.3 is another story. Somehow BS + OC (at least as configured) isn't playing nice with the Quadro. After selecting it from the OC boot menu, I end up with a black screen -- not completely frozen (pointer moves, keyboard responds), but useless. Trying VNC, I can login and see the same black screen, only managing to move the pointer. (The other screen is completely dead.) Checking for services, RFB is all that shows up on the network; usually this machine also offers SMB, SSH, etc.

Is this a known issue with certain Nvidia cards and Big Sur? I had this exact setup working just a week ago (RP/OC and 11.2.3) with a GT 710. I'd suspect the K4000 is just a bad card except that it performs well in Mojave. Any thoughts from the brain trust here would be appreciated.

Hi!
First a disclaimer: I am not really an MacPro expert. But getting a black screen on boot with NVIDIA dGPU sounds familiar with what we know from iMac systems with NVIDIA dGPU. At least we could solve this very often by either patching the AppleGraphicsControl.kext or setting the boot-args with OpenCore as described in this post. Hope this helps!

 

[AlexBurdov]

Hi, I have also asked this question in "Activate AMD hardware acceleration" thread. I had successfully installed OpenCore 0.6.8 on NVMe drive and Windows 10 UEFI on separate NVMe drive. Everything works. Both MacOS Mojave and Windows 10 properly reported 2x x5690 3.46GHz CPUs. After installing OpenCore 0.6.9 and turning on hardware acceleration my MacPro 5,1 with 2 X5690 reports as 2 X5670 @2.93Ghz. Is there a way to fix this. I followed a guide from this thread and double checked my config.plist. Is it something to do with AppleMCEReporterDisabler.kext? I have tried removing dictionary for Disabler kext and nothing changes. Anybody else has similar issues? I see people having hardware acceleration enabled and still showing 2x 3.46GHz cpus. I am puzzled as 0.6.8 OpenCore reported correct data. Thank you.

Edit: Just ran Geekbench and that's what I got! Single-Core 565 and multi-Core 4861...

 

[startergo]

Hi, I have also asked this question in "Activate AMD hardware acceleration" thread. I had successfully installed OpenCore 0.6.8 on NVMe drive and Windows 10 UEFI on separate NVMe drive. Everything works. Both MacOS Mojave and Windows 10 properly reported 2x x5690 3.46GHz CPUs. After installing OpenCore 0.6.9 and turning on hardware acceleration my MacPro 5,1 with 2 X5690 reports as 2 X5670 @2.93Ghz. Is there a way to fix this. I followed a guide from this thread and double checked my config.plist. Is it something to do with AppleMCEReporterDisabler.kext? I have tried removing dictionary for Disabler kext and nothing changes. Anybody else has similar issues? I see people having hardware acceleration enabled and still showing 2x 3.46GHz cpus. I am puzzled as 0.6.8 OpenCore reported correct data. Thank you.

You may want to try enabling debug log and see the frequency report/calculation there.

 

[AlexBurdov]

You may want to try enabling debug log and see the frequency report/calculation there.

I have really low geekbench scores with 0.6.9. Mac Pro is maxed out and looks like should be able to get to ~28000 in multicore test. I only get 4861! I have never tested it with 0.6.8. If I want to revert back to basic 0.6.8 without any advanced features turned on. Do I have to do anything extra besides replacing OpenCore files and config.plist on EFI partition with 0.6.8 version? I am not to well versed in it and I am not sure how writing to SMBIOS during hybridization step and deleting couple keys from NVRAM by following the guide affected it. I am hesitant to brick it...