LRO still doesn’t work for me.
@dangowrt I’m assuming we’re not event at the point yet for any 6 Ghz testing with your build on the R4? I’ve been messing around with different packages/configs with a 7916 module but no luck yet.
I have been using 2 R4 running the code from the WIP on github with one AsiaRF MT7916 card each on 6GHz and achieved stable performance of ~1.5Gbps across the table (also tested the same setup with one AX210 card as client on the R4 and worked perfectly but slightly lower performance of ~1.2Gbps and a Pixel 7 also with similar results).
Was there any configs/packages you needed to configure to get it working on that build? I can’t get 6ghz enabled
Besides the kernel modules for the card itself, the only thing needed was to pick a regulatory domain which permits 6GHz channels and i could select 5GHz vs 6GHz in the UI.
I was building on fedora 39 asahi. I had to remove KERNEL_VARS and BUILD_LOGGER_VARS from kernel.mk and package-defaults.mk.
If anyone is interested, I added the r4 support from bpi repo on top of latest MTK release Filogic 880 WiFi7 Non-MLO SDK Release (20240112)
2 Likes
Hi everyone, is there any information when WiFi 7 NIC card will be available for the BPI-R4 ? if it is already available , where can I buy it?
Hello Valentin,
no, it is not jet released. But releasing the Hardware does not mean, that it will work! This is not how this works …
where can I buy it (for the future):
→ look on aliexpress.
→ Are you in germany? → Look on Joom.
Best regards!
Hello Michael, I’ m pretty aware of that, and not expecting the NIC to work out of the box, or even work at all. I don’t mind fiddling weeks building drivers. But the BPI-R4 is limited without WiFi hardware , so I wonder when it will be available…
I’ve already ordered the main board from the AliExpress
Simply put other wifi cards in the slots, you can simply add a ac + ax card as a temp solution. That’s how I’m doing it: simply put the 2 wifi cards of my bpi r64 in the minipcie slots
Thats good.
I did not find any timetable (For the whole router parts … nic, case and fan’s). For me it i not clear which development state all the components have. Reliability tests for consumer products lasts usually 1000 houers (heat, humitity …) = 40 days. Mass production also needs time. I find no information which says anything about the actual state of the board.
Thee are other NIC chats you now?:
As “jpsollie” sayed: There are wifi 6 cards.
And I think about not buying any NIC Board 
.
The best solution is the solution that matches your needs. Why not take in the future a “normal” wifi 7 card from mediathek? Banana PI gives us the freedom to choose.
I would like to have this freedom for the RAM 
.
I think a good solution would be using an existing AP or your actual router.
I actually thought about that, but with common mpciex cards you will get only 2r2t mimo and wifi 6e card selection is pretty limited, basically Intel’s ax210 and I actually want to explore 6gHz band , because it is pretty empty ATM Another route is to explore set of be200 card with m2 to mpciex adapter , but you will get same story for channel allocation
I don’t mind to wait some time to unleash full potential of wife 7
Waiting sounds good
You have to be carefull with Intel !!! The Wifi boards do not support AP Mode.
Some in this forum fall in the trap 
.
1 Like
They do if it’s not 6GHz or you override the poorly implemented (and wrong) software regulatory enforcement. But there are better options indeed.
1 Like
I know this trap , they always had poor software support for STA modes , so I didn’t considered Intel as a goto option. Event if it will run in STA mode there will be a lot of disabled/missing WiFi spec features
Why You even consider to use this tiny card with low power transmitter? Just wait for wifi module like others. I’m sure it will be working nice for everyone.
Did you get the M.2 or MiniPCIe card?
They even sell a bundle currently for $80 with three antennas and pigtails. Though I’m not sure if this expense is worth it, when I want to buy the Wifi NIC anyway.
I have 4 MiniPCIe MT7916 that I bought from a “local” (european) retailer which should come with the small heatsink (one was delivered with the larger one sadly) but no antennas (which is fine as I use ufl pcb/flex antennas as I don’t have a case right now). The card alone is reasonable for $40, as for the bundle I cannot speak as I don’t have it. I am also looking forward to the official WiFi 7 NIC but honestly I bought these cards for my R3s. Sadly the setup in the M.2 m-key to miniPCIe was not even close to fitting in the case so I tossed them in a box.
As I said I tried the AX210 that was discussed here as client and it worked but had issues with the BE200. The latter work fine in a Raspberry Pi 5 (only tested as client) but did not even shown with lspci – at least in my available m.2 to MiniPCIe converters (might by me though). I have to point out that I also had issues with the BE200 in several Atom based SBCs as well with these adapters – these systems wont even POST afterwards so BE200 is certainly a temperamental card. Either way LAR (location-aware regulatory) is very much annoying to deal with so I would agree with what was said here: even with tildearrow’s workaround it’s not gonna be pretty.
Support for the BPI-R4 was merged into vanilla OpenWrt main just minutes ago: mediatek: switch to Linux 6.1 and add BananaPi BPi-R4 by dangowrt · Pull Request #14140 · openwrt/openwrt · GitHub.
This means people will now be able to use official OpenWrt snapshots, once those are built and available (today or tomorrow). It’s much newer than Banana Pi’s fork, which is based on 21.02. Thanks, @dangowrt.
2 Likes
However, there are still a few problems which will have to be addressed before vanilla OpenWrt is ready for production on the BPi-R4:
-
hardware flow-offloading if using all 4 GiB of RAM
right now it only works withmem=2048Mappended to kernel cmdline) -
pcie@0x11280000 doesn’t work (probably missing clock)
-
Ethernet driver still misses RSS and LRO for better RX-to-CPU performance (eg. when running iperf3) by aggregating RX packets
-
no driver for TOPS yet (ie. no hardware tunnel encap/decap offloading)
-
no driver for EIP-197 yet (no IPSec, TLS or DTLS in hardware, all work has to be done by CPU)
-
only one out of three PPE is being used
To give the things which already work more testing it makes more sense to continue development on the main branch (which apart from providing us with downloadable binaries also reduces my workload of constantly doing git rebase origin/main on that large series)
7 Likes