Contribute
Register

[Success] AMD RX6000 Series working in macOS

Joined
Sep 19, 2011
Messages
403
Motherboard
XPS 13 9360
CPU
i7-8550U
Graphics
UHD 620
Mac
  1. MacBook Pro
That was my forum typo - I wish it were that easy :)

Have attached my ioreg, gfxutil output and SSDT-BRG0.aml
OpenCore says: ACPI Error: [\_SB_.PC00.TRP0.PXSX] Namespace lookup failure, AE_NOT_FOUND
 

Attachments

  • 6650XT.zip
    865 KB · Views: 38

Edhawk

Moderator
Joined
Aug 2, 2013
Messages
4,910
Motherboard
Asus TUF Z390 Gaming
CPU
i5-8500
Graphics
RX 580
Mac
  1. iMac
  2. MacBook Air
  3. MacBook Pro
Mobile Phone
  1. iOS
Have you tried using Corpnewt's SSDTTime script to sort out the missing bridge entries from your GPU's APCI address?

The gfxutil.txt file you provided shows the following:

/PC00/[email protected]/[email protected]/[email protected]/[email protected]/[email protected]/[email protected]

Option #9 in the SSDTTime script should when used with your system DSDT.aml be able to fill out the full APCI path, i.e. translate the pci-bridge entries, so you can use the full address in the SSDT.

Screenshot 2023-03-06 at 19.19.35.png Select option 9 - PCI Bridge


Devices BRG1 and Device BRG2 are probably wrong in the SSDT-BRG0.aml table.

Screenshot 2023-03-06 at 19.28.07.png
 
Joined
Oct 4, 2018
Messages
1,220
Motherboard
Gigabyte C246-WU4
CPU
E-2278G
Graphics
WX7100
Mac
  1. MacBook Pro
  2. Mac mini
That was my forum typo - I wish it were that easy :)
Obviously, I wished that too!
Addresses are correct. The ACPI error message look like the first bridge PXSX is not found, although it does have a name. Should we try to define it as well?
 

Attachments

  • SSDT-BRG.aml
    140 bytes · Views: 16
Joined
Sep 19, 2011
Messages
403
Motherboard
XPS 13 9360
CPU
i7-8550U
Graphics
UHD 620
Mac
  1. MacBook Pro
Have you tried using Corpnewt's SSDTTime script to sort out the missing bridge entries from your GPU's APCI address?

The gfxutil.txt file you provided shows the following:

/PC00/[email protected]/[email protected]/[email protected]/[email protected]/[email protected]/[email protected]

Option #9 in the SSDTTime script should when used with your system DSDT.aml be able to fill out the full APCI path, i.e. translate the pci-bridge entries, so you can use the full address in the SSDT.
Ok so making some progress...

Using SSDTTime's script I have a new BRG0 SSDT. It seems to be recognizing the device but it's now booting to a blank screen. Here's the SSDT generated...

Code:
DefinitionBlock ("", "SSDT", 2, "CORP", "PCIBRG", 0x00000000)
{
    /*
     * Start copying here if you're adding this info to an existing SSDT-Bridge!
     */
    External (\_SB.PC00, DeviceObj)
    Scope (\_SB.PC00)
    {
        Device (BRG0)
        {
            Name (_ADR, 0x00070000)
            Device (BRG1)
            {
                Name (_ADR, Zero)
                Device (BRG2)
                {
                    Name (_ADR, 0x00010000)
                    Device (BRG3)
                    {
                        Name (_ADR, Zero)
                        Device (BRG4)
                        {
                            Name (_ADR, Zero)
                            // Customize this device name if needed, eg. GFX0
                            Device (GFX0)
                            {
                                // Target Device Path:
                                // PciRoot(0x0)/Pci(0x7,0x0)/Pci(0x0,0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)
                                Name (_ADR, Zero)
                            }
                        }
                    }
                }
            }
        }
    }
    /*
     * End copying here if you're adding this info to an existing SSDT-Bridge!
     */
}
 

Edhawk

Moderator
Joined
Aug 2, 2013
Messages
4,910
Motherboard
Asus TUF Z390 Gaming
CPU
i5-8500
Graphics
RX 580
Mac
  1. iMac
  2. MacBook Air
  3. MacBook Pro
Mobile Phone
  1. iOS
How are you connecting the display to the GPU?
  • DP to DP, HDMI to HDMI?
  • Are you using any adapters or adapter cables?

Do you have the agdpmod=pikera boot argument in your config.plist?

Have you tried agdpmod=ignore boot argument in place of the pikera argument?
 
Joined
Sep 19, 2011
Messages
403
Motherboard
XPS 13 9360
CPU
i7-8550U
Graphics
UHD 620
Mac
  1. MacBook Pro
Obviously, I wished that too!
Addresses are correct. The ACPI error message look like the first bridge PXSX is not found, although it does have a name. Should we try to define it as well?

Thanks for this. I still get the same ACPI Error: [\_SB_.PC00.TRP0] Namespace lookup failure, AE_NOT_FOUND, so it's actually the TRP0 device that's the issue. The SSDTTime-generated SSDT is the only one that works.
 
Joined
Sep 19, 2011
Messages
403
Motherboard
XPS 13 9360
CPU
i7-8550U
Graphics
UHD 620
Mac
  1. MacBook Pro
How are you connecting the display to the GPU?
  • DP to DP, HDMI to HDMI?
  • Are you using any adapters or adapter cables?

Do you have the agdpmod=pikera boot argument in your config.plist?

Have you tried agdpmod=ignore boot argument in place of the pikera argument?

So I'm using an eGPU (Razer Core X) connected via thunderbolt cable. The TB mapping is correct: in fact, it works fine with the RX580 which boots up without any need for additional config. agdpmod=pikera/ignore doesn't make a difference at this point...
 
Joined
Oct 4, 2018
Messages
1,220
Motherboard
Gigabyte C246-WU4
CPU
E-2278G
Graphics
WX7100
Mac
  1. MacBook Pro
  2. Mac mini
Using SSDTTime's script I have a new BRG0 SSDT. It seems to be recognizing the device but it's now booting to a blank screen. Here's the SSDT generated...
It defines everything from, and including, TRP0 :eek:
OK, maybe this is just "the safest, fool-proof, way" to ensure that there's a fully named ACPI path. No error message with this one?

I trust you have the spoofing information as DeviceProperties in config.plist. Is this applied?
 
Top