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

[CaseySJ]

@mickelsn,

I also have an Apple Silicon product, namely the 2021 14” MacBook Pro. I bought that because I have never hacked a laptop and didn’t want to buy any existing PC laptop. Unlike PC desktops that we can assemble from our own set of component choices, laptops come pre-built and you either take them or leave them.

So I always left them...

But Apple’s own laptops are the standard by which all other laptops are judged so why not just buy the best?

I am very happy with the Apple Silicon MBP, but I use my desktop hacks far more often. These DIY systems are still a source of pride. But when the time comes to abandon ship and jump completely aboard the Apple Silicon bandwagon, it won’t be so bad. We’ll find other things to tinker with

 

[maeluse]

Hi,

So, regarding the issue with my external hard drive, which could not boot after the OpenCore picker, I did some additional research (which I should have done before my previous post actually, I apologise for that...) and ended up finding out that the "issue" came from Carbon Copy Cloner (I use the latest version 6.1.8), which I have always used to back up my system drive up to now.

Apparently since Big Sur and that new feature introduced with this release, it seems not to be that easy anymore for CCC to create a bootable partition while still supporting their incremental update feature and keeping a trace of the operation history. So backing up a bootable system partition would not create a bootable copy partition anymore on the destination drive, unless (!!) you enable a specific option for it while right clicking on the destination drive and selecting the "legacy boot loader assistant" (see attached screenshot, which is in French , but it might be helpful anyway). When you enable this option, CCC will warn you that it won't be able to do incremental updates anymore on the backup drive and will require to clean it up totally before starting. That's a pity but I can testify that it works well! I can finally boot on my USB external drive.

I also heard that SuperDuper! (which is a CCC clone ) can make bootable backups while still maintaining the incremental update feature (if you buy the full version). That's tempting... but as I already bought a license for CCC back then, I may stick with this software for now.

Regarding the issues I had with Cubase after the Ventura update (13.6.1), well that's weird but it ended up well. The problem that I described was really persistent the whole day long when I restarted after the update. Plus, after hanging around on the Cubase forum, I also found some people who seemed to share the same issue... that confirmed somehow that there was something real lurking around. However then, after a cold boot (I powered off my computer the whole night long), the issue vanished and have not occurred since then after a week of testing.

 

[bazzevo]

Hi,

So, regarding the issue with my external hard drive, which could not boot after the OpenCore picker, I did some additional research (which I should have done before my previous post actually, I apologise for that...) and ended up finding out that the "issue" came from Carbon Copy Cloner (I use the latest version 6.1.8), which I have always used to back up my system drive up to now.

Apparently since Big Sur and that new feature introduced with this release, it seems not to be that easy anymore for CCC to create a bootable partition while still supporting their incremental update feature and keeping a trace of the operation history. So backing up a bootable system partition would not create a bootable copy partition anymore on the destination drive, unless (!!) you enable a specific option for it while right clicking on the destination drive and selecting the "legacy boot loader assistant" (see attached screenshot, which is in French , but it might be helpful anyway). When you enable this option, CCC will warn you that it won't be able to do incremental updates anymore on the backup drive and will require to clean it up totally before starting. That's a pity but I can testify that it works well! I can finally boot on my USB external drive.

I also heard that SuperDuper! (which is a CCC clone ) can make bootable backups while still maintaining the incremental update feature (if you buy the full version). That's tempting... but as I already bought a license for CCC back then, I may stick with this software for now.

Regarding the issues I had with Cubase after the Ventura update (13.6.1), well that's weird but it ended up well. The problem that I described was really persistent the whole day long when I restarted after the update. Plus, after hanging around on the Cubase forum, I also found some people who seemed to share the same issue... that confirmed somehow that there was something real lurking around. However then, after a cold boot (I powered off my computer the whole night long), the issue vanished and have not occurred since then after a week of testing.

I have use SuperDuper for almost 2 decades and it has never failed on me. Highly recommended.

 

[CaseySJ]

The latest instructions for making bootable backups with CCC are located here:

Asus Z690 ProArt Creator WiFi (Thunderbolt 4) + i7-12700K + AMD RX 6800 XT

CaseySJ's Intel Alder Lake i7-12700K: Asus Z690 ProArt Creator WiFi + Intel i7-12700K + AMD RX 6800 XT Please do not quote this guide in its entirety. Post a link instead. All P-cores, E-cores, and Hyper Threads are usable! This build guide starts with macOS 12 Monterey, but supports Big Sur...

www.tonymacx86.com

 

[MacGeoDoc]

I'm was looking for a Thunderbolt NVMe enclosure and bought this one from Amazon:

https://www.amazon.com/dp/B0CKFQ3GLC/?tag=tonymacx86com-20

Unfortunately, it does not not seem to be recognized when connected to the Thunderbolt ports of my hack which is a Vision D using @CaseySJ's EFI files. I've tried hot plug and pre-boot connections. I am running Ventura 13.6 with OC 0.9.5. I've attached a screenshot of my IORegistry which seems to confirm that my Thunderbolt ports are recognized. I have not flashed the Thunderbolt firmware chip. I also do not know what chip this enclosure is using but am actively trying to ascertain this info. Any suggestions? BTW, this enclosure is recognized and works well on my MacBook Air M1 laptop which is running the exact same macOS.

Update: After taking it apart I have determined that this enclosure uses an ASMedia ASM2464PD chip.

 

[CaseySJ]

I'm was looking for a Thunderbolt NVMe enclosure and bought this one from Amazon:

https://www.amazon.com/dp/B0CKFQ3GLC/?tag=tonymacx86com-20

Unfortunately, it does not not seem to be recognized when connected to the Thunderbolt ports of my hack which is a Vision D using @CaseySJ's EFI files. I've tried hot plug and pre-boot connections. I am running Ventura 13.6 with OC 0.9.5. I've attached a screenshot of my IORegistry which seems to confirm that my Thunderbolt ports are recognized. I have not flashed the Thunderbolt firmware chip. I also do not know what chip this enclosure is using but am actively trying to ascertain this info. Any suggestions? BTW, this enclosure is recognized and works well on my MacBook Air M1 laptop which is running the exact same macOS.

Update: After taking it apart I have determined that this enclosure uses an ASMedia ASM2464PD chip.

The screenshot shows that the NVMe enclosure is not connected to either of the two Thunderbolt ports (DSB1 and DSB4). Suggestions:

• Connect the enclosure before booting macOS. Does it show up on either DSB1 or DSB4?
• In BIOS, check Thunderbolt -> Thunderbolt Boot Support and change it to Boot Once
  • Save BIOS settings and boot macOS
  • Does enclosure show up on DSB1 or DSB4?
• Are you using a Thunderbolt cable?
  • It will have a lightning logo on each end

 

[MacGeoDoc]

The screenshot shows that the NVMe enclosure is not connected to either of the two Thunderbolt ports (DSB1 and DSB4). Suggestions:

• Connect the enclosure before booting macOS. Does it show up on either DSB1 or DSB4?
• In BIOS, check Thunderbolt -> Thunderbolt Boot Support and change it to Boot Once
  • Save BIOS settings and boot macOS
  • Does enclosure show up on DSB1 or DSB4?
• Are you using a Thunderbolt cable?
  • It will have a lightning logo on each end

• I tried connecting the enclosure before booting and it still does not show up in either Thunderbolt ports
• I made the change in the BIOS you suggested, Thunderbolt -> Thunderbolt Boot Support > Boot Once, without success.
• I am using the cable which came with the enclosure which is labeled as USB4. Using the same cable, the enclosure is recognized and works well on my MacBook Air M1. It seems to be recognized as a Thunderbolt/USB4 device. I am attaching a screenshot of my MacBook Air system report.
• BTW, the enclosure is recognized and works well on the Vision D USB-A and USB-C ports. It just isn't recognized at all on the Thunderbolt ports.
• I don't have any other Thunderbolt devices to test at the moment but I have ordered another enclosure (Orico) which should arrive later today. I believe this uses a different chip.

• Update: I think I may have a hardware or BIOS problem with the Thunderbolt ports themselves as this enclosure is not recognized using either Windows 10 or Ubuntu. I am using the BIOS settings recommended by this build. Not sure if they should be changed for a different OS. It is interesting that my Vision D Thunderbolt ports are recognized by IORegistry running Ventura. Not sure how to explore this under Windows 10 or Ubuntu.

 

[CaseySJ]

...

• Update: I think I may have a hardware or BIOS problem with the Thunderbolt ports themselves as this enclosure is not recognized using either Windows 10 or Ubuntu. I am using the BIOS settings recommended by this build. Not sure if they should be changed for a different OS. It is interesting that my Vision D Thunderbolt ports are recognized by IORegistry running Ventura. Not sure how to explore this under Windows 10 or Ubuntu.

There may be a compatibility problem between USB4 and NVM 33/50 firmware that comes on Gigabyte Z390 and Z490 boards. I haven't had any first hand experience with USB4 devices, but the symptoms you're seeing in Windows and Linux would suggest the need for a Titan Ridge firmware update.

I'm not sure if a newer Titan Ridge firmware has been posted by Gigabyte, but if it has, it can be installed from Windows without the need for an external flasher.

 

[MacGeoDoc]

There may be a compatibility problem between USB4 and NVM 33/50 firmware that comes on Gigabyte Z390 and Z490 boards. I haven't had any first hand experience with USB4 devices, but the symptoms you're seeing in Windows and Linux would suggest the need for a Titan Ridge firmware update.

I'm not sure if a newer Titan Ridge firmware has been posted by Gigabyte, but if it has, it can be installed from Windows without the need for an external flasher.

Would I have to update the entire BIOS to update the Titan Ridge firmware? I am currently on BIOS version F5

 

[CaseySJ]

Would I have to update the entire BIOS to update the Titan Ridge firmware? I am currently on BIOS version F5

Gigabyte has made Thunderbolt firmware (not driver) updates in the past, but on a very limited basis. These updates are not BIOS updates. Instead, they just update the firmware of the on-board Titan Ridge controller.

Question for All:

• Have you tried connecting any USB4 devices to the Thunderbolt ports of your Z490 Vision D with a Thunderbolt cable?
• If so, has the device connected and worked? If yes, what make/model?