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

[CaseySJ]

Always willing to help if I can. I do not have a dual boot system setup however I do have a VM Windows 10 Installed using VirtualBox. Not sure if it will work through that but am willing to give it a try.

Wonderful! It might be possible to do this through Windows on a VM. Let's start with the following preparatory steps:

• After installing Windows 10 in a VM, please download and run Gigabyte's RGB Fusion application as shown. You may click on the image to go directly to the Gigabyte website.

• After launching RGB Fusion, please see if you're able to control the various lighting channels. If so, we can take the next step.

 

[Ayvan]

Wonderful! It might be possible to do this through Windows on a VM. Let's start with the following preparatory steps:

• After installing Windows 10 in a VM, please download and run Gigabyte's RGB Fusion application as shown. You may click on the image to go directly to the Gigabyte website.

View attachment 478433

• After launching RGB Fusion, please see if you're able to control the various lighting channels. If so, we can take the next step.

I already tested this on Parallels Desktop, even with a directly connected to VM Windows 10 USB ITE device (IT5702), this does not work.

 

[dehjomz]

The SSDT to use with GC-Titan Ridge will always be the one attached to the GC-Titan Ridge Thunderbolt DROM Mini Guide.

Hello @CaseySJ, something is wrong with your SSDT for the flashed GC-Titan Ridge. With this .aml binary loaded, Thunderbolt devices on the GC-Titan Ridge are detected, but they do not start, even after warm boot. However, turning off that SSDT, they start. Of course the problem is without that SSDT, there's no hotplug, nor the 40 gbps port speed.

I checked this both on a z490 and z170 with the GC-Titan Ridge (flashed NVM 23). Interesting that the Titan Ridge works on my z170..... that has no thunderbolt interface in the BIOS. Also, even more interesting is that thunderbolt on the card works without the need to bridge pin 1 and pin 3... although with them bridged it works as well.

I wonder why with your SSDT loaded Thunderbolt Devices are detected, but don't start?

 

[CaseySJ]

Hello @CaseySJ, something is wrong with your SSDT for the flashed GC-Titan Ridge. With this .aml binary loaded, Thunderbolt devices on the GC-Titan Ridge are detected, but they do not start, even after warm boot. However, turning off that SSDT, they start. Of course the problem is without that SSDT, there's no hotplug, nor the 40 gbps port speed.

I checked this both on a z490 and z170 with the GC-Titan Ridge (flashed NVM 23). Interesting that the Titan Ridge works on my z170..... that has no thunderbolt interface in the BIOS. Also, even more interesting is that thunderbolt on the card works without the need to bridge pin 1 and pin 3... although with them bridged it works as well.

I wonder why with your SSDT loaded Thunderbolt Devices are detected, but don't start?

The SSDT works for me on both the Z390 Designare and Asus X99 Deluxe II. So let's start by examining the SSDT itself. Can you please post the following:

• The SSDT you're using for GC-Titan Ridge
• Your IOReg file (IORegistryExplorer --> File --> Save As...)

Interesting that GC-Titan Ridge works even with pins 1 and 3 disconnected. I'll try this myself later in the day.

 

[Josu]

I has been preparing myself to start build, and instead of CPU amazon sent me empty can of antibacterial spray with CPU sticker on it

 

[CaseySJ]

I has been preparing myself to start build, and instead of CPU amazon sent me empty can of antibacterial spray with CPU sticker on it

Ouch, I'm sure Amazon will take care of this mistake.

About three years ago I purchased an Intel Pentium processor, but received an empty box. It was the correct item, but had nothing inside. After a little back-and-forth, Amazon sent a replacement.

 

[ssijak]

This is my first Hackintosh after like 10 years. I have the problem where my installation from this guide just shows apple logo and hangs there. My configuration is as follows :
Z490 Vision D
i7-10700k
64GB (4x16GB)
Sapphire Nitro 5700 XT
1TB Adata 8200 Pro NVMe
512GB Adata 8200 Pro NVMe

I've tried reseting nvram and starting with the -v parameter and this is what it prints (sorry for the bad photo, my phone camera is shattered ):

 

[amarchand]

Hello @Lukey1979,

The development version of liquidctl supports both ITE Tech devices 0x5702 and 0x8297. It has already been tested on an X570 board running Windows so it should work on Gigabyte X390 AORUS Xtreme under macOS, Linux, and Windows.

To test it on macOS, I would suggest:

• Installing liquidctl via Homebrew as explained in the liquidctl installation guide
• But then replace all files in the following directories with files from equivalent directories in my development branch
  • Replace all files inside liquidctl/driver with the ones located here
  • Replace all files inside liquidctl folder with the ones located here
• Then try: liquidctl --hid hid list
  • Do you see the 0x8297 device in the list?

@CaseySJ after my initial troubles with liquidctl I decided to give it a shot again after reading this post. I am pleased to report the Z490 Vision D is now recognized in liquidctl! I was able to successfully execute one of the test commands that you had mentioned earlier in a shell script using-

"cd /Users/Shared
./liquidctl-startup.sh"

However, upon writing the Automator "application" to run the script on startup, I received this message upon first attempt(attached below). Seeming to tell me that lines 4 and 7 of liquidctl-startup.sh have errors. Quite odd as the script worked when I tested in Terminal as said above. I'll attach my startup file so you can take a look if you'd like. But, very glad to at least have gotten past the frustration of the first step!

 

[hughythomas]

This is my first Hackintosh after like 10 years. I have the problem where my installation from this guide just shows apple logo and hangs there. My configuration is as follows :
Z490 Vision D
i7-10700k
64GB (4x16GB)
Sapphire Nitro 5700 XT
1TB Adata 8200 Pro NVMe
512GB Adata 8200 Pro NVMe

I've tried reseting nvram and starting with the -v parameter and this is what it prints (sorry for the bad photo, my phone camera is shattered ):
View attachment 478483

Hey man check your BIOS settings and make sure they match both the version of BIOS recommended by CaseySJ and all of the individual parameters.

I'm no expert but have had my fair share of troubleshooting hackintosh related issues recently and resolved them this way.

I don't know what you're planning to use your system for but I work in the music industry and my hackintosh is now beautifully stable, fast and I'm using it for professional work (ie. its reliable enough for this!) thanks to the above and Casey's guide. The two are not mutually exclusive is what I'm saying in a nutshell.

Hope this helps mate!

 

[Anastasius]

Is the Cintiq a display device as well? Not just a pressure-sensitive pad, but also a display with an LCD monitor built in?

If so, we will need to send a DisplayPort video stream to the Thunderbolt 3 port. This is done in either of two ways:

1. From the RX 590, connect a DP cable to the DP-In port on the rear IO panel.
   • Then connect Cintiq to the Thunderbolt 3 port closest to HDMI port.
   • Does it work?
2. If not, try changing platform ID to 0x3E9B0007 in config.plist --> Device Properties.
   • This will enable video output from the iGPU, but certain apps such as iMovie, Final Cut Pro, ACDSee Photo Studio 5/6 for Mac, etc. will crash on start.
   • This also means that it's not strictly necessary to connect RX 590 to DP-In port.

View attachment 478376

Thanks again for the support! Cintiq tablet/display connection worked out by changing Display ID!

EDIT: Also everything works with DisplayPort IN and no iGPU actually after I added back agdpmod=pikera to the boot args! You are my hero haha! Thank you so much for such a detailed and continuous support!

When iGPU is disabled DisplayPort IN doesn't work, freezes immediately after I connect it.
Also it freezes when I connect Thunderbolt displays that way (without iGPU enabled), please see attached crash report just in case:

Spoiler: Thunderbolt crash report

0300983E
panic(cpu 0 caller 0xffffff800784aa3a): Kernel trap at 0xffffff7f8ade30fd, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x00000000000001dc, CR3: 0x000000000ddb2000, CR4: 0x00000000003626e0
RAX: 0x971eb1489d0700a9, RBX: 0x0000000000000002, RCX: 0x0000000000010002, RDX: 0x0000000000000001
RSP: 0xffffff8747653e20, RBP: 0xffffff8747653ea0, RSI: 0x0000000000000001, RDI: 0xffffff809848a520
R8: 0x0000000000000001, R9: 0x0000000000000002, R10: 0x0000000000000000, R11: 0xffffff809a73ffa0
R12: 0xffffff80995bf000, R13: 0x0000000000000000, R14: 0x0000000000000002, R15: 0x0000000000000000
RFL: 0x0000000000010202, RIP: 0xffffff7f8ade30fd, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x00000000000001dc, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 1
Backtrace (CPU 0), Frame : Return Address
0xffffff8747653880 : 0xffffff800771f5cd mach_kernel : _handle_debugger_trap + 0x49d
0xffffff87476538d0 : 0xffffff8007858b05 mach_kernel : _kdp_i386_trap + 0x155
0xffffff8747653910 : 0xffffff800784a68e mach_kernel : _kernel_trap + 0x4ee
0xffffff8747653960 : 0xffffff80076c5a40 mach_kernel : _return_from_trap + 0xe0
0xffffff8747653980 : 0xffffff800771ec97 mach_kernel : _DebuggerTrapWithState + 0x17
0xffffff8747653a80 : 0xffffff800771f087 mach_kernel : _panic_trap_to_debugger + 0x227
0xffffff8747653ad0 : 0xffffff8007ec27cc mach_kernel : _panic + 0x54
0xffffff8747653b40 : 0xffffff800784aa3a mach_kernel : _sync_iss_to_iks + 0x2aa
0xffffff8747653cc0 : 0xffffff800784a738 mach_kernel : _kernel_trap + 0x598
0xffffff8747653d10 : 0xffffff80076c5a40 mach_kernel : _return_from_trap + 0xe0
0xffffff8747653d30 : 0xffffff7f8ade30fd com.apple.driver.AppleIntelCFLGraphicsFramebuffer : __ZN31AppleIntelFramebufferController20invokeHotplugHandlerEj + 0x62f
0xffffff8747653ea0 : 0xffffff7f8adbf5f3 com.apple.driver.AppleIntelCFLGraphicsFramebuffer : __ZN31AppleIntelFramebufferController18SWInterruptHandlerEP8OSObjectP22IOInterruptEventSourcei + 0x1a5
0xffffff8747653ee0 : 0xffffff8007e2e60d mach_kernel : __ZN22IOInterruptEventSource12checkForWorkEv + 0x17d
0xffffff8747653f30 : 0xffffff8007e2cede mach_kernel : __ZN10IOWorkLoop15runEventSourcesEv + 0x11e
0xffffff8747653f70 : 0xffffff8007e2c4d6 mach_kernel : __ZN10IOWorkLoop10threadMainEv + 0x36
0xffffff8747653fa0 : 0xffffff80076c513e mach_kernel : _call_continuation + 0x2e
Kernel Extensions in backtrace:
com.apple.driver.AppleIntelCFLGraphicsFramebuffer(14.0.6)[7ED5DA83-8E51-33C0-BCDF-5C7C01ECB82E]@0xffffff7f8ad8b000->0xffffff7f8aff1fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[2104A2A7-95AA-34C0-A419-35BB580788D9]@0xffffff7f88131000
dependency: com.apple.iokit.IOACPIFamily(1.4)[56FB6703-BE47-3965-ABF6-03FE7D4C7155]@0xffffff7f88845000
dependency: com.apple.iokit.IOAcceleratorFamily2(438.5.4)[22E3683B-3DA3-3900-8FC1-C7A3A3FD649A]@0xffffff7f89e75000
dependency: com.apple.iokit.IOReportFamily(47)[29D99624-FE09-38D2-8EF2-DBFAC2CE0641]@0xffffff7f884cc000
dependency: com.apple.AppleGraphicsDeviceControl(5.2.6)[5D721472-A96B-3C46-A58C-DA0272E56253]@0xffffff7f88e21000
dependency: com.apple.iokit.IOGraphicsFamily(576.1)[3568F688-DC24-3918-B913-FF0037956D84]@0xffffff7f88aea000
BSD process name corresponding to current thread: kernel_task
Boot args: keepsyms=1 dart=0 debug=0x100 darkwake=9 alcid=11 shikigva=80
Mac OS version:
19F2200
Kernel version:
Darwin Kernel Version 19.5.0: Wed Jun 3 17:39:27 PDT 2020; root:xnu-6153.121.2~7/RELEASE_X86_64
Kernel UUID: 94AC94F4-A094-3AD8-85D1-2089DFC31E83
Kernel slide: 0x0000000007400000
Kernel text base: 0xffffff8007600000
__HIB text base: 0xffffff8007500000
System model name: iMac19,1 (Mac-AA95B1DDAB278B95)
System shutdown begun: NO
Panic diags file available: YES (0x0)
System uptime in nanoseconds: 35370581549

iMovie does crash when I use iGPU