Contribute
Register

Z490 & Z590 - Will Z590 ever have macOS Support ?

Hello to all of you.

I have a Z590 VISION D build working nicely, but the DP/HDMI audio coming from my dGPU is working terrible. I'm experiencing a crackling issues when I'm listening to music through the dGPU HDMI or DP (YouTube, VLC, etc.), audio through the onboard ALC4080 is working perfectly. My build is: Z590 VISION D (F7 BIOS), i7-11700K, Gigabyte Radeon RX580 Gaming 4GB with stock BIOS. I have working AppleVTD incl. enabled VT-d. I'm experiencing this issue on macOS Big Sur, Monterey and Ubuntu 20.04, 21.04, 22.10. On Windows 11 everything is working fine, no issues. I'm start to thinking it's a hardware problem or a BIOS setting. A strange effect: when I put load to the GPU the crackling goes away - no more crackling (both, macOS and Ubuntu). I have tried the GPU on my old build Gigabyte Z270X Gaming 5 with i7-7700K, but no crackling issues. Everything works perfectly.

What I have tried so far:
- CPU PCIe settings: PCIe Gen 1, 2, 3, 4, Auto - nothing changed
- PCH CPIe settings: PCIe Get 1, 2, 3, Auto - nothing changed
- VT-d: Enabled, Disabled - nothing changed
- XMP memory profile: Enabled, Disabled - nothing changed
- CPU C States: Disabled, Enabled - nothing changed

HDMI/DP audio crackling goes away, when:
- I put load to the GPU

Thanks, any help is appreciated.

It's fixed. For more information please read this.
 
Hey @CaseySJ

I am still trying to get hotplug working on the Z590i Vision D. Bios F7.

I noticed the following behavior, maybe this helps you.

1. If I don't use any SSDT-DTGP/SSDT-TB3HP, Thunderbolt works but hotplug doesn't. And Sleep causes a kernel panic with restart, because my eGPU is connected via Thunderbolt.

2. I I use the Hackindrom SSDT for the Titan Ridge Z690 Platform (or the Asus Z590I SSDT) as it is, Thunderbolt isn't initiated under macOS and I don't get any video out of my eGPU.

3. If I use the Hackindrom SSDT but remove the HRUS method, it works and even Wake from Sleep is working. But hotplug doesn't work. And funny thing is, that my RP05 device is causing a wake from sleep soon after it fell asleep.

2021-12-27 20:12:47.397502+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: XDCI CNVW RP05

I remove this section here:
If (CondRefOf (\_SB.PC00.RP05.HRUS))
{
Scope (HRUS)
{
Method (_STA, 0, NotSerialized) // _STA: Status
{
Return (Zero)
}
}
}

So it seems that the HRUS device has something to do with it.

Attached are images of Thunderbolt IOregistry without the HRUS method.

Hope this helps,
Chris
 

Attachments

  • Screen Shot 2021-12-27 at 20.11.50.png
    Screen Shot 2021-12-27 at 20.11.50.png
    925.5 KB · Views: 43
  • Screen Shot 2021-12-27 at 20.12.04.png
    Screen Shot 2021-12-27 at 20.12.04.png
    760.7 KB · Views: 37
  • SSDT-TB3-HackinDROM_after removing HRUS method.aml
    2.1 KB · Views: 33
Hello @SchmockLord19

Deleting HRUS device is necessary for the new Thunderbolt SSDT to take effect. However, @dehjomz found that hot plug does not work on Gigabyte Z590 boards with macOS. It seems to be a Gigabyte BIOS problem.
 
Unfortunately the Thunderbolt hot plug does not work on Gigabyte Z590 VISION D with Windows as well. It seems to be a big issue with the Gigabyte BIOS. It's a shame for such a expensive board... :(
 
Unfortunately the Thunderbolt hot plug does not work on Gigabyte Z590 VISION D with Windows as well. It seems to be a big issue with the Gigabyte BIOS. It's a shame for such a expensive board... :(
Hotplug is mostly working in windows on the Z590 Vision D, and on Linux too. But, and the big but is: not all thunderbolt devices are hot plugging. Specifically, some Alpine Ridge devices with an Intel JHL6240 controller inside seem to have an incompatibility with Maple Ridge NVM 26, 26.5 and 29 in terms of hot plugging.

But Alpine Ridge devices with JHL6340, Titan Ridge, and Goshen Ridge thunderbolt devices hotplug just fine with the Z590 Vision D in Windows and Linux. They also hotplug with macOS, but a sleep/wake cycle is required first so that the ACPI routine(s) necessary for TB hot plugging can be executed, so that the device(s) are registered with the macOS kernel.
 
Ok, thanks. Yeah, because the Z590i Vision D is not getting fixed I just ordered a new ASUS ROG Strix Z590-I Gaming WiFi.
 
Hotplug is mostly working in windows on the Z590 Vision D, and on Linux too. But, and the big but is: not all thunderbolt devices are hot plugging. Specifically, some Alpine Ridge devices with an Intel JHL6240 controller inside seem to have an incompatibility with Maple Ridge NVM 26, 26.5 and 29 in terms of hot plugging.

But Alpine Ridge devices with JHL6340, Titan Ridge, and Goshen Ridge thunderbolt devices hotplug just fine with the Z590 Vision D in Windows and Linux. They also hotplug with macOS, but a sleep/wake cycle is required first so that the ACPI routine(s) necessary for TB hot plugging can be executed, so that the device(s) are registered with the macOS kernel.
Thanks for your reply. Sad but I have 3 Thunderbolt devices and all of them are connecting from cold boot only - so they are all with the incompatibility chips inside. Nevertheless I'm happy to hear that there are a lot of device compatible with the TB controller.
 
Ok, thanks. Yeah, because the Z590i Vision D is not getting fixed I just ordered a new ASUS ROG Strix Z590-I Gaming WiFi.
Good choice, I can confirm Hot Plug is working with it.

 
So, in the meantime I have upgraded Monterey. TB hotplug still works. So far so good.

Now I have the issue, that my W5500 is not used as main display anymore.

I have a 3090 which is inside my case in the PCIE and a W5500 which is in the eGPU Case Razer Core X.

Both are getting detected. But how can I disable the 3090 and tell MacOS to use the W5500?

Before hotplug was working, I just disabled the 3090 using the attached Device Properties and then macOS initialized the W5500 via Thunderbolt instead. But somehow they don't work anymore. When I use them the W5500 Display stays black. And without them, macOS is going into the VESA mode and displays via my 3090 in the low graphics mode.

I guess because the W5500 is detected as GFX1 instead of GFX0.

I think I need something like an SSDT which disabled the 3090 as my GFX0 and injects the W5500 as GFX0 instead.

I have already started the SSDT, but this only disables the 3090. Maybe someone can help me from there or has a better idea.

Attached are my PCIE devices. And these are the location paths from Windows:

3090:

\_SB.PC00.PEG1.PEGP


PCIROOT(0)#PCI(0100)#PCI(0000)
ACPI(_SB_)#ACPI(PC00)#ACPI(PEG1)#ACPI(PEGP)


W5500:
PCIROOT(0)#PCI(1C04)#PCI(0000)#PCI(0300)#PCI(0000)#PCI(0100)#PCI(0000)#PCI(0000)#PCI(0000)
ACPI(_SB_)#ACPI(PC00)#ACPI(RP05)#ACPI(PXSX)#PCI(0300)#PCI(0000)#PCI(0100)#PCI(0000)#PCI(0000)#PCI(0000)
ACPI(_SB_)#ACPI(PC00)#ACPI(RP05)#ACPI(HRUS)#PCI(0300)#PCI(0000)#PCI(0100)#PCI(0000)#PCI(0000)#PCI(0000)

IOService:/AppleACPIPlatformExpert/PC00@0/AppleACPIPCI/RP05@1C,4/IOPP/UPSB@0/IOPP/DSB3@3/IOPP/pci-bridge@0/IOPP/pci-bridge@1/IOPP/pci-bridge@0/IOPP/pci-bridge@0/IOPP/display@0
 

Attachments

  • Screen Shot 2022-01-03 at 11.29.19.png
    Screen Shot 2022-01-03 at 11.29.19.png
    30.9 KB · Views: 35
  • pcidevices.plist
    12.6 KB · Views: 30
  • Screen Shot 2022-01-02 at 23.07.29.png
    Screen Shot 2022-01-02 at 23.07.29.png
    93.5 KB · Views: 37
  • SSDT-Disable-nvidia.aml
    211 bytes · Views: 29
  • Location of the GFX0:3090.png
    Location of the GFX0:3090.png
    167 KB · Views: 34
  • Location of the GFX1:W5500.png
    Location of the GFX1:W5500.png
    71.7 KB · Views: 40
  • Screen Shot 2022-01-03 at 12.36.57.png
    Screen Shot 2022-01-03 at 12.36.57.png
    198.4 KB · Views: 41
Last edited:
Back
Top