Radeon Compatibility Guide - ATI/AMD Graphics Cards

[TESTER321022]

Hi,
what do I have to do, to "change" the third (DVI) connector on my Gigabyte Radeon RX560 OC 4G, so that it works (it's actual recognized, but black). It seems to be shown as LVDS in Hackintool, but my MB is too old, so Hackintool doesn't support it. I'm using latest Mojave.
Any hints?
Thanx a lot in advance.

 

[jaymonkey]

what do I have to do, to "change" the third (DVI) connector on my Gigabyte Radeon RX560 OC 4G, so that it works (it's actual recognized, but black). It seems to be shown as LVDS in Hackintool

@TESTER321022,

It's usually mandatory to install Lilu + WhatEverGreen (WEG) if you want to use more than two outputs from a OEM AMD dGPU. The issue is caused by the OEM dGPU not matching Apples AMD framebuffer definitions, WEG patches the AMD framebuffer so that all outputs work.

Hackintool will only show the IGPU framebuffer connectors, not the dGPU.

Cheers
Jay

 

[TESTER321022]

Hi Jay,
thanks for your support!

I installed Lilu and WhateverGreen and disabled the "ATI-Injection"in clover.
It seems, that the card is now working via LILU/WEG.
All three monitors (old Dell's) are shown in the macOS system information, but the third monitor (DVI) is still black and on the others sometimes there's there's a little "flickering".

Cheers, H.

PS Flickering only on one of the Systems - have to check that!
The second system is working fine (in macOS System-info the card shown as Radeon RX 560 4 GB). DVI - Out doesn't work.
Where could this connector-trouble be fixed/ patched?

 

[jaymonkey]

Where could this connector-trouble be fixed/ patched?

@TESTER321022,

For most users Lilu & WEG should take care of patching the AMD framebuffer ... as such there have not been any updated guides on the subject for a few years (as far as i am aware).

There are a few old resources here at TMx86 that detail the manual methods of how it used to done.

AMD Framebuffer patching is touched on in Section 3 of the AMD Compatibility Guide (1st post in this thread) :-

Radeon Compatibility Guide - ATI/AMD Graphics Cards

Radeon Compatibility Guide ATI/AMD Graphics Cards Last Change: December 2nd, 2017 The "boot to black screen" issue as well as the broken sleep/wake have been fixed! Read below for details. 0. Introduction Most of you might have noticed that the Buyer's Guide doesn't list a single...

www.tonymacx86.com

And in a bit more detail in this guide :-

Guide How to Patch AMD Framebuffers for High Sierra using Clover

So if you recently installed High Sierra and have an AMD graphics card and were greeted at the end of the installation with black screens and Lilu.kext and WhateverGreen.kext wasn't able to resolve it, then try patching the framebuffer that corresponds to your graphics card to try resolving it...

www.tonymacx86.com

Note that both of the above resources are for older AMD GPU's and MacOS versions but the methods should work for a RX 5XX based GPU (although I have never personally tried it). If you are running Mojave or Catalina you will most likely need to disable SIP in order to use a custom/modified AMD FrameBuffer kext (Lilu / WEG dynamically modify the kext in memory once it is loaded).

Cheers
Jay

 

[BigOncleSam]

HDMI definitely did not work but I was able to finally get it to boot with acceleration via DP. Here's what I did since I last posted:

• Booted into single user mode and removed old Multibeast kexts from /L/E
• Updated Clover to 5114
• Incidentally stupid Windows 10 update wiped my Clover UEFI boot manager and I had to recreate it.
• Latest WEG, Lilu, FakeSMC, ALC to EFI/C/k/O
• Changed SMBIOS from iMac14,2 to iMacPro1,1
• agdpmod=pikera (my previous post had it as agdpmode but I don't remember if I actually tried with e or without, probably doesn't matter anyways since WEG 1.3.8 should take care of it but who knows)

It's likely that SMBIOS version was the culprit, and your suggestion of MacPro6,1 probably would have worked too.

So far everything seems to be in a good shape and stable.

Does /L/E need to be empty ?

 

[jaymonkey]

Does /L/E need to be empty ?

@BigOncleSam,

No ....

MacOS installs it's bundled 3rd party kext drivers in /L/E as do many apps (such as LittelSnitch, Anti virus utils ..etc).

Cheers
Jay

 

[LiveSorcerer]

Here I use 3 monitors connected to a Gigabyte Vega 56 OC Gaming 8GB, being 2x Dell UltraSharp U2419H and 1 LG 32 "4K UK550.
In Boot args I'm using agdpmod=pikera, but strangely when MacOS goes into Standby, and I try to go back to the system, using the mouse or keyboard, the screens are flashing several times and then I go back and I can enter the password to enter the system, other times it doesn't come back and I have to manually reset it.

 

[Gigamaxx]

Here I use 3 monitors connected to a Gigabyte Vega 56 OC Gaming 8GB, being 2x Dell UltraSharp U2419H and 1 LG 32 "4K UK550.
In Boot args I'm using agdpmod=pikera, but strangely when MacOS goes into Standby, and I try to go back to the system, using the mouse or keyboard, the screens are flashing several times and then I go back and I can enter the password to enter the system, other times it doesn't come back and I have to manually reset it.

Have you tried without pikera? That boot argument is for Navi RX 5xxx series.

 

[LiveSorcerer]

Have you tried without pikera? That boot argument is for Navi RX 5xxx series.

tks, works.

 

[LiveSorcerer]

The next challenge is to make Intel Wireless AC 9560 CNVi work on MacOS, both wifi and Bluetooth.