I have an Archer C6v2 with OpenWRT 19.07.7 which was working fine for a few weeks. Yesterday I altered the channel for the 5Ghz (I think I set it to 150).
After this, the radio device was disabled and now reads Generic 802.11bg instead of the name of the chipset.
Here is the beginnin of my wireless config:
I noticed some options are missing from my 'radio0' device when compared to those of 'radio1'
I think I've solved it. I made a backup of my config & flashed the firmware again - overwriting the current settings. After this, my 5Ghz radio was working again. I restored my settings and then I switched the firmware for my QCA9888 chip as proposed in this topic (initially I had problems with my 2.4Ghz radio). After reboot I got the same problem.
I reflashed the firmware & restored settings but this time I didn't alter the firmware & now everything (also the 2.4Ghz) seems to be working fine. Let's hope this remains the case.
After second thought, I don't think switching firmware for my QCA9888 chip would really make any difference for my 2.4Ghz, as this chipset only handles 5Ghz if I'm not mistaken?
OK thanks for clarifying this - I did receive this error again right after flashing it again so indeed it not real error.
I meant it was somewhere in the 150's, could be 151, 153...
Either way, I was a bit too optimistic yesterday. After some time of use the problems with my 2.4Ghz wifi started to pop up again (random disconnects - SSID disapearing...).
I guess my initial problem appeared because I didn't restart the 5Ghz after installing the new firmware, which did happen now after changing the channel.
So that has been solved, but still looking to get my 2.4Ghz stable. I cannot find another firmware for the QCA9563 present in my Archer C6 at first sight, is that correct.
Also, are there additional steps necessary to activate the new firmware after installing it?
The C6v2 EU/RU is a 8/128MB device and supports 19.07.7
The C6v2 US is 16/128MB and is on snapshot.
You are saying you are on 19.07.7 = you have the EU/RU device which is 8/128MB.
I don't know if that device has enough NAND memory to handle bigger more comprehensive packages. Check the status-->overview page in LuCI to see how much free memory you have. These upgrades don't use very much memory so if you have 1-2MB left you should be okay.
I like to upgrade wpad-basic to wpad or wpad-openssl
same for dnsmasq to dnsmasq-full
Also you could try different wifi drivers. Type "ath10k" at the "system-->software-->filter" prompt and update it to see all the different packages.
I tried to do a quick search on the C6 to see if the "kmod-ath10k-ct-smallbuffers" would help but didn't see anything. That could be worth a try.
Similarly you could try the ct version of the other drivers or vice versa.
If none of that works and barring any other tips then offhand I would say maybe something on the device itself is flaking out - perhaps the radio or the NAND flash.
Since the log output is complaining so much about ath10k (-2 errors notwithstanding) I would try swapping in different drivers after upgrading wpad and dnsmasq. Or vice versa. Or just one or the other.
I've thinkered with my wifi radio but haven't found a real solution, my 2.4Ghz radio keeps disconnecting from time to time.
This is what I've tried:
Installed wpad instead of wpad-basic (I've skipped dnsmasq-full as this is a dump AP so this isn't in use I guess)
Using different ath10k drivers like ath10k-firmware-qca9887ath10k-firmware-qca9888-ct-httath10k-firmware-qca988xath10k-firmware-qca988x-ct ... and accompanying kmod drivers (I also tried the kmod-ath10k-ct-smallbuffers drivers). This doesn't make any difference. The strange thing is that when I reboot my AP, my 5Ghz won't work (the same problem as in my first post; Generic 802.11bg instead of my chipset name and device disabled message).
What is even more strange is that when I re-install the original drivers ( ath10k-firmware-qca9888-ct & kmod-ath10k-ct and after rebooting the AP again my radio still isn't working. The only thing I can do to make it work again is to re-flash OpenWRT to it.
I also flashed OpenWRT 21.02 RC3 to it. The first thing I've noticed is that under wireless my 2.4Ghz radio had it's chipset name next to it (in 19.07 it's just named `Generic 802.11bgn'). But when connecting to it, it actually performs worse after only some minutes I get disconnected for a minute (in 19.07 this only happens 2-3 times an hour).
So for now I don't have much options I guess. Maybe waiting for a stable release of 21.02 and see what is what? For now, it's not a huge deal as 90% of my devices has 5Ghz wifi and so don't get this problem, but it would be nice to have flawless 2.4Ghz as well
There are additionally more subtle reasons as well, clients take their own regulatory settings from the environment - a mis-configured AP can create quite some havoc in your immediate neighbourhood (forcing clients into a restricted emergency mode); aside from the legal implications of using restricted frequencies or disturbing military- and civilian weather radars.