OpenWRT 24.10.1 reduces TX power (dbm) for MT7981

[Trigger31337]

Hi folks, I'm hoping someone can please help with this (and yes, I've checked the forums for similar posts already):

H/W == Cudy M3000 v1 (AX3000)
S/W == OWRT v24.10.1 r28597-0425664679
Chipset == MediaTek MT7981

The manufacturer states (on their website and physical packaging) an FCC supported output of up to 30dbm.
The original (stock, factory) Cudy firmware could output at this max 30 dbm range (I confirmed this is a valid option in the end-user config interface).
My regulatory domain allows for 30dbm on the freq/width that I'm broadcasting on.
So far, so good.

Now, I upgrade the device to 24.10.1, and the output of tools like "iw" or "iwinfo" or LUCI UI, etc... they will all show max values of less than 30 dbm. (The actual values differ, depending on the band, but neither the 2 nor 5 GHz band can go that high anymore, even though the regulatory domain still shows max 30 dbm).

Given the above, I suspect the "new" driver (supplied by 24.10.1) is the culprit.

Assuming you agree, what are my options to "bring back" the original Cudy driver (which is based on OWRT) for use with 24.10.1?

(Alternatively, could it be anything other than the driver?)

Thanks in advance.

[brada4]

@Trigger31337

Assuming you agree

NO, openwrt.org has no involvement in "cudy drivel" whatever that means. You know mom does not inherit genes from kids.

What output you get from

ubus call system board
iw list
cat /etc/config/wireless

Hide passwords etc

[dunsky]

Official Cudy firmware uses closed-source Mediatek drivers with an outdated OpenWrt fork. There is no way to use it in "vanilla" OpenWrt, unfortunately. At least this is not the right place to ask for it (there are some other forked builds you may find in Chinese forums with closed-source drivers, but you will be stuck with an old kernel as well).