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.
Well I am gob-smacked ; I've owned this MacPro 5,1 for 10 years and today thanks to MartinoLo @h9826790 I am running Big Sur, a PC Asus RX580, with a proper boot screen omg ; and right now exporting HEVC h265 directly out of FCPX 👏🏻 - extremely easy to update it from OC 0.5.4->0.6.3.2 (just swapped the OC and BOOT folders) and installed Big sure natively up from Mojave... cannot believe it! @h9826790 is a legend.
 

Attachments

  • Screen Shot 2020-11-25 at 6.42.42 pm.png
    Screen Shot 2020-11-25 at 6.42.42 pm.png
    81.3 KB · Views: 237
  • Screen Shot 2020-11-25 at 6.39.33 pm.png
    Screen Shot 2020-11-25 at 6.39.33 pm.png
    102 KB · Views: 174

@h9826790-Thanks for info.​

The only issue I notice is a sporadic “internal super drive loading sound” and crash/panics when I tried to update DVD/BD software-(DVD Fab) Thats why I asked re-HWAccel-

Any thoughts??

It isn’t OC related.

Go into System Preferences/ Energy Saver / Uncheck ‘Put hard disks to sleep when possible’ and the super/dvd/BD drive will stop making that loading sound.
 
  • Like
Reactions: zoltm and h9826790
Once I've setup OpenCore and installed Big Sur is it okay to re-enable SIP? I tried to re-enable it from Big Sur recovery partition with "csrutil enable" but I get the following error:

csrutil: failed to update system integrity configuration: failed to set csr-active-config
 
Once I've setup OpenCore and installed Big Sur is it okay to re-enable SIP? I tried to re-enable it from Big Sur recovery partition with "csrutil enable" but I get the following error:

csrutil: failed to update system integrity configuration: failed to set csr-active-config
No need to access recovery partition to control SIP status anymore.

If you want to re-enable SIP, please mount the EFI partition, open the config plist, search dwgAAA and replace that by AAAAAA, then reboot.
 

w1z

Strange, I don’t have the ‘Put hard disks to sleep when possible’ slider in Energy Saver system preferences ???
Only have-Wake for network access, Start up automatically after a power failure, and Prevent computer from sleeping automatically when the display is off (which I have checked)??
 

w1z

Strange, I don’t have the ‘Put hard disks to sleep when possible’ slider in Energy Saver system preferences ???
Only have-Wake for network access, Start up automatically after a power failure, and Prevent computer from sleeping automatically when the display is off (which I have checked)??

The option should be there. You could also disable it via terminal

Code:
sudo pmset -a disksleep 0

Please start a new thread if you still have problems finding or disabling it.
 
Before jumping to conclusions: can we establish the nature of HWA support for various Radeon architectures in this thread—with the goal of maybe updating the first page of the thread?

On my vintage Mac Pro with a Vega Frontier Edition and Big Sur, I've got HWA enabled as per this thread. All green lights in Videoproc and Resolve exports HEVC with good speed..... as long as it's 8bit. Which is the default, if you just select h.265 as the encoder (it defaults to 'Main').

But... if you want to export UHD HDR, you will need 10bit (Main10) and that is not accelerated on my system. It DOES work on my new iMac though (Big Sur, 5700 XT).

I'm wondering if:
  1. anyone with a Vega-based card has achieved HWA in 10bit HEVC?
  2. anyone with a Navi-based card has achieved HWA in 10bit HEVC?
In another thread, members here with a 7.1 Mac Pro say they get good speed on Main10 HEVC exports from a Vega Pro II, which is basically a Radeon VII (Vega 20), which is surprising me a bit—but it's very good news.

Can we clarify?

EDIT: I've got the 7.1 in my sig, but it isn't up and running for a few days, so I can't test myself.
 
If you have my 0.6.3 installed, I recommend you go direct to Big Sur. It works very well on my cMP (better than Catalina).
@h9826790 I installed your 0.6.3 package (from 0.6.1) and then upgraded to Big Sur. The only issue I ran into was the NightShiftEnable.kext I had been using for a while. My cMP wouldn't boot with this kext in the package. So, I had to remove it. Is there another way to enable nightshift? I am using the 5700XT card... Thanks!
 
@h9826790 I installed your 0.6.3 package (from 0.6.1) and then upgraded to Big Sur. The only issue I ran into was the NightShiftEnable.kext I had been using for a while. My cMP wouldn't boot with this kext in the package. So, I had to remove it. Is there another way to enable nightshift? I am using the 5700XT card... Thanks!
At this moment, in Big Sur, you have to make your cMP ident as iMac Pro or the 7,1 to make Night Shift works (without any kext).

However, that will create some other issues (E.g. iStat cannot display the temperature / fan sensors reading properly).

Therefore, the the suggestion is to use F.lux.
 
At this moment, in Big Sur, you have to make your cMP ident as iMac Pro or the 7,1 to make Night Shift works (without any kext).

However, that will create some other issues (E.g. iStat cannot display the temperature / fan sensors reading properly).

Therefore, the the suggestion is to use F.lux.
Thanks! Will try F.lux...
 
At this moment, in Big Sur, you have to make your cMP ident as iMac Pro or the 7,1 to make Night Shift works (without any kext).

However, that will create some other issues (E.g. iStat cannot display the temperature / fan sensors reading properly).

Therefore, the the suggestion is to use F.lux.
@h9826790 F.lux works great! Thanks again! Also, is there any way to let my cMP5,1 sleep and wake up properly? I am using a 5700XT card... Many thanks!
 
@h9826790 F.lux works great! Thanks again! Also, is there any way to let my cMP5,1 sleep and wake up properly? I am using a 5700XT card... Many thanks!
This seems case by case, and may even related to how long the cMP sleep.

I can only tested on my cMP with my hardware, sleep function seems works (I just make it sleep, then wait a minute, wake it up).

I can’t guarantee that can work on other Mac. IMO, the sleep function is MacOS never reliable. Especially after they changed the power management to cut all PCIe power during sleep. Which often cause some hardware unable to wake up properly. And there is nothing we can do about it.
 
Well I am gob-smacked ; I've owned this MacPro 5,1 for 10 years and today thanks to MartinoLo @h9826790 I am running Big Sur, a PC Asus RX580, with a proper boot screen omg ; and right now exporting HEVC h265 directly out of FCPX 👏🏻 - extremely easy to update it from OC 0.5.4->0.6.3.2 (just swapped the OC and BOOT folders) and installed Big sure natively up from Mojave... cannot believe it! @h9826790 is a legend.
@h9826790, question, in Video Proc app, I noticed when I clicked on "Options/Hardware Acceleration Engine" , the "Graphics Card was NA" {not detected} instead of the graphics card that was installed, in my case an AMD Radeon HD 580X. when I encode a video file, it shows using "Intel" GPU was used for hardware engine instead of AMD?
 
@h9826790, question, in Video Proc app, I noticed when I clicked on "Options/Hardware Acceleration Engine" , the "Graphics Card was NA" {not detected} instead of the graphics card that was installed, in my case an AMD Radeon HD 580X. when I encode a video file, it shows using "Intel" GPU was used for hardware engine instead of AMD?
Post #1 Q14 & Q27
 
OpenCore 0.5.6 released. I created a new "easy to install package" as per many requested. [The attached package already updated to 0.6.3]
Hi Martin,

as you know, I use your 0.6.3 package of OpenCore. I had update 10.15.7 to (19H15) and all works fine...

Yesterday I run GeekBench 5.3.0 and stumple into a (maybe only cosmetic) problem or maybe I did not understand all. Your package has included RadeonBoost and I had it installed also with 10.15.7 (19H2) the formerly version. So I had chanched nothing at OpenCore - only macos update.

macos 10.15.6 (19H2) (machine details see attached JPG)
-------------------------
Geekbench 5.3.0 Metal: 44052
Geekbench 5.3.0 OpenCL: 40141

macos 10.15.7 (19H15)
---------------------------
Geekbench 5.3.0 Metal: 25068
Geekbench 5.3.0 OpenCL: 25406

Unfortunately I have no idea what happen...
Thank's for reading and stay healthy...
 

Attachments

  • neofetch.jpg
    neofetch.jpg
    92.6 KB · Views: 114
  • VideoProc.jpg
    VideoProc.jpg
    77.9 KB · Views: 117
Hi Martin,

as you know, I use your 0.6.3 package of OpenCore. I had update 10.15.7 to (19H15) and all works fine...

Yesterday I run GeekBench 5.3.0 and stumple into a (maybe only cosmetic) problem or maybe I did not understand all. Your package has included RadeonBoost and I had it installed also with 10.15.7 (19H2) the formerly version. So I had chanched nothing at OpenCore - only macos update.

macos 10.15.6 (19H2) (machine details see attached JPG)
-------------------------
Geekbench 5.3.0 Metal: 44052
Geekbench 5.3.0 OpenCL: 40141

macos 10.15.7 (19H15)
---------------------------
Geekbench 5.3.0 Metal: 25068
Geekbench 5.3.0 OpenCL: 25406

Unfortunately I have no idea what happen...
Thank's for reading and stay healthy...
My package only has that included, but disabled. You have to turn that on by yourself.
 
  • Like
Reactions: IceHouse
You'll find this in your config:

XML:
            <dict>
                <key>Arch</key>
                <string>x86_64</string>
                <key>BundlePath</key>
                <string>RadeonBoost.kext</string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <false/>
                <key>ExecutablePath</key>
                <string></string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>

Below the key 'enabled', change <false/> to <true/>
 
My package only has that included, but disabled. You have to turn that on by yourself.
Martin, what can I say... :oops:🤪

Unbelievable, the moment when you recognize that you don't see the wood because of the trees...

I saw the key (Enabled) but don't recognize the value (false). I wish it would be often more easy to fix something like that. 🖖
 
  • Like
Reactions: h9826790
Just installed a Radeon RX 580 to replace my GTX 680- Wow Martin, the 0.6.3 package worked like a CHARM, all acceleration VideoProc confirmed-Thanks from all of us! One thing, can anyone point me to steps where I can change the name of my GPU to “AMD" Radeon RX 580” so VideoProc shows it in Common "engine options”?? I know it is just cosmetic but would love to see it-
 
Hi Martin,

as you know, I use your 0.6.3 package of OpenCore. I had update 10.15.7 to (19H15) and all works fine...

Yesterday I run GeekBench 5.3.0 and stumple into a (maybe only cosmetic) problem or maybe I did not understand all. Your package has included RadeonBoost and I had it installed also with 10.15.7 (19H2) the formerly version. So I had chanched nothing at OpenCore - only macos update.

macos 10.15.6 (19H2) (machine details see attached JPG)
-------------------------
Geekbench 5.3.0 Metal: 44052
Geekbench 5.3.0 OpenCL: 40141

macos 10.15.7 (19H15)
---------------------------
Geekbench 5.3.0 Metal: 25068
Geekbench 5.3.0 OpenCL: 25406

Unfortunately I have no idea what happen...
Thank's for reading and stay healthy...
Enabling Radeon Boost doesn't improve those benchmarks.
 
Just installed a Radeon RX 580 to replace my GTX 680- Wow Martin, the 0.6.3 package worked like a CHARM, all acceleration VideoProc confirmed-Thanks from all of us! One thing, can anyone point me to steps where I can change the name of my GPU to “AMD" Radeon RX 580” so VideoProc shows it in Common "engine options”?? I know it is just cosmetic but would love to see it-
Read post #1, part 2 carefully, then follow the Add the device properties section to add the required code

but after you find out your PCIe path, use the following code to only inject the GPU's name

Code:
<key>Add</key>
<dict>
<key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)</key>
<dict>
<key>model</key>
<data>QU1EIFJhZGVvbiBSWCA1ODA=</data>
</dict>
</dict>

N.B. Lilu and WhateverGreen is already included in my package. You only need to make sure the PCIe path is correct. and inject the above code.
 
  • Like
Reactions: IceHouse
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.