Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580

[CaseySJ]

Hello @CaseySJ

I have a question. There is no available gigabyte vision D in US market now, unfortunately. I got a vision G Z490 and bought GC titan bridge separately.

It Looks like your “Modifications for Z490 Vision G” assumes that tb3 is not used.
However, I have GC titan bridge. In this case, what should I do to use GC titan bridge? Can I just skip “Modifications for Z490 Vision G”? Thank you for your time

It's relatively straightforward to add Thunderbolt hot plug support. Your GC-Titan Ridge will work without any changes, except for hot plug. So we need to do this:

• Install GC-Titan Ridge into a long slot.
• Connect Thunderbolt header cable to motherboard.
• In BIOS, set the following:
  • Thunderbolt Support --> Enabled
  • Thunderbolt Security --> No Security
  • GPIO3 Force Pwr --> Enabled
• Download and run IORegistryExplorer and search for Thunderbolt
• Capture and post a screenshot of IORegistryExplorer showing the search results
  • Press CMD-Shift-5 to capture screenshot; it will be saved to desktop
• Then we can provide or point you to the appropriate Thunderbolt hot plug SSDT

 

[ErnieSalad]

I might get in on this Thunderbolt action too. I am also part of this crew of Vision G + GC Titan Ridge users like @leekh3 arriving here now that Vision D is off the market.

Here is my screenshot:

 

[Higgie]

I'm having a little bit of trouble separating my Home folder from my macOS SSD as suggested in the guide.

What I've accomplished:

• Created separate APFS Volume
• Copied original "Home" folder contents to the new volume
• Pointed macOS to my newly created volume containing the Home folder - All works fine.
• Deleted original "Home" folder from the main OS SSD

Now here is where my problem arises: Even after emptying the Trash, macOS refuses to acknowledge the now "free" space. So even though my User folder is completely gone from the SSD, and now lives on a separate volume, macOS still won't backup my macOS volume to my external SSD as the backup drive (240GB) is too small.

Any ideas? I've tried Googling but to no avail.

Ok turns out it was CCC Snapshots taking up the space! I’ve deleted them and now my main OS SSD is down to a tidy ~80GB.

I’ve cloned the macOS drive to my external SSD and copied my EFI folder over using EFIClone.sh - but booting from the EFI on the external backup and choosing the backup drive I get the attached error during startup. If I use my original EFI, the backup boots fine. Very strange!

 

[CaseySJ]

Hello @CaseySJ

I have a question. There is no available gigabyte vision D in US market now, unfortunately. I got a vision G Z490 and bought GC titan bridge separately.

It Looks like your “Modifications for Z490 Vision G” assumes that tb3 is not used.
However, I have GC titan bridge. In this case, what should I do to use GC titan bridge? Can I just skip “Modifications for Z490 Vision G”? Thank you for your time

I might get in on this Thunderbolt action too. I am also part of this crew of Vision G + GC Titan Ridge users like @leekh3 arriving here now that Vision D is off the market.

Here is my screenshot:

Please follow this procedure:

• Step 1: Visit https://hackindrom.zapto.org
• Step 2: Click the drop-down list of controllers

• Step 3: Select your controller

• Step 4: Click Search

• Step 5: Search for RP21 and replace with RP05 as shown
• Step 6: Click All to replace all occurrences

• Step 7: Confirm the changes and click Compile

• Step 8: When compiling is done, a green Download button will appear. Click it and the Thunderbolt hot plug SSDT will download to your Downloads folder.
  • File name will be SSDT-TB3-HackinDROM.aml
  • Copy this file to the EFI/OC/ACPI folder in the EFI partition of your macOS SSD.

Finally, open your config.plist in OpenCore Configurator and make sure it is set to the right version. Look at the OpenCore version string in the title bar of the App.

Then add a reference to the new SSDT as shown:

Save the modified config.plist and reboot. Then test whether Thunderbolt devices can hot plug.

Do NOT go to System Information --> Thunderbolt. Ignore whatever it says. Just check if Thunderbolt devices hot plug and work.

 

[CaseySJ]

Ok turns out it was CCC Snapshots taking up the space! I’ve deleted them and now my main OS SSD is down to a tidy ~80GB.

I’ve cloned the macOS drive to my external SSD and copied my EFI folder over using EFIClone.sh - but booting from the EFI on the external backup and choosing the backup drive I get the attached error during startup. If I use my original EFI, the backup boots fine. Very strange!

View attachment 530302

Hmm, on the backup disk try changing SecureBootModel to Disabled and see if it will boot.

 

[Anastasius]

I know it may be a very exotic question, but when everything works so fine (thanks again to @CaseySJ) you need it to be perfect

Does anybody's Apple TV+ App play HDR content on Big Sur? Mine doesn't. Is there any place/config to look at?

I have an HDR10 DisplayPort 1.4 display, it's totally recognized by macOS 11.6, YouTube plays HDR, IINA plays HDR, it's supported everywhere systemwide. Except Apple TV+ App. It does display the 4K picture, but no HDR.

 

[Higgie]

Hmm, on the backup disk try changing SecureBootModel to Disabled and see if it will boot.
View attachment 530304

Thanks again for your help Casey. Unfortunately it’s already set to disabled.

Just for clarity’s sake:

M.2 Boot drive contains EFI, and macOS
USB-C External is an exact clone made with CCC and EFIclone.sh

I press F12 at boot and the following happens:

• Choose M.2 partition, I can boot macOS from original M.2 or backup with no problem
• Choose the EFI on the cloned drive, I can boot the original M.2 but not the clone

So for some reason, the cloned EFI will not boot the cloned drive. But every other permutation works flawlessly. So there doesn’t seem to be anything wrong with the EFI (as it boots the original M.2) nor the backup (boots fine from the original EFI)

 

[CaseySJ]

Thanks again for your help Casey. Unfortunately it’s already set to disabled.

Just for clarity’s sake:

M.2 Boot drive contains EFI, and macOS
USB-C External is an exact clone made with CCC and EFIclone.sh

I press F12 at boot and the following happens:

• Choose M.2 partition, I can boot macOS from original M.2 or backup with no problem
• Choose the EFI on the cloned drive, I can boot the original M.2 but not the clone

So for some reason, the cloned EFI will not boot the cloned drive. But every other permutation works flawlessly. So there doesn’t seem to be anything wrong with the EFI (as it boots the original M.2) nor the backup (boots fine from the original EFI)

Which version of macOS is this?

On Big Sur and Monterey we have to allow CCC to erase the destination disk as follows:

 

[Higgie]

Which version of macOS is this?

On Big Sur and Monterey we have to allow CCC to erase the destination disk as follows:
View attachment 530306
View attachment 530307View attachment 530305

This is on Big Sur 11.5. I created my backup using the Legacy Bootable Backup Assistant. I'm going to try erasing the drive and starting again. Now that it doesn't have to backup my User folder, the backups are a lot quicker!

 

[Higgie]

Just tried again with identical results. The EFI on the cloned drive will not boot the backup. I guess that's not really a problem as I have other backups of my EFI - As long as I can use one of those to boot the backup, then I guess it's ok.