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

[deathbyflyness]

I may have misread your post. If it is seen in BIOS along with your other 3 NVMe, it should be seen in macOS.

Make sure SATA is set to AHCI in the BIOS.

Thank you. That solved the problem.

 

[MarcoDe]

Hello, everyone. First a big thanks @CaseySJ for this amazing guide and all the hard work that run into it.

This was the second PC I’ve build and the first with Mac OS. I read threw the hole thread, but still had some questions in the end about what might work regarding the LG UltraFine, so maybe my experience might be helpful.

I used following components in my build:
Gigabyte Z490 Vision G
Intel i9 10850k
Noctua NH-D15S chroma.black
Gigabyte GC-Titian Ridge
Asus TUF-3-RX5600XT-T6G
Fenvi T919
HyperX 32GB DDR4-3200
WD Black SN750 500GB and 1TB
SanDisk Ultra 3D 2TB
Seasonic Focus SGX 650W
M-Audio M-Track 2X2
LG UltraFine 5k 27MD5KA (old Version)
Logitech MX Master 3
Logitech K800 Keyboard
Magic Trackpad 2

The installation of Windows went without problems, but I did not use the UltraFine. After installing all drivers my ethernet still did not work, so I used the I225-V driver from Intel’s website instead of the Gigabyte one which made it work.
What works in Windows:
- LG UltraFine in 5k resolution, Camera, Speaker
- Wifi
- Bluetooth

What does not work in Windows:
- LG UltraFine brightness control does not work, but the USB hub works kind of, it is possible to use my audio interface, it has some dropouts in the beginning and windows shows missing drivers for USB ports as soon as plugged in, but still working.

Installing Mac OS Big Sur went without problems following Casey’s guide.

What works in MacOS:
- LG UltraFine works completely, full 5k resolution, brightness, speaker, camera, USB hub
- SideCar with iPad
- App Store, iMessage
- Handoff, Sleep, Wakeup
- Logitech Flow with MacBook

What does not work in MacOS:
- Netflix in Safari (works in Firefox)
- TV App (watching Movies)

I hope everything stays as trouble free as it is now, the Hackintosh has less bugs than my MacBook. The only thing I am not sure of is why my ethernet disconnects sometimes while sleeping, but maybe it is more a problem of my router, or a timeout limit?

 

[CaseySJ]

@MarcoDe,

Good job and welcome to the forum!

 

[austinmrs]

There are several errors in the statements above:

• XHC does not refer to the Thunderbolt controller. Thunderbolt consists of at least three protocols:
  • USB
  • DisplayPort
  • PCIe
• XHC refers to the USB protocol controller. Because USB itself contains multiple protocols (USB 2.x, USB 3.x), the USB protocol controller defines child nodes such as HSxx to refer to USB 1.x/2.x ports and SSPx to refer to USB 3.x ports.
  • In some motherboards, USB 1.x/2.x protocol is handled by the chipset itself (i.e. a companion controller), whereas only USB 3.x is handled by the Thunderbolt controller's USB protocol controller.
  • In this case we will only see SSPx devices listed under the Thunderbolt device tree.
• The Thunderbolt controller itself resides on a Root Port (RP) such as RP05, RP09, RP21, etc.
• One of the SSDTs you posted (the one marked "not working") assumes that the Thunderbolt controller is on RP21. The other SSDT (marked "working") assumes that the Thunderbolt controller is on RP05.

To clear up this confusion, please:

• Disable all Thunderbolt SSDTs
• Reboot the system
• Run IORegistryExplorer and post the IOReg file

here you go

I think I can see the Thunderbolt at RP21

 

[dehjomz]

Hi @CaseySJ. I've been using your Thunderbolt hot plug SSDT since June/July when it was around 1286 lines long. I think I've been having some problems with Thunderbolt on Big Sur (hard crashes). So I took a look at your latest Thunderbolt hotplug code in 0.6.4 and notice the SSDT is much shorter at around 606 lines.

What changed? Why? There's probably been discussion on the thread about it but I didn't find it.
Also, I can't get Thunderbolt hotplug to work using the latest 0.6.4 code. Thunderbolt devices work from cold boot, but not if i unplug and replug them. Any advice? I may just go back to the older SSDT but it seems to be affecting stability... idk.

 

[dehjomz]

Hi @CaseySJ. I've been using your Thunderbolt hot plug SSDT since June/July when it was around 1286 lines long. I think I've been having some problems with Thunderbolt on Big Sur (hard crashes). So I took a look at your latest Thunderbolt hotplug code in 0.6.4 and notice the SSDT is much shorter at around 606 lines.

What changed? Why? There's probably been discussion on the thread about it but I didn't find it.
Also, I can't get Thunderbolt hotplug to work using the latest 0.6.4 code. Thunderbolt devices work from cold boot, but not if i unplug and replug them. Any advice? I may just go back to the older SSDT but it seems to be affecting stability... idk.

Hmmm I changed Security in the BIOS from 'User Authorization' to 'No Security' and seems that I'm getting Hotpluggable support... using the latest 0.6.4 SSDT. Continuing to test.

 

[MasterHouse]

Guys, I just changed my CPU.
I tried to run cpu_name_v2 again with the new CPU information but had no success.
Any suggestions?

Thanks a lot.

 

[hughythomas]

Hey chaps!

I've just successfully updated to 0.6.4 on Vision G.

One small question is how do you remove openshell.efi from the initial bootloader? Its suddenly appeared next to my drives lol

Also, I couldnt boot before because I got confused by the Vision G section saying remove IntelMausiEthernet.kext.

I ASSUMED that to be IntelMausi.kext so went ahead and deleted it.

However, I couldnt boot for last hour until looking at verbose mode and found it wasn't happy with removal of said kext (so I put it back on and here I am!).

Thoughts?

 

[austinmrs]

Hey chaps!

I've just successfully updated to 0.6.4 on Vision G.

One small question is how do you remove openshell.efi from the initial bootloader? Its suddenly appeared next to my drives lol

Also, I couldnt boot before because I got confused by the Vision G section saying remove IntelMausiEthernet.kext.

I ASSUMED that to be IntelMausi.kext so went ahead and deleted it.

However, I couldnt boot for last hour until looking at verbose mode and found it wasn't happy with removal of said kext (so I put it back on and here I am!).

Thoughts?

change HideAuxiliary from false to true

If you need then to see Openshell of resetNvram you can press space on the boot GUI

 

[CaseySJ]

here you go

I think I can see the Thunderbolt at RP21

RP21 is the correct root port, hence the attached SSDT is the right one. But this is the same one that you previously indicated as not-working. Are you sure that there are no other Thunderbolt SSDTs in your ACPI folder? Please post a screenshot of the OpenCore OC/ACPI folder.

Because the SSDT that attaches to RP05 was marked as "working" (which is not possible), it means there is another Thunderbolt SSDT that is attaching to RP21.