Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Going to sound dumb but does HWA in OC affect Windows 10 at all? Having instability with Windows (during gaming) and I'm trying to track down what it is, but I don't think so myself....
Should not.

Instability in Windows gaming usually GPU cooling related (if not because the driver itself is buggy).

In macOS, the graphic card use the voltage, clock, fan curve that defined in the VBIOS.

In Windows, the AMD software override all those value, and use a different set of parameters to run the card. E.g. the fan curve can be less aggressive.

Also, in MacOS, the GPU rarely can run as hard as in Windows gaming.

Therefore, the GPU may end up run at higher temperature in Windows gaming, which can cause stability issue.

I don’t know what problem you are actually having. But you may spin up the PCIe fan more (via MacsFanControl), and make the graphic card’s fan run at higher speed (in the AMD software) to keep the GPU run at lower temperature. And see if it helps.
 
  • Like
Reactions: rx78
Thanks for the clarification, Martin. I might try to test the 7,1 Board ID to check what appears to be a replicable bug in my system. In addition to loosing BT when I boot Big Sur right after Mojave (a known bug), I also loose the following:

1) Audio from one of the DP ports on the RX580 (I use the 2 DP ports and only one looses audio)
2) Sonnet Fusion Dual 2.5-inch SSD RAID on PCIe 4 does not load.

BT regularly comes back on a subsequent (second) Big Sur reboot as reported by other users, but the other two issues usually need a third Big Sur reboot to show up. At that point everything works perfectly, even if i shutdown/restart on a daily basis.

But in order to test the 7,1 Board ID to troubleshoot the above -- I would have to change the Board ID while booted on Mojave and just before rebooting into Big Sur... correct?
2) The problem only exist in slot 4?
 
With gpu prices out of control day by day, what’s the cheapest way to get h264 encoding these days ?

I am not a gamer but I do need boot screens; so a flashed card w boot screen or open core and ???
I haven’t follow the GPU market, but RX460 should be the cheapest card can do that in MacOS on cMP.
 
Should not.

Instability in Windows gaming usually GPU cooling related (if not because the driver itself is buggy).

In macOS, the graphic card use the voltage, clock, fan curve that defined in the VBIOS.

In Windows, the AMD software override all those value, and use a different set of parameters to run the card. E.g. the fan curve can be less aggressive.

Also, in MacOS, the GPU rarely can run as hard as in Windows gaming.

Therefore, the GPU may end up run at higher temperature in Windows gaming, which can cause stability issue.

I don’t know what problem you are actually having. But you may spin up the PCIe fan more (via MacsFanControl), and make the graphic card’s fan run at higher speed (in the AMD software) to keep the GPU run at lower temperature. And see if it helps.
Thanks for the insight.

I thought that would be the case here and didn't think it would have been HWA causing my issues.

I've been monitoring it and had already set a fan curve for the GPU within adrenalin, also linked PCIE fan to PCIE ambient within Mac's Fan Control but it'll either crash due to the driver (BSOD with thread stuck), freeze (probably driver issue again) or black screen and the GPU fan will go full tilt (assuming this is a heat related issue). Temps for the CPU, NB, RAM are fine, even the GPU reports maximum of 65C with my settings.

Might be the card itself (SOL with GPU pricing now lol) will probably take it apart for a repaste and go from there.

Edit: formatting
 
Thanks for the great job! I own Mac Pro 4.1>5.1 / Powercolor RX 580 (4GB - 1DVI only) / Mojave and applied your 0.6.7 package. I've got all benefits except Boot screen (via GOP) (Which I've got when switch to original GT 120). Here is my GPU info, pls have a look at this issue. Thanks in advances.

rx 580.gif
 
2) The problem only exist in slot 4?
I have not tested that card on other slot for that specific transition moment from Mojave to Big Sur.

FYI, I have my x2 NMVe blades in slot 2 and a cheap USB 3.0 card on slot 3. The blades work fine as one of them is the bootable drive with Big Sur. The USB 3.0 card I did not test in that specific transition moment, although I can see now that it’s worth to do and will do.

As far as slot 1, the GPU is there and it is somewhat affected since DP audio is not working for one of the two DP ports.

As for the Sonnet card in slot 4, in addition to the Raid x2 2.5inch SSDs, it has a USB-C port to which i connect a hub (with x2 USB-C ports, x1 USB 3.0 port, x1 SD Card port and x1 miniSD card port.) The Raid show always as external and Sonnet states on their website that it cannot show as internal, therefore cannot be used as boot drive.
 
chiming in...
Just performed an upgrade on my cMP 5,1 from Mojave --> Bigsur.
Currently am successful on my test SSD (cloned from NVMe card). So far multiple monitors works great, hardware acceleration is good.

Am unable to boot into my bootcamp Windows 10 install (loaded on m.2 Sata drive - non UEFI), so will see if I can reinstall this in a different method so the bootpicker will see it???

If anyone has been able to dual boot macOS and Win10 (each on its own NVMe), please let me know.
THanks!
 
chiming in...
Just performed an upgrade on my cMP 5,1 from Mojave --> Bigsur.
Currently am successful on my test SSD (cloned from NVMe card). So far multiple monitors works great, hardware acceleration is good.

Am unable to boot into my bootcamp Windows 10 install (loaded on m.2 Sata drive - non UEFI), so will see if I can reinstall this in a different method so the bootpicker will see it???

If anyone has been able to dual boot macOS and Win10 (each on its own NVMe), please let me know.
THanks!
This may help
 
thank you very much for this! Will be trying this soon (waiting for a new drive so I can clone my existing windows install)... Have been trying to use the windows install method noted here https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/ ....But can't seem to get my USB drive to show up in the picker.

Will let ya know how this works out
For new Windows installation, follow this link, post #1, Appendix
 
yep... this is what I followed, I was having trouble with making my USB stick, finally have it online and built.
Of course this was all using Sata SSD's. Will have to see if my NVMe sticks will work with this setup (as that do in mojave). I'm liking the ease of use with OpenCore a lot more!

Appreciate the help/links provided!
 
@h9826790 Here is an interesting script to enable H264. I wonder if it will enable HEVC encoding too:
macOS 11 Big Sur on Unsupported Macs Thread | MacRumors Forums
In essense:
Code:
sudo /usr/libexec/PlistBuddy -c "Add :System\ Support:$BOARD_ID:allowFrameReordering bool false" "$MOUNT/System/Library/PrivateFrameworks/AppleGVA.framework/Versions/A/Resources/Info.plist"
sudo /usr/libexec/PlistBuddy -c "Add :System\ Support:$BOARD_ID:hwe bool true" "$MOUNT/System/Library/PrivateFrameworks/AppleGVA.framework/Versions/A/Resources/Info.plist"
sudo /usr/libexec/PlistBuddy -c "Add :System\ Support:$BOARD_ID:hwe420 bool true" "$MOUNT/System/Library/PrivateFrameworks/AppleGVA.framework/Versions/A/Resources/Info.plist"
sudo /usr/libexec/PlistBuddy -c "Add :System\ Support:$BOARD_ID:interlacedOff bool true" "$MOUNT/System/Library/PrivateFrameworks/AppleGVA.framework/Versions/A/Resources/Info.plist"
sudo /usr/libexec/PlistBuddy -c "Add :System\ Support:$BOARD_ID:ke1 bool true" "$MOUNT/System/Library/PrivateFrameworks/AppleGVA.framework/Versions/A/Resources/Info.plist"
sudo /usr/libexec/PlistBuddy -c "Add :System\ Support:$BOARD_ID:pp integer 1" "$MOUNT/System/Library/PrivateFrameworks/AppleGVA.framework/Versions/A/Resources/Info.plist"

defaults write com.apple.AppleGVA gvaForceAMDKE -bool YES
defaults write com.apple.AppleGVA gvaForceAMDAVCEncode -bool YES
defaults write com.apple.AppleGVA gvaForceAMDAVCDecode -bool YES
defaults write com.apple.AppleGVA gvaForceAMDHEVCDecode -bool YES

From what I can see here HEVCDecode is forced but not HEVCEncode.
 
@h9826790 Here is an interesting script to enable H264. I wonder if it will enable HEVC encoding too:
macOS 11 Big Sur on Unsupported Macs Thread | MacRumors Forums
In essense:
Code:
sudo /usr/libexec/PlistBuddy -c "Add :System\ Support:$BOARD_ID:allowFrameReordering bool false" "$MOUNT/System/Library/PrivateFrameworks/AppleGVA.framework/Versions/A/Resources/Info.plist"
sudo /usr/libexec/PlistBuddy -c "Add :System\ Support:$BOARD_ID:hwe bool true" "$MOUNT/System/Library/PrivateFrameworks/AppleGVA.framework/Versions/A/Resources/Info.plist"
sudo /usr/libexec/PlistBuddy -c "Add :System\ Support:$BOARD_ID:hwe420 bool true" "$MOUNT/System/Library/PrivateFrameworks/AppleGVA.framework/Versions/A/Resources/Info.plist"
sudo /usr/libexec/PlistBuddy -c "Add :System\ Support:$BOARD_ID:interlacedOff bool true" "$MOUNT/System/Library/PrivateFrameworks/AppleGVA.framework/Versions/A/Resources/Info.plist"
sudo /usr/libexec/PlistBuddy -c "Add :System\ Support:$BOARD_ID:ke1 bool true" "$MOUNT/System/Library/PrivateFrameworks/AppleGVA.framework/Versions/A/Resources/Info.plist"
sudo /usr/libexec/PlistBuddy -c "Add :System\ Support:$BOARD_ID:pp integer 1" "$MOUNT/System/Library/PrivateFrameworks/AppleGVA.framework/Versions/A/Resources/Info.plist"

defaults write com.apple.AppleGVA gvaForceAMDKE -bool YES
defaults write com.apple.AppleGVA gvaForceAMDAVCEncode -bool YES
defaults write com.apple.AppleGVA gvaForceAMDAVCDecode -bool YES
defaults write com.apple.AppleGVA gvaForceAMDHEVCDecode -bool YES

From what I can see here HEVCDecode is forced but not HEVCEncode.
This looks like will have similar effect as my "alternate method". So, I don't think HEVC encoding can work (in earlier macOS).

But I never test this kind of method in Big Sur. So, I can't tell what will really happen.
 
@h9826790 I have a quick question for you -- i just saw this reply by @cdf in the general OC thread about choppy BT mouse movement. I ocassionally experience the same choppiness with an Apple Magic Trackpad 2 and wonder if your OC package would have the same issue, and if so, if upcoming updates would fix this as well? thanks so much!
 
@h9826790 I have a quick question for you -- i just saw this reply by @cdf in the general OC thread about choppy BT mouse movement. I ocassionally experience the same choppiness with an Apple Magic Trackpad 2 and wonder if your OC package would have the same issue, and if so, if upcoming updates would fix this as well? thanks so much!
Yeah, the upcoming 0.6.8 should improve OpenCanopy quite a bit, including improve the mouse pointer smoothness.
螢幕擷取畫面 (158).png
 
Yeah, the upcoming 0.6.8 should improve OpenCanopy quite a bit, including improve the mouse pointer smoothness.

thanks.

Just to better understand, would this improvement apply to mouse pointer smoothness in general or only for the boot picker window at startup?

I have been reading through the OC thread and github trying to learn (mainly parse and identify) all the different parts that make OC work. I dont understand if OpenCanopy is only operational during startup and boot picker screen or instead if it is operational all the time.

in my case, the mouse choppiness happens when i generally use the cMP, and only happens sporadically and for a short time. I don’t use the mouse during the boot picker screen.
 
Just to better understand, would this improvement apply to mouse pointer smoothness in general or only for the boot picker window at startup?
Only in OpenCanopy.

I dont understand if OpenCanopy is only operational during startup and boot picker screen or instead if it is operational all the time.
OpenCanopy is out of the way by the time macOS starts.
 
  • Like
Reactions: Stex and h9826790
thanks.

Just to better understand, would this improvement apply to mouse pointer smoothness in general or only for the boot picker window at startup?

I have been reading through the OC thread and github trying to learn (mainly parse and identify) all the different parts that make OC work. I dont understand if OpenCanopy is only operational during startup and boot picker screen or instead if it is operational all the time.

in my case, the mouse choppiness happens when i generally use the cMP, and only happens sporadically and for a short time. I don’t use the mouse during the boot picker screen.
Are you using a bluetooth mouse? I had that problem. The bluetooth signal is notoriously bad on the old Mac Pro, especially the 2009 model. I installed a new BT antenna and the problem was gone. Just google "mac pro bluetooth antenna upgrade"
 
I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package already updated to 0.6.8]

For those who only need HWAccel, post #594 has everything you need. This new package mainly offer HWAccel + boot screen. Also, this package should work in Catalina for dual processor cMP.

I don't mind you guys discuss anything about this package, but I have no plan to provide any explanation about OpenCore at here. If you want to know more, please join cdf's OpenCore thread. For new joiners, please make sure read through the FAQ in post #1 before you ask anything.

The attached packaged included Clover Configurator and a complete preconfigured OpenCore. All credits goes to the developer teams. If you want to show your support, please give them donation (declaration of interest: I am NOT in any of their developer teams)

For Clover Configurator and OpenCore developers teams, please let me know if you want me to remove the associated software inside my attachment in this post.

This is a "one package fit all" solution. So, it's designed to fit as much setup as possible, which may not be optimized for your setup (e.g. I haven't provide HiDPI boot screen, for those who are running 4K screen, the Apple logo may be quite small during boot). You have to do the optimization by yourself (details in the OpenCore manual, some info also available in cdf's OpenCore thread).

Anyway, for those who have RX 460 or newer AMD GPU, this package should gives you:
  1. Boot screen (via GOP for unflashed card, including some Nvidia card)
  2. Firmware protection (to run Windows in EFI mode without risking the cMP bootROM)
  3. HWAccel (H264 / HEVC hardware decode + encode in Mojave or later)
  4. ability to watch DRM streaming content (Mojave and later)
  5. Boot picker (only support EFI systems, tested with Apple wired keyboard, Magic Mouse, and Magic Keyboard, 10s timeout. If you can't see this. Just don't touch the keyboard, and your cMP should continue to boot to desktop)
  6. NVMe and SATA drives on PCIe card show up as internal
  7. Support for Apple USB SuperDrive
  8. TRIM (regardless trimforce status)
  9. Ability to run non-GUI 32bit software in Catalina
  10. Ability to reset NVRAM in boot picker (disabled at this moment to align with the native Apple boot manager)
  11. Ability to run any natively supported ancient OSX with modern graphic card e.g. Radeon VII in 10.6.8 (only can display, no acceleration) [Update 5th May 2020: Sierra and High Sierra may not fully supported yet. Thanks for pierrox's report]
  12. Ability to boot Catalina / Big Sur Recovery Partition
  13. Sleep should work (tested on my cMP, but I can't guarantee it also work with your hardware)
  14. Possible to run 8x32GB RAM in macOS
It's impossible for me to test every single function in all situations. So, as usual, use at your own risk. But you are welcome to report back if there is any problem / error.

Pre-installation:
  • Recommend to backup your BootROM between step 1 and 2 (e.g. by using ROMTool)
  • If you want to test OpenCore, you can install this package onto a bootable USB thumb drive.
  • Quite a few users reported that can't boot OpenCore from NVMe, please avoid to install this package on NVMe. You can install this package on ANY SATA drive, not necessary your boot drive.
  • If you want to remove OpenCore, please mount the EFI partition by using Clover Configurator, then remove BOOT and OC folders inside the EFI folder on EFI partition.
  • If your cMP stuck at boot. After shutdown, please pull out the hard drive that contain OpenCore, then perform NVRAM reset. If still doesn't work, then please install your emergency graphic card that has boot screen. Hold Option to boot, then select your backup boot drive. This should disable OpenCore.
  • For those who want to report issue / error. Please provide details (e.g. which graphic card, OpenCore installed on NVMe / SATA drive, the issue's details, etc) otherwise it will be extremely hard (or even impossible) for me to work out what's wrong.
  • If you installed Lilu for whatever reason (e.g. because of innie), or applied my previous non-OpenCore HWAccel mod, please remove them or revert them. For Lilu + WEG, that means delete Lilu.kext in /Library/Extensions/ and reboot (caution: these kexts may be installed in System/Library/Extensions/ as well). For hex edit method, that means delete AppleGVA.framework in /System/Library/PrivateFrameworks/ and rename AppleGVA.framework.bak to AppleGVA.framework. Warning: My package already have Lilu and WEG included, "double installation" of these kexts will cause macOS boot failure.
  • For PULSE RX580, users reported that only can see boot screen when boot from gaming mode. There may be no UEFI GOP in the compute mode's ROM.
Anyway, I tried to make the installation as simple as possible. Here is what you need to do
  1. [Optional] 3x NVRAM reset to avoid some unknown issues.
  2. Disable SIP (must do, especially if you performed step 1)
  3. Download the attachment in this post (Some users reported 0.6.1 package has compatibility issue. You may download the 0.5.9 package if you prefer that, same installation procedures)
  4. Follow the steps in this video
  5. For Big Sur only, if some ports on your graphic card are disabled, please follow the steps in this video to re-enable them.
  6. Reboot

For existing OpenCore users, you may follow the step in this video to update OpenCore


Additional option 1: If you have 4K screen, and you want to have "Retina" boot screen. You may do this.

Additional option 2: If you have a flashed Thunderbolt 3 card, you can install that in slot 4, then enable Thunderbolt 3 support by doing this.

Additional option 3: If you want to enable the ability to install / update Catalina [Update: Thanks for cdf's finding. If you are with the 0.6.3 (and newer) package, and want to install Big Sur, your 5,1 should able to do that "natively". No need to touch the VMM flag etc]

Additional option 4: If you have legacy wifi card, you may try the follow steps to re-activate the old wifi card in Big Sur (only avail in my 0.6.4 package or above)

Additional option 5: Since 0.6.3, I allow OC to take over SIP control. There are various reasons, but anyway, that's defaulted to be disabled. If you want to re-enable SIP, please follow the steps in this video.

For FCP(X) users, if you want to export HEVC video by using HWAccel, you will need Compressor.
[N.B. The setting MUST identical to the one that I show in the video. Otherwise, HEVC hardware encoding may not work]

If you want to completely uninstall my OpenCore package, please follow the steps in this video.

N.B. Unflashed graphic card means "the ROM is never modified". For those who bought used card, and can't see the boot screen, most likely the last user flashed the card with modified ROM (e.g. downvolt for mining). In this case, you can go to TechPowerUp to find a ROM that fit your own card, and flash it.

P.S. If you want to support my work, please donate via the following link. Million thanks in advance! https://www.paypal.com/paypalme/martinlo420

[Last update: 6 Apr 2021, OC 0.6.8, Lilu 1.5.2, WEG 1.4.9]
With your OC 0.6.8 package, after choosing to boot with Mojave or Windows, in the next start, the Mac's boot sound (boing) is heard normally, but after booting the Mac from the Big Sur volume, and rebooting, the boot sound (boing) is no longer heard (muted)! Why?
Also, why can't I see the Big Sur disk from the Mojave Startup Disk?
Thanks!
 

Attachments

  • Schermata 2021-04-06 alle 16.03.17.png
    Schermata 2021-04-06 alle 16.03.17.png
    65.4 KB · Views: 85
Are you using a bluetooth mouse? I had that problem. The bluetooth signal is notoriously bad on the old Mac Pro, especially the 2009 model. I installed a new BT antenna and the problem was gone. Just google "mac pro bluetooth antenna upgrade"
Thanks very much for the suggestion. Yes, you are probably correct that my issue is the BT antenna. I just wanted to make sure OC had nothing to do with the problem. I had read several threads about upgrading the BT antenna and and will review them again. I will write in those threads if I have any other question about this.
 
With your OC 0.6.8 package, after choosing to boot with Mojave or Windows, in the next start, the Mac's boot sound (boing) is heard normally, but after booting the Mac from the Big Sur volume, and rebooting, the boot sound (boing) is no longer heard (muted)! Why?
Also, why can't I see the Big Sur disk from the Mojave Startup Disk?
Thanks!
Mojave can't understand the Big Sur APFS system, this is normal.

If you want dual boot, you have to choose Big Sur in the boot picker.

For boot sound, please check your Big Sur internal speaker volume setting.
 
Thanks very much for the suggestion. Yes, you are probably correct that my issue is the BT antenna. I just wanted to make sure OC had nothing to do with the problem. I had read several threads about upgrading the BT antenna and and will review them again. I will write in those threads if I have any other question about this.

i simply use the Magic Trackpad 2 with connected USB Cable. I dont mind the cable like I would on a mouse. Plus it works in preboot situations and in every OS like Linux and Win.
 
  • Like
Reactions: Stex
Hi friends, i have cMP 5,1 with OC 0.6.8 package and BigSur, my filevault shows incorrect password message. Anybody knows how to resolve this? I have tried reset filevault password from recovery but without success.. I got working FileVault without any problems on non-apple hw. It is really sad, that filevault works with OC on non-apple hw but apple hardware is problem.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.