What's new

AX 86u getting weird errors in logs

  • 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!

tilliks

Occasional Visitor
Hello,

I have an ax86u with the current merlin firmware. My internet has been weird, and I wonder if this error log is the issue. discord keeps disconnecting and reconnecting, battle.net client keeps disconnecting, resulting in me unable to play games on it. If i am playing an FPS, while using discord to communicate with friends, the game itself is running smooth, but my discord just keeps disconnecting and reconnecting right away.

Apr 12 15:17:21 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xe832 (36/160)
Apr 12 15:17:21 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xe832 (36/160)
Apr 12 15:17:21 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xe832 (36/160)
Apr 12 15:17:21 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xe932 (40/160)
Apr 12 15:17:21 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xe932 (40/160)
Apr 12 15:17:21 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xe932 (40/160)
Apr 12 15:17:21 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xea32 (44/160)
Apr 12 15:17:21 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xea32 (44/160)
Apr 12 15:17:21 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xea32 (44/160)
Apr 12 15:17:21 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xeb32 (48/160)
Apr 12 15:17:21 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xeb32 (48/160)
Apr 12 15:17:21 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xeb32 (48/160)

I am not well versed in these type of things. Can someone help me what this means?
 
 
Hello,

I have an ax86u with the current merlin firmware. My internet has been weird, and I wonder if this error log is the issue. discord keeps disconnecting and reconnecting, battle.net client keeps disconnecting, resulting in me unable to play games on it. If i am playing an FPS, while using discord to communicate with friends, the game itself is running smooth, but my discord just keeps disconnecting and reconnecting right away.

Apr 12 15:17:21 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xe832 (36/160)
Apr 12 15:17:21 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xe832 (36/160)
Apr 12 15:17:21 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xe832 (36/160)
Apr 12 15:17:21 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xe932 (40/160)
Apr 12 15:17:21 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xe932 (40/160)
Apr 12 15:17:21 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xe932 (40/160)
Apr 12 15:17:21 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xea32 (44/160)
Apr 12 15:17:21 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xea32 (44/160)
Apr 12 15:17:21 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xea32 (44/160)
Apr 12 15:17:21 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xeb32 (48/160)
Apr 12 15:17:21 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xeb32 (48/160)
Apr 12 15:17:21 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xeb32 (48/160)

I am not well versed in these type of things. Can someone help me what this means?
@tilliks

I also have an RT AX86U router with recently loaded Merlin firmware. I am getting these same errors in my system log and erratic connection issues, similar to those you describe. I don't game, but my VoIP connection and streaming TV connections are dropping and buffering in similar time periods as the errors.
Did you ever receive any input or determine the root cause?
 
I too used to get these errors until i learnt what it is.

What I did was to get an app (WiFi Analyzer on Windows) and see which channel is best for each bands. If you have 2.4Ghz set at 20/40MHz, you will get these chanspec logs. Set 2.4Ghz either to 20MHz only or 40MHz only depending on your clients connecting to this WiFi, and find set a channel according to the app if you have it, or by setting it to none overlapping channels (1,6,11). Same with 5Ghz WiFi but I have it set at 20/40/80/160Mhz with control channel 52. And I don’t have these logs anymore.

For me it was trial and error to find what’s the best channel in my area with lots of flats/buildings around. Can’t even get 5G signal on my phone.

Was quite fun reading about WiFi frequencies. But best to set control channel rather than auto. Thread '[GUIDE] Troubleshooting wifi issues'
 
Most WiFi Analyzer apps don't show you available bandwidth. Not good for best channel selection. They only show how many APs around are tuned to specific channels. A channel with one only AP may be the worst one. The app also shows what on-device Wi-Fi controller sees around, not the router.
 
Most WiFi Analyzer apps don't show you available bandwidth. Not good for best channel selection. They only show how many APs around are tuned to specific channels. A channel with one only AP may be the worst one. The app also shows what on-device Wi-Fi controller sees around, not the router.
Too bad WinFI is already dead...
 
Nice to know, considering the author didn't even reply when I tried to reach out to him a few months ago asking if the project was dead or not.

Hopefully this new build no longer has a timebomb. I was using a batch file to work around the timebomb.
WinFI 1.0.22.12 expired again on 1st April 2023. No updated version available for download yet.
 
WinFI 1.0.22.12 expired again on 1st April 2023. No updated version available for download yet.
Guess I better keep my launch batchfile around...
 

Similar threads

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