Contribute
Register

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

The two ASRock boards were purchased about one month apart, well before I gave up on the Creator. I purchased the Taichi to go along with ASRock’s own Thunderbolt 3 add-in-card connected to the Taichi’s Thunderbolt 3 header. This combination actually works!
Would you mind posting a part list for this working build? Or would you stay with Gigabyte and Intel for a Thunderbolt-equipped DAW workstation? Like the Z490 Vision D? I'm not building another machine this soon, but I'm still curious about successful Z490 builds with OpenCore.
 
Hi, my system is working awesome with your 0.6.4 files, thanks you @CaseySJ
Only a doubt: what’s the best smbios for i5 10600k and 5700 xt, 20,1 20,2 or 19,1?
I’m not worry about performance but I prefer stability.
 
Hi, my system is working awesome with your 0.6.4 files, thanks you @CaseySJ
Only a doubt: what’s the best smbios for i5 10600k and 5700 xt, 20,1 20,2 or 19,1?
I’m not worry about performance but I prefer stability.
Hello @santitf

The two best options are iMac19,1 and iMac20,2. The safer among the two is iMac19,1 because we have a much longer history with that so we know it is reliable and stable.
 
Hello @santitf

The two best options are iMac19,1 and iMac20,2. The safer among the two is iMac19,1 because we have a much longer history with that so we know it is reliable and stable.
Thanks for your quickly response!
Is the comet lake’s power management working fine at 19,1?
Reals iMac 20,1 or 20,2 have the T2 chip. Is this important for our builds using this smbios?
Testing between smbios needs some special thing like rest nvram or another procedure?
 
Would you mind posting a part list for this working build? Or would you stay with Gigabyte and Intel for a Thunderbolt-equipped DAW workstation? Like the Z490 Vision D? I'm not building another machine this soon, but I'm still curious about successful Z490 builds with OpenCore.
Sure... My X570 Taichi has the following parts:
  • macOS 11.2 public beta
  • Ryzen 9 3900X 12-core 24-thread CPU
  • ASRock X570 Taichi motherboard
  • ASRock Thunderbolt 3 AIC Rev 2.0
  • PowerColor Red Devil Radeon RX 580 GPU
  • G.Skill Trident Neo DRAM (AMD compatible) -- 4 x 8GB
  • Sabrent Rocket 1TB PCIe 3.0 NVMe SSD
  • NZXT 140mm AIO Liquid Coolor
  • Fenvi FV-T919 WiFi/BT Card
  • EVGA SuperNova G3 750W power supply
  • NZXT H510 Elite Case
For professional use I continue to recommend Intel-based systems because:
  • Better Thunderbolt support (especially on motherboards with on-board Thunderbolt)
  • No problems with Adobe applications
  • No problems with Virtualization (Fusion, Parallels, VirtualBox, Docker, etc.)
Screen Shot 2020-12-28 at 8.38.54 AM.png
 
Last edited:
Thanks for your quickly response!
Is the comet lake’s power management working fine at 19,1?
Yes, no issues here.
Reals iMac 20,1 or 20,2 have the T2 chip. Is this important for our builds using this smbios?
T2 chip can be more of a problem than a benefit. SideCar would not work if we used a T2-based system name, but now there are workarounds.
Testing between smbios needs some special thing like rest nvram or another procedure?
You can literally just change the system name from iMac19,1 to iMac20,2 and back again, without changing anything else. But once you commit to a system name, you should not change it.
 
Sorry if this sounds stupid, but just to be clear: "Perform CMOS Reset" = momentarily shorting across the 2 jumper pins above the pin block for power, HDD light, etc?
View attachment 502705

I actually tried this a couple times. After 5 beeps, I'd shut the system down (power switch on PSU), then take a small screwdriver & momentarily jump across the 2 pins, then try to power on the system again. Wasn't able to get past the 5 beeps so I could get in to apply all prescribed BIOS settings.

I may have a ghost in my machine LOL I went back to F6 - had to remove GPU, then connect monitor to iGPU and boot into Windows to use the Gigabyte @BIOS app to update F5 > F6.

As I recall, I had F5 OoB. I assembled all the components into the case, including m.2 drive and my RX580. Had the same issue with the 5 beeps. So my go-to troubleshoot is to always simplify to the bare bones. Pulled the GPU, pulled the m.2 drive, used a spare SATA 840 EVO SSD and did a quick install of Windows 10 Pro. It was then I discovered the Gigabyte @BIOS app & the F6 version. After the update, I was able to get that initial build of Catalina up & running.

I've got time (I'm on vacay this week), so I'm happy to try F5 again. Another quirk: with F6, CSM "Disabled" would "stick" during the first few reboots after I went back to F6 & Windows + iGPU. BUT...the minute I put in my GPU, and returned to the BIOS, CSM was back to "Enabled." Strange things going on....


Hey there @BoomR -

I see you struggling, and I thought I would offer just a couple of thoughts....

At any rate, here's some ideas: when I was having trouble, I every now and then I forgot to fully connect the DP cable, ergo, five beeps. Easy to do, although completely unintentional. I did it when I was troubleshooting. So, it can happen to anyone. Also, when I was doing research, one person who had this issue with his board found that his cable was faulty and after replacing it, he was fine.

The "other" reason for five beeps: memory. With my Vision D, the memory that worked fine in my Z370 is not so compatible with this board. I underclocked it to 3000 from 3200 and the RAM/Memory options in the BIOS, selected "enhanced compatibility", and, while performance was a tiny bit slower, the difference was very minor, and no more of the five beep solute when booting.

In terms of resetting the BIOS, there is one way that is absolutely bulletproof: pull the battery. Wait 5-10 minutes and I guarantee that will reset the BIOS.

Just some ideas in case you're still working on your issues with this system.
 
This does indicate a larger problem (i.e. not a macOS config issue).



Suggestion 1:
  • With AMD GPU removed, we can switch to config-Intel-iGPU.plist (i.e. just transfer serial numbers into that file and rename it to config.plist). Then we can use all 3 on-board video ports:
    • On-board HDMI
    • Two on-board DisplayPorts (via Thunderbolt/USB-C ports)
  • Now we can check the following:
    • Any shenanigans with CSM Support? Does it "stick" when disabled?
    • Do Thunderbolt devices connect on reboot?
Suggestion 2:
  • To get the AMD RX 580 working again, please keep BIOS F5.
  • With AMD GPU fully installed, do not boot the system yet.
  • Connect monitor to AMD RX 580.
  • Perform CMOS Reset instead.
  • Then enter BIOS Setup and configure all BIOS parameters (including Boot --> CFG-Lock --> Disabled).
    • Does the system still beep 5 times and freeze?
    • Or does it enter BIOS Setup?
@CaseySJ FTW - once again, with great troubleshooting tips! First - reverted back to F5

RE: Suggestion 1 (test with iGPU) - I actually replaced the config.plist on my install USB with the iGPU version, booted from that, then selected my normal m.2 SSD.
  • Booted successfully.
  • CSM support now "sticks" upon bootup or reboot; however, no TB device attachment from bootup (only hot plug).
  • Applied Thunderbolt Boot Support → Boot Once. SUCCESS!! TB dock attaches from cold boot, when I restart, and of course hot-plug.
Note that when I tried this option using F6, I would get a DOS-like message before the Gigabyte splash screen, talking about "...not being able to boot from this device because it wasn't configured properly..." I suspect that might be due to the dock's on-board NIC...?​

RE: Suggestion 2 -
  • Inserted my GPU... back to 5 beeps - could never get into BIOS to do any additional checking
  • Thought to myself: My GPU is great performer, but a "Special Edition" model Sapphire NITRO+ RX 580 G5 Special Edition. Could there be some bizzaro anomaly with the combo of this GPU + F5 + Vision D that is causing problem?
  • I built a CustoMac for my partner to use in his studio; his build uses Sapphire PULSE RX 580. I pulled his card & put in my machine. IMMEDIATE SUCCESS! (no "5 beeps"). Booted normally.
  • CSM "sticks" to "Disabled" + TB Dock continues to attach from cold boot, when I restart, and of course hot-plug.
I think it's safe to say that I can now continue to refine my build & make sure all the important features I need are working properly. Wishing everyone a great week & a Happy New Year!!
 
Hey there @BoomR -

I see you struggling, and I thought I would offer just a couple of thoughts....

At any rate, here's some ideas: when I was having trouble, I every now and then I forgot to fully connect the DP cable, ergo, five beeps. Easy to do, although completely unintentional. I did it when I was troubleshooting. So, it can happen to anyone. Also, when I was doing research, one person who had this issue with his board found that his cable was faulty and after replacing it, he was fine.

The "other" reason for five beeps: memory. With my Vision D, the memory that worked fine in my Z370 is not so compatible with this board. I underclocked it to 3000 from 3200 and the RAM/Memory options in the BIOS, selected "enhanced compatibility", and, while performance was a tiny bit slower, the difference was very minor, and no more of the five beep solute when booting.

In terms of resetting the BIOS, there is one way that is absolutely bulletproof: pull the battery. Wait 5-10 minutes and I guarantee that will reset the BIOS.

Just some ideas in case you're still working on your issues with this system.
Hey @mm2margaret! Thanks for jumping in & offering those suggestions. I think you were making your post at the same time I was making mine. I actually tried all of those things (except for I was not using DP - using HDMI). Note that memory & GPU were working fine in Win10 with BIOS F6 and F7c. It was that blasted F5 that seemed to be the roadblock. But for sure, check out my most recent reply to CaseySJ & you'll see what was the eventual solution.

THANKS AGAIN!! :thumbup:
--B
 
Hey @mm2margaret! Thanks for jumping in & offering those suggestions. I think you were making your post at the same time I was making mine. I actually tried all of those things (except for I was not using DP - using HDMI). Note that memory & GPU were working fine in Win10 with BIOS F6 and F7c. It was that blasted F5 that seemed to be the roadblock. But for sure, check out my most recent reply to CaseySJ & you'll see what was the eventual solution.

THANKS AGAIN!! :thumbup:
--B

You know, it my original reply, I had another thought about AMD cards, but I removed it because I thought it just was too far out there to mention.

I too have had this very similar problem with AMD cards from Sapphire (and also with some PowerColor AMD cards) on two Vega 64s and and a Radeon VII and they both worked in Windows and Ubuntu just fine, but booting would often, but not always, end up with this five beeps issue. I do think in my case, RAM incompatibility is also contributing because after doing what I have done, no more five beeps problems.

Great to hear you got it sorted!
 
Back
Top