[Success] AMD RX6000 Series working in macOS

[WrathOfThePast]

https://twitter.com/x/status/1454132824471130117

Public beta now out. let the reporting begin

@MysticalOS, @dehjomz
Newly Supported GPUs in macOS 12.1 Beta 1:
Navi23:
-73E3: Radeon Pro W6600
-73FF: RX 6600, 6600M, & 6600 XT

 

[CaseySJ]

@MysticalOS, @dehjomz
Newly Supported GPUs in macOS 12.1 Beta 1:
Navi23:
-73E3: Radeon Pro W6600
-73FF: RX 6600, 6600M, & 6600 XT

 

[CaseySJ]

A little bit of bad news for RX 6700 / 6700XT owners?​

On May 4, 2021 we reported that device-id 0x73DF for Navi 22 (RX 6700 / 6700XT) was present in AMDRadeonX6000FrameBuffer.kext in Big Sur:

[Success] AMD RX6000 Series working in macOS

At the OC picker press the space bar. There should then be the option to clear nvram. I'll give it a try, thanks for everything.

www.tonymacx86.com

Here is the full list of device-ids from that post:

<string>0x73101002 0x73121002 0x73181002 0x73191002 0x731A1002 0x731B1002 0x731F1002 0x73BF1002 0x73601002 0x73621002 0x73401002 0x73411002 0x73431002 0x73471002 0x734F1002 0x73A01002 0x73A21002 0x73A31002 0x73AB1002 0x73AE1002 0x73BF1002 0x73C01002 0x73C11002 0x73C31002 0x73DF1002 0x73E01002 0x73E11002 0x73E21002 0x73FF1002</string>

Fast forward to today's release of Monterey 12.1 public beta, where we find a revised list:

<string>0x73101002 0x73121002 0x73181002 0x73191002 0x731A1002 0x731B1002 0x731F1002 0x73BF1002 0x73601002 0x73621002 0x73401002 0x73411002 0x73431002 0x73471002 0x734F1002 0x73A01002 0x73A21002 0x73A31002 0x73AB1002 0x73AE1002 0x73AF1002 0x73BF1002 0x73E31002 0x73FF1002</string>

Namely:

• Navi 21 device ID 0x73AF has appeared in Monterey 12.1. Affects RX 6900 XT.
• Navi 22 device ID 0x73DF has disappeared in Monterey 12.1. Affects RX 6700 / 6700XT. In fact all 0x73C_ and 0x73D_ device IDs are gone.
• Navi 23 device ID 0x73E2 has been replaced with 0x73E3 in Monterey 12.1. Affects RX 6600 / 6600 XT.
• The overall list has been shortened in Monterey 12.1.

Caveat:

• Although device ID 0x73AF has appeared, it may not yet be active due to this:

 

[Gigamaxx]

A little bit of bad news for RX 6700 / 6700XT owners?​

On May 4, 2021 we reported that device-id 0x73DF for Navi 22 (RX 6700 / 6700XT) was present in AMDRadeonX6000FrameBuffer.kext in Big Sur:

[Success] AMD RX6000 Series working in macOS

At the OC picker press the space bar. There should then be the option to clear nvram. I'll give it a try, thanks for everything.

www.tonymacx86.com

Here is the full list of device-ids from that post:

<string>0x73101002 0x73121002 0x73181002 0x73191002 0x731A1002 0x731B1002 0x731F1002 0x73BF1002 0x73601002 0x73621002 0x73401002 0x73411002 0x73431002 0x73471002 0x734F1002 0x73A01002 0x73A21002 0x73A31002 0x73AB1002 0x73AE1002 0x73BF1002 0x73C01002 0x73C11002 0x73C31002 0x73DF1002 0x73E01002 0x73E11002 0x73E21002 0x73FF1002</string>

Fast forward to today's release of Monterey 12.1 public beta, where we find a revised list:

<string>0x73101002 0x73121002 0x73181002 0x73191002 0x731A1002 0x731B1002 0x731F1002 0x73BF1002 0x73601002 0x73621002 0x73401002 0x73411002 0x73431002 0x73471002 0x734F1002 0x73A01002 0x73A21002 0x73A31002 0x73AB1002 0x73AE1002 0x73AF1002 0x73BF1002 0x73E31002 0x73FF1002</string>

Namely:

• Navi 21 device ID 0x73AF has appeared in Monterey 12.1. Affects RX 6900 XT.
• Navi 22 device ID 0x73DF has disappeared in Monterey 12.1. Affects RX 6700 / 6700XT.
• Navi 23 device ID 0x73E2 has been replaced with 0x73E3 in Monterey 12.1. Affects RX 6600 / 6600 XT.
• The overall list has been shortened in Monterey 12.1.

Caveat:

• Although device ID 0x73AF has appeared, it may not yet be active due to this:

View attachment 532514

That is a not a good sign for 6700 cards.

 

[WrathOfThePast]

A little bit of bad news for RX 6700 / 6700XT owners?​

On May 4, 2021 we reported that device-id 0x73DF for Navi 22 (RX 6700 / 6700XT) was present in AMDRadeonX6000FrameBuffer.kext in Big Sur:

[Success] AMD RX6000 Series working in macOS

At the OC picker press the space bar. There should then be the option to clear nvram. I'll give it a try, thanks for everything.

www.tonymacx86.com

Here is the full list of device-ids from that post:

<string>0x73101002 0x73121002 0x73181002 0x73191002 0x731A1002 0x731B1002 0x731F1002 0x73BF1002 0x73601002 0x73621002 0x73401002 0x73411002 0x73431002 0x73471002 0x734F1002 0x73A01002 0x73A21002 0x73A31002 0x73AB1002 0x73AE1002 0x73BF1002 0x73C01002 0x73C11002 0x73C31002 0x73DF1002 0x73E01002 0x73E11002 0x73E21002 0x73FF1002</string>

Fast forward to today's release of Monterey 12.1 public beta, where we find a revised list:

<string>0x73101002 0x73121002 0x73181002 0x73191002 0x731A1002 0x731B1002 0x731F1002 0x73BF1002 0x73601002 0x73621002 0x73401002 0x73411002 0x73431002 0x73471002 0x734F1002 0x73A01002 0x73A21002 0x73A31002 0x73AB1002 0x73AE1002 0x73AF1002 0x73BF1002 0x73E31002 0x73FF1002</string>

Namely:

• Navi 21 device ID 0x73AF has appeared in Monterey 12.1. Affects RX 6900 XT.
• Navi 22 device ID 0x73DF has disappeared in Monterey 12.1. Affects RX 6700 / 6700XT.
• Navi 23 device ID 0x73E2 has been replaced with 0x73E3 in Monterey 12.1. Affects RX 6600 / 6600 XT.
• The overall list has been shortened in Monterey 12.1.

@byteminer -- your 6900XT with device ID 0x73AF is finally supported natively!

@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.

 

[CaseySJ]

@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.

 

[WrathOfThePast]

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.

 

[etorix]

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.

 

[mrt1976]

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

 

[CaseySJ]

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).