[Success] AMD RX6000 Series working in macOS

[RUSSKIYVOLK]

There is a huge difference between the scores from Geekbench 4 and Geekbench 5! The two should never be compared, as it is like comparing Apples and Oranges.

Only about 100,000 points difference between the two scores for the same card using the older version of Geekbench compared to the score for GB5!

Does GB4 test the card for Apple's Metal framework/API?

Indeed, I didn't see that there was a fourth version

 

[Edhawk]

There a five major versions of Geekbench. None should be used to compare against another version. As each version uses different criteria when evaluating a CPU or GPU’s performance.

 

[vrjim]

Please clarify: What is output from ./gfxutil -f gfx0 ?

Assuming this is in response to my trouble getting the XTXH variant working in MacOS...
For me my card doesn't appear as gfx0. I get "DevicePath not found!"

Instead my RX 6900XT appears as:

19:00.0 1002:73af /PC01@0/BR1A@0/SL01@0/pci-bridge@0/display@0 = PciRoot(0x1)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)
19:00.1 1002:ab28 /PC01@0/BR1A@0/SL01@0/pci-bridge@0/pci1002,ab28@0,1 = PciRoot(0x1)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x1)

 

[vrjim]

I made some progress working off this SSDT which was also made for X299 systems. It has a lot of extra stuff in it I don't understand, but I can now name the pci-bridge and display devices, as well as assign a device-id. However, whenever I assign the ID I want to spoof (versus some random id), the system instantly restarts when acceleration kicks in at boot. Others have gotten this card working in MacOS... I don't understand what I'm doing wrong.

 

[vrjim]

I was able to also fix the path using a simpler method w/ WhateverGreen injection in config.plist, but I didn't realize this was working before since the system instantly restarts when I spoof the id. If I use an invalid id I can login and see the path in ioreg. Taken me a few days of troubleshooting to get to this point, but I don't know what to do next short of buying a non-XTXH GPU.

 

[miliuco]

@vrjim
Most users can use a XTXH card with the settings that you are using. I don’t know why you can’t.

 

[Edhawk]

The reason is that the X299 is not a desktop motherboard, so it doesn’t share the same device paths as most other systems.

Using gfxutil or Hackintool should enable you to obtain the correct path for the GPU.

 

[vrjim]

From what I can tell I have the correct path from gfxutil (after making the SSDT changes). When I look in ioreg it seems to confirm I have it right (see previous screenshots). But when the login tries to load the system restarts.

 

[Virtus]

Hi guys,

I recently purchased an ASUS DUAL AMD Radeon RX 6600 card.

It is well recognized in Macos Ventura, and works, except for the parasitic noises called "Coil Whine" emitted by the card.
For the moment I have this phenomenon only with safari or chrome. When I launch a web page, and I scroll, my RX 6600 emits crackling (coil whine).

Have any of you ever encountered this problem?

I wonder if it's not a problem with the management of consumption between power supply and gpu
On some forums, there is talk of an incompatibility with the power supply?

I wonder if this coil whine can't be avoided with proper settings in config.plist?

I would like to know if people here are affected by this phenomenon, or not?

Thank you for your answers


View attachment 562171

Hi brother, it's possible that ROM configuration its not properly to use in MacOS. Using RX 6900 XT the card not make any sound, smooth and silence. Especially because that gpu have switch BIOS, to silence. But in any mode not make noise. I change my older gpu RX 64 Vega...be retired !! kkkk

 

[Edhawk]

From what I can tell I have the correct path from gfxutil (after making the SSDT changes). When I look in ioreg it seems to confirm I have it right (see previous screenshots). But when the login tries to load the system restarts.

ACPI Path - \SB.PC01.BR1A.SL01.PBR0.GFX0 is what I see in the IOReg screenshot. Is that what you are using?

Your SSDT-BRG0.aml table seems to be using a different ACPI path.

It seems to be using - \SB.PC01.BR1A.SL01.BRG0.GFX0