No. 3.0.0.6 will be for newer models starting with the GT-AX6000.Any chance RT-AX88U getting next feature update betas? like 9.0.0.6 series?
@RMerlin
They took down the update from autoupdate and only available from web page, that's a good thing, so they know about the process i mention earlier that takes 50% cpu, reverting with same settings on previous firmware I have 1% cpu.The last two official releases are rock solid for my stand alone ax88u router. There is no any single issue and wifi is super fast. Asus finally did a really great job for stability and functionality and cover all my needs. The auto update is working fine.
Interesting data point. I'm also having no issues with either my AX88Us, which are both used a AI Mesh nodes. it seems the issues are centralized around folks using one as the router for an AI Mesh setup.The last two official releases are rock solid for my stand alone ax88u router. There is no any single issue and wifi is super fast. Asus finally did a really great job for stability and functionality and cover all my needs. The auto update is working fine.
Exactly, and because of that takes too much processing power crawling interface speed, this firmware is bad as i said previously.Same here. 20558 will have to do for now.
Small blips in wifi, impossible to track down in logs. My AX88U is acting as node and although the blips didn't affect too many clients, it was driving me crazy if I had something to do on its coverage. I could live with it but:
kernel: io:GET_GPIO: get val(1) from pa(32772), gpio_num_max=320 logs 4/seconds is the drop that filled the glass!
My syslog was flooded, 80-90% of logs were nothing but this message.
I read this is related to the Kernel not loading a module correctly. TBH i go lost after the second page of reading. What i found strange is if this is a Bug in the Kernel then why only a select few reporting this being such an integral componant. Does anyone know how to find the revision number to these routers?Same here. 20558 will have to do for now.
Small blips in wifi, impossible to track down in logs. My AX88U is acting as node and although the blips didn't affect too many clients, it was driving me crazy if I had something to do on its coverage. I could live with it but:
kernel: io:GET_GPIO: get val(1) from pa(32772), gpio_num_max=320 logs 4/seconds is the drop that filled the glass!
My syslog was flooded, 80-90% of logs were nothing but this message.
Just notice this to on remote logs but not local logs. Anyone can help too?Can someone tell why i am getting log spammed with gpio messages? or point me to a direction ?
Jan 7 16:12:26 kernel: io:GET_GPIO: get val(1) from pa(32772), gpio_num_max=320
Jan 7 16:12:26 kernel: io:GET_GPIO: get val(1) from pa(32795), gpio_num_max=320
Jan 7 16:12:26 kernel: io:GET_GPIO: get val(1) from pa(32799), gpio_num_max=320
Jan 7 16:12:26 kernel: io:GET_GPIO: get val(1) from pa(32797), gpio_num_max=320
that runs in loop continuedly after the update.
Thanks
Same issue here……Just notice this to on remote logs but not local logs. Anyone can help too?
Who said so?new vervion tomorrow?
There are others — GT-AXE16000, RT-AX58U (aka RT-AX3000), RT-AX82U, ...It's the only left to be updated to 3.0.0.4.388.22525, so he assumed will drop sooner or later.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!