Contribute
Register

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

Using the files provided in Catalina 10.15.4 Fresh Install.zip macOS Mojave seems to start normally.

I need clarification: wanting to install macOS Catalina by creating a second APFS Volume on the same drive in a dualboot configuration I should use the same Catalina package 10.15.4 Fresh Install.zip or I should use the new May 2020 Update package to create the new Catalina USB install disk?
It's a good thing that you were able to test both the original "Catalina 10.15.4 Fresh Install" package and the new "May 2020 Update". Now we know that the May 2020 update does not play nicely with Mojave.

If you intend to have both (a) Mojave and (b) Catalina on the same physical SSD, but on different APFS Volumes, then the EFI folder needs to be capable of booting either of the two macOS versions. Right now only the original "Catalina 10.15.4 Fresh Install" can do that.
After having possibly installed macOS Catalina, will it be possible to start Mojave or Catalina using the same configuration that I just verified working with macOS Mojave?
Yes -- if we use the original "Catalina 10.15.4 Fresh Install" zip package.
Furthermore, with the latest changes, a problem arose: in my multiboot system I have a separate drive with Ubuntu 18.04 with GRUB as Master bootloader, using the latest version of Clover (5119) selecting the Ubuntu entry from the Clover menu the GRUB menu appears but selecting any linux boot entry (i have several distributions installed in this drive) none of them start differently than what happen using the Clover 4920 version. I know that between the two versions of Clover there was an update Folders structure but I don't know if it could depend on this or on lack/update of some drivers.
...
I've become quite a fan of Kubuntu 20.04 and also have a copy installed on a separate SSD in the Z490 Vision D. During installation I used the "manual" option to create a 200MB EFI partition and pointed the Boot Loader to the Linux disk (but not specifically to the EFI partition). However, because I'm using OpenCore on the Vision D, it does not currently recognize or boot Linux. So I always press F12 at the BIOS splash screen and choose the Linux disk. That always works.

In your case, however, some questions:
  • Are you saying that with Clover v4920 you were able to boot the Linux installation(s) properly?
  • But after the switch to Clover v5xxx the Grub boot loader appears, but Grub is unable to boot Linux?
 
Hi all,
First: congratulations and thanks for this great job!

I followed this micro guide for flashing firmware of my Gigabyte GC-Titan Ridge using Raspberry Pi.

I'm on the X299 machine that's in signature, OC 0.5.9. Titan Ridge is on slot-2 on the mb and Radeon VII on slot-5.
I patched the Titan Ridge with NVM23 firmware and I think the operation was successful on the first attempt: everything worked out according to the guide: the card showed up in System Report>Thunderbolt, as did the Thunderbolt Bridge in System Preferences>Network.

But... hotplug was broken, which was working without problems before.
By restoring the original firmware, hotplug will work again.

Maybe I did something wrong? Can you please help me?
Many thanks.
 

Attachments

  • EFI-gfabio.zip
    2.2 MB · Views: 67
  • ioReg-gfabio.zip
    5.9 MB · Views: 96
Hi all,
First: congratulations and thanks for this great job!

I followed this micro guide for flashing firmware of my Gigabyte GC-Titan Ridge using Raspberry Pi.

I'm on the X299 machine that's in signature, OC 0.5.9. Titan Ridge is on slot-2 on the mb and Radeon VII on slot-5.
I patched the Titan Ridge with NVM23 firmware and I think the operation was successful on the first attempt: everything worked out according to the guide: the card showed up in System Report>Thunderbolt, as did the Thunderbolt Bridge in System Preferences>Network.

But... hotplug was broken, which was working without problems before.
By restoring the original firmware, hotplug will work again.

Maybe I did something wrong? Can you please help me?
Many thanks.
The IOReg file shows that GC-Titan Ridge is configured correctly. In some cases we need to do one warm-reboot in order to activate the card. But even when activated, the GC-Titan Ridge can behave slightly differently on different motherboards.

Most people who flash their Thunderbolt add-in-cards will determine how to work around some of the limitations or issues. Others will put the original firmware back. So far we have found that the best Thunderbolt behavior occurs only with on-board Thunderbolt controllers instead of PCIe cards.
 
...
This is the current UEFI drivers folder in my previous USB mojave install disk based on Clover v. 4920:
View attachment 476932
this is the current UEFI drivers folders created with Catalina 10.15.4 Fresh Install.zip package and based on Clover v.5119
View attachment 476933
...
Ouch! The drivers64UEFI folder must be deleted completely and immediately. Empty the trash after moving the whole folder into it. Because you're already on Clover 5xxx now, the screenshot below is just FYI.

Screen Shot 2020-06-18 at 11.11.21 AM.png
 
But... hotplug was broken, which was working without problems before.
By restoring the original firmware, hotplug will work again.

Maybe I did something wrong? Can you please help me?
Many thanks.

Use NVM33 on your Titan AIC since in all my testing it works the best.
 
okay I have 10.13.6 installed and the interface will not connect can she my efi pls ? Apollo twin work pervekt and the
Vendor Name: GIGABYTE
this the antelope thunderbolt buss found not under pci I have not the perfect kext and ssdt ? for the 390 designer can help me ?

Code:
  Device Name:    iMac


  UID:    0x00ED0482A1405400


  Route String:    0


  Firmware Version:    50,0


  Domain UUID:    C59A91DD-ED88-4767-A06D-0A61B952621D


  Port:


  Status:    Device connected


  Link Status:    0x2


  Speed:    Up to 10 Gb/s x2


  Current Link Width:    0x1


  Receptacle:    1


  Cable Firmware Version:    1.0.16


  Cable Serial Number:    C4M733201LFF798AZ


  Link Controller Firmware Version:    1.37.0


  Port:


  Status:    No device connected


  Link Status:    0x7


  Speed:    Up to 20 Gb/s x2


  Current Link Width:    0x1


  Receptacle:    2


  Link Controller Firmware Version:    1.37.0





Discrete4:





  Vendor Name:    Antelope Audio


  Device Name:    Discrete4


  Vendor ID:    0xB4


  Device ID:    0x80


  Device Revision:    0x1


  UID:    0x00B431A5A5BD27B0


  Route String:    1


  Firmware Version:    25,1


  Port (Upstream):


  Status:    Device connected


  Link Status:    0x2


  Speed:    Up to 10 Gb/s x2


  Current Link Width:    0x1


  Cable Firmware Version:    1.0.16


  Cable Serial Number:    C4M733201LFF798AZ


  Link Controller Firmware Version:    0.14.0
 

Attachments

  • EFI.zip
    4.5 MB · Views: 76
Use NVM33 on your Titan AIC since in all my testing it works the best.

Are you using DESIGNARE-Z390-NVM33-Elias64Fr.bin? I forgot if you were using any thunderbolt docks with display out? Using both display outs on the Caldigit TS3 Plus did not work for me on flashed NVM23 and NVM50 or stock NVM43.
 
okay I have 10.13.6 installed and the interface will not connect can she my efi pls ? Apollo twin work pervekt and the
Vendor Name: GIGABYTE
this the antelope thunderbolt buss found not under pci I have not the perfect kext and ssdt ? for the 390 designer can help me ?
...
If Antelope Audio does not work automatically with High Sierra then you have two options:
  • Contact Antelope Audio technical support
  • Use a real Mac
Please see Thunderbolt 3 Experiences in Post #1:

Screen Shot 2020-06-18 at 1.04.01 PM.png
 
*** Mini-Guide ***
Mojave Users: Configure Carbon Copy Cloner for One-Key Bootable Backup


These instructions are for Mojave (10.14.x) users only. Catalina users should refer to the Mini-Guide below.

Update 8-Mar-2020:
We are now using @byteminer's EFIClone from his GitHub repository. Instructions are provided in the spoiler below. Note that the script has TEST_SWITCH set to "Y". This puts the script in dry-run mode in which it will only log the files to be deleted and copied, but will not delete or copy any files.
  • Your first cloning operation should be run with TEST_SWITCH set to "Y". Then examine EFIClone.log as described at the bottom of the procedure to ensure that only files in the source and target EFI partitions are listed in the log.​
  • If files from any other disks or partitions are listed in the log, then STOP AND POST YOUR EFIClone.log file.​
  • However, if the log looks good, then edit the script, change TEST_SWITCH to "N" at the top of the file and save. The file can be found by selecting Utilities --> Reveal CCC's Scripts Folder from within Carbon Copy Cloner. Edit the file located in the Finder window that opens and save it with TEST_SWITCH changed to N.​
Prerequisites: These steps are only performed once on a new SATA SSD.
  • Purchase or use a 2.5-inch SATA SSD that is large enough to hold everything in your Mojave OS disk. The backup disk only needs to be as large as the amount of space used on the source disk. If the source disk is 1TB, but only 100GB is used, then a 128GB backup SSD is sufficient.
  • Purchase or use a USB 3 external SSD enclosure. These can be purchased from Amazon for under US$10. Here's an example.
  • Install the SATA SSD into the USB 3 enclosure and connect the USB 3 cable to an available blue, yellow or red USB 3 port on the Hackintosh.
  • Run Disk Utility, select View --> Show All Devices, and click on the parent name of the external USB SSD. Double-check that all of these steps have been followed; ask for help if necessary.
  • Select Erase and make sure that a dialog appears with 3 options:
    1. Name: Select something like "Mojave Local Backup".
    2. Format: Select "APFS" (the first item in the pop-up menu).
    3. Scheme: Select "GUID Partition Map". This option is necessary so that an EFI partition gets created.
  • Click Erase at the bottom right of the dialog.
  • Check that Carbon Copy Cloner has Full Disk Access by selecting Grant Full Disk Access to CCC... as shown:
    full

Your SATA SSD will be divided into a primary APFS partition and a secondary EFI partition. When formatting is complete, only the APFS partition will be mounted.

Now we're ready to set up our one-key backup task in Carbon Copy Cloner. This task will copy everything from the APFS and EFI partitions to the external USB SATA SSD.

Step 1: Create Backup Task
  • Run Carbon Copy Cloner (CCC) and create a new backup task by selecting your Mojave SSD as the SOURCE disk and your external USB SATA SSD as the DESTINATION disk. Note that you must select the currently booted Mojave SSD as the Source disk.
  • Click on ADVANCED SETTINGS to expand that section, but don't make any changes there yet.
  • Give the task a name on the left side panel.
  • Compare your screen with the screenshot below. I've named my task Full Mojave Local Backup.
    full
Step 2: Attach EFIClone.sh script for automated backup of EFI partition
  • Download EFIClone.sh by clicking here and selecting the green button Clone or download as shown:
    View attachment 453650
  • IMPORTANT NOTE: Because this file is downloaded from the web, it may automatically receive a "quarantine" flag in macOS. Simply run Terminal, "cd" to the folder containing the file, and type xattr -d com.apple.quarantine EFIClone.sh. Then quit Terminal and continue to next step.
  • Open Finder and navigate to the folder containing this file.
  • From Carbon Copy Cloner's Utilities menu, select Reveal CCC's Scripts Folder as shown.
    full
  • Drag and drop EFIClone.sh into the Scripts folder. Mojave will ask for authentication, so enter your password when requested. The Scripts folder should look like this:
    View attachment 453651
  • Now we need to fix ownerships and permissions, which is done easily from the same Utilities menu. When this menu is now selected, notice that the last option has changed to Secure CCC's Scripts folder. Choose this item now.
    full
  • Great. We're nearly done. Now let's attach our script to the backup task by clicking the folder icon next to AFTER COPYING FILES --> Run a Shell Script and selecting EFIClone.sh.
    View attachment 453653
  • Verify that your screen matches the items in the red box below.
    View attachment 453654
  • Save the task by pressing CMD-S or File --> Save.

Step 3: Test Run
  • Make sure that the external USB SATA SSD is mounted.
  • Click the Clone button at the bottom right of the CCC window.
  • From the Utilities menu, select Terminal to open a Terminal window.
  • In the Terminal window, type tail -f /EFIClone.log.
  • When the main APFS partition has been backed up, CCC will invoke the EFIClone script. At that time you will see detailed logs messages in the Terminal window.
  • Press CONTROL-C to stop the log display and quit Terminal.
  • When the CCC backup task is complete, press OK at the top right.
  • Use Clover Configurator or EFI Agent to mount the EFI partition of the external USB SATA SSD.
  • Open the CLOVER folder on that partition and check that everything has been copied.
  • Finally, reboot your machine and press F12 at the BIOS splash screen to select the USB SSD as the boot drive.
  • From the Clover Boot Menu, select "Boot macOS from Mojave Local Backup" (replace "Mojave Local Backup" with the actual name you gave to the USB SSD).
  • Make sure Mojave can boot up fully. Then reboot, disconnect the USB SSD, and boot from the internal Mojave SSD.

Keep your bootable USB SSD up to date by running CCC periodically. Simply boot from the normal internal disk, mount the USB SSD, and run the CCC backup task. It will mount both the source and destination EFI partitions automatically and then dismount both EFI partitions after the clone is complete.

If your clone or backup disk is internally mounted (always present in the system), it may be a good idea to disable Spotlight search on that drive because it's just a duplicate. This can be done from System Preferences --> Spotlight as follows:
View attachment 431606

I have followed this guide before and it worked great. But on a new system I'm building, the backup clone doesn't seem to work on its own. When I boot to Clover on the internal disk, I can open MacOS on the backup just fine. But when I boot to Clover on the backup disk, Clover recognizes MacOS on both the disks (see photo attached), but it can't actually initialize the boot sequence on either one (see second photo attached).

I tried updating Clover to 5xxx but got the same result. Any suggestions?
 

Attachments

  • IMG_20200618_152933.jpg
    IMG_20200618_152933.jpg
    4.7 MB · Views: 54
  • IMG_20200618_152951.jpg
    IMG_20200618_152951.jpg
    4.3 MB · Views: 62
@CaseySJ I'm having the most I'll fated time trying to follow the mini guide on Clean Installing Catalina 10.15.4+. I've stumbled at every bloody hurdle so far!
First I could not get SIP disabled, but I managed to figure that out after quite a bit of experimenting. Now I get this error when installing. Before you ask, it is a new (ish). Sandisk 16Gb USb 3.0. It has only been used for the previous successful Catalina Install late last year. Now I'm getting an error "The Install failed". Install log is attached.
When I look at my USB it looks like the clever and EFI was installed....
 

Attachments

  • Installer Log 19-Jun-2020.txt
    41.3 KB · Views: 100
  • Screen Shot 2020-06-19 at 09.21.22.png
    Screen Shot 2020-06-19 at 09.21.22.png
    1.1 MB · Views: 70
Last edited:
Back
Top