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

[wilsonngai]

Hi everyone,

I'm faced an issue and have no clue why it happened. I'm sure someone here may give me hope.

I attempted to update my Hackintosh to 10.15.4 yesterday, with updated Lilu, Whatevergreen, AppleAlc kext and 5108 Clover. By the time I restarted and enter installer/macOS drive, my clover went dark and 'freeze'. It literally freeze at the second it boot into the hack.

At normal times my backlit keyboard will turn off and on during the boot, but not now anymore (keeping on now). When I press ctrl+alt+del it reboots itself. Even Verbose can't help as it went dark and freeze completely. I tried enabling/disabling all options in the clover it doesn't work. It's driving me crazy as I never face such a situation in my 3 years hackintosh life.

My PC setup is as follows:
CPU: Intel i7-8700K
GPU: MSI Vega 56
RAM: 32.0GB@3600MHz
Motherboard: Gigabyte Z370

My injected kext is as follows (tried turning individuals on and off and can't see any hope ;( ):
Lilu
Whatevergreen
AppleAlc
AMD10000controller

Countless thanks.

 

[CaseySJ]

All,

I have temporarily lost access to this website through my ISP. Replies might be limited or delayed until the problem is fixed. Thank you for your patience.

Update:

• After contacting Tech Support, we believe the problem lies with my WiFi mesh router (Netgear Orbi RBR50).
• The router might have a strange conflict with the cable modem, so a new more advanced cable modem should arrive on Wed or Thurs of this week.
• An old router that had been lying in the closet for the past 2 years works perfectly, but does not support mesh WiFi, which is necessary for covering all areas.

Therefore:

• If you are using a mesh WiFi router (not a standard router), have you had any trouble accessing this website?
• If your mesh WiFi router has accessed this website flawlessly for 6 months or more, please let me know the make/model by Private Message.

Thanks again for your patience with my delayed replies. Hopefully this will be sorted out within a few days.

 

[CaseySJ]

But what does it mean?
g\

Those differing bytes in the configuration section (not the DROM section) are related to some really obtuse low-level operating details about transmission coefficients and so forth. It might be an interesting experiment to flash the firmware from IOCARD to a GC-Titan Ridge. Both the IOCARD and GC-Titan Ridge are add-in-cards.

 

[StefanAM]

Does your Linux boot from Clover okay? I have Catalina, Windows 10 and Ubuntu 19.10 and all show up in Clover but only Windows and Catalina will boot. If I choose 'Linux' from the choices I just end up with the pinky purple screen and it just hangs there. It boots fine in I F12 and select the drive manually. A 1st world problem, as I only occasionally use Ubuntu, but it would be nice to fix it. I haven't looked into it too much.

Same issue. If u change with OsxAptioFix2Drv-free2000.efi or another boot driver it will work. It' because of "OcQuirks.efi family".

 

[hamzab]

I'll leave the other parts of your question to others.

Windows dual boot
The advice to put the Windows drive in the M2M slot only applies if you are using M.2 drives for both Windows and macOS. Since the 850 EVO is a 2.5" form factor, install it in one of the hard drive bays and connect it to a SATA port.

If you now have Windows 10 installed on the EVO on another computer and you want to move that EVO to your new machine: it's worth a try to install the EVO with your new motherboard/case before doing any macOS installs. Make a FULL BACKUP of the EVO. then install the EVO and see what happens. Unlike with previous versions of windows, Win10 is much more forgiving when moving a Win10 drive from one computer to another. The worst case is you get a blue screen and you'll need to do a wipe and reinstall. Best case is that after Windows boots you'll need to re-authorize the install. Go to Settings--Update--Activation.

Once you have a working Win10 installation (either just porting the EVO or needing to do a full wipe and install using a win10 USB installer), remove the EVO and start with the guide on Page 1 of this thread and install Catalina and get everything working to your satisfaction.

Then shut down and install the EVO. Turn on your machine and go to BIOS settings. Set the boot order so that your macOS drive boots first. Then reboot, and, if all goes well, your machine will boot to the Clover screen. There will be a Windows boot selection (it might say something like Boot Microsoft EFI from EFI).

I have both Windows and Linux on separate hard drives in my machine and both show up as boot options

Thank you. I'm going to do a clean windows install on the 850 EVO and will do that first and then follow your steps (as well as the Catalina guide) above.

Just a quick follow-up question. Does it make a difference to Windows/Dual boot or anything to do with dual booting that I'm going to be installing Mac OS Catalina on a NVMe Drive, whereas windows will be on a SATA drive?

 

[Ploddles]

Same issue. If u change with OsxAptioFix2Drv-free2000.efi or another boot driver it will work. It' because of "OcQuirks.efi family".

Ok, thanks for letting me know. I'll try again when a newer version is available. For now pressing F12 isn't too troublesome.

Thank you. I'm going to do a clean windows install on the 850 EVO and will do that first and then follow your steps (as well as the Catalina guide) above.

Just a quick follow-up question. Does it make a difference to Windows/Dual boot or anything to do with dual booting that I'm going to be installing Mac OS Catalina on a NVMe Drive, whereas windows will be on a SATA drive?

No it doesn't make any difference. When you next install Windows Updates you may find that Clover disappears and you boot straight into Windows. Just go back into BIOS and change the boot order back to what it should be, ie Clover disk 1st.

 

[smashdownbabylon]

Firmware flash success last night, port 7 working, IO tree looking good. Didn't quite understand the mini guide about setting a UID to get port 7 working, like which bytes to use from where and how, but when I threw the attached DSDT in ACPI/patched, seems to work fine.

As far as the Apollo goes, it now sits on the bus of the driver as opposed to on a a PCI bus before I flashed. The driver is on DSB1@1 while all the Apple Thunderbolt tree is on DSB0@0. Could this be patched by the DSDT? Is the driver supposed to be on a thunderbolt bus at all?Seems to reason that it should. (see attached pic)

@CaseySJ Using Google WIFI (dont hate) mesh routers right now, site loads fine.

 

[scottkendall]

Those differing bytes in the configuration section (not the DROM section) are related to some really obtuse low-level operating details about transmission coefficients and so forth. It might be an interesting experiment to flash the firmware from IOCARD to a GC-Titan Ridge. Both the IOCARD and GC-Titan Ridge are add-in-cards.

I will do it point me at the file

 

[CaseySJ]

Firmware flash success last night, port 7 working, IO tree looking good. Didn't quite understand the mini guide about setting a UID to get port 7 working, like which bytes to use from where and how, but when I threw the attached DSDT in ACPI/patched, seems to work fine.

As far as the Apollo goes, it now sits on the bus of the driver as opposed to on a a PCI bus before I flashed. The driver is on DSB1@1 while all the Apple Thunderbolt tree is on DSB0@0. Could this be patched by the DSDT? Is the driver supposed to be on a thunderbolt bus at all?Seems to reason that it should. (see attached pic)

@CaseySJ Using Google WIFI (dont hate) mesh routers right now, site loads fine.

Congratulations, that looks correct!

• Thunderbolt Bus is on DSB0.
• Thunderbolt devices on Port 1 are on DSB1.
• Thunderbolt devices on Port 2 are on DSB4.
• USB-C devices on Port 1 are on DSB2.RHUB.SSP1.
• USB-C devices on Port 2 are on DSB2.RHUB.SSP2.

The default SSDT in the ThunderboltDROM Micro Guide will enable Port 7. That isn't the issue! The issue is that each person should create a unique (random) UID by following the ThunderboltDROM Micro-Guide. If you don't do this, it can lead to unforeseen problems in the future.

 

[smashdownbabylon]

Congratulations, that looks correct!

• Thunderbolt Bus is on DSB0.
• Thunderbolt devices on Port 1 are on DSB1.
• Thunderbolt devices on Port 2 are on DSB4.
• USB-C devices on Port 1 are on DSB2.RHUB.SSP1.
• USB-C devices on Port 2 are on DSB2.RHUB.SSP2.

Thanks! Only one problem, like the guy with Antelope interface, i get no audio stream. Trying to find a way to poke around in the UAD driver software to see what it would be looking for to enable it.