Agree, but TBH this should be continued on Openwrt forum where the patch was proposed. in short, current luci feature proposed by @rmandrad contains bugs, that by choosing ax/be, you might not be able to choose wave length.
It is ok,can you add link to the forum thread
Dan, i am running that version created 2 days ago. I used the openwrt-mediatek-filogic-bananapi_bpi-r4-sdcard image, there’s also the mda-bananapi4-openwrt-6.6.50-10-mediatek-filogic-bananapi_bpi-r4-sdcard one as well. What’s t he difference?
Also, i got a MT7925 card. Tried to install the kmod-mt7925e module, but it said kernel incompatible.
The installed version of package kernel is not compatible, require 6.6.52~93f1158f…-r1 while 6.6.52~441a43eb…-r1 is installed.
Any idea how to solve this?
because kmods needs to be included into the build.
Ian, There a few items not mentioned here. Meditek is the most widely used chip for home and commercial media products. Its at the heart of all US bluetooth and ethernet based systems. MediaTek does share information with manufactures under NDA and their documentation is excellent. They are ni different than Broadcom on the network industry side. Their “partnership” means the BPi folks have an NDA with MediaTek and access to MediaTeks techs, nothing more.
Open source is a mixed bag that is like anything else, good and bad. BananaPi isn’t known for great FOSS support on Linux, either. There are certain Banana Pi boards the work well with openWRT. I have BananaPi R3 and have no issues at all. But even if you finf a board well supported, you will have to maintain your own updstes after a much smaller time window thsn commercial products.
1 Like
If something is described as working, and the instructions specify steps to follow to achieve a certain result, it’s natural to make decisions based on that information. I feel the user has a valid point—if the documentation isn’t maintained, the instructions reference commands that don’t exist, paths that are incorrect, or similar issues, it can be incredibly frustrating.
While it’s true that you can research and find alternative commands or locate the missing packages, it’s understandable to feel frustrated or even misled if you purchase something based on the provided descriptions and getting-started guides, only to find that things don’t work as stated. Clear and accurate documentation is crucial for ensuring a positive user experience.
getting things working is a complex task. vendor (bpi) relases an old image as reference where (due to mtk sdk base) more things working than in mainline.
only a few people (afaik < 10) contributing to getting things to work and discussing with linux/openwrt maintainers to get the changes merged.
while some functions are working in upstream openwrt, linux kernel-support is still ongoing, writing a full documentation for a unfinished state is nearly impossible for these few people.
Also some changes may break existing functionality…not all corner cases can be tested everytime. devs not having each possible 3rd party hardware (nvme,m.2/pcie-cards,sfp) to test it or simply time to test against each one. We had issues multiple times where patches are added to linux which brake working things and have to be fixed again.
from user-perpective i understand that you all want a step-by-step guide to get all working, but this would need more people working on the support. Sometimes commands in one guide need additional packages to be installed which were simply missed or already installed in the used version from the author (e.g. a guide in bpi-wiki is mostly targeting the bpi-image and not the mainline one which have maybe different software installed).
Best example is that there are still many guides using the old ifupdown (ifconfig) commands which are retired for many years and replaced by iproute2 (ip). Or Network config via /etc/network/interfaces is also disabled in actual (debian-based) distributions as systemd is default init for at least 2 major releases. but there are still guides about them (also in my wiki for comparision)…
1 Like
I know, my own experience so far is incredibly frustrating. At first the WIFI card didn’t work, assuming it was a software issue I wanted to update it only to find out that the sources don’t exist
Failed to download the package list from https://downloads.openwrt.org/releases/21.02-SNAPSHOT/targets/mediatek/mt7988/packages/Packages.gz
I did some research and downloaded a new firmware, installed it on an SD card, and was able to get it to boot from there. I did some testing and decided to write it to the eMMC, since the eMMC is faster, more reliable, and has more space than the SD card. There I discovered that opkg had been replaced by apk, but it wasn’t a problem because it warns about it at startup, then I found that the commands to write the eMMC had changed, that the mount points also changed, I continued testing replacing the paths with the ones I understood corresponded and the commands I understood replaced the aforementioned ones and it stopped responding completely, with fear of having bricked the device I tried to boot from the SD again and it didn’t, finally I recorded a clean image from 0 and managed to get it to boot, from there I flashed the original images again and I’m retrying everything. After two weeks investing a couple of hours each day I still can’t get the router working properly Clearly it’s not for end users but neither for technical users who aren’t willing to invest dozens of hours trying to make it work.
Good to hear you are enjoying your new hobby.
1 Like
it is fun if one is here to learn & that’s is why i invested $ & time …otherwise is rage
Trying my best to enjoy this, but my enthusiasm meter is stuck on 'shit I’ve chosed the wrong option again´ This is so much fun, I think I’ll do it again…never.
You should have bought a R3. That is much more stable.
Secondly, I don’t understand all the issues you are having.
I connected a serial usb I ordered from Ali express. Put the openwrt snapshot on an SD card. Booted from that. Selected install to nand. Then rebooted from NAND and selected install to eMMC. Then rebooted from eMMC.
And since then I have been only using sysupgrade to update to newer snapshots.
Finally I was able to make some progress
I’ve flashed and boot from eMMC the new firmware and recognizing the wireless card. 
I wasn’t able to set up the wireless network by the normal way
as encryption options aren’t available there
Instead I’ve went to mtk wifi Configuration and was able to set it up from there
Now I’m being able to use the device as basic wifi router but my connected devices doesn’t appear en the corresponding window.
Ecryption options still aren’t available And If I try to install or update any package got errors
Network is working ok as I’m answering from my laptop connected to the BPI trough WIFI (even when is not being shown as commented) and I could navigate the web without any issues.
So I guess the last point could be fixed by replacing the opkg sources by the corresponding ones as seems they where moved to another place. (may you share yours?)
I couldn’t find yet the reason why I’m not being able to set up wireless in the normal way, what should I do to enable wireless encryption in the usual network–wireless setup page
Any clue?
Why are you still using that completely outdated and unsupported mediatek fork of openwrt and not the official snapshot?
That was the image recommended by the AliExpress vendor, later I’ve applied sysupgrade but seems it hasn’t impacted.
Just do it again using yesterday sysupgrade and till shows same version
Is it this URL? Index of /snapshots/targets/mediatek/filogic/
Then yes, that’s the latest snapshot. Alternatively, you could try the 24.10 branch, which is the upcoming release. https://downloads.openwrt.org/releases/24.10.0-rc4/targets/mediatek/filogic/
But seeing that other screenshot, it seems your sysupgrades are never taking effect.
What is your boot medium? NAND? EMMC? SD-Card? Did you ever do the full installation cycle I described in my other post?
SD-Card to NAND. NAND to EMMC?
Please don’t spread your issue across three (or even more) threads. We can help you here, if you share what you are actually doing and what is not working.
The versioninfo says openwrt 21.02 snapshot,so the vendor (mtk-sdk based bpi) image,not mainline openwrt (23.5/24.10)
Maybe install was not successful and atill booting the old image (e.g. from emmc instead of sdcard)