Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580

[dehjomz]

thanks again for all your help with this. I feel like I should tip you.

indeed, me too. @CaseySJ is the man.

 

[trs96]

You can contribute to support the community as a whole but individuals do not accept any pay for help as stated in the site rules. The money goes toward the expenses of running this site, "keeping the lights on." The other way you can give back is to help someone else that knows less than you do.

From the Home page:

There is also a contribute button on the top of every page in the upper left corner.

 

[emistral]

The config.plist method is identical to the SSDT method. Both are used to inject the same device properties. In the Dortania guide they inject these properties:

• name = #display
• IOName = #display
• class-code = 0xFFFFFFFF

"23646973706C6179" is just the ASCII code equivalent of "#display". A string can be specified either as (a) type String followed by the letters and symbols, or (b) type Data followed by the ASCII codes of each character of the string.


Have you tried using the Dortania SSDT? If so, does it work?

@CaseySJ no I have not tried Dortania SSDT. I went for the easiest one first but it looks like it is not working since I can still see the 6800 XT in the system reports and IOReg. I am assuming that if it is working I would not be able to see anything related to PEG1/6800 XT in the system report or IOReg.

 

[kikap]

Maybe the issue is because this internal port is not directly connected to the XHCI controller, it sits on the USB 2.0 hub (the port the hub is connected to is marked "internal" in my map, but that doesn't help). Maybe, just maybe, MacOS considers all hub ports "external"?

@CaseySJ @RandC That ^^^ was the case. I crafted a USB cable with a normal USB-A plug on one side and 4-pin JST connector on another to attach to the YOUBO card. Plugged it into the rear I/O panel USB port, created a USB map with Hackintool, declared this port "internal" in the map and it all works beautifully.

I didn't like how Intel BT works in macOS and ended up removing the CNVi module to completely wipe it out. Otherwise, I wasn't able to predict which one system will use after each reboot - either Intel or Broadcom on the YOUBO card.

It kind of annoys me that I've lost 2 USB ports as the result - one external and one that CNVi module was connected to. So maybe I'll pick up a cheap M.2 PCB and solder to the USB pins that CNVi connector provides. According to the doc they should be there.

 

[kikap]

@CaseySJ You recommend a NativeMonitorBrightness tool in your build guide. I should report that it doesn't work correctly with Apple LED Display (the one that just like Thunderbolt, but only Displayport ).
As soon as you touch the slider it dims the display and there's no way to get the old brightness back. Its 100% is actually around 50%. And there's no way to fix it (unplugging monitor from power doesn't help, it remembers the setting) unless you can manipulate the DDC/CI signals.

I've found and installed MonitorControl and it correctly works with both my monitors and seems to be better maintained and polished.

 

[emistral]

@CaseySJ I have tried the Dortania SSDT-Spoof and as opposed to the first one that I tried based on the Z390 (that you reviewed a few weeks ago), this one load and does not crash when macos boots.
Now if the SSDT is loaded/executed properly, am I supposed to see the second video card under graphics/displays in the system report?
Here is a quick screenshot:

As you can see above, Display is obviously my 6800 XT and here is IOreg screenshot:

what I don't get is that the SSDT is loading class-code with FFFFFFFF but we can see from the above that it is not the case

 

[CeruleanCloud]

Very thorough indeed!

Apologies for posting a Thunderbolt question here despite my different board, but this is by far the best / most thorough / easiest to understand setting out of the Thunderbolt issue I have seen.

So... I have an Asus Z490A Prime with 10900K and an Asus ThunderboltEX 3-TR card. Absolutely everything working.... except the Thunderbolt card. At least, it is not clear whether the card is working or not. It works fully under Windows (both eGPU and USB ports) with the condition that it needs to be permission after logging in to Windows (presumably the required resources would be too large for the Windows default). In Big Sur I see it in the ioRegistryExplorer as attached. But, when connecting it to my Razer CORE X Chroma containing a 5700XT, Big Sur does not appear to see either the graphics card or any of the USB sockets on the CORE X. This doesn't appear to be different whether I have connected prior to boot, during boot, or post boot.

I have tried both with and without adding ACPi / KEXT / DRIVER but without impact.

Questions:

- is it also required to flash a chip in relation to my ThnderboltEX 3-TR card?
- if so, is it a chip on the motherboard or the card which one would flash?
- is there a guide comparable to the one here which anyone is aware of?
- if I go. that route, would it prevent the card from working in Windows?
- is there a "proper" guide somewhere which describes the correct ACPI / KEXT / DRIVER configurations? (this is likely a far easier task than wasting your valuable time looking at the results of my hackery if I begin again using a guide you guys recommend, and then provide the necessary downloads and results from there!)

I would truly appreciate your guidance!

 

[qbe]

Anyone using intel BT with Magic Trackpad 2 can confirm all working in macos?

 

[xtreem.p]

Im looking forward to see this mobo in this forum. https://www.gigabyte.com/Motherboard/Z590I-VISION-D-rev-10/gallery#gallery

Gigabyte Z590i Vision D miniITX with 2 Thunderbolt4 ports!

 

[hughythomas]

You guys seen this?

Apple apparently moving to randomized serial numbers in early 2021. So Z490 might be last hackable platform:

https://www.macrumors.com/2021/03/09/apple-randomized-serial-numbers-early-2021/

What kind of impact is this going to have? Could be death of hackintosh no?