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

[mrfatcatt]

I have good news for you all. With this VTD mod, I was able to get pro tools carbon hardware working via the apple to ethernet adapter on my 390 board. Both tb ports worked and i used both the akiko tb 2 to 3 and star tech 2-3 adapter. I tired the original apple tb adapter but that never worked even in catalina.

My bottom Ethernet works but not my top. I didn't try wi fi as ill never use it. I also only have 2 8 gig sticks of ram so im at 16 gigs

Since i have the 10g card thats a pcie slot ...ill most likely be going back to that and using that for my avb setup. Plugging into that directly also works with this mod so i can use pt carbon via both tb ports and also my asus 10g nick card
But im happy to know this is working. TY

Also, if someone has a second, my amd 5700 gpx card is in my vision Dp board since i was working on that last week. I have a nvidia 1070 in pcie slot 1 on this 390 and is there a way to disable that only in mac so when i run this machine i can just use the intel built in gpx card. and the nvidia in windows? I tired to boot using the 390 hackindrom efi with intel but that hangs half way on boot and i think its cause of this nvida card. I can get into big sur but some of my plug ins in pro tools wont load cause no gpx support

thanks

 

[CODYQX4]

I'm not sure what the difference in RAM modules is, but I wonder if adjusting the timings in the BIOS effects the results.

 

[suren6791]

Does anyone have an SSDT for the RX580. On mine when playing music or videos the sound plays then stop for a quick millisecond and plays again. This happens every 10 to 20 seconds of the song/video. The fact that this is also happening in windows leads me to believe the RX580 needs patching or how do I extract my own SSDT from my DSDT.

 

[Sapricot]

@CaseySJ Update on my PTT situation. I tried flashing official F9i through Qflash but it said invalid file, tried both the one in this thread and the one from Softpedia. Then I booted Windows directly (not through OC), installed Gigabyte bios updater and that was able to do it. Since it worked I ran it again but also updated the backup bios (I have a suspicion I somehow screwed that one up with the failed modified F9i). Then loaded safe defaults, set PTT to enabled, save&restart and... BOOM, it stayed enabled

Is it possible that my failed flash (using the complete setting to update Intel ME and stuff) didn't get fully fixed by manually flashing your bios and the Gigabyte tool was able to correct that? Can't think of any other reason since it was literally the same bios.

I also noticed that before flashing now, there was no Intel ME available at all in Device Manager in Windows. Haven't checked yet if it's there now since I wanted to make sure MacOS booted correctly first. Will update.

 

[jiffyslot]

The problems I had with BIOS updates was solved by temporarily removing the BIOS' admin password.

 

[Kalypso478]

I confirm that WLAN (Fenvi-T919) and Ethernet (bulit-in Intel I211 and Intel I219V7) do not work with the following configuration:
- Bios F9i (modified)
- VT-d in BIOS enabled
- uncheck "DisableIOMapper" (config.plist -> kernel section)
- removed "dart=0" from Boot-Args (NVRAM section)

AppleVTD appears in IORegistryExplorer.

Hardware:
- Gigabyte Z390 Designare
- Intel Core i9-9900K
- WLAN Card Fenvi-T919
- RAM Corsair Vengeance LPX DDR3-3200 32GB-Kit (CMK32GX4M2B3200C16); 16GB in Bank-A1 and 16GB in Bank-B1

I would like to add:
- Running Big Sur 11.4 (20F71)
- OC (OpenCore) 0.7.0

 

[NCMacGuy]

I wondered how reducing total memory from 32GB to 16GB for Experiment #3 would affect Geekbench 5.4.1 scores. In my case with a i9-9900K it was significant number-wise. The 32GB score was run in late Dec. 2019, which might also be a factor. In actual real-world performance for the way I use this hackintosh, probably not noticeably.

16GB 32GB
------ ------
Single-core 1233 1289
Multi-core 7301 9537

Now the question for @CaseySJ is whether I should return my BIOS, and EFI folder to pre-experiment settings. Or is there more experimenting to come?

 

[CaseySJ]

I wondered how reducing total memory from 32GB to 16GB for Experiment #3 would affect Geekbench 5.4.1 scores. In my case with a i9-9900K it was significant number-wise. The 32GB score was run in late Dec. 2019, which might also be a factor. In actual real-world performance for the way I use this hackintosh, probably not noticeably.

16GB 32GB
------ ------
Single-core 1233 1289
Multi-core 7301 9537

Now the question for @CaseySJ is whether I should return my BIOS, and EFI folder to pre-experiment settings. Or is there more experimenting to come?

This is a good question. Thanks to the response from everyone who tried AppleVTD, here are some preliminary conclusions:

• If you use Antelope’s Thunderbolt audio interfaces, enabling AppleVTD is the only known solution. If you also happen to have a system based on X99 or X299, you can use as much memory as you like because AppleVTD does not appear to cause any side effects on those systems. Gigabyte’s Z170X also has no side effects.
  
  
• If you need AVB through Apple Thunderbolt to GbE adapter, then AppleVTD is also required. But you can also use a 10GbE PCIe card instead (e.g. Sonnet) and disable AppleVTD.
  
  
• On all systems other than X99, X299 and GA-Z170X, using a maximum of 16GB also avoids side effects with AppleVTD.
  
  
• The option to enable or disable AppleVTD is up to each person based on their circumstances.
  
  
• I will, however, test @jiffyslot’s memory later in the week to see if there is at least one memory configuration that allows us to exceed 16GB on standard desktop platforms (not X99, X299, or GA-Z170X).
  • UPDATE: Jiffyslot tested this with Big Sur and found that WiFi/Ethernet will in fact disconnect.

 

[faithie999]

@CaseySJ

at the outset of this news about enabling AppleVTD, was there also mention of a modded BIOS? I've lost track of that. what were the purported benefits of the mods?

also, IIRC you were looking for a volunteer with an apple TB monitor to test the BIOS. did that test ever take place?

thanks

ken

 

[CaseySJ]

@CaseySJ

at the outset of this news about enabling AppleVTD, was there also mention of a modded BIOS? I've lost track of that. what were the purported benefits of the mods?

Yes we originally started with a modded BIOS that imports a real Mac’s Thunderbolt PEI/DXE drivers into our Gigabyte Z390 Designare BIOS. That BIOS allows Thunderbolt to be fully initialized and set up the way it is done on a real Mac.

But we soon discovered that Apple’s TB-to-GbE adapter still didn’t work in Big Sur, which led us on the chase for AppleVTD. This caused the experiment to diverge because we found that simply enabling AppleVTD (without modifying the BIOS) is sufficient to enable both TB-to-GbE adapter and Antelope Audio Thunderbolt interfaces.

Coming back to the modified BIOS, it seems we may need to import additional DXE and/or PEI drivers to enable video signal to Thunderbolt monitors in the pre-boot environment. We’re still working on that. AppleVTD alone does not help with Thunderbolt monitor video signal loss in pre-boot.

also, IIRC you were looking for a volunteer with an apple TB monitor to test the BIOS. did that test ever take place?

thanks

ken

We got a volunteer who owns LG UltraFine 5K, but not someone with Apple Thunderbolt Display. If you have one of these ATD monitors and would like to try the modified BIOS, I can send you the file in private message. We don’t want to publicly release the new BIOS yet because it is still being worked on.