[SUCCESS] Ongoing Status of Designare Z390 with i7-9700K

[scottkendall]

I have a Thunderbolt 2 Drive with a TB3 ----> TB2 Dongle. The Drive works as long as I boot up with it, and do not unplug it or let my system sleep it will remain. If either happen the drive will unmount and you will need to reboot to get it back. I would guess that would be the same for any other hardware.

 

[Markzers]

Hey guys thought I would chime in here and see if we can figure out this TB3 thing. I have a z390 designare 8700k with dual vegas. Trying to get my TB pro audio interface working. It's an Antelope Zen Tour.

I notice that the interface always shows up in IOReg, even hotplugging shows the red text/green text, according to the text even the TB drivers are installed and loaded, but I can not for the life of me get it to actually recognize the audio interface.

Messing around with the SSDT aml the best I could get was it to be recognized as a "unknown expresscard" with a "power off low power device" icon/button in the top bar... trashed that and currently using the same .aml Casey is. Also the interface does work fine over usb, but would really like TB for the latency. Attached are some screens. First PCI screenshot is without interface plugged in, further is with plugged in.
Feels like we are close but need to tweak SSDT more, since we are not using a thunder ridge card in a pci slot, but using built in mobo. However the built in mobo TB3 does show up under PCI0/RP05 in IOReg without any SSDT installed. I have not been able to get anything to show up in the thunderbolt tab other than the default no drivers loaded. I have tried disabling/enabling TB controller with different options in BIOS, doesn't seem to affect any of these results.

 

[scottkendall]

Hey guys thought I would chime in here and see if we can figure out this TB3 thing. I have a z390 designare 8700k with dual vegas. Trying to get my TB pro audio interface working. It's an Antelope Zen Tour.

I notice that the interface always shows up in IOReg, even hotplugging shows the red text/green text, according to the text even the TB drivers are installed and loaded, but I can not for the life of me get it to actually recognize the audio interface.

So you can plug and unplug your TB devices and they leave and return to the IOreg? IE the red and green text? You might not ever see anything in TB even if it is working. Are you not able to use the Audio device in your audio application? Because the stuff under PCI is purely cosmetic.

 

[Markzers]

So you can plug and unplug your TB devices and they leave and return to the IOreg? IE the red and green text? You might not ever see anything in TB even if it is working. Are you not able to use the Audio device in your audio application? Because the stuff under PCI is purely cosmetic.

Correct they leave and return via red/green text. However no I can't use the audio device, it does not appear anywhere in sound preferences like it does when attached via USB or TB to my real macbook. I'm currently looking at the IOReg on my real macbook with it plugged in and trying to match what's missing via SSDT. Surprisingly most of it is the same.

Does anyone know how to return a boolean in a .aml SSDT file?
For example :
"PCI-Thunderbolt",
One

in aml Store function returns
PCI-ThunderBolt -> Number -> 0x1 in IOREG.

How do I store a boolean True instead of a string/data/number?

 

[CaseySJ]

Correct they leave and return via red/green text. However no I can't use the audio device, it does not appear anywhere in sound preferences like it does when attached via USB or TB to my real macbook. I'm currently looking at the IOReg on my real macbook with it plugged in and trying to match what's missing via SSDT. Surprisingly most of it is the same.

Does anyone know how to return a boolean in a .aml SSDT file?
For example :
"PCI-Thunderbolt",
One

in aml Store function returns
PCI-ThunderBolt -> Number -> 0x1 in IOREG.

How do I store a boolean True instead of a string/data/number?

The TB3 SSDT I posted may be an early version. Have you tried getting the latest version from KGP's repository of SSDTs? The file name is "SSDT-X299-TB3HP.dsl". You'll have to globally replace RP01 with RP05 for your Designare Z390 board.

You can compile DSL to AML with MaciASL. Be sure to use Rehabman's latest version from here.

 

[CaseySJ]

Thank you for the updates!
Hope you manage to make a build guide when you get it all working.
This board combined with the RX580 and a i7-8700k is what I'm looking at for building an DAW / Audio workstation with an Apollo 8P Thunderbolt card. If TB3 works, I'll be ordering one ASAP.

My OWC 14-port TB3 dock should be delivered this evening. I can then test a limited number of additional devices through this dock: monitor, SD cards, gigabit Ethernet, external USB 3 hard drives. I'll check for hot-plug and sleep/wake capabilities. Unfortunately I don't have any native TB3 audio interfaces or native TB3 hard drive enclosures.

And certainly once the system is operational to a certain "reasonable" threshold, I'll create a Build Guide.

 

[jaymonkey]

Status: Internal Graphics UHD 630

• This has been a real pain. I have tried using iGPU as the only graphics device (removing the RX580 completely), trying different Platform IDs, trying different graphics Device IDs, following every post-installation Graphics fix procedure I could find, using Intel FB-Patcher to change Framebuffer Connector Types and enabling/disabling various connectors, all to no avail.

@CaseySJ,

You should really configure the IGPU with a headless PaltformID .. which is how real Macs with AMD GPUS and IGPU's are configured (IE: IGPU is enabled but no physical display ports) .. This way MacOS will use the IGPU for Intel QuckSync (used when previewing video and pictures in finder) and Airplay mirroring + a few other IGPU optimised features.

See the Headless PlatformID instructions in the WhatEverGreen section of this guide :-

https://www.tonymacx86.com/threads/an-idiots-guide-to-lilu-and-its-plug-ins.260063/

Cheers
Jay

 

[CaseySJ]

@CaseySJ,

You should really configure the IGPU with a headless PaltformID .. which is how real Macs with AMD GPUS and IGPU's are configured (IE: IGPU is enabled but no physical display ports) .. This way MacOS will use the IGPU for Intel QuckSync (used when previewing video and pictures in finder) and Airplay mirroring + a few other IGPU optimised features.

See the Headless PlatformID instructions in the WhatEverGreen section of this guide :-

https://www.tonymacx86.com/threads/an-idiots-guide-to-lilu-and-its-plug-ins.260063/

Cheers
Jay

Thanks Jay. Your Lilu guide is very helpful and I must have read it at least twice when I started the build. Based on what you said above, the graphics behavior I'm seeing makes sense -- in my current dual-GPU setup, the iGPU does not appear in System Report, but does appear in IOReg. And VideoProc confirms that QuickSync and other "compute" units are enabled.

When I started building the Hackintosh, I was using only the iGPU (single GPU configuration).

Because the UHD630 in the 9th generation Core processor has a different device ID (3E98), neither MacOS nor WhateverGreen recognized it. So with only the iGPU installed (RX580 removed) and SMBIOS set to a single-GPU Mac model, MacOS simply defaulted to the Apple graphics driver, and System Report could not identify the iGPU by name. With the default driver, I was able to get video output from the HDMI port on the Designare motherboard.

And this is why I could complete the basic Mojave installation with UniBeast -- because I had basic (non-accelerated) video output from the HDMI port.

But of course I wanted to get accelerated graphics with just the iGPU in the system. So I spoofed the Device ID to 3E92, which is also a UHD630, but from the 8th gen Core processor. Subsequently, the HDMI port (which is also the only video output port on this motherboard) went blank, but the system booted normally otherwise. Using a remote desktop connection via TeamViewer confirmed that MacOS was now properly recognizing the UHD630 and the AppleIntelFramebuffer was activated! But of course there was no video output...

So I struggled with this for a while. And when all attempts failed, I decided to install the AMD RX 580 and switch to a dual-GPU configuration, which is working fine now.

However, it would be nice to have the 3E98 device ID supported, either by a subsequent release of Mojave or a subsequent release of WhateverGreen.

 

[jaymonkey]

However, it would be nice to have the 3E98 device ID supported, either by a subsequent release of Mojave or a subsequent release of WhateverGreen.

Ok Understood ... I did not realise that 9th Gen CPU's use a different device ID for the IGPU to 8th Gen .. seems odd as i thought both where UHD 630 .... i guess you've already tried spoofing it as a 8th gen IGPU ?

I'm sure it wont be long before we see an update to WhatEverGreen for the new 9th Gen IGPU's ...

Might be worth posting on the official WEG support thread with your IGPU device id ...

Cheers
Jay

 

[scottkendall]

However, it would be nice to have the 3E98 device ID supported, either by a subsequent release of Mojave or a subsequent release of WhateverGreen.

It is possible that it could be fixed as early at 14.2 as been confirmed by a member currently using the beta.


When you spoofed the 630 and lost video did you try TB -----> HDMI were you on SM 18,1?