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

[supaMac]

Please try setting BIOS --> Thunderbolt Boot Support --> Boot Once.

I should have noted this earlier, but better late than never:

View attachment 519446

Thanks, I flashed back to F5 Bios still having issues connecting my Apollo. Will start with fresh eyes tomorrow...

If it was easy everybody would do it!

 

[jaymonkey]

The OpenCore 0.6.9 EFI that I uploaded for the Z490 Vision G uses iMac19,1 instead of iMacPro1,1. Regarding sleep, what change(s) would you say solved the problem?

@CaseySJ,

I went with iMac20,2 as it's a better match for the CPU generation, iMac20,X uses Comet Lake CPU's where as iMac19,X are based on Coffee lake CPU's, in reality there is very little difference between the two generations (I think Comet Lake was more of a Coffee lake refresh than anything else) but since switching to the iMac20,2 SMBIOS the system has felt much more responsive than it did with the iMacPro SMBIOS which would indicate that the iMac20,X SMSBIOS is well optimised on this hardware.

Additionally as the iMac20,X was the last (to date) Intel Mac released, one could also argue that it's a good SMBIOS to go for as it should (theoretically) get the longest support from Apple, although I believe we will soon see Apple release a refresh to the 2019 MacPro ... Apple simply have too much money invested in that platform to not refresh it at least once ... if that does happen then I also expect Apple to release a AMD 6000 series MPX GPU module alongside the refresh.

I'm guessing that you went with the iMac19,X SMBIOS as that was the latest iMac at the time (May 2020) you created your Z490 Vision D build guide, iMac20.X was not released until a few months later (August 2020).

As for changes that I made ..... other than the SMBIOS and associated S/N, ROM, MLB, SM-UUID .. etc I changed very else little in the config. I think it may have been possible to get the iMacPro config sleeping by using the CPUFriend kext to inject custom/correct CPU properties for a desktop class CPU rather than the iMacPro's Xeon CPU that is baked into the iMacPro SMBIOS.

I have the IGPU enabled in BIOS and configured as 'Headless' which results in IQS working along side my Vega 64 LC. The system is super responsive now, when I tried the iMacPro SMBIOS there were occasional times when the system did not "feel" as responsive as it should, nothing major but noticeable.

I'll continue down the iMac20,X road for now as everything is working extremely well. Once I'm 100% happy with the system I might create a quick build guide giving an overview of the system with links to your guide ...

Cheers
Jay

 

[jd6]

Hey Guys,

Has anyone with Z490 Vision G managed to get sleep working with Big Sur 11.3.1 ?
...

I updated to 11.3.1 today and sleeps/wake is still working on vision G.

 

[jd6]

That is odd...sleep should work.

Vision G owners:

• If you're running Big Sur 11.3 or newer, is sleep working?

Yes, it is working.

 

[sckn]

Today, I got my Motherboard.

I started with updating Mobo to F5. And edit the EFI file for usage.
I have couple of problems. I inserted two GPU, RX 580 and GT 710. Only GT 710 giving display output. Can I get help for this?

A friend, nicely warn me to told this detail:
HW: Z490 VD, i5 10600K, MSI Armor RX 580 8GB, Asus GT 710 (fanless).
SW: EFI (the one from this Golden Guide, I will share my branch with GitHub Repo), Catalina with pure install.

Hackintool says:

Which is not true. I have 5 ports. I injected my configuration for RX 580 that I tweaked carefully. But, it still is wrong.

If I connect display to the RX 580, it remains gray. Constantly. But, I know that there is a running OS, that I can connect from my MBP.

I can confirm that the card is working REALLY great. I tested it with GeekBench 5 and it gives me a great score in both, Metal and OpenCL.

And I attached my IOreg dump. All helps are very welcome!

@jaymonkey, sir, can I manage this or should I abandon this approach?
Because a few messages ago, they told me it's possible. But I couldn't manage it to work.

 

[supaMac]

On that note, i can say that my Asrock x570 Phantom Gaming ITX/TB3 works great! Apollo and Satellite TB3 OCTO are working fine, however Satellite TB2 OCTO will show up but will hang when loading plugins, even with an OCTO PCI-e in a TB3 chassi is behaving the same way. So conclusion Apollo+Satellite TB3 OCTO/QUAD works with this motherboard.

My hacks -
Gigabyte B550 Vision D - UAD Apollo and Satellite intermittenly working.
Gigabyte Z590 Vision D - UAD Apollo (not showing) Satellite TB3 and Satellite TB2 working. Even with PCI-e OCTO in a TB3 chassi.
Asrock x570 Phantom Gaming ITX/TB3 - UAD Apollo and Satellite TB3 are working. Satellite TB2 - not working.
Gigabyte z390 Designare - Purrrfect - all working.

However everything is working great with my Macbook Air M1 (i sold my mac Mini M1).

Heya, looks like we have similar systems and UAD hardware I have the Z490 Vision D i10900K Radeon 570 OC Armour.. I have everything working WIFI BlueTooth iCloud stuff..
I just can't seem to get my Apollo to connect to the TB3. It is TB 1 but as far as I am aware that should still connect to 1-2 and 3.
The Z490 TB-3 connects to my Satellite Quad fine, and my PCI card also runs fine.

I'm on F5 BIOS for the Z490, and I have tried Bios Settings for TB-3.
1 Boot once (and a few others for this setting),
2 No Security
3 enabled the GPIO3.
I have tried the Apple TB3-2 adapter as well as the Startech TB 3-2 and 2 different cables

I'm stumped. Got any insight?

 

[bazzevo]

I had a kind of the same issue, and it turned out to be the TB3 card in my Apollo Quad. I returned the card and got another TB3 card. Worked right off the bat. I have the same system config pretty much too.

 

[m4rk0]

I went with iMac20,2 as it's a better match for the CPU generation

Hi @jaymonkey

You might find out that iStat Menus won't work with iMac20,2, but you may well know it already. Doesn't work on iMacPro1,1 either but it does when using iMac19,1

Actually, I did a side install as iMacPro1,1. I'll boot it and see whether sleep works or not, if you want to know.

Can I ask you a question?

I have the IGPU enabled in BIOS and configured as 'Headless' which results in IQS working along side my Vega 64 LC.

If disabling the iGPU, do you believe the x264 encoding using Intel Quick Sync would be carried by the installed AMD card? Do you see any advantage in that?

Thanks

 

[ncortines]

Just to avoid any confusion:

• The kernel patch by vit9696 is equivalent to using FakePCIID. We can use either the patch or the kext.
• However, vit9696 states that Big Sur 11.4 beta natively supports the i225-V with device ID 0x12F3. This means turning off all patches and FakePCIID kexts. However, when we do this, Big Sur 11.4 attaches the 1GbE driver instead of the 2.5GbE driver, so either the kernel patch or FakePCIID kext is still needed.
• Let's hope that 11.4 release version supports device ID 0x12F3 natively.

Hey, has anyone tested already i225-V support in Big Sur 11.4?

According to this user FakePCIID.kext and and FakePCIID_Intel_I225-V.kext are still required (no native support):

macOS 11.4 Update

Easy peasy lemon squeezy. Was already up to date on OC 0.6.9 with current kexts (ALC, Lilu, WhateverGreen). Last month, finally took the plunge and learned how to map USB ports using USBMap tool (https://github.com/corpnewt/USBMap), so never have to worry about that again. Today... clicked...

www.tonymacx86.com

 

[CaseySJ]

Hey, has anyone tested already i225-V support in Big Sur 11.4?

According to this user FakePCIID.kext and and FakePCIID_Intel_I225-V.kext are still required (no native support):

macOS 11.4 Update

Easy peasy lemon squeezy. Was already up to date on OC 0.6.9 with current kexts (ALC, Lilu, WhateverGreen). Last month, finally took the plunge and learned how to map USB ports using USBMap tool (https://github.com/corpnewt/USBMap), so never have to worry about that again. Today... clicked...

www.tonymacx86.com

There appears to be support for our I225-V device ID (0x15F3), but the right driver does not load. Perhaps macOS is looking for some other qualifying Device Properties. I tried setting subsystem-device-id to 0x106B (Apple), but still no luck. (The Broadcom Bluetooth module also sets subsystem-device-id to 0x106B.)