macOS Sierra PB: Need testers for new AMD Radeon drivers!

[Mork_vom_Ork]

Thank you, I thought a fresh set of eyes would catch the problem. Do you have a favorite guide for doing things like the re-mapping?

Yeah, send me a copy of your cards VBios and i will make a working patch for you for the framebuffer to use with CLOVER

 

[jerryy2345]

Yeah, send me a copy of your cards VBios and i will make a working patch for you for the framebuffer to use with CLOVER

I extracted the vbios using :

ioreg -arw0 -d1 -n PEGP@0 | xpath '//key[.="ATY,bin_image"]/following-sibling::*[1]/text()' | base64 -D -o ~/Desktop/vbios.rom

(At the moment I am in 10.12.3) but that should not make a difference. I did not really compress it since it is a small file ~ 66KB, but added the .zip extension to get it uploaded.

I am following along the following guides:

1) https://www.tonymacx86.com/threads/radeon-compatibility-guide-ati-amd-graphics-cards.171291/
2) http://www.insanelymac.com/forum/topic/303186-how-to-modification-of-amd-fb-clover-injection/

in attempting to solve the issue, and am about half way through their instructions, but I am very interested in your fix, since it might be easier.

Thank you for your time and help.

 

[Mork_vom_Ork]

The attached ZIP file is NO good. Can't unzip it. Please try again

COMMAND BACK: i just removed the ".zip" and could use it. So stay tuned...

 

[jerryy2345]

The attached ZIP file is NO good. Can't unzip it. Please try again

COMMAND BACK: i just removed the ".zip" and could use it. So stay tuned...

Some uploaders will not let you send out any type of file, so you have to add the .zip extension in order that it will get picked up. Just removing it will do the trick as you saw.

 

[Mork_vom_Ork]

Please try one of the last 2 parts of this post (but could be used both):

Original BERBICE
(taken from SIERRA 10.12.4 beta4 build16E175b)

020000000001000039050108000000002001010100000000 —> internal Display
000400000001000000010243000000001000020200000000 -> DVI
000400000403000000010313000000002103030300000000 -> DisplayPort
000400000403000000010453000000001102040400000000 -> DisplayPort
000400000403000000010533000000001204050500000000 -> DisplayPort

020000000001000039050108000000002001010100000000000400000001000000010243000000001000020200000000000400000403000000010313000000002103030300000000000400000403000000010453000000001102040400000000000400000403000000010533000000001204050500000000

Modified BERBICE
(! only for THAT specific card, other cards may NOT like this FB-Patch, cause they have other values for their connectors !):

000400000403000000010453000000001102050100000000 -> DisplayPort
000800000402000000010313000000002103030400000000 -> HDMI
000400000001000000010243000000001000040500000000 -> DVI
020000000001000039050108000000002001010100000000 -> internal Display (not used by your Card)
000400000403000000010533000000001204050500000000 -> DisplayPort (not used by your card)

000400000403000000010453000000001102050100000000000800000402000000010313000000002103030400000000000400000001000000010243000000001000040500000000020000000001000039050108000000002001010100000000000400000403000000010533000000001204050500000000

So CLOVER patch look like this
(look for similar code in your actual "info.plist" file and paste in section „KernelAndKextPatches“):

<key>ATIConnectorsController</key>
<string>9510</string>
<key>ATIConnectorsData</key>
<string>020000000001000039050108000000002001010100000000000400000001000000010243000000001000020200000000000400000403000000010313000000002103030300000000000400000403000000010453000000001102040400000000000400000403000000010533000000001204050500000000</string>
<key>ATIConnectorsPatch</key>
<string>000400000403000000010453000000001102050100000000000800000402000000010313000000002103030400000000000400000001000000010243000000001000040500000000020000000001000039050108000000002001010100000000000400000403000000010533000000001204050500000000</string>

Or something like this
(look for similar code in your actual "info.plist" file and paste somewhere at „KextsToPatch“-section):

<dict>
<key>Comment</key>
<string>Connectors Patch for Framebuffer BERBICE for RX460</string>
<key>Disabled</key>
<false/>
<key>Find</key>
<data>AgAAAAABAAA5BQEIAAAAACABAQEAAAAAAAQAAAABAAAAAQJDAAAAABAAAgIAAAAAAAQAAAQDAAAAAQMTAAAAACEDAwMAAAAAAAQAAAQDAAAAAQRTAAAAABECBAQAAAAAAAQAAAQDAAAAAQUzAAAAABIEBQUAAAAA</data>
<key>Name</key>
<string>AMD9510Controller</string>
<key>Replace</key>
<data>AAQAAAQDAAAAAQRTAAAAABECBQEAAAAAAAgAAAQCAAAAAQMTAAAAACEDAwQAAAAAAAQAAAABAAAAAQJDAAAAABAABAUAAAAAAgAAAAABAAA5BQEIAAAAACABAQEAAAAAAAQAAAQDAAAAAQUzAAAAABIEBQUAAAAA</data>
</dict>


BUT REMEMBER: this is JUST the Framebuffer patch. You have to inject your cards ID "0x67EF1002" into AMDRadeonX4100.kext and AMD9510Controller.kext to make it work and accellerated

 

[jerryy2345]

Please try one of the last 2 parts of this post (but could be used both):

Original BERBICE
(taken from SIERRA 10.12.4 beta4 build16E175b)
...
BUT REMEMBER: this is JUST the Framebuffer patch. You have to inject your cards ID "0x67EF1002" into AMDRadeonX4100.kext and AMD9510Controller.kext to make it work and accellerated

Thanks!

Some Notes: I only used the very last version you listed. The 9510 controller and the 4100 kext already have the 67EF1002 id in them, so it is not necessary to add them. Also I had to use the <key>FBName</key><string>Berbice</string> addition in the Graphics section along with the Inject-ATI = true option. So in spite of what the Clover documentation says, F1Orian is correct about that part.

I am almost finished following the instructions from the guides I mentioned earlier, (I tend to be more slow) but I suspect, based upon where I am at, that I will end up with a similar solution to the one you have found. Which means 'good news, everybody! The cards work with 10.12.4, so far. Bad news everyone, the cards will need modifications to use inject-ati = true options.'

Thank you again, I really appreciate your generosity.

 

[Gigamaxx]

" ...... cards will need modifications ......" -> RX4** BIOS tweakings?

No, it's a different approach using clover to inject fixes vs. just fixing the kexts.

Sierra 12.4 so far will require adding the ID 0x67DF1002 to the AMD9510controllerkext and to the AMD4100kext info.plists. It's the same as now for the 4100kext info.plist modification in sierra 12.3 if you're using it. For those that don't and only use fake ID and clover injections it may be troublesome to fix going to 12.4.

Sierra 12.4 version 4 my RX 480 is working (9510 and 4100 kext fixes) but the CU limit fix no longer works because the find data/values are not recognized anymore. This is a big problem for those enjoying the peak performance of th 480s in 12.3.

My RX 460 is natively recognized in sierra 12.3 and 12.4 as well it works fine without any clover ATI injection, the only fix needed is the R9 XXX but that is only cosmetic.

So the 460s (Gigabyte) are no problem, it is the 480 we need to find a CU limit fix or find the new values that need replacing. The Fury Card values provided by FlOr!an no longer take.

 

[jerryy2345]

" ...... cards will need modifications ......" -> RX4** BIOS tweakings?

I do not think so. That would be a different area of modifications

There are some things that Clover supplies for the graphics cards in a generic way (using Inject-ATI = false) and things very specific to the frame buffer (using inject-ati = true).

The generic approach is quite good, but there may be features found only in the specific framebuffers that may go beyond the cosmetic items. Unfortunately, what was working to get at those features in macOS 10.12.3 is not working in 10.12.4 ---as far as the RX 460 cards are concerned, I cannot say much about the 470 and 480 cards.

So some changes are being worked on.

p.s. Audio is still horrifically bad.

 

[corpselight]

Quick note to say that I've gotten an XFX RX-460P2TFG5 working with a Clover-injected Sapphire BIOS from techpowerup and a framebuffer patch.

Update: framebuffer works; acceleration does not, and the GPU hangs. Back to the drawing board.

 

[sparco1987]

10.12.4 beta 5 rolled out... , any news?