[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

[CaseySJ]

...
However, when moving over to the Designare, all but one of the ports on my PowerColor Vega 64 stopped displaying properly. With either a DisplayPort cable or HDMI (for the one HDMI port) I would see a perfectly rendered mouse cursor and a few artifacts (greenish boxes like mpeg artifacts) and everything was container in a small (5" by 6") square are of the center of my monitor. I could VNC in to the machine and see the desktop draw perfectly, but not on the monitor. If I move the display cable to the last port on the card (a DisplayPort) then the display works just fine, but no other port on the card seems to work. Has anybody run in to this before?

Hello @svandive,

Some thoughts and suggestions regarding the Vega 64:

• If you're running 10.14.5, set Platform ID to 0x3E980003. This in itself is not a cure for the problem, but it is a step in the right direction. If you need help with this, just upload your config.plist with serial numbers redacted.
• In BIOS, try enabling CSM Support. Just set the parameter to Enabled and reboot. Does it make a difference?
• Are you running the latest BIOS (vF6)?

Also if I may, I'd like to ask what is the function of these three SSDTs that are part of the Post-Install files?

SSDT-DTPG.aml, SSDT-EC.aml, and SSDT-DESIGNARE-Z390-NO-CNVW.aml

This is the easy part:

• SSDT-DTPG.aml provides a helper function for the Thunderbolt hot-plug SSDT.
• SSDT-EC.aml creates a dummy device called EC (Embedded Controller). Designare already has this device with the name H_EC. Instead of renaming it, we're just injecting EC by as a dummy device by itself. Its sole purpose is to allow USB Bus Power Properties to be injected so that high current devices such as iPads can charge.
• SSDT-DESIGNARE-Z390-NO-CNVW is explained throughout the Post Installation section of the guide. Its purpose is to render the Intel CNVi module invisible to macOS. This module contains the Intel AC-9560 WiFi/BT chipset that is not compatible with macOS.

 

[jb007]

The experience you described triggered a thought (much earlier in the day, but today being Saturday, there were many distractions):

• If eGPU drivers are attached when the Thunderbolt hot-plug SSDT is not used, then it follows that macOS really doesn't need the lion's share of the SSDT.
• Technically, macOS doesn't need the SSDT at all -- the only feature we'll lose is hot-plug capability (including ability to connect USB-C devices).

Therefore:

• What if we pare down the SSDT to the bare essentials?
• What if we inject the hot-plug property, but remove most other injected properties?
• But the question is: What constitutes the bare essentials? Just how much should we purge?

A first answer:

• What if we remove ThunderboltDROM, Pathcr, ThunderboltUUID, and a couple of other such properties?
• This has been done in the attached SSDT.
• Testing this on my spare boot disk resulted in no observable issues with the Thunderbolt devices I own, which unfortunately excludes an eGPU.

Please try the attached file (backup the previous one) and see whether it makes any difference -- does the driver for the external RX580 get loaded?

If not, I can incrementally pare the SSDT down a couple more times to see if any progress is being made. But if this begins to look like a dead end, then of course we'll have to give up until some other clue emerges.

Still the same, the RX580 display driver doesn't get attached, or if it does, it unattached quickly).
I've captured the following:

Spoiler: Screen grabs

1. First Boot. Notice that RX580 is using same address as my TB3 OCW 10GBe - Thunderbolt@190,0,0

2. Turned off eGPU, this is the 'standard' disconnect message, that I only get if I have the TB3 SSDT loaded.

3a. I turned eGPU on. 10GBe is still @ 190,0,0

3b. Now eGPU moves both the eGPU and audio to 123,0,0 & 123,0,1 respectively.

All of these where done in the same boot session.

Is the eGPU attaching to the wrong slot/PCI/TB3 address in step 1?

Back to you, I appreciate you looking at this, and understand it's hard for you since you don't have a eGPU.

 

[f10]

Regarding front panel audio jacks -- these are connected to the audio pins on the motherboard itself. I believe Layout ID 7 will enable them, but some of the rear ports might not work. Feel free to try Layout ID 7 by changing the green field from 10000000 to 07000000:
View attachment 411789
In hexadecimal, "10" is decimal 16. But "07" is still 7.

In my case, audio quality through the front audio jack is so poor and choppy that I happily switched to Layout 16 and use the rear green jack to drive a headphone.

With Layout ID 16 front audio panel is always recognized as “internal speaker” and obviously has a heavy compressor effect applied to the audio, which makes sense for a tiny internal speaker but sounds bad and unnatural on headphones etc.
I am a sound-engineer so this naturally bothered me
So I changed to layout 7 and all rear-jacks are still correctly recognized. But now when I plug-in my headphone in the front-panel the selected audio device name changes from “internal speakers” to “headphone”, just like it did for the green rear jack in layout16 already.
This is the only difference I found between 7 and 16. ID7 should be better for most users, because the front-port works normally and the green rear port is muted when the front-jack is occupied. So you can run an analogue aux cable from the back of the PC to your stereo that is auto-muted when using a headphone
Perhaps other users can confirm this advantage from layout ID7 over 16?!

Either way I want to thank you for your ongoing efforts, I got a designare 390 board for €150 and the i7 for €300 and
planned this weekend to install and try to get everything to work. Thanks to this thread I was done by friday evening after just 2 hours. Everything works - Fantastic!

 

[svandive]

Hello @svandive,

Some thoughts and suggestions regarding the Vega 64:

• If you're running 10.14.5, set Platform ID to 0x3E980003. This in itself is not a cure for the problem, but it is a step in the right direction. If you need help with this, just upload your config.plist with serial numbers redacted.
• In BIOS, try enabling CSM Support. Just set the parameter to Enabled and reboot. Does it make a difference?
• Are you running the latest BIOS (vF6)?

This is the easy part:

• SSDT-DTPG.aml provides a helper function for the Thunderbolt hot-plug SSDT.
• SSDT-EC.aml creates a dummy device called EC (Embedded Controller). Designare already has this device with the name H_EC. Instead of renaming it, we're just injecting EC by as a dummy device by itself. Its sole purpose is to allow USB Bus Power Properties to be injected so that high current devices such as iPads can charge.
• SSDT-DESIGNARE-Z390-NO-CNVW is explained throughout the Post Installation section of the guide. Its purpose is to render the Intel CNVi module invisible to macOS. This module contains the Intel AC-9560 WiFi/BT chipset that is not compatible with macOS.

I am running 10.14.5
BIOS version F6 (Came pre-loaded, but I reloaded it just to be safe)
I have CSM enabled, If I disable it I loose all but my Windows EFI boot entry... odd behavior but for another day
--
I have removed the CNVi card all together so I removed the SSDT (NO-CNVW) as well, thank you for the explanation. I added a screen shot of the SSDTs, EFI Drivers, and Kexts I am loading. I'd love your opinion if the others I am loading are necessary?

Also I should have stated I also have an Intel x520-DA2 (Dual SFP+ 10G_ card (Works GREAT)) in this machine...

 

[skittlebrau]

Are fellow Radeon VII owners running iMac19,1 or iMacPro1,1 SMBIOS with this board?

Roughly 1 in every 5 bootups I do don't seem to advance past 'AppleKeyStore failed' and error messages about 'ACM' with mentions of GFX0 timeout 60s. Sometimes WEG spits out errors during VRAM tests for the Radeon VII.

Doesn't seem to happen with iMacPro1,1. I've found also when using iMacPro1,1 that you're probably better off not setting a custom shikigva value in boot args as H264+HEVC should work fine. I found setting a manual figure ended up disabling H264.

 

[MuffinCrumbs]

Hi,

I have used the provided SSDTs, but ThunderBolt 3 is still not working. I tried the Samsung X5 for testing, as well as MacBook Pro with thunderbolt used as a target disk (pressing T at boot up).

The MacBook finds the hackintosh with thunderbolt 3, when plugged in. This can be shown in System Report > Thunderbolt.

However, on the hackintosh, the system report shows no Thunderbolt at all. It says: "Thunderbolt: No drivers are loaded".

I have tried to plug in the ThunderBolt Samsung X5 drive before turning on the hackintosh, and even after, as a hot-plug. Whilst, I know hot-plug might not work. I still tried it.

Does anyone know a fix to this? I believe I have the UEFI BIOS configured the way it was listed in the main post.


The SSDTs I am using are from the original post was well:

1. SSDT-DESIGNARE-Z390-NO-CNVW.aml
2. SSDT-DTPG.aml
3. SSDT-EC.aml
4. SSDT-PMCR.aml
5. SSDT-UIAC-DESIGNARE-Z390-V6.aml
6. SSDT-XOSI.aml
7. SSDT-Z390-DESIGNARE-TB3HP-V4

I've uploaded the screenshots of how my TB config is in the UEFI BIOS.
Any help would be appreciated.

 

[svandive]

Hi,

I have used the provided SSDTs, but ThunderBolt 3 is still not working. I tried the Samsung X5 for testing, as well as MacBook Pro with thunderbolt used as a target disk (pressing T at boot up).

The MacBook finds the hackintosh with thunderbolt 3, when plugged in. This can be shown in System Report > Thunderbolt.

However, on the hackintosh, the system report shows no Thunderbolt at all. It says: "Thunderbolt: No drivers are loaded".

I have tried to plug in the ThunderBolt Samsung X5 drive before turning on the hackintosh, and even after, as a hot-plug. Whilst, I know hot-plug might not work. I still tried it.

Does anyone know a fix to this? I believe I have the UEFI BIOS configured the way it was listed in the main post.


The SSDTs I am using are from the original post was well:

1. SSDT-DESIGNARE-Z390-NO-CNVW.aml
2. SSDT-DTPG.aml
3. SSDT-EC.aml
4. SSDT-PMCR.aml
5. SSDT-UIAC-DESIGNARE-Z390-V6.aml
6. SSDT-XOSI.aml
7. SSDT-Z390-DESIGNARE-TB3HP-V4

I've uploaded the screenshots of how my TB config is in the UEFI BIOS.
Any help would be appreciated.

I'm brand new to this board so please take what I say with a grain of salt. I can say your BIOS settings are the same as mine so that's good. I will tell you, you won't see anything listed under Thunderbolt in the "System Report" section. You should, however see your Thunderbolt 3 reported in PCI (see attached).

also I have been told the SSDT-DTPG and the SSDT-Z390-DESIGNARE-TB3HP are part of getting Thunderbolt 3 working with hot swap.

I hope this helps a little.

 

[CaseySJ]

I am running 10.14.5
BIOS version F6 (Came pre-loaded, but I reloaded it just to be safe)
I have CSM enabled, If I disable it I loose all but my Windows EFI boot entry... odd behavior but for another day
--
I have removed the CNVi card all together so I removed the SSDT (NO-CNVW) as well, thank you for the explanation. I added a screen shot of the SSDTs, EFI Drivers, and Kexts I am loading. I'd love your opinion if the others I am loading are necessary?

Also I should have stated I also have an Intel x520-DA2 (Dual SFP+ 10G_ card (Works GREAT)) in this machine...

A handful of issues:

• In drivers64UEFI, delete AptioMemoryFix-64.efi and replace it with OsxAptioFix2Drv-free2000.efi
• In Clover Configurator —> Kernel and Kext Patches click the Disabled checkbox next to each and every “USB port limit” patch. Because of the USB SSDT, these patches must be turned off or removed.
• In Clover Configurator —> System Parameters set Inject Kexts to Detect
• Also set Platform ID to 0x3E980003 via WhateverGreen (Devices —> Properties).

Please try making these changes (I can do this in a couple of hours when I get back to the computer).

 

[CaseySJ]

Hi,

I have used the provided SSDTs, but ThunderBolt 3 is still not working. I tried the Samsung X5 for testing, as well as MacBook Pro with thunderbolt used as a target disk (pressing T at boot up).

The MacBook finds the hackintosh with thunderbolt 3, when plugged in. This can be shown in System Report > Thunderbolt.

However, on the hackintosh, the system report shows no Thunderbolt at all. It says: "Thunderbolt: No drivers are loaded".

I have tried to plug in the ThunderBolt Samsung X5 drive before turning on the hackintosh, and even after, as a hot-plug. Whilst, I know hot-plug might not work. I still tried it.

Does anyone know a fix to this? I believe I have the UEFI BIOS configured the way it was listed in the main post.


The SSDTs I am using are from the original post was well:

1. SSDT-DESIGNARE-Z390-NO-CNVW.aml
2. SSDT-DTPG.aml
3. SSDT-EC.aml
4. SSDT-PMCR.aml
5. SSDT-UIAC-DESIGNARE-Z390-V6.aml
6. SSDT-XOSI.aml
7. SSDT-Z390-DESIGNARE-TB3HP-V4

I've uploaded the screenshots of how my TB config is in the UEFI BIOS.
Any help would be appreciated.

On Hackintosh we have so far been unable to activate a feature of Thunderbolt known as the Thunderbolt Local Node. Without this, we cannot connect two Macs together. Hence, Target Disk Mode, Target Display Mode, and Thunderbolt Ethernet Bridge will not work.

But the Samsung X5 should not give you any trouble. Your CLOVER/ACPI/patched folder seems okay, but you have 2 SSDTs that we don’t use:

• SSDT-PMCR
• SSDT-OSI

To troubleshoot the Samsung X5 issue, please connect the drive and run IORegistryExplorer and select File —> Save As... to save the IOReg file. Upload this file. It will show us which USB/Thunderbolt ports are in use, and what devices are connected (if any).

 

[svandive]

Thank You!!

Replaced AptioMemoryFix-64.efi
Disabled the USB Limit Patch entries
Changed Kext Inject to Detect
And I think I have set the WEG