No idea.
Maybe all that's needed it to remove the two extra ubi partitions.
But rest of the ubi partitions will have different size and will stay on one mtd. Maybe mtd level is a problematic.
Hi . I performed some tests on the stock software and I confirm that this router is MUMIMO 3x3:2. I performed all tests with disabled 2.4GHz, on the 36 channel 160MHz wide. 3 meters away from router.
WIFI client 1 (ax210) -> WIFI client 2 (ax210)
iperf3 -c 192.168.10.41 -i 1 -t 60 -P 2
.....
[ 5] 55.00-56.00 sec 43.8 MBytes 367 Mbits/sec 0 1.31 MBytes
[ 7] 55.00-56.00 sec 37.5 MBytes 315 Mbits/sec 0 1.19 MBytes
[SUM] 55.00-56.00 sec 81.2 MBytes 682 Mbits/sec 0
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 56.00-57.00 sec 46.2 MBytes 388 Mbits/sec 0 1.33 MBytes
[ 7] 56.00-57.00 sec 33.8 MBytes 283 Mbits/sec 0 1.26 MBytes
[SUM] 56.00-57.00 sec 80.0 MBytes 671 Mbits/sec 0
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 57.00-58.00 sec 41.2 MBytes 346 Mbits/sec 0 1.36 MBytes
[ 7] 57.00-58.00 sec 40.0 MBytes 336 Mbits/sec 0 1.31 MBytes
[SUM] 57.00-58.00 sec 81.2 MBytes 682 Mbits/sec 0
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 58.00-59.00 sec 35.0 MBytes 294 Mbits/sec 364 737 KBytes
[ 7] 58.00-59.00 sec 43.8 MBytes 367 Mbits/sec 0 1.34 MBytes
[SUM] 58.00-59.00 sec 78.8 MBytes 661 Mbits/sec 364
WIFI client 1 (ax210) <- WIFI client 2 (ax210)
iperf3 -c 192.168.10.41 -i 1 -t 60 -P 2 -R
....
5] 56.00-57.00 sec 71.9 MBytes 603 Mbits/sec
[ 7] 56.00-57.00 sec 2.92 MBytes 24.5 Mbits/sec
[SUM] 56.00-57.00 sec 74.8 MBytes 627 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 57.00-58.00 sec 73.3 MBytes 615 Mbits/sec
[ 7] 57.00-58.00 sec 3.07 MBytes 25.8 Mbits/sec
[SUM] 57.00-58.00 sec 76.4 MBytes 641 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 58.00-59.00 sec 73.0 MBytes 612 Mbits/sec
[ 7] 58.00-59.00 sec 1.86 MBytes 15.6 Mbits/sec
[SUM] 58.00-59.00 sec 74.8 MBytes 628 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 59.00-60.00 sec 74.4 MBytes 624 Mbits/sec
[ 7] 59.00-60.00 sec 1.11 MBytes 9.35 Mbits/sec
[SUM] 59.00-60.00 sec 75.6 MBytes 634 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.02 sec 4.27 GBytes 611 Mbits/sec 948 sender
[ 5] 0.00-60.00 sec 4.27 GBytes 611 Mbits/sec receiver
[ 7] 0.00-60.02 sec 102 MBytes 14.2 Mbits/sec 2433 sender
[ 7] 0.00-60.00 sec 99.1 MBytes 13.9 Mbits/sec receiver
[SUM] 0.00-60.02 sec 4.37 GBytes 625 Mbits/sec 3381 sender
[SUM] 0.00-60.00 sec 4.36 GBytes 624 Mbits/sec receiver
WIFI client 1 (ax210) -> WAN
iperf3 -c 192.168.10.31 -i 1 -t 60
....
[ 5] 52.00-53.00 sec 111 MBytes 933 Mbits/sec 0 1.16 MBytes
[ 5] 53.00-54.00 sec 112 MBytes 944 Mbits/sec 0 1.23 MBytes
[ 5] 54.00-55.00 sec 111 MBytes 933 Mbits/sec 1 950 KBytes
[ 5] 55.00-56.00 sec 111 MBytes 933 Mbits/sec 1 751 KBytes
[ 5] 56.00-57.00 sec 111 MBytes 933 Mbits/sec 0 858 KBytes
[ 5] 57.00-58.00 sec 108 MBytes 902 Mbits/sec 1 659 KBytes
[ 5] 58.00-59.00 sec 108 MBytes 902 Mbits/sec 0 738 KBytes
[ 5] 59.00-60.00 sec 108 MBytes 902 Mbits/sec 0 793 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 6.30 GBytes 902 Mbits/sec 670 sender
[ 5] 0.00-60.04 sec 6.30 GBytes 901 Mbits/sec receiver
WIFI client 1 (ax210) <- WAN
iperf3 -c 192.168.10.31 -i 1 -t 60 -R
....
[ 5] 50.00-51.00 sec 110 MBytes 923 Mbits/sec
[ 5] 51.00-52.00 sec 111 MBytes 929 Mbits/sec
[ 5] 52.00-53.00 sec 112 MBytes 938 Mbits/sec
[ 5] 53.00-54.00 sec 112 MBytes 942 Mbits/sec
[ 5] 54.00-55.00 sec 112 MBytes 937 Mbits/sec
[ 5] 55.00-56.00 sec 112 MBytes 937 Mbits/sec
[ 5] 56.00-57.00 sec 112 MBytes 937 Mbits/sec
[ 5] 57.00-58.00 sec 112 MBytes 938 Mbits/sec
[ 5] 58.00-59.00 sec 112 MBytes 939 Mbits/sec
[ 5] 59.00-60.00 sec 112 MBytes 939 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.04 sec 6.54 GBytes 936 Mbits/sec 616 sender
[ 5] 0.00-60.00 sec 6.54 GBytes 937 Mbits/sec receiver
WIFI client 3 (AC8265) with MIMO -> WAN
around 70 MBytes - 600 Mbits/sec
WIFI client 3 (AC8265) with MIMO <-> WIFI client 2 (ax210)
around 45MBytes
Vendor software based on the AsusWRT. When you enable ssh via web page you can login as a root user. So all processess in the system also work in the root context (UID 0).
@Gingernut Could you perform tests on the OpenWRT and/or verify that that we can revert to the stock software when we delete partitions?
best regards,
1 Like
Hello:
Is someone knows how to recover to asuswrt firmware from openwrt firmware.
I have a TUF-AX4200 and update to openwrt firmware,
Now i want to recover to asuswrt firmware but failed. It seems that the volume size is small.
Thank you.
how was it done ?
I know that @Gingernut tried revert to the stock firmware without success. We compared mtd devices and UBI partitionos. You could try delete last two partitions but probably you will need to restore whole mtd and ubi devices structure.
@frollic have you reverted router to the stock software with success?
@LLY cloud you confirm that OpenWRT supports 160MHz channels or not on the RX and TX ?
I dont want to flash openWRT before any working solution to restore stock software. I can still send router back to the shop without any reason. 
best regards.
Patryk
I've drafted how NVMEM from UBI volumes could look like and it works already on top of linux-next:
Review would be very welcome 
2 Likes
Maybe we should change the openwrt partitions layout for this router like for https://github.com/openwrt/openwrt/blob/openwrt-23.05/target/linux/ramips/dts/mt7621_dlink_dir-xx60-a1.dtsi
currently dts file contains only:
partitions: partitions {
compatible = "fixed-partitions";
#address-cells = <1>;
#size-cells = <1>;
partition@0 {
label = "bootloader";
reg = <0x0 0x400000>;
read-only;
};
partition@400000 {
label = "UBI_DEV";
reg = <0x400000 0xfc00000>;
};
};
for factory partition we can see also:
&factory {
compatible = "nvmem-cells";
#address-cells = <1>;
#size-cells = <1>;
macaddr_factory_e000: macaddr@e000 {
reg = <0xe000 0x6>;
};
macaddr_factory_e006: macaddr@e006 {
reg = <0xe006 0x6>;
};
};
btw. lets try to create pull request to the github repo with your driver.
@blocktrron Could you confirm or deny that we have to change partitions layout in the dts file and add factory ?
best regards,
Thank you all for the unseful info.
I've installed day before via Raspberry PI, using it's UART serial console to the AX4200. Works beutifully well.
A few issues I noticed, wanted to share:
- set 5Ghz channel 149 (or above), AX + 160Mhz: the displayed frequency than 6.xxx Ghz (on luci), and no channel, the 160Mhz does not work on lower channels (36-40) as well, it says set, but externally I can't see anything on 5Ghz, radio seems does not work.
- router get frozen, need to reset after switched on: Firewall -> SW offloading + HW offloading.
- is that possible to switch off LEDs completely, these are very bright and annoying nighttime.
Question: in original Asus FW, I've seen two parameters to adjust:
- 1024QAM
- beamforming
wheter these ones are automatically ON, or inaccessible from owrt, or just missing from it's settings.
Thanks,
minato
Hi,
"he 160Mhz does not work on lower channels (36-40) as well, it says set, but externally I can't see anything on 5Ghz, radio seems does not work."
do you have AX intel client? Please confirm your reg on the client. You could try restart client system and check again with channel set 36. You can also test channel 100. Other options shouldn't work.
router get frozen, need to reset after switched on: Firewall -> SW offloading + HW offloading.
Probably doesn't support HW offloading on the firewall.
is that possible to switch off LEDs completely, these are very bright and annoying nighttime.
Only one option which I know is the dts modification.
1024QAM
Please supply link values like MCS or NSS. You can compare it also with MCS tables and inform us
You can also confirm coding type for QAM.
beamforming
Please paste output from command:
grep vht_capab /var/run/hostapd*.conf
best regards,
I have a mobile phone, checked with Asus original firmware, the 160Mhz option worked on lower and upper 5Ghz channels as well. With OpenWRT, it does not. Checked the channel 100/160Mhz option, it's working! Thanks.
Phone does see the 2x80Mhz channel, BUT on upper 5Ghz channels, I can see this:
Channel 149 6.695Ghz
root@OpenWrt:~# grep vht_capab /var/run/hostapd*.conf
vht_capab=[RXLDPC][SHORT-GI-80][SHORT-GI-160][TX-STBC-2BY1][SU-BEAMFORMER][SU-BEAMFORMEE][MU-BEAMFORMER][MU-BEAMFORMEE][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][SOUNDING-DIMENSION-3][BF-ANTENNA-3][VHT160][MAX-MPDU-11454][MAX-A-MPDU-LEN-EXP7]
The 160 MHz channel and SU-BEAMFORMEE are supported by kernel drivers. Please confirm frequency on the client site and show the screen with connected client to the AP ( wifi tab of luci) when you transfer data.
best regards,
@minato Have you installed 23.05-rc1 or snapshot build ? I have similar problem with older devices and MT76.
latest, snapshot
@patrykk Here is it:
An another question:
It looks the Disk space / Temp space has some disproportion, should be reversed. not? The temp would be better to keep small and the "normal" Dosk space a bit higher. Anyways, thois does not affect me, because I use very minimal installed opkg extra packages...
'Temp space' refers to the tmpfs mounted on /tmp/, which defaults to half of your RAM - looks o.k. to me.
2 Likes
I have another one router with mediatek MT7615E. It looks like we have here that same driver and will have that same problems with 160MHz on linux kernel 5.15.x. I prefer to stay with vendor software because I prefer more stable wifi than LACP and 802.11r/v support.
Is still serial connection required for installation on this device? Thank you
Unfortunately yes
2 Likes