Adding OpenWrt support for Xiaomi AX3600

It seems that i was wrong, and it's the same build as before (OpenWrt SNAPSHOT r17806-0cb68fdabd / LuCI Master git-21.286.73463-1a0c1b7).
I thought that this was a different one (at night).
I tried sysupgrading with 21.10.29_512MB_patched_working.
Should one clean flash it?

I also have do sysupgrade 4 or 5 times till the upgrade work. For me a normal "dirty" flash was working well.
You also can
ubiformat /dev/mtd12 -f /tmp/openwrt-ipq807x-generic-xiaomi_ax3600-squashfs-nand-factory.ubi -s 2048 -O 2048
the not in use partition and boot it with
fw_printenv flag_boot_rootfs
fw_setenv flag_boot_rootfs 0
fw_setenv flag_last_success 0

I didn't open mine so I can't see the serial logs

Hello,

Can someone link me to a full tuto (or explain how) to install openwrt or how to get SSH on the Redmi AX6 please, I'm a little lost, I tried with this tuto.
I have the AX6 and another router running openwrt (can reset it to default in order to follow the instructions)

I getting these annoying connect/disconnect every few seconds on a few of my mobile phones making it impossible for them to stay connected to the AX 5GHz radio. I've tried numerous different configuratios without luck.

Sun Oct 31 10:50:24 2021 daemon.info hostapd: wlan1: STA 88:46:04:50:77:9c WPA: pairwise key handshake completed (RSN)
Sun Oct 31 10:50:24 2021 daemon.notice hostapd: wlan1: EAPOL-4WAY-HS-COMPLETED 88:46:04:50:77:9c
Sun Oct 31 10:50:27 2021 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED 88:46:04:50:77:9c
Sun Oct 31 10:50:29 2021 daemon.info hostapd: wlan1: STA 88:46:04:50:77:9c IEEE 802.11: authenticated
Sun Oct 31 10:50:29 2021 daemon.notice hostapd: wlan1: STA-OPMODE-N_SS-CHANGED 88:46:04:50:77:9c 2
Sun Oct 31 10:50:29 2021 daemon.info hostapd: wlan1: STA 88:46:04:50:77:9c IEEE 802.11: associated (aid 3)
Sun Oct 31 10:50:29 2021 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 88:46:04:50:77:9c
Sun Oct 31 10:50:29 2021 daemon.info hostapd: wlan1: STA 88:46:04:50:77:9c WPA: pairwise key handshake completed (RSN)
Sun Oct 31 10:50:29 2021 daemon.notice hostapd: wlan1: EAPOL-4WAY-HS-COMPLETED 88:46:04:50:77:9c
Sun Oct 31 10:50:32 2021 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED 88:46:04:50:77:9c
Sun Oct 31 10:50:34 2021 daemon.info hostapd: wlan1: STA 88:46:04:50:77:9c IEEE 802.11: authenticated
Sun Oct 31 10:50:34 2021 daemon.notice hostapd: wlan1: STA-OPMODE-N_SS-CHANGED 88:46:04:50:77:9c 2
Sun Oct 31 10:50:34 2021 daemon.info hostapd: wlan1: STA 88:46:04:50:77:9c IEEE 802.11: associated (aid 3)
Sun Oct 31 10:50:34 2021 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 88:46:04:50:77:9c
Sun Oct 31 10:50:34 2021 daemon.info hostapd: wlan1: STA 88:46:04:50:77:9c WPA: pairwise key handshake completed (RSN)
Sun Oct 31 10:50:34 2021 daemon.notice hostapd: wlan1: EAPOL-4WAY-HS-COMPLETED 88:46:04:50:77:9c
Sun Oct 31 10:50:37 2021 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED 88:46:04:50:77:9c
1 Like

Unfortunately, not a solution, but hopefully information that may help find one. I found I had exactly he same problem with my 2018 iPad Pro (3rd Gen), whereas my partner's 2016 iPad Pro (1st Gen) was fine. Also that the feature Apple has of scrambling your device's MAC address for each network you connect to seemed to make it worse (buyt turning it off didn't resolve it fully). I was just wondering if your phone are also all Apple post-2016? I also install DAWN on my routers, and had two AC (ie not AX) routers acting as dumb wireless APs. If any of this sounds familiar, it may be the root cause.

1 Like

It happens on a Xiaomi 2021 phone and started after the latest mac80211 update, I haven't actually tested reverting that yet.

From what I have read it seems to be a wireless power saving mechanism that causes the problem.

I also noticed issues with AX capable Devices. Though my notebook with a AX200 is working fine on 5Ghz, it has problems on 2.4 Ghz (disconnects and high latency)

A iPhone 12 on the other hand isn't even able to connect to the 5 Ghz band.

Do you have a link to the mac80211 issue?

I also had issues with a smartphone resulting in choppy VoIP over wifi. I applied these patches from coolsnowwolf on top of the backports branch and it works now:

    package/kernel/mac80211/patches/ath11k/011-ath11k-fix-4-addr-tx-failure-for-AP-and-STA-modes.patch
    package/kernel/mac80211/patches/ath11k/033-ath11k-fix-for-peer-memory-corruption.patch
    package/kernel/mac80211/patches/ath11k/143-ath11k-disabling-credit-flow-for-ath11k.patch
    package/kernel/mac80211/patches/ath11k/191-ath11k-add-mgmt-and-data-ack-rssi.patch
    package/kernel/mac80211/patches/ath11k/237-001-ath11k-Disable-unused-CE8-interrupts.patch
    package/kernel/mac80211/patches/ath11k/302-ath11k-tx-mgmt-cleanup-fix.patch
    package/kernel/mac80211/patches/ath11k/314-002-ath11k-fix-ce-dp-address-alignment.patch
    package/kernel/mac80211/patches/ath11k/802-ath11k-small-tx-queue.patch
2 Likes

I am just guessing that it could be caused by the mac80211 updates.

Figured out for SSH access but still not how to install openwrt nor from which git repo...
I always get is too large when flashing, guess it's all about that 512Mb patch I saw on some posts but I'm completely unable to find the install process.
Can someone guide me (Redmi AX6 on 1.0.16) please?

Can someone clarify the difference between @robimarko AX3600-5.10-restart branch and the IPQ807x-5.10-backports branches? From reading some other posts in this thread, I understand that the latter includes backports from Linux Kernel 5.14?

I guess the reason I'm asking is just that I've had major issues with the new backports branch. I tried building it twice with basically an identical config to what I've been using on the restart branch, and the results were basically:

-The first build flashed successfully, but resulted in significantly reduced effective range for the AX3600 router. Although not an exact metric, I would just say it's a difference between "The signal can reach everywhere in my condo with full bars and near-full speed" vs. "The signal only reaches about half of my condo". It was like an invisible barrier was present at a certain distance where my phones (all iOS) would either show they were connected but not be able to send/receive data, or where the phones would just flat out refuse to connect to the network despite being able to see the SSID on the list.

-With the first build behaving so oddly, I tried basically a "fresh" build by starting from scratch and checking out the repo fresh and manually selecting everything again via menuconfig. The second build, however, ended up being quite a bit worse than the first, however, as it just soft-bricked my device.

I was able to recover using the TFTP methods - but I guess my primary question at this point is just has anyone been able to use the backports branch without major issues?

Its simple, the backports is newer, one being worked on and it includes the 5.15 based mac80211

1 Like

robi did you notice they just branched 5.15 to be lts ? i tought 5.16 was the next lts...

Yeah, I anticipated that.
The LTS version is whichever is the last one to be released in the year since this year there were multiple releases running into RC8 that pushed everything back and now 5.16 obviously won't be released in 2021, hence 5.15 being LTS.
Hopefully, OpenWrt gets generic support soon.

will have some fun with testing ipq806x with 5.15 as i need to test new dsa feature... (sorry for ot)
Wonder how much patch i will have to remove from generic

I gave 5.15 in OpenWrt a go recently, lets just say that it was a pain and I gave up.
There is just too many hacks that weren't upstreamed and that wont apply

Sad... i tried 5.11 some times ago and i didn't have to remove that much stuff from it...

So i did some more digging into the high memory usage on ath11k and it kind of seems to be expected behaviour ? As in the memory doesn't seem to be leaking as such it's just seems to be a large amount of references held. (It's odd, although it could just be that it's not developed on devices that are limited to 512mb of memory)

It would be interesting to see how the 1gb devices fair

1 Like

Sysupgrade only updates the rootfs partition right?

I was trying to keep the Xiaomi firmware on rootfs_1 and run OpenWRT on rootfs but I can't for the life of me get a system upgrade to apply.

I think it's been mentioned a few times on here, that to so a sysupgrade you MUST have flashed both mtd12 and mtd13 partitions first (i.e. flash the one you are NOT booted into first using either:
nvram get flag_boot_rootfs
or from openwrt:
fw_printenv flag_boot_rootfs
to find out which one). Then reboot into openwrt and flash the OTHER partition.

P.S. I can't instantly see this on the wiki, should I add it?

2 Likes