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

[McGregorWin]

There are several versions of HWMonitor. The one that comes with FakeSMC will not work with VirtualSMC. With VirtualSMC and HWMonitorSMC 2.5.x we can monitor CPU speed, CPU temp, one core voltage, and motherboard fans. To switch from FakeSMC to VirtualSMC, please see the guide here:

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

First a thank you for your efforts on this one - I managed to get a working Designare system working from this thread with no problems at Then I thought I'd resurrect my Maximus ROG Hero X MB with Mojave Now having made a complete backup of my Designare system, I thought I'd try booting my Hero...

www.tonymacx86.com

To have more PCI entries show up, please see Post #1, Specifying Device Names and Types.

What are you running? Fake or Virtual? I'm not that hyped from the stats, was just curious. Also will FakeSMC even work with Z390?

 

[CaseySJ]

What are you running? Fake or Virtual? I'm not that hyped from the stats, was just curious. Also will FakeSMC even work with Z390?

I’m using VirtualSMC, which is recommended for now and the future. I think we used VirtualSMC in your setup already, so you’ll just need to download HWMonitorSMC 2.5.x from the HWSensors3 project or from the link in previous reply.

 

[CaseySJ]

Good Morning,
I noticed a problem on Catalina with external disks.
When I have it ejected correctly, only when the disk is a clone and has a DATA partition, this partition is not ejected and I always get the message that the disk was not ejected correctly.
Do you rent solution for this?
Thanks

When you eject a disk that has multiple mounted partitions, macOS will present a dialog asking whether you want to eject all mounted volumes. Click Yes.

 

[Rag]

When you eject a disk that has multiple mounted partitions, macOS will present a dialog asking whether you want to eject all mounted volumes. Click Yes.

Thank you @CaseySJ
But that's not what happens, here does not appear the option to unmount all drives.
I believe the problem is related to the disks being mounted on Thunderbolt, and this .DATA partition does not appear on the desktop when mounted. The system only complains when I turn off the disk, then it says that the .DATA partition was not ejected correctly.

 

[McGregorWin]

I’m using VirtualSMC, which is recommended for now and the future. I think we used VirtualSMC in your setup already, so you’ll just need to download HWMonitorSMC 2.5.x from the HWSensors3 project or from the link in previous reply.

Mine is showing these, as in pic. Also ive followed your guide on Specifying Device Names and Types but the config file doesnt save the added text, everytime i press synchronize and save and close and re open it, the text is gone from Devices line.

 

[WhosMac]

Hello @WhosMac

Because you're planning to do a fresh install of Catalina 10.15.1 with a Radeon RX 5700 XT, you could be our test subject for an updated installation procedure. Certain steps will be replaced with new versions of UniBeast and MultiBeast in the future.

If you're willing to be a test subject, please try the mini guide below that streamlines most of the work. By the way:

• What is the make/model of your NVMe SSD?
• Are you using a WiFi/BT card such as Fenvi FV-T919? If so, which slot is it in?

** Experimental Mini-Guide for Direct Installation of Catalina 10.15.1 **​

Preparation:

• Set BIOS parameters according to main guide in Post #1.
  • Set Initial Display Output to PCIe 1 Slot (if RX 5700 XT is in Slot 1)
• Connect monitor to RX 5700 XT.

Step 1: Create USB Install Disk

• Use a 16 to 32 GB flash disk.
• Format the disk in Disk Utility. Select View --> Show All Devices and click the parent name of your USB disk on left sidebar. Then select Erase and enter:
  • Name: Catalina-USB (use exactly this name)
  • Format: MacOS Extended (Journaled) --- do not use APFS here
  • Scheme: GUID Partition Map
• Download Clover v5098 or newer from GitHub by clicking here and downloading the xxxx.pkg file.
  • Launch the Clover installer and allow the app to run (System Preferences --> Security & Privacy --> General).
  • Click Continue, Continue, Change Install Location... and select the USB flash disk!
  • Then click Customize -- don't overlook this.
  • These 2 buttons are located here:
    View attachment 436339
  • Check that the Customize page looks exactly like this:
    View attachment 436340
  • Notice that Install RC scripts on target volume is unchecked. This is where you become our test subject! We'd like to start the installation without rc scripts and see what happens with shutdown and reboot. If shutdown and reboot don't work, then we can come back and install rc scripts.
  • Click the Install button.
• Download Catalina installer from App Store on a supported Mac. Check that it's in the Applications folder.
  • Also check that the USB disk has been mounted and its name is Catalina-USB
  • Open a Terminal window and type:
    sudo "/Applications/Install macOS Catalina.app/Contents/Resources/createinstallmedia" --volume /Volumes/Catalina-USB
  • Enter your Mac password when requested.
  • If you encounter any errors, stop and report those errors.
• Copy Clover Configurator to the standard partition of the USB flash disk (not the EFI partition).
• The EFI partition of the USB install disk will already be mounted (Clover installer will do this automatically).
  • Open the EFI Folder on the EFI partition of USB disk. You'll see a CLOVER folder, of course.
  • Open the CLOVER folder.
  • Download the attached Catalina Fresh Install.zip into your Downloads folder on the Mac (not on the USB disk).
    • Open the CLOVER/drivers/UEFI folder on the USB disk (EFI partition) and:
      • Delete all files in that folder and empty the trash.
      • Locate the folder Copy-to-drivers-UEFI in the above ZIP file you downloaded.
      • Copy all .efi files from this folder into the CLOVER/drivers/UEFI folder.
    • Open the CLOVER/kexts/Other folder on the USB disk (EFI partition) and:
      • Delete all files in that folder and empty the trash.
      • Locate the folder Copy-to-kexts-Other in the above ZIP file you downloaded.
      • Copy all .kext files from this folder into the CLOVER/kexts/Other folder.
    • Open the CLOVER/ACPI/patched folder on the USB disk (EFI partition) and:
      • Locate the Copy-to-ACPI-patched folder in the above ZIP file you downloaded.
      • Copy all .aml files from this folder into the CLOVER/ACPI/patched folder.
    • Finally, locate config.plist in the same ZIP file you downloaded.
      • Copy the config.plist to the CLOVER folder on the USB install disk, overwriting the one that is there already.
      • Now open the config.plist (from USB install disk) with Clover Configurator 5.7.0.0 or newer.
        • Go to the SMBIOS page.
        • Click the pop-up menu on the lower right and select iMac19,1.
          View attachment 436342
        • Everything else is already set in this file. So save it and quit Clover Configurator.
• Eject the USB flash disk.

Step 2: Install Catalina

• Insert the USB install disk into the Hackintosh and boot.
• Press F12 at BIOS Splash screen to bring up the BIOS Boot Menu and select the USB flash disk.
• When Clover Boot Menu appears, select Boot macOS Install from Catalina-USB
• Follow the onscreen progress and report any issues.
• When the installer starts, you'll need to run Disk Utility from inside the installer, select your target Catalina NVMe SSD, and format it.
  • Be sure to select View --> Show All Devices
  • Then select:
    • Name: Catalina (you can change it later)
    • Format: APFS
    • Schema: GUID Partition Map
  • Then begin the macOS installer.
• There might be one or two reboots.
• Whenever the system reboots and you're back in the Clover Boot Menu:
  • Whenever you see a boot option called Boot macOS Install from Catalina, choose that option.
  • Do not select the USB disk. The USB disk is selected only one time at the very beginning.
• If everything goes according to plan, you'll be greeted with the Catalina Welcome screen.
  • Follow the onscreen guide.
  • You may also sign in to iCloud when asked.
• If you encounter any problems, stop and let us know.

Step 3: Post Installation

• We'll make this really simple for now.
• Run Clover Configurator which was copied to the USB flash disk in Step 1.
  • Click Mount EFI on left sidebar of Clover Configurator
  • Mount EFI partitions of (a) USB flash disk and (b) Catalina SSD.
  • Copy the entire EFI Folder from EFI partition of USB disk to EFI partition of Catalina SSD.
• Eject USB flash disk.
• Reboot directly from Catalina SSD.
• Does it work? Report any issues.

I’m more than willing to be a test subject for a fresh install method especially if I’ve got y’all a support haha as soon as parts arrive I can update I’ll follow the mini guide.

Also because of the limitations to SATA on the Mobo was only planning on populating 1 m.2 slot in the Mobo in M.2P which would lose me only 1 SATA port in comparison to 3 with both populated.
- Samsung 970 EVO 500GB NVMe
Also will be using WiFi/BT card ordered the
-Fenvi FV-T919
you recommended In the guide. Any particular slot it should be populated in?

 

[zipb]

I adapted the EFI folder that CaseySJ posted a couple of pages back for my setup.
This means I updated to VirtualSMC/OcQuirks-4/Clover 5098.
All is well for now. Let's see what happens over the coming weeks. I made a backup of my EFI folder just in case something goes wrong.
Still on MacOS10.14.6, BTW.

 

[gandem]

Ouch! We appreciate your sacrifice on the alter of the bleeding edge.

Does this mean that devices connected directly to the Thunderbolt 3 ports on back panel are working properly?

But devices connected to the CalDigit dock are not working?

Have you tried all the "basic" things yet such as:

• Fully power down the dock (unplug it) for about 10 seconds.
• Fully power down the computer (unplug it) for about 10 seconds.
• Then boot to macOS first.
• Re-verify that BIOS --> Thunderbolt Security is still No Security.
• It might even be worth reseting CMOS (shorting two designated pins on motherboard) and reconfiguring BIOS parameters.

Not sure what this means. Updating the FW should not move the card to a different ACPI path, but you're probably not referring to that. Where are you seeing "NVM 43"?

So I’m away from the system but here is what I have determined so far:

To answer your questions- when I boot into macOS or Windows- I can then plug in any TB3 device I choose, and it works. This includes the TS3 plus. The NVM the firmware version of the TR card itself. I can only see this on the Windows side using the Thunderbolt Software Panel. I have a screen capture of this which I will post later today. This originally reported the card at NVM Firmware version 23. After the update it shows NVM Firmware version 43. I have reset the MB several times now. Have also reverted the bios F9 (now back at F10) The behavior continued exactly the same in Windows and in macOS- with no security setting in BIOS, if you boot into either OS with any TB3 device plugged in it will not be recognized. The only exception to this is the DP port on the TS3 Plus and USB-c to HDMI (video devices). On the Windows side- booting with the TS3 Plus connected-nothing is recognized, however the Thunderbolt Software panel shows the CalDigit connected. So I decided to turn User Authentication on. I then boot into Windows- get prompted to allow the device- and all works! I then then disabled security- booted into macOS and nothing- still dead sky. Then still in macOS- I plug in TB3 Drives directly to the TR card and they mount and eject as normal. Hot plug is still working. Next I thought well what happens if I unplug the TS3 Plus and plug it back in? Guess what, it came to life! All USB ports, audio in/out ports, Ethernet, card reader, all of it. So what I have determined, I have to wait until after boot to plug in any TB3 devices. If it’s plugged in during boot, it’s ignored. Again, identical behavior in Windows. The only time it works in Windows on boot is if user authentication is enabled in bios and I have allowed the device in Windows. So No security setting appears to be broken in the bios (or bug in new TR firmware) as this affects Windows as well.

I might try changing the slot I have the card in- but I doubt that will work. If you have any suggestions let me know. It sounds like it could be resolved with a bios update. Hoping!

UPDATE- I have the GC-Titan Ridge card working 100% again. I had to change one item in the bios- Thunderbolt Boot Support had to change from "disabled" to "boot once". Hot plug and all devices now work again when plugged in on boot! Happy Happy Joy Joy! Have also attached the Thunderbolt Software panel from Windows indicating the new NVM firmware version from the update.

 

[CaseySJ]

Mine is showing these, as in pic.

That's actually not the correct HWMonitor app. The one we want is in the post I linked to previously (Mini-Guide for switching from FakeSMC to VirtualSMC). See Step 5 here.

Also ive followed your guide on Specifying Device Names and Types but the config file doesnt save the added text, everytime i press synchronize and save and close and re open it, the text is gone from Devices line.

Please check that you're selecting the correct config.plist -- in the EFI/CLOVER folder of the EFI partition of the Catalina SSD.

 

[CaseySJ]

I’m more than willing to be a test subject for a fresh install method especially if I’ve got y’all a support haha as soon as parts arrive I can update I’ll follow the mini guide.

Also because of the limitations to SATA on the Mobo was only planning on populating 1 m.2 slot in the Mobo in M.2P which would lose me only 1 SATA port in comparison to 3 with both populated.
- Samsung 970 EVO 500GB NVMe
Also will be using WiFi/BT card ordered the
-Fenvi FV-T919
you recommended In the guide. Any particular slot it should be populated in?

Very good -- yes of course we'll support you with the installation.

As for the Fenvi, it should be installed in the bottommost short (PCIe x1) slot.

Have you considered the NZXT H710i? The built-in Smart Device RGB/Fan controller can be controlled from within macOS with liquidctl 1.3.0rc1. We've streamlined the installation process for liquidctl by using Homebrew as described at the bottom of this post.