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

CaseySJ said:

Looks like you might have overlooked the following section of the Post-Installation procedure:
View attachment 407981

Please go through that section again and then check if USB-related problems are still present.

Click to expand...

Yep I see the missing files now, although I remember doing this, I stuffed it up somewhere. Just plugged in a bunch of usb devices and restarted so far so good. I'll give it a few days and test it out. Thanks again.

CaseySJ said:

*** macOS 10.14.5 Update ***

• Ensure that your USB SSDT is installed and your USB port limit patches in config.plist are Disabled.
  • The Mojave 10.14.4 USB port limit patch is not compatible with 10.14.5.

Click to expand...

Hi,
Some question about 10.14.5 update:
- in the update guide you mean that you need to set the "Kernel and Kext Patches" section as in Your "final steps in post-installation" guide disabling the 3 USB port limit patches (and USB SSDT installed)?
- Is it more appropriate using on-line update or off-line (downloading the update file)?

A separate question about multiboot on M.2 nvme pcie connectors:
it is possible to determine which M.2 slot is first recognized in this motherboard during boot, to prevent windows 10 from overwriting the EFI partition on the Mojave drive as explained in this thread:

Thanks in advance

ex

CaseySJ said:

I use a Kill-a-Watt device to monitoring wattage under both idle and high-load conditions. I don't keep this connected at all times, but only when needed.

Click to expand...

Think I have a similar device in my basement somewhere, simple but good advice, thanks!

CaseySJ said:

I omit darkwake altogether. The computer will still wake from sleep with one key, but the monitor will remain asleep until a second keystroke. I have a Logitech mouse as well, but I don't think mouse movements wake up the machine. I'm not aware of a strict two-key-to-wake setting -- I think that would require custom code.
Are you using a custom USB SSDT on your current build? If you can provide the make/model of your MIDI keyboard, perhaps someone with a similar device can respond or provide suggestions...

Click to expand...

Alight, assembling my new setup as-we-speak. Hope to get it up and running by Saturday. Keyboard is a Kawai VPC1 (usb 2.0) midi controller, thus far connected to my 3.5" front-bay USB2.0/3.0/sd-reader bay. And yes I've made my own USB SSD for mobo and external/Fenvi USB ports etc.

Since I'm assembling my new setup today/tomorrow I guess I'll forego my current case's front port bay for now (which now connects to my kawai vpc1) and opt for a DVD R/RW drive since the Fractal R6 case only sports a single 3.5"-bay. We'll see how it turns out, and I'll report when worth it.

SardusX said:

Hi,
Some question about 10.14.5 update:
- in the update guide you mean that you need to set the "Kernel and Kext Patches" section as in Your "final steps in post-installation" guide disabling the 3 USB port limit patches (and USB SSDT installed)?

Click to expand...

Because we have a USB SSDT, we should not use the USB port limit patches. But we still need to keep the USB SSDT and USBInjectAll.kext.

- Is it more appropriate using on-line update or off-line (downloading the update file)?

Click to expand...

On-line software update through System Preferences --> Software Update is the recommended way.

A separate question about multiboot on M.2 nvme pcie connectors:
it is possible to determine which M.2 slot is first recognized in this motherboard during boot, to prevent windows 10 from overwriting the EFI partition on the Mojave drive as explained in this thread:

macOS 10.14.X/WIN10/Linux UEFI Multiboot on separate 2 x nvme pcie SSD + 1 x Sata SSD

Hi All, I installed my current triple boot system (macOS 10.13.6/WIN10/Linux Clover Legacy) on a 1 x Sata SSD + 2 x Sata HDD connecting each time only the drive affected by each O.S. installation and installing Clover boot loader on the masOS Sata SSD. Now in my new build (Gigabyte Z390...

www.tonymacx86.com

Click to expand...

The M2M slot is recognized first (the one closest to the CPU). I learned this from (bad) experience:

• Mojave installed on M2M.
• Windows 10 installed on M2P.
• After a Windows update, it created a WINDOWS folder in the EFI directory on M2M, which prevented Clover from starting.

gundogg9999 said:

Yep I see the missing files now, although I remember doing this, I stuffed it up somewhere. Just plugged in a bunch of usb devices and restarted so far so good. I'll give it a few days and test it out. Thanks again.

Click to expand...

Casey..
Nope still got the USB problem. Just got a boot fail, unplugged some USB sticks, restarted and then it booted.
So USB ports still causing a problem it would seem.

What did you notice in the post install that I missed? I did all the steps but it seems the miss was files being copied to the patched folder.

Only thing I can think of is to double check all the steps (entire instructions) again... unless you got any more ideas?

Thanks,

SardusX said:

Hi,
Some question about 10.14.5 update:
- in the update guide you mean that you need to set the "Kernel and Kext Patches" section as in Your "final steps in post-installation" guide disabling the 3 USB port limit patches (and USB SSDT installed)?
- Is it more appropriate using on-line update or off-line (downloading the update file)?

A separate question about multiboot on M.2 nvme pcie connectors:
it is possible to determine which M.2 slot is first recognized in this motherboard during boot, to prevent windows 10 from overwriting the EFI partition on the Mojave drive as explained in this thread:

macOS 10.14.X/WIN10/Linux UEFI Multiboot on separate 2 x nvme pcie SSD + 1 x Sata SSD

Hi All, I installed my current triple boot system (macOS 10.13.6/WIN10/Linux Clover Legacy) on a 1 x Sata SSD + 2 x Sata HDD connecting each time only the drive affected by each O.S. installation and installing Clover boot loader on the masOS Sata SSD. Now in my new build (Gigabyte Z390...

www.tonymacx86.com

Thanks in advance

Click to expand...

Windows install doesn't actually "overwrite" anything on your Clover boot drive. It installs into your EFI partition's EFI folder, at the same level as the BOOT and CLOVER folders, a folder called Microsoft. inside that folder is a folder named Boot, inside which is a file named bootmgfw.efi. the presence of that file causes your machine to boot to windows rather than booting to the Clover screen.

So, before you install Windows, make sure you have a working USB boot stick. After you finish the Windows installation, including all the automatic reboots that are part of the Windows install process, boot from your USB stick, and ,at the Clover screen, select your OS X drive. At the Desktop, mount the EFI partition and navigate to EFI/Microsoft/Boot and rename bootmgfw.efi to something like bootmgfw-orig.efi.

Then remove your USB boot stick and reboot. It should boot to the Clover screen. There will be a new boot option called something like Boot from Microsoft EFI that will take you to your new Windows installation.

When Windows does one of its famous background major upgrades you may wake up one morning, turn on your hack, and find that it boots to Windows once again. Perform the above process, and you will find a new instance of EFI/Microsoft/Boot/bootmgfw.efi. Just rename it once again.

Just to give an update, the newly released LG UltraFine Display 4k (24MD4KL) works GREAT with the setup. Apple just started selling this display in the Apple store. Definitely worth it.

I currently have:

• i9-9900k
• Z390 Designaire w/ Thunderbolt 3
• 32gb Corsair Vengeance 3000Mhz
• ADATA SU8000 (128gb) (Clover/EFI)
• ADATA SU8000 (512gb) (Windows 10)
• Samsung 960 evo NVMe(256gb) (Scatch Disk/Test updates)
• Samsung 970 Pro NVMe (512gb) (MacOS Mojave 10.14.5 - Main)
• 860 evo (500gb) (MacOS Mojave 10.14.5 Bootable Backup)
• Sapphire RX580 8GB Nitro+
• NZXT H500

Will dual Vega 64's work with this build? Just curious !

tdcam said:

Will dual Vega 64's work with this build? Just curious !

Click to expand...

I don't see why not.

igadgetry said:

I don't see why not.

Click to expand...

Thanks I guess worth a try - I have one for another build that never happened so will see what happens thanks !