Contribute
Register

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

In system information --> PCI, I do not see Intel JHL7540 Titan Ridge Thunderbolt 3 NHI, I see XHC5, and pci8086,15eb. Ive tried all other steps you have provided, did not work.
 
Hi @CaseySJ, I just flashed the thunderbolt chip successfuly thanks to your guide :clap:
This seemed like the only solution, but i still can't get the vrs8 to work, even though it shows on the system report thunderbolt information. :(
 

Attachments

  • Captura de Pantalla 2020-10-22 a la(s) 03.17.35.png
    Captura de Pantalla 2020-10-22 a la(s) 03.17.35.png
    218 KB · Views: 60
Has anybody tried adding the Thunderbolt card to the Vision G?
 
I experienced this again yesterday, but even more extreme - Everything was running fine, I restarted from MacOS to load up Windows for some gaming, and I got the hang at the Gigabyte logo, so I powered off and back on again, only for it to hang again. So I performed a cold boot, and the same thing happened. I started to panic as not only could I not get to OpenCore, I couldn't even get into the BIOS. After my 7th or 8th attempt at booting and it hanging at the Gigabyte screen, I checked the error code on the motherboard and it was A2. I decided to just leave it while I googled the error code on my phone. Lo and behold, after a few minutes, the OpenCore picker appeared, albeit with reduced options to choose from. My Catalina Backup drive which usually appears in the picker was absent, and the only things there were Windows and MacOS. Have either of you taken note of the code on the motherboard when you experience your hangs? Next time it does it, if you can afford to wait a few minutes, please do so and see if the OpenCore picker eventually appears on its own.
@Higgie Yes I did and it was also A2. I googled about the gigabyte A2 code and all I could find was that the A2 code is raised when there is an issue with SATA. I could not understand why it was A2 until now. Thinking of it now, the only SATA drive i have in my system in my macos clone which is just a standard old fashion magnetic HDD with STA interface. I only use it when I clone my main system. I might unplug it and see what happens. It could be the culprit. I never thought about it until now.
 
In system information --> PCI, I do not see Intel JHL7540 Titan Ridge Thunderbolt 3 NHI, I see XHC5, and pci8086,15eb. Ive tried all other steps you have provided, did not work.
Please post the IORegistryExplorer file (as explained in previous reply).

Also post a screenshot of the OpenCore OC/ACPI folder and your config.plist (remove serial numbers from PlatformInfo —> Datahub before posting).
 
Hi @CaseySJ, I just flashed the thunderbolt chip successfuly thanks to your guide :clap:
This seemed like the only solution, but i still can't get the vrs8 to work, even though it shows on the system report thunderbolt information. :(
Good job flashing the controller!!

Have you created a custom DROM using HackinDROM or using the manual method described in the Thunderbolt DROM mini-guide for this board?

The VRS8 is connecting to Thunderbolt Bus, but maybe the drivers are not working or seeing the device. Anyway, we should first use a properly configured Thunderbolt SSDT by following the Thunderbolt DROM mini-guide for this board.
 
@Higgie Yes I did and it was also A2. I googled about the gigabyte A2 code and all I could find was that the A2 code is raised when there is an issue with SATA. I could not understand why it was A2 until now. Thinking of it now, the only SATA drive i have in my system in my macos clone which is just a standard old fashion magnetic HDD with STA interface. I only use it when I clone my main system. I might unplug it and see what happens. It could be the culprit. I never thought about it until now.
Good to know that you are experiencing the same error code - looks to me like we have found the cause. I may try unplugging my backup drive too.
 
@Higgie Yes I did and it was also A2. I googled about the gigabyte A2 code and all I could find was that the A2 code is raised when there is an issue with SATA. I could not understand why it was A2 until now. Thinking of it now, the only SATA drive i have in my system in my macos clone which is just a standard old fashion magnetic HDD with STA interface. I only use it when I clone my main system. I might unplug it and see what happens. It could be the culprit. I never thought about it until now.
We are having the same problem. My hang is at A2 also. i have the sata controller disabled but it still hangs at A2. Sent all the information to Gigabyte and they issued a RMA. The problem is I will not have a computer for who knows how long.
 
We are having the same problem. My hang is at A2 also. i have the sata controller disabled but it still hangs at A2. Sent all the information to Gigabyte and they issued a RMA. The problem is I will not have a computer for who knows how long.
Ah - that sounds less encouraging!
 
Good job flashing the controller!!

Have you created a custom DROM using HackinDROM or using the manual method described in the Thunderbolt DROM mini-guide for this board?

The VRS8 is connecting to Thunderbolt Bus, but maybe the drivers are not working or seeing the device. Anyway, we should first use a properly configured Thunderbolt SSDT by following the Thunderbolt DROM mini-guide for this board.
Yes, I think I created the custom drom, but I was not sure what I was doing following the steps, is there any way to check it?
 
Back
Top