Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

MP 1,1-5,1 Activate AMD hardware acceleration

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.
I just test, it work but need a reboot like before obviously, and hotplug doesn't work anymore I guess right?

Well, I need the last slot (slot 4) for a needed PCIe card... I own a UAD Apollo Twin TB, and I want to add the Universal Audio UAD-2 Quad PCIe extension card)
 
Vvglyy Wzxit said:
I just test, it work but need a reboot like before obviously, and hotplug doesn't work anymore I guess right?

Well, I need the last slot (slot 4) for a needed PCIe card... I own a UAD Apollo Twin TB, and I want to add the Universal Audio UAD-2 Quad PCIe extension card)
Click to expand...
Why not install the Universal Audio UAD-2 Quad PCIe extension card in slot 2 or 3?
 
haha yeah why not? 🤫
EDIT : Well i have
Sapphire RX580 Pulse on slot 1
nothing on slot 2 as I thought it was needed for ventilation...
a dual bootable SATA SSD card in slot 3
and the Titan Ridge in slot 4.
 
I wanted to share my experiences with getting DRM to work with AppleTV/iTunes -

Tests were conducted using MP7,1 board ID with cMP / 5700XT under Big Sur 11.2.

- Patching through DeviceProperties (using config posted in OC wiki) seems to do nothing (no DRM capability) and yes I am using the correct PCI device root. Applying these values through boot-args works although some are not needed.
- No need for Lilu or WEG beta arguments so those can be removed from the boot-args
- No need for agdpmod=pikera boot argument (at least on my setup I didn't need to use it)
- While shikigva is supposedly not compatible with Big Sur as per WEG's wiki on GitHub, both 80 and 128 values seem to work with the latter adding hardware DRM capability to iTunes trailers and movies in addition to Netflix, Prime and AppleTV - see chart

My final boot-args looks like this:

Code: 
boot-args    shikigva=128 unfairgva=1 -wegtree

Hope this helps anyone experiencing DRM playback issues.
 
w1z said:
80 and 128 values seem to work with the latter adding hardware DRM capability to iTunes trailers and movies in addition to Netflix, Prime and AppleTV
Click to expand...
Your 5700XT is obviously one of the "Select AMD GPUs" but any idea where these are listed?
 
Dayo said:
Your 5700XT is obviously one of the "Select AMD GPUs" but any idea where these are listed?
Click to expand...

You mean on the market? Last time I checked, the AMD reference cards aren't available anywhere except on eBay for inflated prices. You may still get non-reference cards online but they're not easy to find.
 
Sorry, the WhateverGreen chart says certain features are only available on "Select AMD GPUs".
That is, only some specific AMD GPU Models but doesn't seem to say which ones fall into this select group.

Screen Shot 2021-02-07 at 12.12.26.jpg


Was wondering whether you have an idea
 
Dayo said:
Sorry, the WhateverGreen chart says certain features are only available on "Select AMD GPUs".
That is, only some specific AMD GPU Models but doesn't seem to say which ones fall into this select group.



Was wondering whether you have an idea
Click to expand...

Nope. My best guess - probably GPUs based on the same architectures and same or similar models officially supported by Apple in macOS ie. Vega, Navi etc.
 
  • Like
Reactions: Dayo
w1z said:
I wanted to share my experiences with getting DRM to work with AppleTV/iTunes -

Tests were conducted using MP7,1 board ID with cMP / 5700XT under Big Sur 11.2.

- Patching through DeviceProperties (using config posted in OC wiki) seems to do nothing (no DRM capability) and yes I am using the correct PCI device root. Applying these values through boot-args works although some are not needed.
- No need for Lilu or WEG beta arguments so those can be removed from the boot-args
- No need for agdpmod=pikera boot argument (at least on my setup I didn't need to use it)
- While shikigva is supposedly not compatible with Big Sur as per WEG's wiki on GitHub, both 80 and 128 values seem to work with the latter adding hardware DRM capability to iTunes trailers and movies in addition to Netflix, Prime and AppleTV - see chart

My final boot-args looks like this:

Code: 
boot-args    shikigva=128 unfairgva=1 -wegtree

Hope this helps anyone experiencing DRM playback issues.
Click to expand...

I'm surprised by all this. Do the device properties show up in the ioreg?

Perhaps you should report this to Acidanthera:

github.com

GitHub - acidanthera/bugtracker: Acidanthera Bugtracker

Acidanthera Bugtracker. Contribute to acidanthera/bugtracker development by creating an account on GitHub.
github.com github.com
 
@cdf Using the values posted in OC's thread/wiki on here

2021-02-08_14-44-06.png


Can't watch AppleTV or Netflix but I can watch Spider Man's trailer on Amazon Prime as shared here

Once I revert back to using the boot-args "shikigva=128 unfairgva=1 -wegtree" without adding the above to DeviceProperties, I can view all streaming services (no green/red screens or failed viewer checks)
 
  • Like
Reactions: Ausdauersportler
w1z said:
@cdf Using the values posted in OC's thread/wiki on here

View attachment 1726921

Can't watch AppleTV or Netflix but I can watch Spider Man's trailer on Amazon Prime as shared here

Once I revert back to using the boot-args "shikigva=128 unfairgva=1 -wegtree" without adding the above to DeviceProperties, I can view all streaming services (no green/red screens or failed viewer checks)
Click to expand...
Well, it's definitely a good thing that you have a working solution! But it's a curious thing that the device properties are being set but not working like they should. Then again, maybe these settings are specific to your video card...

If you want to experiment further, maybe you can try applying your working boot arguments as device properties instead to rule out a possible WEG issue:

XML: 
<key>rebuild-device-tree</key>
<data>AA==</data>
<key>shikigva</key>
<data>gA==</data>
<key>unfairgva</key>
<data>AQAAAA==</data>
 
Last edited:
  • Like
Reactions: f329 and h9826790
hi guys, I have OC 0.6.4 installed. I want to update OC to 0.6.6 to unlock the DRM streaming. I have RVII and my problem is I don't know if I should follow this tutorial from first page to unlock Hardware Acceleration or should I simply unpack and use @h9826790 package? I'm a bit lost here as I inspected the mentioned package and it uses shikigva 80 in NVRAM section and the first page uses shikigva 96. Maybe those are different things? omg I'm so lost haha
 
Norbert Mikołajczyk said:
hi guys, I have OC 0.6.4 installed. I want to update OC to 0.6.6 to unlock the DRM streaming. I have RVII and my problem is I don't know if I should follow this tutorial from first page to unlock Hardware Acceleration or should I simply unpack and use @h9826790 package? I'm a bit lost here as I inspected the mentioned package and it uses shikigva 80 in NVRAM section and the first page uses shikigva 96. Maybe those are different things? omg I'm so lost haha
Click to expand...
For Big Sur, shikigva is irrelevant. It’s the unfairgva activate DRM streaming.

TBH, both options work, and both cdf and me are base on the same fix provided by WhateverGreen.

It’s your choice to go for the lazy route (my package). Or try to learn to config OC by yourself.
 
  • Like
Reactions: SirVikon, Ausdauersportler and Norbert Mikołajczyk
cdf said:
Well, it's definitely a good thing that you have a working solution! But it's a curious thing that the device properties are being set but not working like they should. Then again, maybe these settings are specific to your video card...

If you want to experiment further, maybe you can try applying your working boot arguments as device properties instead to rule out a possible WEG issue:

XML: 
<key>rebuild-device-tree</key>
<data>AA==</data>
<key>shikigva</key>
<data>woA=</data>
<key>unfairgva</key>
<data>AQAAAA==</data>
Click to expand...

No go! It seems only boot-args are having an effect. I also tested with the short and long form of the GPU's PciRoot path.

2021-02-10_10-43-22.png


2021-02-10_10-46-26.png


I need to find some time to load the debug version of OC to gather the needed logs for submitting a bug report - most probably over the weekend.
 
  • Like
Reactions: cdf and Ausdauersportler
w1z said:
I need to find some time to load the debug version of OC to gather the needed logs for submitting a bug report - most probably over the weekend.
Click to expand...
I noticed that the base64 value I gave you for 128 was incorrect. It should be gA==. See Post #2,317.
 
Another thing: Your ioreg output shows only one set of properties. Perhaps that's due to your card, but in my case, I see one set of properties under the display controller (GFX0) and another set under the card's audio device (PXS1).
 
  • Like
Reactions: startergo
Installed the latest package on my 5,1 and works great in Mojave - no issues at all. Was thinking of upgrading to Big Sur, have a test install on a separate drive and Geekbench compute score for my AMD RX 580 has gone from 134309 to 78298 !!
Is this just crap software (Big Sur) or is there some tweaks I need to do for this version os OS X?
Thanks in advance
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back