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

[CaseySJ]

Hello @CaseySJ, quick question:

My FENVI T-919 is arriving next week. A friend of mine who traveled to the states bought it for me and it's getting here next week. I forgot that having an NZXT Kraken X52, the only F_USB port in de Designare is already taken by the cooler.

My friend does not have any time left to buy the splitter you mentioned and wait for Amazon to send it back to the hotel. I found only one seller here in Argentina that sells one similar. Would it be too much if I ask you to take a look on this website to see if it is actually the same thing before I buy it?

Sorry for the inconvenience, I realized just now about this issue.

BTW, along with the FENVI card I also bought a 1-84 bits screwdriver set from Amazon so I don't strip any more screws...

Thanks in advance Master!

Hello @nifranza,

That splitter is perfect! Because it has 2 circuit boards tied together, one board will connect to HS11 and the other to HS12. If you connect the Kraken and Bluetooth to one of those boards, we can modify the USB SSDT to set the type to “Internal”. That allows the other board to connect to USB 2 ports on the front of your computer case (so we will set the Type to external). So once you have installed the splitter and connected Kraken and Bluetooth, please run IORegistryExplorer and upload the IOReg file (File —> Save As...) — or just grab a screenshot of HS11 and HS12.

 

[swoop69]

The problem should not occur in this case. Remember to physically remove macOS NVMe drives and disconnect any other SATA drives before starting to install Windows.

Removing NVMe drives can be inconvenient, but they will prevent Windows from being installed.

Would the Windows install then be visible on the Clover boot menu or do you have to specify a boot drive in bios?

Also, for backups using the method described in the guide, do the backup drive have to be the same size as the boot drive rice even though only a small portion is used (only system info).

 

[Blomski]

I updated just now, and all I did the computer do its work. All in black screen. Verbose mode stopped at some time and screen went black till it booted. After that, the welcome Catalina screen was there and configured the Mac.
My Firewire port with Apogee ensemble works with wake sleep, etc.
I'll use this for audio. So I am investigating if there are 32 / 64 bit problems in Logic, etc.

All looks good to me, till further notice.

Did not test second Ethernet port, and I do not use WiFi.

 

[kwalter]

In that case enable Verbose mode during boot. No need to change config.plist. Instead, at the Clover Boot Menu, press spacebar then move down to Verbose and press spacebar once to turn it on. Then boot Mojave and perhaps grab a video with your smartphone. There will be a barrage of log messages that might help narrow this down.

Since installing the Catalina update my system appears to be booting quicker, but I'm still having a weird problem with Bluetooth. On starting the computer, Bluetooth will either play up and drop connections or refuse to connect at all. If I delete the Bluetooth preference file and reboot, everything will be fine and will continue that way until I switch off. Next time I boot up I'll have the same problem again.
I have a card similar to the Fenvi with a Broadcom 94360 module, which worked 100% under Mojave
Any ideas anyone?

 

[CaseySJ]

...
next question - if i install windows on the top M2 slot, and install macOS on a PCI card w/ apple ssd (SSUBX) would the EFI partition issue from a windows update still be an issue for the macOS drive?

Good question. We haven't come across this case before so you're welcome to try it. Even if a future Windows Feature Update interferes with EFI partition of your Mojave SSD, it is quite easy to recover from it. Windows will just add a "WINDOWS" folder to the EFI partition, and Gigabyte's firmware prioritizes that. So we can always boot from a "non-interfered" EFI folder perhaps on a USB flash disk, login to MacOS, and from there we can Mount EFI partition and simply delete the "WINDOWS" folder.

 

[CaseySJ]

@CaseySJ
Finally, the Luna Display works now with SSDT-UIAC-DESIGNARE-Z390-V7B.aml. You made my day extremely. Thank you so much.

One thing to update, I've successfully connected the TB3 audio interface, Universal Audio Arrow. Arrow works like a charm with my DAW. This device would only work and be recognized after the UA software installation or it did not work before any UA software installation.

Glad to hear it! And UAD Arrow has been added to Thunderbolt 3 Experiences.

 

[CaseySJ]

That's the problem, I do exactly that and none of my EFIs agree to mount

Understood. Please try the following in Terminal:

1. Type the following command and post the output:

diskutil list

2. You have been trying to mount disk0s1. But first, let's verify disk0. Type this command:

diskutil verifyDisk disk0

If everything is okay you should see something like this:

Started partition map verification on disk0
Checking prerequisites
Checking the partition list
Checking the partition map size
Checking for an EFI system partition
Checking the EFI system partition's size
Checking the EFI system partition's file system
Checking the EFI system partition's folder content
Checking all HFS data partition loader spaces
Checking booter partitions
Checking Core Storage Physical Volume partitions
The partition map appears to be OK
Finished partition map verification on disk0

3. Now let's verify the disk0s1 volume by typing the following:

diskutil verifyVolume disk0s1

If everything is okay you should see something like this:

Started file system verification on disk0s1 EFI
Verifying file system
Volume is already unmounted
Performing fsck_msdos -n /dev/rdisk0s1
** /dev/rdisk0s1
** Phase 1 - Preparing FAT
** Phase 2 - Checking Directories
** Phase 3 - Checking for Orphan Clusters
96 files, 177023 KiB free (354046 clusters)
File system check exit code is 0
Restoring the original state found as unmounted
Finished file system verification on disk0s1 EFI

Please perform steps 1, 2, 3 and post the output from those commands.

 

[CaseySJ]

Thank you.
I calculated the system power usage that why i choose Bitfenix 550W.
https://www.bequiet.com/en/psucalculator . In system load 270 w maximum.
but if you think I'd rather buy 650w!

The memory has XMP 2.0 certified: https://www.kingston.com/dataSheets/HX430C15PB3K2_32.pdf

550W will be fine. Just keep in mind that if you upgrade to a more powerful GPU (e.g. AMD Vega or RX 5700/XT) or a more powerful CPU (i7-9700K or i9-9900K) then power consumption will increase significantly. But for the components in your current list, 550W is sufficient.

 

[CaseySJ]

Thanks for your reply Casey! Because it was also checked in your guide (Final steps in post installation) I also checked it. Followed it to the letter, still learning in hindsight what the options do.
Both MX500 have different names: MacOS and MacOS Backup. I'll keep an eye on the nvram.plist if I was just mistaken.

I'll have to revise that screenshot!

Update: Screenshots revised.

 

[Etyel]

Let's go :

1.
/dev/disk0 (internal):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                         2.0 TB     disk0

   1:                        EFI EFI                     209.7 MB   disk0s1

   2:                 Apple_APFS Container disk1         2.0 TB     disk0s2



/dev/disk1 (synthesized):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      APFS Container Scheme -                      +2.0 TB     disk1

                                 Physical Store disk0s2

   1:                APFS Volume Hackintosh SSD          355.5 GB   disk1s1

   2:                APFS Volume Preboot                 45.3 MB    disk1s2

   3:                APFS Volume Recovery                510.4 MB   disk1s3

   4:                APFS Volume VM                      2.1 GB     disk1s4



/dev/disk2 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *6.0 TB     disk2

   1:                        EFI EFI                     209.7 MB   disk2s1

   2:                  Apple_HFS Stockage                6.0 TB     disk2s2



/dev/disk3 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *8.0 TB     disk3

   1:                        EFI EFI                     209.7 MB   disk3s1

   2:                  Apple_HFS Applications            8.0 TB     disk3s2



/dev/disk4 (external, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *3.0 TB     disk4

   1:                        EFI EFI                     209.7 MB   disk4s1

   2:                  Apple_HFS Sauvegarde              3.0 TB     disk4s2



/dev/disk5 (external, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *4.0 TB     disk5

   1:                        EFI EFI                     209.7 MB   disk5s1

   2:                  Apple_HFS Hackintosh SSD Local... 4.0 TB     disk5s2



/dev/disk6 (external, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *4.0 TB     disk6

   1:                        EFI EFI                     209.7 MB   disk6s1

   2:                  Apple_HFS DD 8 Applications       4.0 TB     disk6s2


2.
Started partition map verification on disk0

Checking prerequisites

Checking the partition list

Checking the partition map size

Checking for an EFI system partition

Checking the EFI system partition's size

Checking the EFI system partition's file system

Checking the EFI system partition's folder content

Checking all HFS data partition loader spaces

Checking booter partitions

Checking Core Storage Physical Volume partitions

The partition map appears to be OK

Finished partition map verification on disk0

3.
Started file system verification on disk0s1 EFI

Verifying file system

Volume is already unmounted

Performing fsck_msdos -n /dev/rdisk0s1

** /dev/rdisk0s1

** Phase 1 - Preparing FAT

** Phase 2 - Checking Directories

** Phase 3 - Checking for Orphan Clusters

227 files, 176374 KiB free (352748 clusters)

File system check exit code is 0

Restoring the original state found as unmounted

Finished file system verification on disk0s1 EFI