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

[Josu]

What about Z590 itx?))

 

[dehjomz]

What about Z590 itx?))

I mean the Z590 Vision D boards work okay, let me be clear. But the BIOSs are still in beta, even though Rocket Lake launched at the end of March, and z590 launched months ago.

Gigabyte has already 4 beta BIOSs of the F5 series, some released within days of each other, and a 5th one is in testing and yet to be posted.

The Z590 Vision D is somewhat sluggish to post (compared to the Z490 Vision D), and for some Thunderbolt 3 devices (seems like *some* with Alpine Ridge inside), hot-plug is not working. So, if you want to use your Thunderbolt 3 device, you either need to plug it in prior to booting, or put Windows/Linux/macOS to sleep, so that the wake up cycle will reset the Maple Ridge controller and your device *may* receive its pcie lanes and then be usable. Seems that hot-plug is working with Goshen Ridge Tthunderbolt 4, however, at least in windows/linux.

It appears that the Maple Ridge NVM26.x may be contributing to the incompatibility with hot-plugging Thunderbolt 3 devices, but only time will tell if this is so, of if Intel will release a newer NVM.

The Zz490 Vision D doesn't have these problems... it just works.

 

[Hackintoshron]

** Speed Tests and Observations with New OpenIntelWireless 2.0.0-alpha Drivers **
Finally we have 192 Mbps/201 Mbps!! Much faster than Fenvi FV-T919
802.11ac works, but I don't have 802.11ax so cannot test
See below (may need to disable 2.4 GHz SSID on some routers)​

...

Hey CaseySJ. I have the Z390 Designare and have been using the OpenIintel 1.3 driver since it came out but when I do the update to the 2.0 Alpha, the WiFi driver doesn't seem to load. Is there something special I need to do for my board or is this Big Sur 11.3 specific?

 

[CODYQX4]

The specs are correctly listed:

• AX201 is an Intel CNVi module
• AX200 is a regular M.2 Key A/E module (this is nice because we can replace it with BCM94360NG, which is a natively supported Broadcom 802.11ac/BT 4.x module)

So if I understand correctly, it would just be a matter of swapping the M.2 card and could use the same antenna.

If so, would this card be a suitable replacement for the Z590's AX200? It's a Youbo which I think some were using as a replacement Fenvi, and it's the cheapest BCM93460NG I saw on Amazon.
https://www.amazon.com/dp/B083YXS7VF/?tag=tonymacx86com-20

 

[CaseySJ]

Hey CaseySJ. I have the Z390 Designare and have been using the openintel 1.3 driver since it came out but when I do the update to the 2.0 alpha, the WiFi driver doesn't seem to load. Is there something special I need to do for my board or is this Big Sur 11.3 specific?

Do you mean to say that you’re running Big Sur 11.2 and the Big Sur version of the driver fails to load?

 

[CaseySJ]

So if I understand correctly, it would just be a matter of swapping the M.2 card and could use the same antenna.

If so, would this card be a suitable replacement for the Z590's AX200? It's a Youbo which I think some were using as a replacement Fenvi, and it's the cheapest BCM93460NG I saw on Amazon.
https://www.amazon.com/dp/B083YXS7VF/?tag=tonymacx86com-20

Yes that should work. However I do not have a Z590 Vision D so haven’t tested it first hand.

 

[Maxdem]

Hello everyone,
Has anyone tried using the Intel AX200 based Fenvi FV-AX3000 PCI-E?

 

[Hackintoshron]

Do you mean to say that you’re running Big Sur 11.2 and the Big Sur version of the drover fails to load?

Yes. But the 1.3 version of the driver for Big Sur was working prior to swapping out the updated 2.0 kext.

 

[CaseySJ]

Hello everyone,
Has anyone tried using the Intel AX200 based Fenvi FV-AX3000 PCI-E?

Yes indeed I have!

It worked with the 1.2.0-stable drivers when I last tested it so it should work even better with the new 2.0.0-alpha drivers.

 

[CaseySJ]

Yes. But the 1.3 version of the driver for Big Sur was working prior to swapping out the updated 2.0 kext.

macOS 11.3 will be released any day now. I'm running the release candidate at the moment, but I suspect the problem you mention lies elsewhere.

Can you list the exact steps taken to update the driver in your EFI folder?