We've used the Intel AX210 on everything except the original 11th Gen pre-built systems which use AX201 and the Chromebook Edition, which uses AX211.
AX210 on Ryzen is a YMMV situation. Neither Intel nor AMD will provide any guidance or support around the combination, and we don't have access to any of the needed source to resolve issues as they come up.
The Killer AX1650 is an Intel chip and without the Killer software is the same as an Intel AX200. You just need a version of the Linux kernel that recognizes the AX1650 as an AX200, 5.2.2 or later.
It sure looks to me like "Some guy" got the "random speculation" right in this case.
The link shows the BE200 as the "M.2: PCIe*, USB" type in the highlighted Intel Ark screenshot. In contrast to the "WinModem" version you're conflating this with, which should say "M.2: CNVio2" (or similar) like the AX210 and AX211 pair.
The BE200 should be like the AX210. The "WinModem" variant should be BE201 like the AX211.
Edit: I guess I should say that I don't know if "may be locked via Firmware" is a reasonable conclusion, just that the correlation is present, and the assumption of interface compatibility (given an M.2 slot with PCIe and USB).
Ah. Sorry I was hasty, some don't support a. All the more reason to include the good one. :) I believe all the intel chips are essentially identical driver wise, but dunno about the unlabeled one. Then again, I would not be picking the unlabeled mystery chip if I were concerned about drivers.
I don't think Intel has even decided whether to fuse them off or not. In my newest Intel desktop, a Core i7-13700K, AVX-512 is actually available. It wasn't available on the i7-12700K that was in the same system on the same motherboard a few weeks ago.
So both can be true at the same time: your AX210 works fine with the i7-2600, while the AX201 would not.
Thanks for those product names Intel. Very helpful!
0: https://www.intel.com/content/www/us/en/products/sku/204836/... 1: https://ark.intel.com/content/www/us/en/ark/products/130293/...
reply