It will be released this month
Hello Good day every one can somebody help me how i can fix the cpu problem..i build nss from hikarishi 24.10 but i notice when making a speed test one of the cpu getting 100 percent, and rmnet_nss is not initializing theres no nss context created in the log..can somebody give me an idea how to correct my nss build?
have you tried installing irqbalance?
Theres no irqbalance in my build sir, is that package need to be installed to work rmnet nss properly?
it can address overloading a single core
there has been some discussion of this error on the ROOter forum, Iām not certain of the resolution but if irqbalance doesnāt solve the problem (or if itās not available) you can ask on the forum - https://forums.whirlpool.net.au/thread/3vx1k1r3?p=1934
might be best not to mention youāre running an alternative fork
Thanks for the reply sir,what firmware you are using right now is there qmodem installed ?i build nss firmware from xhirashii with qmdem installed but my problem was tthe rment nss not initializing and there n NSS context created in the logā¦
Hi if Iām using a usb flashdrive for system files is it possible to use the expanded version or do I have to follow the boot interupt process?
Thanks for your time
ROOter has the fix embedded so you could try using that fork otherwise youāll have to ask on whirlpool or hope someone pops up here with a solution
@Chmod thank you for 5.8 release. Btw is it safe to keep settings from ver. 5.7?
Yes but It is best not to save settings in this release.
No, you cannot use the expanded version, even if a usb drive is plugged in. There are scripts that can do this without interrupting the boot process, but I donāt have.
I' ve just flashed v.5.8 and kept settings from 5.7. Everything is working fine so far. Even better - I can see received SMS' s. Thanks again for your efforts. Happy New 2026 Year.
Hello to everyone in this extremely helpful thread, particularly the developers of the community firmwares for the AW1000.
I have two Telstra branded AW1000 units - 1 with the standard Telstra firmware (0.06.01r), and the other one with the latest HikariWrt release. Iāve just finished the initial setup of the Hikari unit and have found that the speeds Iām getting on the 5G network are only about two thirds of what the stock Telstra unit is getting - ~ 350/40 for the Hikari, 525/90 for the Telstra.
Iām very close (~100m) to a 5G tower and noted that in the Telstra unit, the band it appears to be using is 78.
The band the Hikari unit was set to by default was 7 (was only getting 150/20 with that) so Iāve changed it exclusively to 78 for both the SA and NSA settings in the Lock Band section.
Iām hoping someone can direct me to some resources for learning more about the band locking/carrier aggregation settings in this firmware, or if you just have some suggestions of things to try to improve the speeds, Iām all ears!
Thanks,
Bill.
Hi Bill, not sure where in the world you are but thereās a very long thread hosted by the ROOter developer (author/maintainer or the bandlocking tools in hikari) thatās populated with some very knowledgable folks about the areas youāre seeking clarification on (ROOterās oriented to cellular broadband) ā https://forums.whirlpool.net.au/thread/3vx1k1r3?p=1945
Thanks 0jay, yes Iāve been there and got some great help from jhend and am now running the Rooter build for this unit very happily. I found that the behaviour of the band locking in the Hikari firmware wasnāt particularly consistent - selecting or deselecting bands didnāt seem to stick after a soft reboot, and in any case, given the limits of the speed available from our local cells (maxing out at around 600 Mb/s and more typically around 450Mb/s), the absence of NSS isnāt really a limiting factor for me. If the speeds available from towers around me changes I might revisit these NSS builds.
Hi everyone. So i build successfully nss image with wwan packages, and everthing is fine. NSS offload works, but i have a problem with LEDās. The power led doesnāt light up, i have 5g and mobile signal led white, and thatās it. Even on reboot they donāt work properly. Did anyone had a problem like that ?
Nevermind, i solved the problem by adding missing gpio kmods.




