I understand everything, thank you very much.
1 Like
Did anyone test kernel 6.6.59 already?
I've tftpbooted a testbuild and I'm facing lan issues.
I didn't investigate further (have not time right now). Does anyone have the same issue and can confirm the error?
[ 3.696478] ------------[ cut here ]------------
[ 3.700062] gcc_usb1_master_clk status stuck at 'on'
[ 3.700090] WARNING: CPU: 0 PID: 1 at drivers/clk/qcom/clk-branch.c:86 clk_branch_wait+0x114/0x124
[ 3.709619] Modules linked in:
[ 3.718376] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.6.59 #0
[ 3.721418] Hardware name: Zyxel NBG7815 (DT)
[ 3.727231] pstate: 604000c5 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 3.731750] pc : clk_branch_wait+0x114/0x124
[ 3.738515] lr : clk_branch_wait+0x114/0x124
[ 3.743030] sp : ffffffc082dbbc70
[ 3.747281] x29: ffffffc082dbbc70 x28: ffffffc080b400b0 x27: ffffffc080aeb0d0
[ 3.750500] x26: ffffffc080b32990 x25: 0000000000000011 x24: ffffffc080b96078
[ 3.757618] x23: ffffffc080a918d0 x22: 0000000000000000 x21: ffffffc08046fdc0
[ 3.764736] x20: 0000000000000000 x19: ffffffc082cfa148 x18: ffffffc082c6c2a8
[ 3.771855] x17: ffffffc082d02ca8 x16: 00000000ac908281 x15: 00000000000000c8
[ 3.778973] x14: 00000000000000c8 x13: 00000000ffffffea x12: ffffffc082cc4250
[ 3.786091] x11: ffffffc082c6c2a8 x10: ffffffc082cc42a8 x9 : 0000000000000001
[ 3.793209] x8 : 0000000000000001 x7 : 0000000000017fe8 x6 : c0000000ffffefff
[ 3.800327] x5 : 0000000000057fa8 x4 : 0000000000000000 x3 : ffffffc082dbba70
[ 3.807445] x2 : ffffffc082c6c1e8 x1 : ffffffc082c6c1e8 x0 : 0000000000000028
[ 3.814563] Call trace:
[ 3.821672] clk_branch_wait+0x114/0x124
[ 3.823931] clk_branch2_disable+0x2c/0x3c
[ 3.828097] clk_disable_unused_subtree+0x98/0xfc
[ 3.832005] clk_disable_unused_subtree+0x2c/0xfc
[ 3.836781] clk_disable_unused_subtree+0x2c/0xfc
[ 3.841468] clk_disable_unused_subtree+0x2c/0xfc
[ 3.846156] clk_disable_unused_subtree+0x2c/0xfc
[ 3.850842] clk_disable_unused+0x64/0x148
[ 3.855529] do_one_initcall+0x6c/0x1f8
[ 3.859521] kernel_init_freeable+0x208/0x2e8
[ 3.863254] kernel_init+0x2c/0x1e0
[ 3.867767] ret_from_fork+0x10/0x20
[ 3.871067] ---[ end trace 0000000000000000 ]---
[ 3.875211] ------------[ cut here ]------------
[ 3.879489] gcc_usb0_master_clk status stuck at 'on'
[ 3.879505] WARNING: CPU: 0 PID: 1 at drivers/clk/qcom/clk-branch.c:86 clk_branch_wait+0x114/0x124
[ 3.889045] Modules linked in:
[ 3.897803] CPU: 0 PID: 1 Comm: swapper/0 Tainted: G W 6.6.59 #0
[ 3.900849] Hardware name: Zyxel NBG7815 (DT)
[ 3.908395] pstate: 604000c5 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 3.912652] pc : clk_branch_wait+0x114/0x124
[ 3.919418] lr : clk_branch_wait+0x114/0x124
[ 3.923932] sp : ffffffc082dbbc70
[ 3.928184] x29: ffffffc082dbbc70 x28: ffffffc080b400b0 x27: ffffffc080aeb0d0
[ 3.931403] x26: ffffffc080b32990 x25: 0000000000000011 x24: ffffffc080b96078
[ 3.938521] x23: ffffffc080a91988 x22: 0000000000000000 x21: ffffffc08046fdc0
[ 3.945640] x20: 0000000000000000 x19: ffffffc082cfa4c8 x18: ffffffc082c6c2a8
[ 3.952758] x17: ffffffc082d02ca8 x16: 00000000ac908281 x15: 00000000000000ea
[ 3.959875] x14: 00000000000000ea x13: 00000000ffffffea x12: ffffffc082cc4250
[ 3.966993] x11: ffffffc082c6c2a8 x10: ffffffc082cc42a8 x9 : 0000000000000001
[ 3.974111] x8 : 0000000000000001 x7 : 0000000000017fe8 x6 : c0000000ffffefff
[ 3.981229] x5 : 0000000000057fa8 x4 : 0000000000000000 x3 : ffffffc082dbba70
[ 3.988347] x2 : ffffffc082c6c1e8 x1 : ffffffc082c6c1e8 x0 : 0000000000000028
[ 3.995466] Call trace:
[ 4.002574] clk_branch_wait+0x114/0x124
[ 4.004834] clk_branch2_disable+0x2c/0x3c
[ 4.009001] clk_disable_unused_subtree+0x98/0xfc
[ 4.012909] clk_disable_unused_subtree+0x2c/0xfc
[ 4.017683] clk_disable_unused_subtree+0x2c/0xfc
[ 4.022370] clk_disable_unused_subtree+0x2c/0xfc
[ 4.027058] clk_disable_unused_subtree+0x2c/0xfc
[ 4.031746] clk_disable_unused+0x64/0x148
[ 4.036431] do_one_initcall+0x6c/0x1f8
[ 4.040423] kernel_init_freeable+0x208/0x2e8
[ 4.044157] kernel_init+0x2c/0x1e0
[ 4.048670] ret_from_fork+0x10/0x�[ 4.067614] Freeing unused kernel memory: 33856K
I did, and no problem so far
1 Like
Ty, then the error is on my side. I'll do a clean build.
1 Like
Sorry for the lazy question but...i'm very lazy! 
I'm running my router with an "old" @asvio build.
I'd like to update to a newer NSS enabled buold but I miserably failed on building the image from source.
I know that its safer to build from source than loading a pre-build image from someone else, but given my lack of tech understanding I'd be unable to analyze the source code to find backdoors etc, so apart from building from official repo everything else is "unsecure" even if built from source.
Now the question: have someone a recent build with NSS and latest patches/fix for 160Mhz?
I have a FTTH 1G/300MB but I'm not facing any performance issue as my router usage is fairly basic (streaming, VPN and usual internet usage), so I'd update to keep the router current with fixes than performance improvements.
TY
@wrongisthenewright I can confirm 160Mhz works with the latest asvio build for AX but only for Channels below 100
@wrongisthenewright @schlund
160mhz also works on 100+ channels but you needs to wait 600 sec for dfs-scan. It is the same for factory firmware.
For 80mhz dfs-scan go down to 60 sec.
For 160mhz if you go to 36-64 channel dfs-scan is 60 sec because devices only need check 52-64 channels (80mhz). there is no need to check dfs on 36-48 channels.
1 Like
@asvio , @schlund,
Sorry English is not my native tongue so I haven’t been clear in my question.
Can someone provide me a mostly up-to date image for this router?
Features like nss offloading and 160mhz are welcome but not essentials.
I've upload a new nss image. I've not tested all stuff it has, but all essential thing is working fine. (lan, wifi, wan, vlan, samba, wireguard, adblock).
Normally there are no stability issues with the builds I test but I have to admit that I change them frequently and therefore I don't know how they work in the long term (more than 10 days without restarting them)
You can report if you detect any problem
Don't keep setting when sysupgrading from a previous nss image if you don`t know how to modify some parameters that have changed since my last nss build.
1 Like
I am really appreciated for you creating this build. I see its different to the builds that I create from your repository (40MB vs 20MB). May I ask you about your build settings?
Download config.buildinfo and copy It to your openwrt build dir.
Rename to .config and make defconfig
Make the build and voilà, you wil have the almost 40Mb build.
Hello! There is 200% interest in the implementation of the built-in fan) now I use the firmware from asvio in which the cooler simply turns on by 100% and makes noise like a vacuum cleaner. If you need tests, let me know, I'll do the tests)
I will test this version build in the coming months. Thank you for your work!
Hi, I installed the software version you added to my device. But I have a problem with speed. I have a 1000Mbs FTTH connection. The ISP's original router reaches speeds of 950Mbs. But I couldn't go over 750Mbs with Armor G5. It seems to be limited there. I tried both with Ethernet connection and over wifi. Do you have any suggestions?
Is your ISP using PPPOE for your connection?
If so, check this out:
I have pppoe ftth and can easily max out gigabit connection both ways on ethernet and wifi.
cheers
1 Like
Thank you for this trick. Yes my ISP using PPPOE for connection. I will try.
I'm a long time user of your builds, but with this last, installed 3 days ago, 3 days where several devices are not connected to the 5G 160Mhz wifi where I come home ... Google NestHub, Nvidia Shield, OP12, Denon amplifier... 2 devices stays online, My Nokia STB 8000 and my Yamaha amplifier.
No relevant logs, the last today are these on the concerned AP:
Fri Nov 15 13:53:09 2024 daemon.info hostapd: free_5G: STA 3c:8d:20:fe:43:44 IEEE 802.11: authenticated
Fri Nov 15 13:53:10 2024 daemon.info hostapd: free_5G: STA 3c:8d:20:fe:43:44 IEEE 802.11: authenticated
Fri Nov 15 13:53:19 2024 daemon.info hostapd: free_5G: STA 3c:8d:20:fe:43:44 IEEE 802.11: disconnected due to excessive missing ACKs
Fri Nov 15 13:53:19 2024 user.info usteer: station 3c:8d:20:fe:43:44 disconnected from node hostapd.free_5G
Fri Nov 15 13:53:49 2024 daemon.info hostapd: free_5G: STA 3c:8d:20:fe:43:44 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
This logs appears at 13:53, when I come home at 20:30, no log about the free_5G AP ... no error ... nothing
The last kernel log before wifi stopping :
[ 8172.046166] softirq: huh, entered softirq 3 NET_RX 00000000c1604313 with preempt_count 00000101, exited with 00000301?
[ 8172.046473] softirq: huh, entered softirq 3 NET_RX 00000000c1604313 with preempt_count 00000101, exited with 00000301?
I change the AP to 80Mhz to see if disconnections disapeers, the configuration is the same for months
I'll keep you in touch
Edit : I say that 2 devices stay connected, but I've not check their connectivity before restarting AP, just present in the Overview of OpenWrt
Edit 2 : Sorry, I miss a thing, I use ethtool to limit the rate of the 10G port to 5000Mbps since we are able to use the 160Mhz on wifi, this help the device to stay "fresh", but with this nss image, I can't do this anymore with my rc.local scipt
ethtool -s 10g speed 5000 duplex full autoneg on
1 Like
Thanks for the report.
What channel were you using?
Did you try to disable the usteer service?
I have the same disconnection problems with my old iPad on the 2.4g network
If possible, try to put channel 36 with 160mhz and disabling the usteer service.
If it works try your original channel without usteer.
Do you mean that you are no longer able to keep it "fresh" or that the ethtool function no longer works for you?
I understand the thing about keeping it "fresh".
Despite the long time waiting after restart, I use the channel 100, my wifi cover is better with this channel in my home.
Nothing to say about the 2.4G network, I have several olds devices (esp8266, old tablet to manage home assistant for the house ...) all working fine !
For the rc.local, the 10G port go down, just down 
and the device is hotter but no worries, the fan is here !
1 Like