Adding OpenWrt support for Xiaomi AX3600 (Part 1)

At first Thanks for the amazing work here.

I have four of that devices, 3 are in use with @robinmarko's software and one is for testing purpose, on this one I have flashed today the bigger space Image. No Problems doing that. But now Iḿ a little bit confused. What is now to do? There are several Images from @robinmarko and @dimfish. What are they used for? Iḿ new here and a little bit confused about ubi, bin and other files. What will I have to do to get a full working Router?

I've been editing the wiki. I think now all is clearer including the new instructions for single partition installation. When merged into OpenWrt I will update it again. Please take a look at it to see if something is wrong or the structure is not right.

@Herald I think was you who removed the information about the high memory usage of the ath11k because you are not suffering it. Me (an others) can confirm that the problem remains, I can replicate it without problem with latest version.

Regards!

2 Likes

Hey guys!

Both my partitions are with Robi's firmware before the partition change. How should I update?

Hi,

cat /proc/mtd
fw_printenv flag_boot_rootfs

if 0
ubiformat /dev/mtd13 -y -f /tmp/openwrt-ipq807x-generic-xiaomi_ax3600-initramfs-factory.ubi -s 2048 -O 2048 && fw_setenv flag_boot_rootfs 1 && fw_setenv flag_last_success 1

if 1
ubiformat /dev/mtd12 -y -f /tmp/openwrt-ipq807x-generic-xiaomi_ax3600-initramfs-factory.ubi -s 2048 -O 2048 && fw_setenv flag_boot_rootfs 0 && fw_setenv flag_last_success 0

reboot

sysupgrade -n /tmp/openwrt-ipq807x-generic-xiaomi_ax3600-squashfs-sysupgrade.bin

finish

4 Likes

And will I still have two partitions after that? Should I flash the other partition after the sysupgrade?

you should end up with one rootfs partition like this:

root@ax2:/# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "0:sbl1"
mtd1: 00100000 00020000 "0:mibib"
mtd2: 00300000 00020000 "0:qsee"
mtd3: 00080000 00020000 "0:devcfg"
mtd4: 00080000 00020000 "0:rpm"
mtd5: 00080000 00020000 "0:cdt"
mtd6: 00080000 00020000 "0:appsblenv"
mtd7: 00100000 00020000 "0:appsbl"
mtd8: 00080000 00020000 "0:art"
mtd9: 00080000 00020000 "bdata"
mtd10: 00100000 00020000 "pstore"
mtd11: 023c0000 00020000 "ubi_kernel"
mtd12: 0d240000 00020000 "rootfs"
root@ax2:/# df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root                 6.8M      6.8M         0 100% /rom
tmpfs                   203.4M    916.0K    202.5M   0% /tmp
/dev/ubi0_1             175.2M      2.0M    168.4M   1% /overlay
overlayfs:/overlay      175.2M      2.0M    168.4M   1% /
tmpfs                   512.0K         0    512.0K   0% /dev

and fwiw: I just did the same as stixi described on two devices an hour ago and it worked well.

After that I was able to (manually) restore the config backups without changes (I did the lan device renames in a previous update).
Looking forward to going official :slight_smile:

1 Like

After 1 Year i checked back to the latest experimental fw from robi.
Great work was done since that!
Good job guys!

2 key problems i found so far. i think this will never be fixed due driver limitations.

a) Main AX radio, cant change channel (if you set it, it will not start up)
b) 160mhz on Main AX radio is not working (if you set it, it will not start up)

OpenWrt SNAPSHOT, r0-71addb3

root@OpenWrt:~#
root@OpenWrt:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "0:sbl1"
mtd1: 00100000 00020000 "0:mibib"
mtd2: 00300000 00020000 "0:qsee"
mtd3: 00080000 00020000 "0:devcfg"
mtd4: 00080000 00020000 "0:rpm"
mtd5: 00080000 00020000 "0:cdt"
mtd6: 00080000 00020000 "0:appsblenv"
mtd7: 00100000 00020000 "0:appsbl"
mtd8: 00080000 00020000 "0:art"
mtd9: 00080000 00020000 "bdata"
mtd10: 00100000 00020000 "pstore"
mtd11: 023c0000 00020000 "ubi_kernel"
mtd12: 0d240000 00020000 "rootfs"
root@OpenWrt:~# df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root                 6.8M      6.8M         0 100% /rom
tmpfs                   203.4M    112.0K    203.3M   0% /tmp
/dev/ubi0_1             175.2M    428.0K    170.0M   0% /overlay
overlayfs:/overlay      175.2M    428.0K    170.0M   0% /
tmpfs                   512.0K         0    512.0K   0% /dev`

Do you set a wireless country code?

1 Like

I've been using 160mhz for more than a month now. Try setting the country to US

1 Like

Had the same problem. You have to set the country code (I think 00 world will work or choose US) and then you have to wait 30 - 60 seconds until 160 MHz works

Failsafe works fine with the new ax3600 extended partition image. I used it today multiple times while messing up with firewall. It is available in lan1 interface.

1 Like

Failsafe will get autoconfigured on the first LAN zone interface, in 99% of the cases on lan1 interface.

2 Likes

Hi Guys, I have installed an 2022 AX3600 OpenWrt image, with the dual image layout and wanted now to switch to the new image layout. But for some reasons, I don't find my MTD partition table layout compared to others seen here in this thread, so therefore asking (before shooting my current working Ax3600 to the moon), what went wrong at my side? Which actions do I need to perform?

root@OpenWrt:/tmp# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "0:sbl1"
mtd1: 00100000 00020000 "0:mibib"
mtd2: 00300000 00020000 "0:qsee"
mtd3: 00080000 00020000 "0:devcfg"
mtd4: 00080000 00020000 "0:rpm"
mtd5: 00080000 00020000 "0:cdt"
mtd6: 00080000 00020000 "0:appsblenv"
mtd7: 00100000 00020000 "0:appsbl"
mtd8: 00080000 00020000 "0:art"
mtd9: 00080000 00020000 "bdata"
mtd10: 00080000 00020000 "crash"
mtd11: 00080000 00020000 "crash_syslog"
mtd12: 06640000 00020000 "rootfs"
mtd13: 00080000 00020000 "rsvd0"

many thanks!

After a long wait, I finally bit the bullet now and installed the latest OpenWrt Firmware with the extended partition, that was practically the thing I was waiting for, including with normal sysupgrades.
(Finally I have tailscale on my router instead of my NAS.)

Just want to confirm that my experience is as expected, here is my setup:
I have Fibre to the Home (FTTH), 500 Mbps down and 100 Mbps up.
Using a AX3600 with VLAN tagged PPPoE. Was getting my 500/100 and even more then that on original firmware.

Was experimenting with some settings, for example, SQM, never heard of SQM and bufferbloat before, therefore I tried that out.
Did my tests from my PC on LAN with speedtest net and the waveform bufferbloat test, if there are better/ more accurate tests to do, please tell me.

SW offloading off, SQM off:
~420-440 down, ~100-115 up
Bufferbloat "A", bad max latency on active download
Unloaded ~12ms, DL ~+22ms, UP ~+2ms

SW offloading on, SQM off:
~480-500 down, ~100-115 up
Bufferbloat "A", slightly better latency from the stats I got
Unloaded ~12ms, DL ~+20ms, UP ~+2ms

With SQM (set to cake and piece of cake) things started getting weird for me.
Setting 120000 (kbit/s) on upload got me overall better upload latency with 0 downsides that I could see so I left it on 120000.
With download it's a different story, I don't understand my results with the download speed ingress I enter. Theoretically I should enter ~80-95% of my received speed, but that kind of didn't matter so I stayed on 475000.

SW offloading off, SQM on:
DL ingress/ UL egress: 475000/120000
~420-300 down, ~100-115 up
Bufferbloat "A+"
Unloaded ~13ms, DL ~+2ms, UP ~+0ms

SW offloading on:, SQM on:
DL ingress/ UL egress: 475000/120000
~320-350 down, ~100-115 up
Bufferbloat "A+"
Unloaded ~13ms, DL ~+2ms, UP ~+0ms

Latency on both is comparable, probably doesn't matter if there are any small discrepancies here.

TL;DR: ~20-30% worse download speeds with SQM enabled, is that normal/ expected?

Did you use the third-party uboot? Looks like you modify the partition layout.

Not that I am aware off...I updated my image with the temporary "corrupted" robimarko image once and had to revert to stock. Did basically all again from scratch to have OpenWrt. No further issues until now with this device...I could update to all other robimarko images without any problem.

And the time has finally come:

53 Likes

Hell of a journey and glad it's finally coming to an end :blush:

Are there any post merge plans yet? I suppose this does not yet include the fixed AX3600 BDF that's required for 2.7 to load?

Handle all the stuff will come up when the device will be upstream

3 Likes

Thank you for sharing your work and congratulations for the ipq807x-5.15-pr-final release!
:clap::clap::clap::clap:

Sent you a much deserved coffee


Also sent you a pizza @Ansuel , Thank you for all your work in openwrt!


Thank you all that contribute to this release and make openwrt possible!

5 Likes