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

[NCMacGuy]

Why do I get the feeling there might soon be a rush for Corsair Vengeance!

@CaseySJ

Don't jump too quickly to Corsair Vengeance memory as the solution.

I had temporary access over the weekend to a second Gigabyte Designare Z390 I built.

Setup per Experiment #3. Memory in A1/B1 - 16GB, 3200MHz in each slot. CMK32GX4M2B3200C16.



AppleVTD DID NOT appear in IORegistryExplorer. Ethernet and WiFi remained active.

A strange result based on other reported results.

 

[CaseySJ]

@CaseySJ

Don't jump too quickly to Corsair Vengeance memory as the solution.

I had temporary access over the weekend to a second Gigabyte Designare Z390 I built.

Setup per Experiment #3. Memory in A1/B1 - 16GB, 3200MHz in each slot. CMK32GX4M2B3200C16.



AppleVTD DID NOT appear in IORegistryExplorer. Ethernet and WiFi remained active.

A strange result based on other reported results.

AppleVTD should appear regardless of the type of memory. Is it possible that the second Gigabyte Z390 Designare had boot argument dart=0 that prevented AppleVTD?

 

[NCMacGuy]

AppleVTD should appear regardless of the type of memory. Is it possible that the second Gigabyte Z390 Designare had boot argument dart=0 that prevented AppleVTD?

@CaseySJ

No, dart=0 was definitely removed. I duplicated the setup several times and made sure the proper EFI was being used because of the results I was seeing. This is admittedly an "outlier."

BIOS F9i, Flashed TB 33, Fenvi T-919, Big Sur 11.4, OC 0.7.0, i9-9900K

 

[CaseySJ]

@CaseySJ

No, dart=0 was definitely removed. I duplicated the setup several times and made sure the proper EFI was being used because of the results I was seeing. This is admittedly an "outlier."

BIOS F9i, Flashed TB 33, Fenvi T-919, Big Sur 11.4, OC 0.7.0, i9-9900K

I'm thinking (just thinking) of testing what appears to be a newer model:

• CMW32GX4M2E3200C16 (2020 model)
• W is for Vengeance RGB Pro
• 16GB DIMM

Yours is the:

• CMK32GX4M2B3200C16 (2015 model)
• K is for Vengeance LPX
• 16GB DIMM

 

[gandem]

@CaseySJ

No, dart=0 was definitely removed. I duplicated the setup several times and made sure the proper EFI was being used because of the results I was seeing. This is admittedly an "outlier."

BIOS F9i, Flashed TB 33, Fenvi T-919, Big Sur 11.4, OC 0.7.0, i9-9900K

Something I had a problem with was I always had to reset NVRAM as the dart=0 argument would stay active after I removed it.

 

[CaseySJ]

Something I had a problem with was I always had to reset NVRAM as the dart=0 argument would stay active after I removed it.

We can solve this by putting boot-args into NVRAM --> Delete, as shown:

 

[maccaroni]

In your Clover config.plist, please try deleting DMAR as shown below (i.e. remove that line), then reboot (VT-d must be enabled in BIOS). Does AppleVTD now appear in IOReg?
View attachment 523102

Holy cow! @CaseySJ , you're an evil Genius! They should bronze your brain when you're finished with it! AppleVTD showed up and the Antelope device works thru Thunderbolt! Game-changer!

The only caveat is that I can't daisy-chain my UAD Apollo and my Antelope. When I do, they disappear and Thunderbolt Bus shows up. I'm gonna go get a second TB3 -> TB2 adapter today and try to run them from both ports... AFTER I play with my AFX2DAW effects.

Asus X299 Prime Deluxe II
bios 0802
4x16GB G.Skill Aegis 3000 (2) 3200 (2)
Clover 5122
macOS X 10.13.6 (17G6030)
Wifi -> working
Ethernet -> still out, 1G and 5G

Update: Shutdown and started back up in Windows 10 to confirm all devices were attached. Shutdown and booted to macOS X and BOOM, FULL Thunderbolt with both devices daisy-chained!

 

[Sapricot]

Not to be a bother but did you have a chance to try activating PTT @CaseySJ? I tried resetting CMOS and enabling PTT before touching any bios settings but it still comes back disabled. Wondering if there could be a problem with my 9900K, or if it's somehow still related to my bios screwup (seems a bit unlikely as I flashed the full chip using your bios).

 

[SardusX]

Hello @SardusX,

It's highly highly highly recommended (i.e. Just Do It ) to install F9g or F9i. I would recommend F9i. Then unlock MSR 0xE2 just by doing this: BIOS Setup --> Boot --> CFG-Lock --> Disabled. As easy as that to unlock MSR 0xE2.

When you suggest updating with the BIOS version F9i do you mean the "official" one?
I downloaded the F9i version from Softpedia:

Download Gigabyte Z390 DESIGNARE (rev. 1.0) BIOS F9i for Windows 9X, Windows ME, Windows NT, Windows 2K, Windows XP, Windows 2003, Windows Vista, Windows XP 64 bit, Windows 2008, Windows Vista 64 bit, Windows 7, Windows 7 64 bit, Windows 8, Windows 8

Download Gigabyte Z390 DESIGNARE (rev. 1.0) BIOS F9i (BIOS)

drivers.softpedia.com

and compared its SHA-1 /256/384/512 signature with those of the file You linked in Your "Quick Reference to Mini-Guides and Micro-Guides": they coincide so I can think they are both verified files?

Use the same SSDT-UIAC... that you are using now. Copy that file into OpenCore's OC/ACPI folder and add a reference to it in config.plist --> ACPI section using OpenCore Configurator:
View attachment 522718

Please, i have two questions:
Is the use of the OpenIntelWireless Driver (and therefore of the SSDT-UIAC-DESIGNARE-Z390-V7D.aml) compatible with the use of iMac 19.1 sysdef?
When I made the first installation of macOS mojave by following your Guide you provided me with the SSDT-UIAC-DESIGNATE-Z390-FD-DEFINE-C-TG.aml file (which I attach to this post). Do you think it can still be used with OpenCore and Catalina/Big Sur?

Thanks in advance

 

[CaseySJ]

Not to be a bother but did you have a chance to try activating PTT @CaseySJ? I tried resetting CMOS and enabling PTT before touching any bios settings but it still comes back disabled. Wondering if there could be a problem with my 9900K, or if it's somehow still related to my bios screwup (seems a bit unlikely as I flashed the full chip using your bios).

Just walked 2.65 miles down the hill to nearest Starbucks. Will be back soon.