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

[luckyal]

For those interested in getting the stock Intel CNVi Bluetooth going with this board, I just wrapped up a short guide here.

 

[burgush]

A USB-C cable is NOT the same as a TB3 cable... You need proper TB cables for the Apollo

So i think the first thing to do is to buy this two and then do what @CaseySJ said?

Apple Cable Thunderbolt (0,5 m) - Adaptador - Comprar en Fnac

Adaptador: Apple Cable Thunderbolt (0,5 m). 5% de descuento para Socios. Compra la mejor tecnología con las garantías Fnac.

www.fnac.es

Adaptador Apple MMEL2ZM/A de Thunderbolt 3 (USB-C) a Thunderbolt 2 - Adaptador - Comprar en Fnac

Adaptador: Adaptador Apple MMEL2ZM/A de Thunderbolt 3 (USB-C) a Thunderbolt 2. 5% de descuento para Socios. Compra la mejor tecnología con las garantías Fnac.

www.fnac.es

 

[zipb]

So i think the first thing to do is to buy this two and then do what @CaseySJ said?

Apple Cable Thunderbolt (0,5 m) - Adaptador - Comprar en Fnac

Adaptador: Apple Cable Thunderbolt (0,5 m). 5% de descuento para Socios. Compra la mejor tecnología con las garantías Fnac.

www.fnac.es

Adaptador Apple MMEL2ZM/A de Thunderbolt 3 (USB-C) a Thunderbolt 2 - Adaptador - Comprar en Fnac

Adaptador: Adaptador Apple MMEL2ZM/A de Thunderbolt 3 (USB-C) a Thunderbolt 2. 5% de descuento para Socios. Compra la mejor tecnología con las garantías Fnac.

www.fnac.es

Can't read Spanish. But you have to go from TB3 (Z390) to TB2 (your UAD) I'm using a Startech adapter for TB3-TB2. But the Apple TB3-TB2 thingy will work too.

 

[pianistslogic]

Two suggestions worth trying one by one to see which, if any, solves the problem:

• Enable "High Current" as shown.
  View attachment 409009
• Copy the attached SSDT-EC.aml to CLOVER/ACPI/patched.

Thanks for the reply!
Neither of those two options worked, unfortunately.

Will be getting a powered USB hub over the next few days. So not too much of an issue but still.

It's weird though. When I plug a USB3.0 stick into the front port, it draws +/- 900 mA. But the iPad doesn't go any higher than 500mA (see screenshots).

Edit: come to think of it, that makes some sense considering the iPad runs on USB 2.0. Yet, I don't understand why it's not properly loading even though it's supposedly maxing out its draw?

 

[burgush]

Can't read Spanish. But you have to go from TB3 (Z390) to TB2 (your UAD) I'm using a Startech adapter for TB3-TB2. But the Apple TB3-TB2 thingy will work too.

Yeah, sorry but im in Madrid so this is one of the stores that actually have pieces for this process. So both are safe or which is the safest one?

 

[AlBeast]

Some additional comments after a closer look:

• In your ACPI section there is a patched named "ACPI PATCH". What is that for?
• In SMBIOS section, the Trust checkbox should be turned on.
• In Kernel and Kext Patches, all 4 of the USB port limit patches should be disabled. The bottom 2 are still enabled.

I've made these changes in the attached config.plist. I've checked-on the "disabled" flag for "ACPI PATCH", but if this patch is absolutely necessary, please uncheck that column.

Additionally, if you're running 10.14.5 you may delete SSDT-Z390-VEGA64.aml from CLOVER/ACPI/patched.

When you run the BruceX test, maybe the Vega is doing 100% of the work?


Unfortunately my video editing adventures are limited to iMovie! So if anyone reading this can offer any input, please do so.

Thanks for that! The ACPI patch recently seems necessary on a bunch of Z390 boards with their latest BIOSes; otherwise we get stuck on an early apfs_driverloading. I don't know the specifics about its working, but the current Designare BIOS does indeed not require it.

My problem is exactly the same as bsholbrook, I believe. A flatline anywhere I look for the HD630; it doesn't seem to partake. Oddly enough, this was one of the reasons I switched to the Designare, besides the IGP + TB3 AIC combination that didn't work well on the ASRock Z390 Gaming SLI.

Appreciate your look at this. I've finally had a chance to swap your recommended Clover folder into place. Post reboot headless mode is still not working. I compared your written details to zipped Clover director and found a few small variances:

• the appleintelcpupm was not checked; I have a Desigare board so I checked that.
• the platform id in the config.plist was 0300923E vs the 0300983E listed above. I've tried both without either working.

Any other thoughts on what may be going on? What other details can I share that would help identify where things go off the rails?

Here is a view of the Intel Power Gadget. You can see the CPU rates jump during H265 playback, and the GFX graph remains flat. Also, you already said you were no familiar with the VDADecoderChecker. So this may not help matters. It says there is a problem. It will normally report SUCCESS when headless mode is operating properly.

View attachment 409096

VDADecoderChecker results for me are:

GVA info: Successfully connected to the Intel plugin, offline Gen95 

An error was returned by the decoder layer. This may happen for example because of bitstream/data errors during a decode operation. This error may also be returned from VDADecoderCreate when hardware decoder resources are available on the system but currently in use by another process.

VDADecoderCreate failed. err: -12473

bsholbrook did you try 10.14.4 as well? All my testing was done through 10.14.5 with either SMBIOS 18,3 or 19,1.

Perhaps we have a better chance of finding our answer(s) in the Whatevergreen Intel Framebuffer Patching thread.

 

[zipb]

Yeah, sorry but im in Madrid so this is one of the stores that actually have pieces for this process. So both are safe or which is the safest one?

I've used both, they worked fine for connecting TB2 UAD Apollo's
There's a technical difference, I think user @joevt on this site explained it at some point. You may be able to find his remark by searching.

Just watch out for TB1 connections (that look exactly like TB2 connectors). These supposedly don't work on Z390 Designare.

 

[burgush]

I've used both, they worked fine for connecting TB2 UAD Apollo's
There's a technical difference, I think user @joevt on this site explained it at some point. You may be able to find his remark by searching.

Just watch out for TB1 connections (that look exactly like TB2 connectors). These supposedly don't work on Z390 Designare.

So, this store has both, the Thunderbolt Cable + TB2 to TB3 apple adapter, and also the Startech Adapter,. The thing is that the sellers at that store are not really capable of knowing the difference. So I guess it is better to go for the Startech adapter in that case? Also, there's no further information on the Apollo box; it doesn't say if it is TB1 or TB2. I guess is TB1? Sorry for so many questions, and thanks for your help

 

[zipb]

So, this store has both, the Thunderbolt Cable + TB2 to TB3 apple adapter, and also the Startech Adapter,. The thing is that the sellers at that store are not really capable of knowing the difference. So I guess it is better to go for the Startech adapter in that case? Also, there's no further information on the Apollo box; it doesn't say if it is TB1 or TB2. I guess is TB1? Sorry for so many questions, and thanks for your help

User @xanderevo says your UAD works. See this thread p.1 . Ask him what adapter he has. But I don't think it makes a difference if you only connect your UAD. Get whatever is cheaper. If it doesn't work, swap it or ask for a refund.

 

[bsholbrook]

Can you please run IORegistryExplorer followed by File —> Save As... and upload the saved file? This will tell us whether IGPU is in headless mode. It would also be good to update Lilu, WhateverGreen, and AppleALC (and run Kext Utility to rebuild kernel cache). All three were updated recently.

I-registry attached and at present this is the device setting.....
AAPL,ig-platform-id - 0300923E