Ha, I didn’t notice that. Same here.RT-AX88U's initial test looks good and function properly except for the 2.4 GHz temp status.
View attachment 43136
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.Ha, I didn’t notice that. Same here.
Ditto, log is looking very clean24+ hours here, nothing to report.
Which Guest Network stopped? I´ve got my IOT devices stable on guestnet 1I see my Guest wifi-(2.4Ghz) rebooted after 22hrs into flashing this alpha, 5Ghz channel is still going strong
That message also appears in 386.7_2. Probably related to Trend Micro and this error: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?
Jul 29 14:57:07 kernel: potentially unexpected fatal signal 11.
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?
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 on two axe16000 in aimesh configuration. No problems running pretty smooth all clients connected ok.
I think it would be good to mention your model of router - perhaps you may add a signature?Installed dirty updated [Alpha]386.8 build (posted 2 hours ago as of this post)-no problems so far.
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!