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

[thrf]

Hey there, are you able to power-up and mount/load the UAD (TB3) device after the Hack has been booted?

We tested and UAD will work after reboot without need of re powering the interface, (HotPlug), you must check you Thunderbolt settings at BIOS (as this guide tells), and thunderbolt hotplug SSDT, you must have a normal reboot, without KP

 

[thrf]

Hey guys.. I have problem with using optical output from my connection. I can get the sound but I can't increase or decrease the sound manually. If I use analog connection then I am able to use line in option and increase or decrease the sound. I prefer to use digital output. Is there anything I can do to fix it.

This is spected behaviour using Digital Out, even on real Mac, volume should be controlled in SPDIF host, as USB Firewire or Thunderbolt Interfaces / DAC.

 

[CaseySJ]

Thanks.. TB3 does work but its slow. 1G

Im testing a drive that can do 4G.

I'll go through the POST install again.

Please check that your CLOVER/ACPI/patched folder contains at least these two files:

• SSDT-Z390-DESIGNARE-TB3HP-V4.aml
• SSDT-DTPG.aml

Also confirm that your Thunderbolt BIOS settings are correct, especially Thunderbolt Security.

 

[Rag]

Great Apple !!! Work now 5700 RX

 

[CaseySJ]

Unfortunately, no, the Disk Utility didn't see any permissions issues but EFI partitions still don't mount.

Stage 1: Boot a working copy of macOS like this:

• Do you have a bootable backup?
  • If so, please boot from the backup disk.
• If you do not have a working bootable backup:
  • Reinstall macOS from scratch on a new SSD.
  • You can use a cheap SATA SSD mounted inside a USB 3 enclosure.
    • Example of cheap SATA SSD.
    • Example of USB 3 enclosure.
  • Then boot the new installation of macOS.

Stage 2: Run Terminal and "cd" to the correct "usr/bin" folder like this:

• After booting from a working copy of macOS, we are ready to try and remove ACL entries from your /usr/bin folder.
• Open Terminal.
• cd to the original (bad) macOS drive.
  • Example:
    • If the original macOS drive is called MacHD then type this:
    • cd /Volumes/macHD/usr/bin

Stage 3: Remove ACL entries:

• Now that you are in the correct "usr/bin" directory, type this:
  • sudo chmod -N sudo
• If there are no errors, type this:
  • sudo chmod -N *

Stage 4: Verify result:

• Now let's make sure ACL entries are gone. Type:
  • ls -l
• There should not be a "+" sign after the set of file permissions on the left.
• Here's an example:
  

  -rwxr-xr-x 1 root wheel 70288 Sep 29 13:28 AssetCacheLocatorUtil
  -rwxr-xr-x 1 root wheel 67360 Sep 29 13:28 AssetCacheManagerUtil
  -rwxr-xr-x 1 root wheel 57792 Sep 29 13:28 AssetCacheTetheratorUtil
  -rwxr-xr-x 1 root wheel 31488 Sep 29 13:28 BuildStrings
  -rwxr-xr-x 1 root wheel 31456 Sep 29 13:28 CpMac

• Note that there is no "+" after "-rwxr-xr-x".

 

[BerndVP]

Ok, finally got Mojave installed on my Motherboard (Z390 Gaming X). But now, when try to get it booted from the NVMe drive, it gives me directly the prohibition sign.

 

[lathoskaneis]

Hello @CaseySJ very nice guide!Very well documented!

I do not know if you aware of the downsides and possible hardware issues by using OsxAptioFix2Drv-free2000.efi driver.You can find the post of the developer if you search on google "I unleashed a plague upon you guys and I am sorry for OsxAptioFix2Drv-free2000".

I use AptioMemoryFix r27 with emuvariableuefi and my system seems to be fine.Nvram working, boots faster and shutdown/restart without any issues and without clover "shutdown fix".

 

[CaseySJ]

Ok, finally got Mojave installed on my Motherboard (Z390 Gaming X). But now, when try to get it booted from the NVMe drive, it gives me directly the prohibition sign.

At the Clover Boot Menu, press <spacebar> then move down to "Verbose" and press <spacebar> again to check ON this option. Now boot into macOS and note the error message.

 

[CaseySJ]

Hello @CaseySJ very nice guide!Very well documented!

I do not know if you aware of the downsides and possible hardware issues by using OsxAptioFix2Drv-free2000.efi driver.You can find the post of the developer if you search on google "I unleashed a plague upon you guys and I am sorry for OsxAptioFix2Drv-free2000".

I use AptioMemoryFix r27 with emuvariableuefi and my system seems to be fine.Nvram working, boots faster and shutdown/restart without any issues and without clover "shutdown fix".

We've been following this issue since the day the author wrote that post. The general conclusion for Designare Z390 owners is:

• Use AptioMemoryFix or OsxAptioFix3Drv if they work.
• If they don't, then fall back to OsxAptioFix2Drv-free2000.
• Make regular full backups of your system.
  • Protect the data first and foremost.
  • All other system components can fail, most notably spinning hard drives. Those will fail much sooner than anything else.
• The sheer severity of the author's warning (sky is falling, sun is going supernova, Andromeda is colliding, and protons are decaying) is diametrically opposed to actual reality.
  • In other words, given the harshness of the warning, we would expect motherboards to be failing left and right every minute of every day.
  • So where are those problem reports?
• Nevertheless, protect the data by making regular full backups.
  • Only the data matters.
  • Hardware is replaceable. Data is not.

 

[trs96]

Nevertheless, protect the data by making regular full backups.

• Only the data matters.
• Hardware is replaceable. Data is not.

This is great advice for anyone no matter what AptioFix driver they decide to use. The one thing in common for everyone that experiences data loss: They didn't think it would happen to them. "Why take steps to avoid data loss if it's never going to happen to me ?"