Dynalink DL-WRX36 Askey RT5010W IPQ8072A technical discussion

I finally got around to building the openwrt-23.05 image with flush queues on station disconnect patches removed.

rm package/kernel/mac80211/patches/subsys/331-wifi-mac80211-flush-queues-on-STA-removal.patch
rm package/kernel/mac80211/patches/subsys/333-wifi-mac80211-add-flush_sta-method.patch
patch -l -p1 << EOF
--- a/package/kernel/mac80211/patches/subsys/360-wifi-mac80211-do-not-pass-ap_vlan-vif-pointer-to-dri.patch
+++ b/package/kernel/mac80211/patches/subsys/360-wifi-mac80211-do-not-pass-ap_vlan-vif-pointer-to-dri.patch
@@ -53,12 +53,3 @@ Signed-off-by: Sasha Levin <sashal@kernel.org>
        if (sdata && !check_sdata_in_driver(sdata))
                return;
  
-@@ -623,6 +626,8 @@ static inline void drv_flush_sta(struct
- {
-       might_sleep();
- 
-+      sdata = get_bss_sdata(sdata);
-+
-       if (sdata && !check_sdata_in_driver(sdata))
-               return;
- 
EOF
patch -l -p1 << EOF
--- a/package/firmware/ath11k-firmware/Makefile
+++ b/package/firmware/ath11k-firmware/Makefile
@@ -60,7 +60,7 @@ $(eval $(call Download,qcn9074-board))
 define Package/ath11k-firmware-ipq8074/install
        $(INSTALL_DIR) $(1)/lib/firmware/IPQ8074
        $(INSTALL_DATA) \
-               $(PKG_BUILD_DIR)/ath11k-firmware/IPQ8074/hw2.0/testing/2.9.0.1/WLAN.HK.2.9.0.1-01385-QCAHKSWPL_SILICONZ-1/* \
+               $(PKG_BUILD_DIR)/ath11k-firmware/IPQ8074/hw2.0/2.7.0.1/WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1/* \
                $(1)/lib/firmware/IPQ8074/
 endef
 
EOF

This fully resolves the issue where station disconnect causes wifi outage for a few seconds and queue flush errors in syslog.

Is firmware-selector.openwrt.org br0ken lately? When I customize my build for SNAPSHOT and request build, nothing happens.

Not device specific, use/read The OpenWrt Firmware Selector.

1 Like

Thank you.

Re: the flush patch

This seems like good news; I haven’t had time to figure this out but I am very interested in a second attempt and upgrading my wifi to these devices … have you seen any other instabilities yet , I had issues like losing ARP replies , etc over time.

Right now because of wifi instability I had re activated my old network, thats been perfectly stable now for 2 months so I am back in credit.

I never really had any instability issues that others reported. The multicast issue was resolved by downgrading firmware from 2.9.0.1-01385 (testing) to 2.7.0.1-01744 (stable). That I did long time ago. I am not using any multicast to unicast workarounds, IPv6 works fine.

The queue flush errors causing a few seconds outage for all clients ware fixed by removing the queue flush patches. That I did recently as it required to rebuild system image. It's been running stable for about a week.

Also, I learned that putting phone in airplane mode or turning WiFi off is not the same effect as going out of Wi-Fi range when leaving home. The later is more prone to cause queue flush errors.

1 Like

That’s good to know. 01744 was skipped for the overall target because it caused crashes on a different model:

I understand but isn't there a way to install different firmware for different target? Like have package different than ath11k-firmware-ipq8074 for Redmi AX6. Maybe wasn't worth the effort...

I don't know how people don't notice the issues with 2.9.0.1-01385 firmware. Maybe they are manifesting differently on different hardware. Not having IPv6 and getting constant outages in online gaming when people move out of Wi-Fi range (which happens a lot for me) was a show stopper.

Anyway, probably the newest 2.12-01368 firmware from latest QSDK may be the choice moving forward once it's pushed to upstream git. I haven't tried that on DL-WRX36 but will play around with it once my new LN1301 toy arrives.

"inventreason697"
SSID: DYNALINK-AE
For users looking for the wifi password it is : "inventreason697"

This is for the config file that enables SSH. WiFi is enabled with the above password.

I think it's time for me to create a new image.

I don't have any problems at the moment, but my image is probably about 9 months old.