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

[faithie999]

I don't own an Apple Thunderbolt Display, but know a thing or two about Firewire (Oh how I miss thee). Firewire 400, IEEE 1934A, has two port variations. 4 pin port found on many DV camera and 6 pin port found on old external hard drives and the original iPod. Firewire 800, IEEE 1934B, is what is on the back of the ATD.

I'm thinking if the Firewire 400 cable you have is too big, it is a 6 pin port and you need the 4 pin variety. You might be able to find a 6 pin to 4 pin adapter, or just buy a Firewire 800 to 400 4pin cable.

I hope this helps!

thanks!

 

[maso95yo]

With both Platform ID 0x3E9B0007 and 0x3E980003 my Designare Z390 has both H.264 and HEVC enabled. This screenshot is with Platform ID 0x3E9B0007 (same as yours).

Have you clicked the "Refresh" button as shown?

View attachment 506121
The other difference between your system and mine is the version of macOS. I'm running macOS 11.2 public beta.

Also check whether you’re on OpenCore 0.6.5.

Hi, I checked a little bit and I find strange that Hackintool reports "Metal Device Name KBL Unknown" when it should know it's CFL, right? and also it's 0x3E980000 when it should be 0x3E9B0007. Am I correct?

 

[rondark]

@CaseySJ

OpenCore.65
strange thing: upgraded BIOS to F9j and everything seemed to be fine until I noticed that the two USB 3.1 devices that I had plugged into the TB ports no longer worked. These devices: an external NVME enclosure and a Logitech camera. They both worked before I messed with the BIOS. I have checked the BIOS settings. A mistake somewhere by me I'm sure.

Anything that I might try?

Thanks

 

[brousseau6933]

Some devices require relatively large memory buffers (I/O buffers) and therefore take up more than their fair share of the memory map region. So enabling Above 4G Decoding is particularly necessary for such device types, particularly GPUs.

So, a must or not for TB3 functionality?

Possibly related to UEFI memory driver too?

Curious...

« Decoding », sorry for the confusion in my other post...

 

[riverrat42]

Add boot argument -v

That's what I was trying to do, but I wasn't finding the location for it using opencore, but I think I have it now. Will try later. Thanks.

 

[riverrat42]

@riverrat42

Are you running BIOS F9g or F9i? If so, have you disabled CFG-Lock from the Boot section of BIOS Setup?

Yes to both.

 

[CaseySJ]

It's been awhile! Hello there. Hope you're well.

This explanation is incredible. Thanks for that.

How does this play with the RebuildAppleMemoryMap quirk? Is that quirk also related to DisableIoMapper that we enable if we're using above 4G Encoding ?

Hello @NorthAmTransAm,

It's certainly been a while. All is well here, and looking forward to a promising year in the world of Macs. To answer your questions:

• RebuildAppleMemoryMap is concerned with a small subset of memory that is reserved for UEFI firmware (BIOS) and the boot process. The macOS kernel, for example, needs a suitably large space in which to load and run. UEFI drivers also need to allocate memory. This is all part of the UEFI spec instead of the PCIe spec. Above 4G Decoding does not affect this (as far as I've been able to determine).
• DisableIOMapper has the same effect as disabling VT-d in BIOS. VT-d (Virtualization Technology for Directed I/O) provides a means for virtual machines to access hardware directly (i.e. to perform I/O on physical hardware directly) while maintaining security. Intel has the definitive explanation here, an excerpt from which is as follows:
  • Intel® Virtualization Technology for Directed I/O provides VMM software with the following capabilities:
    • Improve reliability and security through device isolation using hardware assisted remapping
    • Improve I/O performance and availability by direct assignment of devices
• This "direct assignment of devices" could very well be affected by Above 4G Decoding because VMs will need to address/access those devices wherever in memory they happen to be mapped.

 

[CaseySJ]

Hi, I checked a little bit and I find strange that Hackintool reports "Metal Device Name KBL Unknown" when it should know it's CFL, right? and also it's 0x3E980000 when it should be 0x3E9B0007. Am I correct?

Please run Hackintool and post a screenshot of the front page where it shows the Platform ID. You may redact serial numbers from the screenshot.

 

[CaseySJ]

@CaseySJ

OpenCore.65
strange thing: upgraded BIOS to F9j and everything seemed to be fine until I noticed that the two USB 3.1 devices that I had plugged into the TB ports no longer worked. These devices: an external NVME enclosure and a Logitech camera. They both worked before I messed with the BIOS. I have checked the BIOS settings. A mistake somewhere by me I'm sure.

Anything that I might try?

Thanks

Some things to check:

• Please double check all BIOS parameters.
  • XHCI Handoff must be Enabled.
  • Thunderbolt parameters must be set correctly, including GPIO3 Force Pwr, which must be Enabled.

If problem persists please run IORegistryExplorer and select File --> Save As..., then post that file.

 

[CaseySJ]

So, a must or not for TB3 functionality?

Not a must, but as we start adding more PCIe devices we will need to enable Above 4G Decoding.