I wanted to report that I was successfully able to replace my Framework Laptop 13’s AX210 chip with a BE200 chip. I’m sharing this information because there’s a lot of misinformation floating online:
I would not call it entirely false, it definitely doesn’t work on a lot of systems (afaik works on some intel platforms, even some older ones but I have not seen anyone that got it working on any amd platform)
Good to know it works on the 13th gen intel framework though.
Interesting… Well at home I have a 1500Mbps internet connection and my 13th gen Intel Framework laptop using it’s AX210 gets an average of 1400Mbps down using a Wifi 6E router (always get full 1500Mbps using a 2.5Gb dongle)… so even though a Wifi 7 card isn’t needed… it sure is nice to know it can work. Thanks @Nadim!
be200 is a M.2 Type E card, and the slot on the Framework AMD motherboard is a M.2 type E slot, so the hardware should be compatible.
Given that the symptoms on the Framework are very similar to the symptoms in the Lenovo (URL above).
Maybe the Framework AMD motherboard BIOS has such a “BIOS whitelist”. In which case, if Framework are so inclined (have enough time on their hands, given all the other higher priority items they are dealing with at the moment) a BIOS update is likely to fix the problem. Probably a first step to that, is someone to publish what is on the current “BIOS whitelist”. Maybe a second step is for Framework to remove the “BIOS Whitelist” so users have the freedom to plug in any future, better wifi card they wish to use.
That’s allmost certainly not the problem in this case (and likely not in the linked lenovo one either). Lenovo bios whitelists bitch at you with an error message not just refuse to post at all and it would not cause the crash when plugged in after boot (via thunderbolt or some suspend workaround).
The framework also doesn’t have a bios whitelist at all and I am not sure lenovo does either, at least on the thinkpads they stopped doing that a while ago.
This is less of a case of the manufacturer not wanting us to use it and more of an “it’s bugged”. The way it crashes and refuses to boot makes me pretty confident it’s between the soc and the card, maybe it uses pcie in a weird way the cpu really doesn’t like or tries to mess with some proprietary intel registers that causes the amd platform to crash or otherwise throw a fit. It may be solvable in an agesa update (even if it may be the card doing something wrong)
I thought it might be interesting.
The BE200 is recognized on a “banana PI R64” that is an - ARM 64 bit based system.
The driver has a bug so does not actually work, but it does not crash anything.
So, this proves the BE200 is doing PCIe OK and not any proprietary protocol.
root@bpi-r64-1:~# dmesg |grep iwl
[ 8.512368] iwlwifi 0001:01:00.0: assign IRQ: got 149
[ 8.517556] iwlwifi 0001:01:00.0: enabling device (0000 → 0002)
[ 8.523657] iwlwifi 0001:01:00.0: enabling bus mastering
[ 8.559207] iwlwifi 0001:01:00.0: Detected crf-id 0x2001910, cnv-id
0x2001910 wfpm id 0x80000000
[ 8.568086] iwlwifi 0001:01:00.0: PCI dev 272b/00f4, rev=0x472, rfid=0x112200
[ 8.784501] iwlwifi 0001:01:00.0: api flags index 2 larger than
supported by driver
[ 8.792276] iwlwifi 0001:01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.97.4.2
[ 8.891945] iwlwifi 0001:01:00.0: loaded firmware version
83.d24e06ed.0 gl-c0-fm-c0-83.ucode op_mode iwlmvm
[ 8.913864] iwlwifi 0001:01:00.0: Detected Intel(R) TBD Bz device, REV=0x472
[ 8.956221] iwlwifi 0001:01:00.0: WRT: Invalid buffer destination
[ 9.226787] iwlwifi 0001:01:00.0: loaded PNVM version e28bb9d7
[ 9.340335] iwlwifi 0001:01:00.0: base HW address: xx:xx:xx:xx:xx:xx (anonymized, it is a valid MAC address)
[406544.812198] iwlwifi 0001:01:00.0: WRT: Invalid buffer destination
[406545.164882] iwlwifi 0001:01:00.0: Registered PHC clock:
iwlwifi-PTP, with index: 0
[407167.666475] iwlwifi 0001:01:00.0: Unhandled alg: 0x707
Update. WiFi with 12th gen!
I get a speed of 1.7 gbit/s when sitting right next to my router.
Windows doesn’t seem to recognize the bluetooth adapter though, so I’m going to mess with that for a while
Edit, I had to manually delete the old bluetooth adapter from the device manager and then re-install the bluetooth drivers. It completely works now!