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

[CaseySJ]

Yes and some spare chips I bought just in case!
It also has 3 VCC pins which means no need for a splitter for the 3.3v.

This is sounding better and better!

 

[CaseySJ]

@CaseySJ were you ever able to patch the DROM for the Asus z490 ProArt? I cant seem to find the firmware. I am able to provide the unmodified firmware (once I figure out how to flash it, as of now I am unable to read the rom) Does the motherboard need to be powered for it to work? I havent found a clear answer on this.

We should turn on the power switch on PSU, but not actually power up the motherboard. Are you using a Raspberry Pi?

No one has yet provided the ProArt firmware so if you do, I would be glad to modify it. It may require a couple of iterations, however.

 

[phrfpeixoto]

Yup, tried 3 'monitors'. Actually, 1 physical monitor with 3 connections as follows:

• On-board HDMI with HDMI to HDMI cable
• On-board TB3 with USB-C to DisplayPort cable
• AMD RX 580 with HDMI to HDMI cable

All of them working correctly with no graphics glitches.

My monitor is a somewhat midrange-to-high-end model: the AOC Agon 27" AG273QS4 with two DisplayPort and two HDMI inputs (4 total), which of course allows me to connect up to 4 video inputs.

I can check the full EFI folder. Feel free to compress and upload.

@CaseySJ There you go. Thanks!

 

[PTuser]

@CaseySJ

I thought Id try alt wiring for the header cable as I had a spare - Theres a thread on another forum regarding what is pin 1 and 3 or if it is 3 and 5 . Tried it the other way and curiously it made no difference -nothing looks any different either- tried the other port as Im only using one TB port - no change there either- hopefully the guy you know who has Focusrite TB working may be able to shed some light as Im stumped....

 

[Jamesbond007]

Hello @Jamesbond007,

When Catalina 10.15.4 was released it caused a bit of havoc for users who did not have native NVRAM enabled. Near the end of the update process, 10.15.4 would display a "Bless Tool" error indicating that the Bless Tool was unable to set the startup disk. Consequently, the MacOS Update volume was not removed from the Clover Boot Menu. The solution was to (a) enable native NVRAM, (b) download the combo updater, and (c) reinstall the 10.15.4 update.

Ever since then we made it a requirement to enable native NVRAM. This makes the Hackintosh behave more like a real Mac. With the F9g beta BIOS, MSR 0xE2 is unlocked by default, which further diminishes the argument for not doing so.

Problems with shutdown are often related to NVRAM. Previously we used EmuVariableUEFI to get past this, but we've also removed that because of conflicts with OpenRuntime.

I see. To follow your installation process will necessitate enabling NVRAM and unlocking the MSR register, but since I am not following your installation process and have gotten Catalina 10.15.6 to boot, I think I shall leave it at that.

I am aware that shutdown problems are often related to NVRAM and in fact I use EmuVariableUEFI when I boot High Sierra / Mojave on my system to resolve that.

I have just found that using FwRuntimeServices, OCQuirks, OCQuirks.plist (found in your Catalina 10.15.4 Fresh Install) together with EmuVariableUEFI-64 allows Catalina 10.15.6 to boot and shutdown successfully on my Z390 system. I am satisfied and shall leave it at that at this point without trying to unlock the MSR register. I am wary of any kind of beta BIOS from Gigabyte and don't want to act as Gigabyte's beta tester for its experimental BIOSes.

Edit : I saw people having problems with the F9h beta BIOS (black screen when attempting to enter BIOS). Seeing that it is not available for download on Gigabyte's site and only available from TweakTown, I am not going to touch these BIOSes. I may eventually try your unlocking procedure in the future.

By the way, since you apparently have switched to OpenRuntime over FwRuntimeServices, I am curious : in what way(s) is OpenRuntime superior to FwRuntimeServices?

 

[PTuser]

looking closely at system profiler thunderbolt extensions to check things - anyone with working titan ridge see the same or are yours different?

 

[yosoyoco]

looking closely at system profiler thunderbolt extensions to check things - anyone with working titan ridge see the same or are yours different?

Looks the same for me

 

[PTuser]

@yosoyoco - thanks for your input - everything working ok with yours?

 

[CaseySJ]

@CaseySJ

I thought Id try alt wiring for the header cable as I had a spare - Theres a thread on another forum regarding what is pin 1 and 3 or if it is 3 and 5 . Tried it the other way and curiously it made no difference -nothing looks any different either- tried the other port as Im only using one TB port - no change there either- hopefully the guy you know who has Focusrite TB working may be able to shed some light as Im stumped....

The Focusrite Red 16Line is an expensive high-end audio interface. Looks like a really nice product. But if its drivers are anything like those of Antelope Audio, then alas it may be a lost cause. @qthegaijin has made a valiant effort to connect his Antelope interface to Mojave and Catalina, but the drivers continue to fail. They do work on real Macs and they do work on Hackintoshes running High Sierra. But they don't work on Hackintoshes running Mojave or Catalina.

These are some of the options I see:

1. Wait for other Focusrite owners to respond.
2. Try installing High Sierra on a spare SSD.
3. If you have an Alpine Ridge Thunderbolt card or a friend/colleague with a different Thunderbolt-capable Hackintosh, try those alternatives.
4. Consider purchasing a real Macintosh.

Hopefully the community here will be able to find a solution or workaround... May take a little time.

 

[CaseySJ]

...
By the way, since you apparently have switched to OpenRuntime over FwRuntimeServices, I am curious : in what way(s) is OpenRuntime superior to FwRuntimeServices?

OpenRuntime replaces FwRuntimeServices. It's the same code with a different name. But unlike FwRuntimeServices, OpenRuntime continues to evolve.