What's new

[Alpha]386.8 Build

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

bluepoint

Very Senior Member
RT-AX88U's initial test looks good and function properly except for the 2.4 GHz temp status.
rt-ax88u1.jpg
 
Ha, I didn’t notice that. Same here.
The extent channel is also wrong. That's because the GT-AXE16000 does not have the radios in the same order as all other models, wl3 is the 2.4 GHz instead of wl0. That required me to rewrite the backend code dealing with temperature and extent channel polling from the radios, and that introduced a few minor bugs for other models.
 
Applied alpha1 (dirty over 386.7_2) on node and it´s working: all wlan clients reconnected.
Will deliver alpha1 to meshrouter at weekend.
 
GT-AXE16000-did a clean install over ASUSWRT firmware (stock) with no issues and as RMerlin pointed out the 2.4 GHz temp reports correctly. No abnormalities, to include VPN (Express VPN) client and director, detected so far. Thanks RMerlin!
 
Installed on my RT-AX88U (on top of 386.7_2) with 2x RT-AX86U mesh nodes running 3.0.0.4.386_49599. I removed and re-added the nodes to give them a factory reset and then rebooted the entire system. All looking good after waiting quite a while for DFS to finish checking my 5Ghz channels (I use ch 128 at 80Mhz).

The only noted problem so far is the mis-reporting of WiFi radio temps as previously noted.

WiFi performance seems to be nice and smooth. My nodes have run well for a few days on stock previously but it seems the new drivers for the RT-AX88U are an improvement.
 
I installed the alpha software with family permission. Router works without errors. Node, bridge and all clients are reconnected. OVPN via IPv6 is stable. All IOT devices online.
 
Last edited:
24h.JPG


After 24 hours everything smooth. All IOT devices and bridge continuously connected. VPN absolutely stable.

GREAT WORK @RMerlin !
 
I just installed it. on my AX88, took a long time to startup. Seems good. speeds are back up again. So for now it seems good. No wifi drops.
 
I see my Guest wifi-(2.4Ghz) rebooted after 22hrs into flashing this alpha, 5Ghz channel is still going strong
 
I see my Guest wifi-(2.4Ghz) rebooted after 22hrs into flashing this alpha, 5Ghz channel is still going strong
Which Guest Network stopped? I´ve got my IOT devices stable on guestnet 1

Found this in System Log:

Jul 29 19:06:14 kernel: CPU: 3 PID: 12172 Comm: roamast Tainted: P O 4.1.51 #2
Jul 29 19:06:14 kernel: Hardware name: Broadcom-v8A (DT)
Jul 29 19:06:14 kernel: task: ffffffc032aa2a80 ti: ffffffc02bca4000 task.ti: ffffffc02bca4000
Jul 29 19:06:14 kernel: PC is at 0xf6d3f6a4
Jul 29 19:06:14 kernel: LR is at 0xf6d0b858
Jul 29 19:06:14 kernel: pc : [<00000000f6d3f6a4>] lr : [<00000000f6d0b858>] pstate: 60000030
Jul 29 19:06:14 kernel: sp : 00000000f6cc7cb0
Jul 29 19:06:14 kernel: x12: 00000000ffffffff
Jul 29 19:06:14 kernel: x11: 00000000f6cc81ac x10: 0000000000000000
Jul 29 19:06:14 kernel: x9 : 00000000f6e057a8 x8 : 00000000f6e07000
Jul 29 19:06:14 kernel: x7 : 00000000f6cc9920 x6 : 0000000000000021
Jul 29 19:06:14 kernel: x5 : 00000000001b96a1 x4 : 0000000000000000
Jul 29 19:06:14 kernel: x3 : 0000000000000000 x2 : 0000000000000001
Jul 29 19:06:14 kernel: x1 : 00000000000000d0 x0 : 00000000fffffff8
Jul 29 20:12:25 kernel: CPU: 0 PID: 27931 Comm: roamast Tainted: P O 4.1.51 #2
Jul 29 20:12:25 kernel: Hardware name: Broadcom-v8A (DT)
Jul 29 20:12:25 kernel: task: ffffffc032a45580 ti: ffffffc013dd0000 task.ti: ffffffc013dd0000
Jul 29 20:12:25 kernel: PC is at 0xf6bf372e
Jul 29 20:12:25 kernel: LR is at 0xf6bbf858
Jul 29 20:12:25 kernel: pc : [<00000000f6bf372e>] lr : [<00000000f6bbf858>] pstate: 20000030
Jul 29 20:12:25 kernel: sp : 00000000f6b7bcb0
Jul 29 20:12:25 kernel: x12: 00000000ffffffff
Jul 29 20:12:25 kernel: x11: 00000000f6b7c1ac x10: 0000000000000000
Jul 29 20:12:25 kernel: x9 : 00000000f6cb97a8 x8 : 00000000f6cbb000
Jul 29 20:12:25 kernel: x7 : 00000000f6b7d920 x6 : 0000000000000021
Jul 29 20:12:25 kernel: x5 : 00000000001b96a1 x4 : 0000000000000004
Jul 29 20:12:25 kernel: x3 : 0000000000000000 x2 : 0000000000000001
Jul 29 20:12:25 kernel: x1 : 00000000000000e8 x0 : 00000000000000ec

Something to worry about?

Loglevel is notice -- notice
Should I change this?
 
Which Guest Network stopped? I´ve got my IOT devices stable on guestnet 1

Found this in System Log:

Jul 29 19:06:14 kernel: CPU: 3 PID: 12172 Comm: roamast Tainted: P O 4.1.51 #2
Jul 29 19:06:14 kernel: Hardware name: Broadcom-v8A (DT)
Jul 29 19:06:14 kernel: task: ffffffc032aa2a80 ti: ffffffc02bca4000 task.ti: ffffffc02bca4000
Jul 29 19:06:14 kernel: PC is at 0xf6d3f6a4
Jul 29 19:06:14 kernel: LR is at 0xf6d0b858
Jul 29 19:06:14 kernel: pc : [<00000000f6d3f6a4>] lr : [<00000000f6d0b858>] pstate: 60000030
Jul 29 19:06:14 kernel: sp : 00000000f6cc7cb0
Jul 29 19:06:14 kernel: x12: 00000000ffffffff
Jul 29 19:06:14 kernel: x11: 00000000f6cc81ac x10: 0000000000000000
Jul 29 19:06:14 kernel: x9 : 00000000f6e057a8 x8 : 00000000f6e07000
Jul 29 19:06:14 kernel: x7 : 00000000f6cc9920 x6 : 0000000000000021
Jul 29 19:06:14 kernel: x5 : 00000000001b96a1 x4 : 0000000000000000
Jul 29 19:06:14 kernel: x3 : 0000000000000000 x2 : 0000000000000001
Jul 29 19:06:14 kernel: x1 : 00000000000000d0 x0 : 00000000fffffff8
Jul 29 20:12:25 kernel: CPU: 0 PID: 27931 Comm: roamast Tainted: P O 4.1.51 #2
Jul 29 20:12:25 kernel: Hardware name: Broadcom-v8A (DT)
Jul 29 20:12:25 kernel: task: ffffffc032a45580 ti: ffffffc013dd0000 task.ti: ffffffc013dd0000
Jul 29 20:12:25 kernel: PC is at 0xf6bf372e
Jul 29 20:12:25 kernel: LR is at 0xf6bbf858
Jul 29 20:12:25 kernel: pc : [<00000000f6bf372e>] lr : [<00000000f6bbf858>] pstate: 20000030
Jul 29 20:12:25 kernel: sp : 00000000f6b7bcb0
Jul 29 20:12:25 kernel: x12: 00000000ffffffff
Jul 29 20:12:25 kernel: x11: 00000000f6b7c1ac x10: 0000000000000000
Jul 29 20:12:25 kernel: x9 : 00000000f6cb97a8 x8 : 00000000f6cbb000
Jul 29 20:12:25 kernel: x7 : 00000000f6b7d920 x6 : 0000000000000021
Jul 29 20:12:25 kernel: x5 : 00000000001b96a1 x4 : 0000000000000004
Jul 29 20:12:25 kernel: x3 : 0000000000000000 x2 : 0000000000000001
Jul 29 20:12:25 kernel: x1 : 00000000000000e8 x0 : 00000000000000ec

Something to worry about?

Loglevel is notice -- notice
Should I change this?
That message also appears in 386.7_2. Probably related to Trend Micro and this error:
Code:
Jul 29 14:57:07 kernel: potentially unexpected fatal signal 11.
 
“Roamast“ might be roam assist?
Dunno, above my pay grade.
The only “tainted” error I see is “Dcd” a known product of interaction between Pixelserv & Aiprotect. I ignore it.
Which Guest Network stopped? I´ve got my IOT devices stable on guestnet 1

Found this in System Log:

Jul 29 19:06:14 kernel: CPU: 3 PID: 12172 Comm: roamast Tainted: P O 4.1.51 #2
Jul 29 19:06:14 kernel: Hardware name: Broadcom-v8A (DT)
Jul 29 19:06:14 kernel: task: ffffffc032aa2a80 ti: ffffffc02bca4000 task.ti: ffffffc02bca4000
Jul 29 19:06:14 kernel: PC is at 0xf6d3f6a4
Jul 29 19:06:14 kernel: LR is at 0xf6d0b858
Jul 29 19:06:14 kernel: pc : [<00000000f6d3f6a4>] lr : [<00000000f6d0b858>] pstate: 60000030
Jul 29 19:06:14 kernel: sp : 00000000f6cc7cb0
Jul 29 19:06:14 kernel: x12: 00000000ffffffff
Jul 29 19:06:14 kernel: x11: 00000000f6cc81ac x10: 0000000000000000
Jul 29 19:06:14 kernel: x9 : 00000000f6e057a8 x8 : 00000000f6e07000
Jul 29 19:06:14 kernel: x7 : 00000000f6cc9920 x6 : 0000000000000021
Jul 29 19:06:14 kernel: x5 : 00000000001b96a1 x4 : 0000000000000000
Jul 29 19:06:14 kernel: x3 : 0000000000000000 x2 : 0000000000000001
Jul 29 19:06:14 kernel: x1 : 00000000000000d0 x0 : 00000000fffffff8
Jul 29 20:12:25 kernel: CPU: 0 PID: 27931 Comm: roamast Tainted: P O 4.1.51 #2
Jul 29 20:12:25 kernel: Hardware name: Broadcom-v8A (DT)
Jul 29 20:12:25 kernel: task: ffffffc032a45580 ti: ffffffc013dd0000 task.ti: ffffffc013dd0000
Jul 29 20:12:25 kernel: PC is at 0xf6bf372e
Jul 29 20:12:25 kernel: LR is at 0xf6bbf858
Jul 29 20:12:25 kernel: pc : [<00000000f6bf372e>] lr : [<00000000f6bbf858>] pstate: 20000030
Jul 29 20:12:25 kernel: sp : 00000000f6b7bcb0
Jul 29 20:12:25 kernel: x12: 00000000ffffffff
Jul 29 20:12:25 kernel: x11: 00000000f6b7c1ac x10: 0000000000000000
Jul 29 20:12:25 kernel: x9 : 00000000f6cb97a8 x8 : 00000000f6cbb000
Jul 29 20:12:25 kernel: x7 : 00000000f6b7d920 x6 : 0000000000000021
Jul 29 20:12:25 kernel: x5 : 00000000001b96a1 x4 : 0000000000000004
Jul 29 20:12:25 kernel: x3 : 0000000000000000 x2 : 0000000000000001
Jul 29 20:12:25 kernel: x1 : 00000000000000e8 x0 : 00000000000000ec

Something to worry about?

Loglevel is notice -- notice
Should I change this?
 
Installed on two axe16000 in aimesh configuration. No problems running pretty smooth all clients connected ok.
Same setup, everything's been smooth so far. There were a couple of devices that couldn't connect to wifi for some reason, but after a reset no complaints.
 
Installed dirty updated [Alpha]386.8 build (posted 2 hours ago as of this post)-no problems so far.
 
Installed dirty updated [Alpha]386.8 build (posted 2 hours ago as of this post)-no problems so far.
I think it would be good to mention your model of router - perhaps you may add a signature?
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top