Contribute
Register

[Success] AMD RX6000 Series working in macOS

@CaseySJ, I investigated the 73AF support as according to MacRumors, it came with 12.0.1. However, upon my testing on both 12.0.1 & 12.1 Beta, it doesn't work and causes kernel panics. Furthermore, the eGPU Apple Support article still says it's not supported.

Upon further investigation, support is partially added: AMDRadeonX6000Framebuffer.kext includes 73AF while AMDRadeonX6000.kext & AMDRadeonX6000HWServices.kext do not... no changes in the 12.1 Beta.

I'm spoke to Apple Support and they immediately gave up & scheduled a manager to call me to address the issue, but I expect to get no where considering my findings.
See that last line in my quoted text:
@byteminer -- your 6900XT with device ID 0x73AF is finally supported natively!
That line was removed moments after being posted. If you refresh the page you'll see what I mean.
 
See that last line in my quoted text:

That line was removed moments after being posted. If you refresh the page you'll see what I mean.
I did see that right after I replied, but I wanted to set the record straight for others that may not of noticed regardless. I don't understood why MacRumors claims it's support as of 12.0.1. I left a comment over there asking them on whether they have evidence to back their claims.
 
1. Wouldn't my existing dGPU be causing an issue since it's assigned "GFX0"? Should I edit the SSDT to say "GFX1"?

2. Would the first nested PCI-bridge be "BRG1" since the first Pci-bridge is "pci-bridge@1"?
As far as I understand this stuff, you can give any legal ACPI name you want. The trick is that all unnamed devices have to be defined one by one and in order. "Device" means that it has an address (@0, @1), and this address is to be reflected in the SSDT; IOReg entities without an address (IOPP) do not exist in ACPI, do not belong in the ACPI path and should not be in the SSDT. You can't jump to the GPU if there are three PCI bridges without ACPI names in the way; you have to define the first bridge @1, then the second bridge @0 within the first bridge, the third bridge @0 within the second, and finally you get to the eGPU.

SSDT-EGFX.aml attempts to does that. If it works, then assigning device-id through "Device Properties" should work.

SSDT-EGFX-SPOOF.aml attempts to define the path and to spoof the device-id to <BF730000> within the SSDT itself, without further requiring a Device Properties entry for WEG patching.
Try either, but not both at the same time.
 

Attachments

  • SSDT-EGFX-SPOOF.aml
    223 bytes · Views: 111
  • SSDT-EGFX.aml
    151 bytes · Views: 101
Hi, I think I now have Big Sur up and running. I used a 1070ti for the build and as expected it's very laggy. I plan to upgrade to a 6800XT or 6900XT. Please could you let me know if this will run out of the box: https://www.powercolor.com/product?id=1607314166

If not, would you mind letting me know what steps are needed?

Thanks in advance.

Nick
 
Hi, I think I now have Big Sur up and running. I used a 1070ti for the build and as expected it's very laggy. I plan to upgrade to a 6800XT or 6900XT. Please could you let me know if this will run out of the box: https://www.powercolor.com/product?id=1607314166

If not, would you mind letting me know what steps are needed?

Thanks in advance.

Nick
This one should be fine. It’s likely that it has device ID 0x73BF, which is natively recognized. But on the off chance that it has the unsupported device ID 0x73AF, then we can still make it work by spoofing its device ID with a simple device property. Just install it in a PCIe slot (not eGPU).
 
Just install it in a PCIe slot (not eGPU).
Lol. I'm hoping to change that in the near feature. I spoke to Apple's engineers today to get them to add support for 0x73af... it could be as soon as next week (soonest Weds. or Thursday, if not more than likely the following Weds. or Thursday). I have a follow up call with the engineers on Thursday next week. I wasn't able to get them to add Navi22, unfortunately. Everyone may be out of luck for the 6700 XT. They're more likely to add Navi24 GPUs than the 6700 XT which aren't even released yet.

In the meantime, I'm going to try the SSDTS @etorix provided.
 
SSDT-EGFX.aml attempts to does that. If it works, then assigning device-id through "Device Properties" should work.
I just looked at the code for the SSDT-EGFX.aml you provided... I've actually tried that exact code a few days ago and it didn't work (it was one of the earliest things I tried), so I'm down to trying the SSDT-EGFX-SPOOF.aml you provided. I'll let you know how that goes tomorrow.
 
Hi, I think I now have Big Sur up and running. I used a 1070ti for the build and as expected it's very laggy. I plan to upgrade to a 6800XT or 6900XT. Please could you let me know if this will run out of the box: https://www.powercolor.com/product?id=1607314166

If not, would you mind letting me know what steps are needed?

Thanks in advance.

Nick
@mrt1976 : That should work out of the box, but you never know!
 
I just looked at the code for the SSDT-EGFX.aml you provided... I've actually tried that exact code a few days ago and it didn't work (it was one of the earliest things I tried), so I'm down to trying the SSDT-EGFX-SPOOF.aml you provided. I'll let you know how that goes tomorrow.
SSDT-EGFX-SPOOF is SSDT-EGFX with an additional _DSM method to inject the device-id. If the simple SSDT doesn't work, the more elaborate will not work either. @CaseySJ is probably right that we shouldn't make static changes to removable devices. And it just cannot work if the removable device is not fully initialised when the ACPI table is loaded.
Well, I suppose it was worth trying. Out of curiosity, does IOReg shows the renames along the path (PCI0.PEG2.UPSB.DSB1.UPS0.BRG1.BRG0.BRG0.EGFX)?
 
Public beta now out. let the reporting begin
Confirming PowerColor RED DEVIL Radeon RX 6600 XT 8GB GDDR6 PCI Express 4.0 ATX Video Card 6600XT 8GBD6-3DHE/OC working with 2020 MacBook Pro and Razor Core X via Thunderbolt and using Monterey Beta 12.1.
EDIT: Next step will be to get it into a PC and get it working but the new drivers seem to be working.
 
Last edited:
Back
Top