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

[alchemistics]

Hey I'm trying to test this as a viable alternative to the lilu method since the traditional method won't work to to boot arg conflicts. Working on cloned drives don't care if I brick os, I can alway repair or reinstall. I've got the info plist done, but I'm having some difficulty with the Apple VGA bit. Hex Editors aren't really my thing, I only use them on occasion for vBios modifications or blck OC in RW/Everything, any help would be appreciated, and you can PM me if you don't want it posted on here

I‘d happy to know more about it as well. As I often have to rely on PRAM reset to allow me to boot into windows again to activate my TB3 devices, from there I have to warmboot into macOS. So the benefit of having it fixed would be obvious..

Thanks so far.

 

[h9826790]

I‘d happy to know more about it as well. As I often have to rely on PRAM reset to allow me to boot into windows again to activate my TB3 devices, from there I have to warmboot into macOS. So the benefit of having it fixed would be obvious..

Thanks so far.

You need PRAM reset to boot into Windows?

Anyway, which GPU and OS you are running now?

 

[alchemistics]

You need PRAM reset to boot into Windows?

Anyway, which GPU and OS you are running now?

Yes. To get proper Display Signal I first have to boot into W10 (see https://forums.macrumors.com/threads/testing-tb3-aic-with-mp-5-1.2143042/page-10#post-27072213), then warmboot into macOS. A reliable way (without preparation) to boot into W10 after macOS shut down is the PRAM reset, unfortunately but it works ..

Using a Reference Vega56 in Mojave 10.14.5.

 

[h9826790]

Yes. To get proper Display Signal I first have to boot into W10 (see https://forums.macrumors.com/threads/testing-tb3-aic-with-mp-5-1.2143042/page-10#post-27072213), then warmboot into macOS. A reliable way (without preparation) to boot into W10 after macOS shut down is the PRAM reset, unfortunately but it works ..

Using a Reference Vega56 in Mojave 10.14.5.

You can’t just select Windows 10 or Mojave via startup disk selection?

https://forums.macrumors.com/thread...ut-a-boot-screen.2114788/page-9#post-26689280

Keep doing PRAM reset just for switching PS doesn't sounds a good way to me.

Anyway, I really have no idea if this file modification approach is better / worse for Vega users. You want to be the beta tester?

 

[h9826790]

Hey I'm trying to test this as a viable alternative to the lilu method since the traditional method won't work to to boot arg conflicts. Working on cloned drives don't care if I brick os, I can alway repair or reinstall. I've got the info plist done, but I'm having some difficulty with the Apple VGA bit. Hex Editors aren't really my thing, I only use them on occasion for vBios modifications or blck OC in RW/Everything, any help would be appreciated, and you can PM me if you don't want it posted on here

I can post the whole procedure here. My test shows very safe actually, worst case just some apps can’t open, and a warning window pops up.

WARNING: only do the following if the WhateverGreen method in post #1 doesn’t work, AND you know how to recovery the ENTIRE OS.

1) Remove all Lilu, WhateverGreen, and boot argument if applicable. (If you need innie, you can keep Lilu). If you remove boot argument by NVRAM reset, you have to disable SIP again in order to modify system files.

2) Go to System⁩ ▸ ⁨Library⁩ ▸ ⁨PrivateFrameworks⁩

3) right click AppleGVA.framework

4) Duplicate this file

5) single click the ORIGINAL AppleGVA.framework

6) Press “Command + i”

7) in the pop up window, rename “AppleGVA.framework” to “AppleGVA.framework.bak” (the file icon should now change to normal folder icon)

8) Rename the duplicated “AppleGVA copy.framework” to “AppleGVA.framework”. (This file’s permission should be wrong at this moment, but tests shows no adverse effect. In fact, make it easier for us to mod. For beta testing, I intentionally keep this “wrong” file permission)

9) double click the current AppleGVA.framework, you should able to open it.

10) continue to Version -> A, and locate “AppleGVA” (this file has no extension)

11) open this AppleGVA file with a Hex editor.

12) find 37 42 41 35 42 32 44 39 45 34 32 44 44 44 39 34 (should have TWO match result in Mojave. If you want to try this in 10.15, you may find only one result)

13) replace BOTH by 46 32 32 31 42 45 43 38 00 00 00 00 00 00 00 00 (make sure you replace the original byte, NOT insert).

14) save the file

15) open terminal

16) enter

sudo codesign -f -s - /System/Library/PrivateFrameworks/AppleGVA.framework/Versions/A/AppleGVA

17) in Finder, in that folder “A”, continue go into folder “Resources”

18) open the info.plist with text editor

19) search 7BA5B2D9E42DDD94

20) replace that by F221BEC8

21) Reboot.

The Hardware acceleration state now should be same as using the WhateverGreen method.

For those who prefer to keep SIP ON. Once you confirm everything is working as expected, you may now turn SIP back on.

Optional steps to repair all modified files' permission.

22) In terminal, enter

sudo codesign --deep -fs - /System/Library/PrivateFrameworks/AppleGVA.framework

23) Enter

sudo chown -R root:wheel /System/Library/PrivateFrameworks/AppleGVA.framework

24) Enter

sudo update_dyld_shared_cache -force

If anything wrong. Do the following recovery action.

A) go to System⁩ ▸ ⁨Library⁩ ▸ ⁨PrivateFrameworks⁩

B) delete AppleGVA.framework

C) rename AppleGVA.framework.bak to AppleGVA.framework (you should able to see the icon change again).

Now, your system should back to normal.


One of the advantage of using this alternate method is that you can turn ON/OFF hwaccel without reboot.

To turn OFF:

1) Rename the modded AppleGVA.framework to AppleGVA.framework.mod.bak.

2) And rename the original AppleGVA.framework.bak to AppleGVA.framework.


To turn it back ON:

1) Rename the original AppleGVA.framework to AppleGVA.framework.bak.

2) And rename the modded AppleGVA.framework.mod.bak to AppleGVA.framework.

 

[donvito4ever]

I can post the whole procedure here. My test shows very safe actually, worst case just some apps can’t open, and a warning window pops up.

WARNING: only do the following if the WhateverGreen method in post #1 doesn’t work, AND you know how to recovery the ENTIRE OS.

1) Remove all Lilu, WhateverGreen, and boot argument if applicable. (If you need innie, you can keep Lilu)

2) Go to System⁩ ▸ ⁨Library⁩ ▸ ⁨PrivateFrameworks⁩

3) right click AppleGVA.framework

4) Duplicate this file

5) single click the ORIGINAL AppleGVA.framework

6) Press “Command + i”

7) in the pop up window, rename “AppleGVA.framework” to “AppleGVA.framework.bak” (the file icon should now change to normal folder icon)

8) Rename the duplicated “AppleGVA copy.framework” to “AppleGVA.framework”. (This file’s permission should be wrong at this moment, but tests shows no adverse effect. In fact, make it easier for us to mod. For beta testing, I intentionally keep this “wrong” file permission)

9) double click the current AppleGVA.framework, you should able to open it.

10) continue to Version -> A, and locate “AppleGVA” (this file has no extension)

11) open this AppleGVA file with a Hex editor.

12) find 37 42 41 35 42 32 44 39 45 34 32 44 44 44 39 34 (should have TWO match result in Mojave. If you want to try this in 10.15, you may find only one result)

13) replace BOTH by 46 32 32 31 42 45 43 38 00 00 00 00 00 00 00 00 (make sure you replace the original byte, NOT insert).

14) save the file

15) open terminal

16) enter

sudo codesign -f -s - /System/Library/PrivateFrameworks/AppleGVA.framework/Versions/A/AppleGVA

17) in Finder, in that folder “A”, continue go into folder “Resources”

18) open the info.plist with text editor

19) search 7BA5B2D9E42DDD94

20) replace that by F221BEC8

21) Reboot.


The Hardware acceleration state now should be same as using the WhateverGreen method.


If anything wrong. Do the following recovery action.


A) go to System⁩ ▸ ⁨Library⁩ ▸ ⁨PrivateFrameworks⁩

B) delete AppleGVA.framework

C) rename AppleGVA.framework.bak to AppleGVA.framework (you should able to see the icon change again).

Now, your system should back to normal.

But which method is better? This one or the first one?

 

[h9826790]

But which method is better? This one or the first one?

My suggestion, go for WhateverGreen first whenever feasible.

This system files modification method is more for those suffering from system freeze / crash with Lilu. Or often need to perform NVRAM reset. Or very reluctant to install 3rd party kext. Etc.

 

[donvito4ever]

My suggestion, go for WhateverGreen first whenever feasible.

This system files modification method is more for those suffering from system freeze / crash with Lilu. Or often need to perform NVRAM reset. Or very reluctant to install 3rd party kext. Etc.

Ok...

In both cases we need to disable SIP or only in the Lilu method?

 

[h9826790]

Ok...

In both cases we need to disable SIP or only in the Lilu method?

That “keep SIP disable” thing is for unsigned 3rd party kext loading. So, only required for WhateverGreen method.

For system file modification. You will need to disable SIP during modification. But once finished, can turn SIP back ON.

 

[donvito4ever]

Second method didn't work in my cMP...

The Lilu method was worked fine, but I'm in the group of those that “suffering from system freeze / crash with Lilu. Or often need to perform NVRAM reset. Or very reluctant to install 3rd party kext. Etc."...

In my case, Photoshop crash saving works, for example...

 

[donvito4ever]

Second method didn't work in my cMP...

The Lilu method was worked fine, but I'm in the group of those that “suffering from system freeze / crash with Lilu. Or often need to perform NVRAM reset. Or very reluctant to install 3rd party kext. Etc."...

In my case, Photoshop crash saving works, for example...

Working!!

I redo with your "new" instructions and all ok!! (before you edit your instructions I don't know if I didn't read fine, because I only change "37 42 41 35 42 32 44 39 45 34 32 44 44 44 39 34" one time on the AppleGVA file, but with the pictures in the thread is clean and easiest...)

Thanks!

 

[h9826790]

Working!!

I redo with your "new" instructions and all ok!! (before you edit your instructions I don't know if I didn't read fine, because I only change "37 42 41 35 42 32 44 39 45 34 32 44 44 44 39 34" one time on the AppleGVA file, but with the pictures in the thread is clean and easiest...)

Thanks!

Good! Please report back how’s the stability etc.

I did quite a bit of tests in Photoshop, Affinity Photos, Photos, Compressor, FCPX, VideoProc, AME, FFMpeg, DV, Handbrake…

So far, only AME will cause the Video Engine stall. Basically just stop to perform, but no crash / system freeze, but more like encoding at 1 FPS.

All other apps are absolutely flawless in my own tests. (Of course, no HEVC encoding yet).

 

[donvito4ever]

At this moment Photoshop works ok.

Only a problem with the process "CEPHtmlEngine" and "CEPHtmlEngine Helper", but I think that isn't related with the trick...

 

[h9826790]

At this moment Photoshop works ok.

Only a problem with the process "CEPHtmlEngine" and "CEPHtmlEngine Helper", but I think that isn't related with the trick...

I am quite sure not really related.

 

[Sharky II]

Hi all,

This is really interesting! Did anybody notice that the GFX card fans are spinning up more/faster or are noisier because of the hardware decode?

Thanks!

Ed

 

[h9826790]

Hi all,

This is really interesting! Did anybody notice that the GFX card fans are spinning up more/faster or are noisier because of the hardware decode?

Thanks!

Ed

If you compare to idle, of course it will stress the card a bit more, and eventually need more cooling.

But it shouldn’t be that significant. More like keep using the browser (web browsers are also accelerated by GPU).

 

[alchemistics]

Now using the "AppleGVA.framework" way. It does work, fantastic. Thanks.

 

[itdk92]

For me, the second method with appleGVA works much much better.

Better performance in MacOS in general and more reliable in Final Cut.

 

[h9826790]

For me, the second method with appleGVA works much much better.

Better performance in MacOS in general and more reliable in Final Cut.

Thanks for the sharing.

Radeon VII perform better with this Hex edit method?

 

[Ludacrisvp]

How / why would performance be better / more reliable?

 

[Slash-2CPU]

How / why would performance be better / more reliable?

You’re using Apple’s drivers with the second method. First method is 3rd party software. Apple’s software should be more reliable.

 

[mavots]

That “keep SIP disable” thing is for unsigned 3rd party kext loading. So, only required for WhateverGreen method.

For system file modification. You will need to disable SIP during modification. But once finished, can turn SIP back ON.

Thanks for developing and outlining the procedure.
I was a little confused about what you just wrote about disabling SIP. Are you saying that the WhateverGreen method would require SIP to be disabled permanently, or just during the first install? I thought after my first read through of your steps that, after rebooting and the AMD acceleration .kext loaded, SIP could be turned on again. Is this not the case?

 

[h9826790]

Thanks for developing and outlining the procedure.
I was a little confused about what you just wrote about disabling SIP. Are you saying that the WhateverGreen method would require SIP to be disabled permanently, or just during the first install? I thought after my first read through of your steps that, after rebooting and the AMD acceleration .kext loaded, SIP could be turned on again. Is this not the case?

You have to keep SIP OFF. Or at least the kext signing part OFF.

In fact, one of the reason that the Mac / OS can easily be recovered by using NVRAM reset is because NVRAM reset will re-enable SIP automatically, which stop Lilu and WhateverGreen to be loaded by the OS. This will ensure that they can't destabilise the system.

 

[SnakeCoils]

I also confirm this second method (direct framework edit) works much better than Lilu/WhateverGreen.
With Lilu/WEG I have H264 acceleration but lost my framebuffer "Orinoco" replaced by generic "Radeon Framebuffer"
With direct editing of AppleGVA I have both "Orinoco" profile and AMD video acceleration (both H264 and HEVC works, I verified this with some 4K HEVC demos from the Web while VideoProc as usual still report H264 only).
Excellent! Thank you very much!

 

[cdf]

You’re using Apple’s drivers with the second method. First method is 3rd party software. Apple’s software should be more reliable.

That's not how this works. In both methods, you are using patched versions of Apple's drivers. The difference is that the second method "hardwires" the modifications. The advantage of the first method is that the patches can easily be turned on and off with the original files remaining untouched.