Hello,
my AMD 13 is working really nice but I have a little problem. Now I want to swap the wi-fi card to Intel BE200. But when I do this, I can’t get post boot anymore. Only black screen and this led sequence: 11001000 (BBGGBGGG)
B for blue and G for green.
Maybe I need to enable something in BIOS ?
FYI the AX211 have a CNVio2 interface. But the BE200 have a PCIe, USB interface, exactly like the AX210 (which works everywhere)
any tips ? thanks
Yeah the be200 doesn’t post in mine either, and from what I have seen on the internet it does that on a lot of other platforms too.
According to the specs ti should work but jet it doesn’t.
BE200 is locked to specific Intel configs, this is not a Framework issue
https://www.reddit.com/r/framework/comments/17q4gwx/has_anyone_tried_installing_an_intel_be200_to/
Do you have any proofs that BE200 is locked to specific intel configs ? Any official confirmation ?
Probably more bugged than locked, there is very little information at this point. Mostly reports of various platforms able to post and not post with it. From what I have seen for intel platforms it sometimes works and sometimes doesn’t and on amd platforms it just doesn’t.
But the thing is very new and not a lot of people have it jet, let alone have it in a system that didn’t ship with it.
I can tell you that https://www.aliexpress.com/item/1005007267465725.html does not work in the Framework 13 AMD 7040 with BIOS 3.09
It does work in a Beelink U59 Pro. I would really like an answer about why this doesn’t work in the Framework.
Yes this is known not to work on AMD configs. And I think it’s not just frameworks amd this card has issues.
I’ve tried both “regular” BE200 cards as well as Killer branded BE200 cards (which apparently lack vPro which was speculated might be the issue) and neither of them work with Framework boards. I also have tried them with the DeepComputing RISC-V board and, while it boots, it doesn’t show the device at all in lspci once booted.
Something the be200 does on the pcie bus seems to reeeally offend some amd platforms.
If you plug one of them in via thunderbolt it hard crashes the system as soon as the connection is authorized.
This may get fixed in some future agesa update but more likely you’ll have to wait for a be210 or pick a mediatek or qualcom chipset instead.
Hi guys, some people have used an m.2 adapter E type to A+E type & is successfully using BE200.
I was wondering if we can cover corresponding pins with cellotape & use.
And what do you imagine that kind of adapter would solve for you?
We don’t yet know the incompatibility between some AMD boards and the BE200 cards.
But that adapter card just adapts between different M.2 slot types. Framework has been using E-Key sockets, so any E-Key or A+E-Key card will physically fit, as that signifies fundamental port features and the Wifi cards all just need PCIe x1 + USB2.
That adapter would only be needed if the board was using an A+E-Key slot and the WiFi card you want to plug into it was just A or E key.
Which Lenovo was probably doing with on that users board, because E-Key is what you need for modem cards. So when WiFi cards are A+E, because they don’t need any of the additional functionality, then Thinkpad users cannot plug modem cards into the WiFi slot.
Unfortunately for us this isn’t an issue you can adapter away. It’ll even crash the system when connected through thunderbolt (and an E-key to pcie adapter XD).
I have a thunderbolt enclosure and E-key adapter.
When I tried the BE200 in it, the laptop did not crash, but at the same time the PCIe device for the BE200 never appeared. It was just the same as not plugging in the BE200 at all.
I am guessing that maybe the thunderbolt enclosure did the failing bit, and isolated the problem from the laptop.
When instead, I plugged in a different (not the BE200) Wifi card, it worked OK via the enclosure.
It was this enclosure:
Mine was an intel based tb adabter, it is possible whatever the be200 does on pcie allready offends the asmedia chipset in the enclosure so it doesn’t get to the point of crashing the system XD.
That is what I suspected also. That is why I posted details of the exact TB enclosure I was using.
I don’t have a full PCIe analyser to hand, so I have no idea why the BE200 failed to work.
Unfortunately it looks like noone that cares does, would probably be pretty easy to track down what pcie activity crashes the system since it seams pretty instant.
But even if we’d get it to work, it probably still would have the same sleep problems as the AX210 has in the AMD Frameworks (where it may waste unreasonable amounts of power while sleeping, because it seems AMD as well as Intel develop their cards for their respective platforms and mainly test with their own cards).
In desktops that aspect is irrelevant, especially if the desktop still uses S3. But it probably matters to most FW users. And that one might be much harder to fix, so really only becomes relevant if AMD takes up the testing.
There definitely won’t be any way to fix it on the wifi card side (even if the fault is there) as the system crashes well before there would be any chance to load new firmware. Not sure the sleep issues are a thing on the 7040U platform but I am personally more an on or hibernate kind of guy so I probably would not notice it.
I am personally hoping an eventual be210 will solve those issues. Not going to upgrade to wifi7 for quite a while so I can wait and the ax210 is reeeally good and already uses barely any power (I got the be200 cause I thought it may use even less)