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

[verydanny]

I'm having a pretty serious random issue now. After I enabled the "Windows Insider Version" and updated to Windows 10 v.2004 + installed "Windows Subsystem for Linux" and "Virtual Machine Platform", I cannot boot into Windows from Clover anymore. I need these things for WSL2.

I can press F12 and select Windows just fine, but Clover -> Windows EFI entry results in a Windows BSOD (SYSTEM THREAD EXCEPTION NOT HANDLED).

I thought it was Windows and then re-installed Windows, repeated the same steps, and Voila! Same exact issue. No issue booting Windows until I update to 2004 (very stable version), add "Windows Subsystem for Linux" and "Virtual Machine Platform", then Clover can't boot anymore.

My only guesses are that it's something to do with OcQuirks or Vt-d. I'm not sure yet. Anyone else have issues of this sort?

 

[3rdPowerCitizen]

Is anyone still working on Antelope interfaces and Thunderbolt? I have the z390 Designare working great with my Apollo Thunderbolt. I am toying with the idea of buying and antelope to test with.

 

[TinkerTenor]

My experience is that you can move the macOS to either M.2 slot. Just make sure when you install Windows, that you remove any other disks including SATA disks as Windows is known to overwrite the wrong EFI partitions. For the SATA disks, if you are using them, you can just disable the Drives in the BIOS without physically disconnecting them. Hope this helps.

Thanks @jb007 that sounds about right. I assumed there wasn't a lot of voodoo attached to the process but I've got pre-build paranoia. lol

 

[smashdownbabylon]

@smashdownbabylon hi, just wondered how your getting on with the UAD? I've got the Apollo 8 TB2/3 - Quad satellite TB2 and an 8Core PCie.. I've had a more stable OS and Hack in the past - however after updating last year to newer OS and Clover updates etc I've been having a few niggles with the Apollo not being recognised, audio stuttering once or twice.. Hotplug now and then.. So I thought it may have been the updates I'd done etc. and have been trying to find a new solution, Opencore was one recent 'project', now looking to flash the onboard TB via the Pi route.. after just reading over your post I'm even more optimistic.

Still working very well. Highly recommend. I even installed the 10.15.4 update as on a normal Mac, and everything is still working. I have the UAD Apollo 16 x2 chained and working as an aggregate device with two expert sleepers eurorack interfaces, with sample accurate timing. It is indeed the future

 

[jb007]

Thanks @jb007 that sounds about right. I assumed there wasn't a lot of voodoo attached to the process but I've got pre-build paranoia. lol

Just follow this build by @CasseySJ very carefully. It is a very detailed and complete guide, and you can't go wrong (famous last words). If you do, post back here as there always is someone to help, usually @CaseySJ.

 

[c0c0p0ps]

Yeah I definitely can't get this to work on my Asus Z370 i9-9900ks system. Have double checked all the device properties for iGPU and each time I add the boot flag it gives a super slow startup and has no iGPU enabled in macOS.

@CaseySJ I found out why I can’t get this to work here -https://github.com/acidanthera/bugtracker/issues/790

Seems to need a Z390 chipset and even then it may not be supported as found by the bug reporter who also is on an Asus!

Guess I should double check everything first... I think I have got carried away after finding your thread as it has been a wealth of cutting edge Hackintosh developments!

 

[FormerUser-594785]

** Micro-Guide: Significantly Speed Up Intel UHD630 iGPU **
Please do not quote this guide in its entirety. Post a link instead.


My result:

 

[verydanny]

@CaseySJ

I figured something out. I thought it was suspicious that after adding WSL2 ("Windows Subsystem for Linux" and "Virtual Machine Platform") to Windows 10 build 2004 my Clover Windows 10 EFI couldn't boot. The Windows logo would start spinning, then stop. It reminded me of a "Couldn't Allocate Runtime Memory" bug.

Instead of disabling OcQuirks.efi and OpenRuntime.efi, I simply used the default settings. Lo and behold, I can boot into Windows 10 from EFI just fine! I cannot boot into Mac because of "Couldn't Allocate Runtime Memory" now.

Well...sh*t

EDIT:

After upgrading to OcQuirks.efi/OpenRuntime.efi Rev22, I don't have the issue anymore. I attached my OpenRuntime patch.

It seems to me that the configuration for OpenRuntime needs to be fine-tuned because it impacts a lot more than we realize.

 

[CristianP]

Hello guys! It looks now that my computer is stable and works properly. I am very happy about it, thanks to @CaseySJ! I still have emulated NVRAM running, and I'm thinking to switch to the native one. But, honestly, I'm a little afraid to do this! There's something about modifying the firmware that makes me nervous
I'm curious if this procedure would affect Windows in any way since I have it dual boot.

 

[zipb]

I had exactly same problems, fixed going back to 0.71

And what method did you use to fix the 15 USB ports max requirement?