Mediatek filogic
It isn't in OpenWRT 22, will it be added?
try this snapshot :
https://firmware-selector.openwrt.org/?version=SNAPSHOT&target=mediatek%2Ffilogic&id=asus_tuf-ax4200
Wow, this looks like they are storing EEPROM-data (calibration, mac addresses) redundantly in two UBI volumes. Very nice. But we will need NVMEM support for UBI volumes for this to work nicely... Should not be too hard to do in terms of code, but lots of discussion to bring this upstream as of now neither UBI devices nor volumes have any representation in device tree...
2 Likes
No, 23.xy.0, but not 22.03.x.
Do you know when they are planning to create the next release?
@blocktrron Do you know how we could flash back to OEM firmware?
A sysupgrade from OpenWRT or using the Asus firmware restoration tool doesn't seem to do the job.
Any help would be appreciated.
23 should mean 2023.
Btw xdr6088 is supported now:https://github.com/openwrt/openwrt/commit/21be2c26d555b33e9faf85be3e980876810b29d3
Do you have these transfers with openwrt. How looks transfer WAN-> WAN ? I have this router with stock software and I can see transfers around 830Mbits. WAN->LAN and LAN-> WAN, I have AX210 on the client site. best regards.
The tests were done on OpenWRT
Have you have possibility to compared coverage and transfers between OenWRT and vendor software? Maybe you alredy know how to revert the router to the vendor software and maybe you compared the router with other router. I compared with D-Link DIR-2660. Eveything what is farther then 2 meters looks better on the D-Link which was on the OpenWRT.
I wasn't able to reflash to vendor firmware, tried from bootloader and also with the Asus restoration tool, it just boots to OpenWRT.
This method didn't seem to work either:
Could you share structure of the ubi devices?
root@Asus:~# ubinfo -a
UBI version: 1
Count of UBI devices: 1
UBI control device major/minor: 10:127
Present UBI devices: ubi0
ubi0
Volumes count: 8
Logical eraseblock size: 126976 bytes, 124.0 KiB
Total amount of logical eraseblocks: 2016 (255983616 bytes, 244.1 MiB)
Amount of available logical eraseblocks: 0 (0 bytes)
Maximum count of volumes 128
Count of bad physical eraseblocks: 0
Count of reserved physical eraseblocks: 40
Current maximum erase counter value: 11
Minimum input/output unit size: 2048 bytes
Character device major/minor: 250:0
Present volumes: 0, 1, 2, 3, 4, 5, 6, 7
Volume ID: 0 (on ubi0)
Type: dynamic
Alignment: 1
Size: 1 LEBs (126976 bytes, 124.0 KiB)
State: OK
Name: nvram
Character device major/minor: 250:1
-----------------------------------
Volume ID: 1 (on ubi0)
Type: dynamic
Alignment: 1
Size: 8 LEBs (1015808 bytes, 992.0 KiB)
State: OK
Name: Factory
Character device major/minor: 250:2
-----------------------------------
Volume ID: 2 (on ubi0)
Type: dynamic
Alignment: 1
Size: 8 LEBs (1015808 bytes, 992.0 KiB)
State: OK
Name: Factory2
Character device major/minor: 250:3
-----------------------------------
Volume ID: 3 (on ubi0)
Type: dynamic
Alignment: 1
Size: 31 LEBs (3936256 bytes, 3.7 MiB)
State: OK
Name: linux
Character device major/minor: 250:4
-----------------------------------
Volume ID: 4 (on ubi0)
Type: dynamic
Alignment: 1
Size: 578 LEBs (73392128 bytes, 69.9 MiB)
State: OK
Name: linux2
Character device major/minor: 250:5
-----------------------------------
Volume ID: 5 (on ubi0)
Type: dynamic
Alignment: 1
Size: 799 LEBs (101453824 bytes, 96.7 MiB)
State: OK
Name: jffs2
Character device major/minor: 250:6
-----------------------------------
Volume ID: 6 (on ubi0)
Type: dynamic
Alignment: 1
Size: 147 LEBs (18665472 bytes, 17.8 MiB)
State: OK
Name: rootfs
Character device major/minor: 250:7
-----------------------------------
Volume ID: 7 (on ubi0)
Type: dynamic
Alignment: 1
Size: 398 LEBs (50536448 bytes, 48.1 MiB)
State: OK
Name: rootfs_data
Character device major/minor: 250:8
root@Asus:~# cat /proc/mtd
dev: size erasesize name
mtd0: 00400000 00020000 "Bootloader"
mtd1: 0fc00000 00020000 "UBI_DEV"
Do you remember distance to the router when you tested throughput ?
I didn't do any wireless testing
Hi, cloud you perform test WIFI<-> WIFI and WIFI<->LAN clients ?
I can do that for the stock software. Could you confirm that OpenWRT supports or not 160MHz channels?
EDIT1. Could you paste whole output from /proc/mtd ?
My stock volumes
ubinfo -a
UBI version: 1
Count of UBI devices: 1
UBI control device major/minor: 10:62
Present UBI devices: ubi0
ubi0
Volumes count: 6
Logical eraseblock size: 126976 bytes, 124.0 KiB
Total amount of logical eraseblocks: 2016 (255983616 bytes, 244.1 MiB)
Amount of available logical eraseblocks: 0 (0 bytes)
Maximum count of volumes 128
Count of bad physical eraseblocks: 0
Count of reserved physical eraseblocks: 40
Current maximum erase counter value: 4
Minimum input/output unit size: 2048 bytes
Character device major/minor: 250:0
Present volumes: 0, 1, 2, 3, 4, 5
Volume ID: 0 (on ubi0)
Type: dynamic
Alignment: 1
Size: 1 LEBs (126976 bytes, 124.0 KiB)
State: OK
Name: nvram
Character device major/minor: 250:1
-----------------------------------
Volume ID: 1 (on ubi0)
Type: dynamic
Alignment: 1
Size: 8 LEBs (1015808 bytes, 992.0 KiB)
State: OK
Name: Factory
Character device major/minor: 250:2
-----------------------------------
Volume ID: 2 (on ubi0)
Type: dynamic
Alignment: 1
Size: 8 LEBs (1015808 bytes, 992.0 KiB)
State: OK
Name: Factory2
Character device major/minor: 250:3
-----------------------------------
Volume ID: 3 (on ubi0)
Type: dynamic
Alignment: 1
Size: 578 LEBs (73392128 bytes, 70.0 MiB)
State: OK
Name: linux
Character device major/minor: 250:4
-----------------------------------
Volume ID: 4 (on ubi0)
Type: dynamic
Alignment: 1
Size: 578 LEBs (73392128 bytes, 70.0 MiB)
State: OK
Name: linux2
Character device major/minor: 250:5
-----------------------------------
Volume ID: 5 (on ubi0)
Type: dynamic
Alignment: 1
Size: 799 LEBs (101453824 bytes, 96.8 MiB)
State: OK
Name: jffs2
Character device major/minor: 250:6
cat /proc/mtd
dev: size erasesize name
mtd0: 00400000 00020000 "Bootloader"
mtd1: 0fc00000 00020000 "UBI_DEV"
mtd2: 0001f000 0001f000 "nvram"
mtd3: 000f8000 0001f000 "Factory"
mtd4: 000f8000 0001f000 "Factory2"
mtd5: 045fe000 0001f000 "linux"
mtd6: 042df514 0001f000 "rootfs"
mtd7: 045fe000 0001f000 "linux2"
mtd8: 042df514 0001f000 "rootfs2"
best regards
There are no other mtd partitions listed, only 0 and 1.
If I get time I might do some wireless tests.
Take care
Probably that's why you cant revert software to the stock one. Maybe we can revert structure of the mtd's and ubifs manually or openWRT image will change volumes structure for this router if its possible.