And i am using the unified thing from mediatek, so i am not sure how all i wrote above works with snapshots from openwrt. so @RafalB82 you could be right if not using unified from mediatek
I tried the official 24.10.0 and also got the error
I think the 24.10.0 is too early for mediatek master branch...
OpenWRT has some branches and tags. Go to branch(!) 24.10.
Also be sure that after the prepare command you reoverwrite your config cause the mediatek feed makes a strong .config after calling "prepare".
If you are on the tag "24.10.0" you are wrong (i think). Just can tell you which last build worked for me.
OpenWRT -> branch 24.10
Mediatek -> master
I did this on tuesday..
WOW
I didn't know that openwrt-24.10 release has such a high kernel version, I thought kernel 6.6.85 is only in snapshot
No not the release... look every major and minor version has a branch:
This is not the release. This will be the release for 24.10.1 at some time. If they are ready at the branch they make a tag called for example "24.10.1" this is the release.
24.10-Snapshot: https://github.com/openwrt/openwrt/tree/openwrt-24.10
24.10.0-Release: https://github.com/openwrt/openwrt/tree/v24.10.0
23.05-Snapshot: https://github.com/openwrt/openwrt/tree/openwrt-23.05
23.05.5-Release: https://github.com/openwrt/openwrt/tree/v23.05.5
and so on...
so i hope i can explain it clearly now 
24.10-Snapshot is using kernel version like mine, and get updated every week or two
24.10.0 is using the kernel you mentioned above (and will not get upgraded before 24.10.1 which will come from 24.10-Snapshot when its finished)
1 Like
Dev for version 25-Snapshot is at the main branch.. other branche(-snapshot)s are mostly for fixes and kernel or driver upgrades
Thank you!
I assumed that snapshot is the current test release (main from github)
Believe me, i thought this too till i looked a bit more in depth into the repo
and some tryouts at
After i found the links (You dont see them at https://mirror-03.infra.openwrt.org/releases/) i got a 
@RafalB82
1 Like
Hmmm...looking at the posts from the users of this thread, some of them would like to create their own releases and are having problems with it. Maybe this could help them
https://github.com/woziwrt/bpi-r4-openwrt-builder.git
5 Likes
Thank you for all developers' contribution. @woziwrt @RafalB82 Do you have plan merge these changes to OpenWRT main line? Or, what's the status of OpenWRT support on BPI R4 (including WiFi 7).
1 Like
silly question, i made a config change in configs/bpi-r4_basic_config and it didn't make it into the build folder... is there a trick?
~/temp/bpi-r4-openwrt-builder$ cat configs/bpi-r4_basic_config | grep -i 'ed25519'
CONFIG_DROPBEAR_ED25519=y
~/temp/bpi-r4-openwrt-builder$ cat openwrt/.config | grep -i 'ed25519'
# CONFIG_DROPBEAR_ED25519 is not set
otherwise script worked perfect and i'm running on my router now, thx heaps!
Hmm, do you know whats the difference between calling "prepare" from autobuild or make a build with it and after make a second again?
Cause by doing "only" the prepare the build time looks much shorter for me 
just want to know if you have a specific reason why doing it this way, or just cause of it works like i often do
I also have to take a look at your patches cause my tx power is ok by the driver default but the available are crazy values..
and thanks, many of your stuff is/was the base for mine 
1 Like
Good afternoon @RafalB82, for keeping the 10GB XGS-PON ONU SFP 8311-was-110 in your new build.
It works perfectly.
Thanks for your work.
1 Like
What is the advantage of Kernel 6.6.86?
I noticed in this build is has the "too high" TX power problem. Even if I set TX power low, it blasts at full power:
Going back to the previous build (Kernel 6.6.79) results in the TX Power on 2g and 5g limited top6/7 dBm:
Looking at post 248 from this thread from @woziwrt, there is a value that can be changed to allow TX power adjustment. @RafalB82 was this implemented?
Since the OpenWRT UCI haven't introduce the formal MLO config yet, please refer to the MAC80211 MT76 Programming Guide to Setup AP MLD and non-AP MLD (STA MLD) The default power control from user space is disabled to follow the maximum power from eFuse. If you would like to enable power-relevant features (e.g., SingleSKU/iw set Tx Power) make sure to set 'sku_idx' to zero for a single SKU table or to any positive number for the index of SKU tables you want in the hostapd configuration to enable it. You can double-check whether the value under '/sys/kernel/debug/ieee80211/phy0/mt76/sku_disable' is 0.
Yes thats one problem i have too for now, i am trying those steps from wozi
### wireless-regdb modification - this remove all regdb wireless countries restrictions
rm -rf openwrt/package/firmware/wireless-regdb/patches/*.*
rm -rf mtk-openwrt-feeds/autobuild/unified/filogic/mac80211/24.10/files/package/firmware/wireless-regdb/patches/*.*
\cp -r my_files/500-tx_power.patch mtk-openwrt-feeds/autobuild/unified/filogic/mac80211/24.10/files/package/firmware/wireless-regdb/patches
\cp -r my_files/regdb.Makefile openwrt/package/firmware/wireless-regdb/Makefile
### jumbo frames support
\cp -r my_files/750-mtk-eth-add-jumbo-frame-support-mt7998.patch openwrt/target/linux/mediatek/patches-6.6
### tx_power patch - required for BE14 boards with defective eeprom flash
\cp -r my_files/99999_tx_power_check.patch mtk-openwrt-feeds/autobuild/unified/filogic/mac80211/24.10/files/package/kernel/mt76/patches/
1 Like
@Zerogiven - When you get a working build, are you able to share it?
I also noticed OpenWrt 24.10.1 is now out officially. Might be worth while to make it based on that so people can easily install packages.
3 Likes
Yeah i saw the release..
First, maybe you could try the default 24.10.1 image without the mediatek feed. This is also i want try out, cause adding the mediatek feed is one step i only consider if it is worth If all is fine with the released bpi r4 image from OpenWRT, the only reason why i would build it by myself is cause i wanted set some GPIO pins as pull up and also do the PWM6 registration at the DTSI file. And yes one more cooling trip point i've added. However, like i already said, try the stable release pls, cause there is no reason if all works fine to make a custom build for others If not, one of my tasks is try an image with stable 24.10.1 source and the mediatek feed but building takes time
@Zerogiven I agree with the person above. I am a simple user who does not know how to compile firmware with patches, and I have the same problem. I am interested in a ready-made solution.