Release ASUS RT-AX86 Series(RT-AX86U/RT-AX86S) Firmware version 3.0.0.4.388_24243 (2024/05/13)

[aardbeix15]

I rolled back the update yesterday to the firmware version of November 2023 (FW_RT_AX86U_AX86S_300438823285).
Installation went smoothly, but I continued to have a very slow signal on all kinds of clients, wired and via WiFi. Also after rebooting or reconnecting the clients. Slow DNS resolving or no response at all. To be sure, I also restarted my cable modem, but that made no difference. Also rebooted the router several times. After an hour of frustration with mobile phones not working, an Android TV that received a kind of super slow signal when wired, the trade was put back again, and it was arranged in a minute.

I don't have anything special running;
- a ZenWiFi AX Mini via 1Gpbs swtich wired in AImesh-mode
- custom dns on 1.1.1.3 and secondary AdGuard dns
- OpenVPN server configured in ASUS-WRT
- a few port forwards to access my Plex server, among other things.
- QoS, Analyzer, Game things I have all turned off.
- router is behind a DMZ IP that my modem passes on.

In a running household with a wife and children, it is too much work for me to have to reset everything manually/then I really have to schedule it at some point, but perhaps that is the only method to be able to make the step to this firmware.

Very strange what this can cause.
I did notice that Asus also downloaded the latest firmware from the site after November 2023 for the AX86U Game/non-pro.

Normally a nice router when it works, but these kinds of crazy firmware upgrades are really terrible.

 

[SeriousFamily]

updated and running smoothly for a couple of days now.

 

[camaro322hp]

Dirty flashed this update from 3.0.0.4_388_24231 and all is working fine for about a week now. My use case for this router is pretty basic. I do use DDNS and WireGuard VPN server, and those are confirmed working after update.

 

[Volfi]

Getting these errors after upgrade. Anybody knows how to solve this?

May 29 19:50:17 kernel: wl0: PSM microcode watchdog fired at 208361 (seconds). Resetting.
May 29 19:50:17 kernel: wl0: reason = psm watchdog at 208361 seconds. corerev 131 ucode revision 1626.38205 features 0x3106
May 29 19:50:17 kernel: psmdebug 0x000001ff pc 0x01ff000e phydebug 0x0 macctl 0x84160403 maccmd 0x4
May 29 19:50:17 kernel: psm_brc 0x0181 psm_brc_1 0x0000 M_UCODE_DBGST 0x2

 

[1ceLaz0r]

Getting these errors after upgrade. Anybody knows how to solve this?

May 29 19:50:17 kernel: wl0: PSM microcode watchdog fired at 208361 (seconds). Resetting.
May 29 19:50:17 kernel: wl0: reason = psm watchdog at 208361 seconds. corerev 131 ucode revision 1626.38205 features 0x3106
May 29 19:50:17 kernel: psmdebug 0x000001ff pc 0x01ff000e phydebug 0x0 macctl 0x84160403 maccmd 0x4
May 29 19:50:17 kernel: psm_brc 0x0181 psm_brc_1 0x0000 M_UCODE_DBGST 0x2

Yeah, don't worry about it.

 

[willyburz]

Updated and still working great! 160HZ is staying locked and wifi TRX rates are 1900-2499 on my 2.5gb line connections. Stable, and great so far.

 

[willyburz]

I will add, I found a really good open channel on the 160 hz mode, I have NOT checked or tried to auto channel in 160 for a year now...I found all previous auto locked channel with minimal interference would kick out of 160hz mode but stay on same channel. It was NOT radar kicks, but legitimate low interference with channels would drop the 160hz to 80hz. It was and is annoying, I highly recommend channel scanning "WiFiAnalyzer - open source" for a day or two and find the cleanest channel spot for yourself, then hardlock 160hz and the channel...even the jack butt neighbor eeros avoid my locked channel now, when they channel dance around! I legitimately have not dropped 160hz for months. If I ever do drop, I just reboot and it's back.