Contribute
Register

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

My apollo x6 is not working on Catalina 10.15.5 Uad software is saying no devices found. I'm using a Belkin Thunderbolt 3 cable.
 
Last edited:
My apollo x6 is not working on Catalina 10.15.5 Uad software is saying no devices found. I'm using a Belkin Thunderbolt 3 cable.
Please check the following:
  • In System Information --> PCI, do you see Intel JHL7540 Titan Ridge Thunderbolt 3 NHI?
  • If yes, please run IORegistryExplorer and select File --> Save As..., then post that file.
  • Have you tried hot-plugging the UAD Apollo x6 (disconnect Thunderbolt 3 cable and plug it back in with macOS already running)?
  • Have you tried a cold boot? (Shutdown the Hackintosh, flip power switch on PSU to OFF for 10 seconds, then power back on.)
  • Have you tried Resetting the UAD Apollo? (Please check Apollo owner's manual for reset procedure.)
 
@CaseySJ ,

Did you have some time to checkout the issue I mentioned earlier here? ;-)
 
@CaseySJ , I know you have been very busy for the past 12 hours (as usual answering to all comments and requests :) )
Did you have time to investigate the issue on NVRAM csr-active-config I mentionned earlier?
The value on your EFI folder #1 is E7030000, which enable to install V10 BIg Sur but prevent to reboot when install is completely done. Only Catalina booting with this setup
I found on another forum that the value should be 00000000, and this is confirmed on the Dortania guide.
No longer an issue for me as i installed both OSX and can boot on them. But it could be helpful for some other users...
Thanks again for all your support !
Hello @DominiqueGormand,

I have not personally encountered an issue with csr-active-config set to E7030000 when installing each of the six Big Sur public betas. Are you certain that the reboot problem you mention is due to csr-active-config? It is okay to change it to all-zeros. I considered making this change to the OpenCore 0.6.2 EFI, but decided at the last minute to minimize changes that might affect existing Catalina users. In the future I may change it to 00000000.
 
Hello @DominiqueGormand,

I have not personally encountered an issue with csr-active-config set to E7030000 when installing each of the six Big Sur public betas. Are you certain that the reboot problem you mention is due to csr-active-config? It is okay to change it to all-zeros. I considered making this change to the OpenCore 0.6.2 EFI, but decided at the last minute to minimize changes that might affect existing Catalina users. In the future I may change it to 00000000.


Well, I don't know if you already tried to install the latest V10 version. All was fine before.
For this one I had to change the value to 00000000 otherwise I was not able to reboot after logging off. But the install in itself was ok up to the end.
And I confirm that this change does not affect Catalina use.
Once again I am not as expert as you are, but Dortania guide mentions the same value of 00000000 in their set up.
I let you judge of recommendations for the future :)
 
Thanks again for your advice.

This problem is driving me mad as once I have a successful boot, all is well.

I will try your suggestions.

I am using Corsair MP600 NVMe for Windows and Catalina. Are you aware if anyone else has tried these and had problems?

I do not have any Thunderbolt devices.

I am having the same issue but only on restart and only if I perform the restart from MacOs. It will restart then will hang on the Gigabyte logo splash screen and the various options (F12, etc.) displayed at the bottom of the screen. Only solution is to power off then power on and then boot is ok.
If I boot windows 10 from OC then restart, no problem at all. Gigabyte logo is displayed along with the options at the bottom of the screen, options disappear, OC boot picker/icons are displayed and everything is fine. I can boot again windows 10 then restart and it will work 100% of the time. I have not figure out what the issue is.

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.
 
Well, I don't know if you already tried to install the latest V10 version. All was fine before.
For this one I had to change the value to 00000000 otherwise I was not able to reboot after logging off. But the install in itself was ok up to the end.
And I confirm that this change does not affect Catalina use.
Once again I am not as expert as you are, but Dortania guide mentions the same value of 00000000 in their set up.
I let you judge of recommendations for the future :)
I did not encounter any issues with all six Big Sur public betas. If I had, I would certainly have made the change.

Screen Shot 2020-10-21 at 5.42.32 PM.png
 
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.

Page 113 in the owner's manual: :)
Screen Shot 2020-10-21 at 5.47.58 PM.png


There shouldn't be an legacy IDE devices. Do you have SATA HDDs or SATA SSDs? If so, is BIOS --> SATA Configuration set to AHCI?

Recommendation: Re-flash the BIOS and configure BIOS parameters again.
 
Page 113 in the owner's manual: :)
View attachment 492725

There shouldn't be an legacy IDE devices. Do you have SATA HDDs or SATA SSDs? If so, is BIOS --> SATA Configuration set to AHCI?

Recommendation: Re-flash the BIOS and configure BIOS parameters again.
I have two Sata SSDs. One is my Catalina Backup so has an EFI partition, the other is MacOS storage.

I’ll check my BIOS configuration, but it boots fine 99% of the time so I can’t see why that would happen? I’ll try reflashing the BIOS if I have this problem again.
 
Page 113 in the owner's manual: :)
View attachment 492725

There shouldn't be an legacy IDE devices. Do you have SATA HDDs or SATA SSDs? If so, is BIOS --> SATA Configuration set to AHCI?

Recommendation: Re-flash the BIOS and configure BIOS parameters again.
It is indeed set to AHCI
 
Back
Top