V 3.4 did not fix a thing for me… CT firmware crashing constantly. Again, I had to revert to a non-CT firmware and live on with everyday updater collision errors but also with working wifi. When is this going to get fixed? It’s already gotten highly annoying…
2016-12-26T11:23:00+01:00 warning kernel[]: [326793.312883] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon
2016-12-26T11:23:00+01:00 warning kernel[]: [326793.415280] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon
2016-12-26T11:23:00+01:00 warning kernel[]: [326793.517671] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon
2016-12-26T11:23:00+01:00 warning kernel[]: [326793.620071] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon
2016-12-26T11:23:01+01:00 warning kernel[]: [326793.722472] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon
2016-12-26T11:23:01+01:00 debug kernel[]: [326793.820072] ath10k_pci 0000:02:00.0: ath10k_pci ATH10K_DBG_BUFFER:
2016-12-26T11:23:01+01:00 debug kernel[]: [326793.820079] ath10k: [0000]: 03F277AF 0BFC4C20 0000000A 0000000B 03F277C4 0BFC4C20 0000000A 0000000B
2016-12-26T11:23:01+01:00 debug kernel[]: [326793.820084] ath10k: [0008]: 03F277D8 0BFC4C20 0000000A 0000000B 03F277ED 0BFC4C20 0000000A 0000000B
2016-12-26T11:23:01+01:00 debug kernel[]: [326793.820090] ath10k: [0016]: 03F27801 0BFC4C20 0000000A 0000000B 03F27818 0BFC4C20 0000000A 0000000B
2016-12-26T11:23:01+01:00 debug kernel[]: [326793.820094] ath10k_pci 0000:02:00.0: ATH10K_END
2016-12-26T11:23:01+01:00 warning kernel[]: [326793.824865] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon
2016-12-26T11:23:01+01:00 warning kernel[]: [326793.927264] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon
2016-12-26T11:23:01+01:00 warning kernel[]: [326794.029661] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon
2016-12-26T11:23:01+01:00 err kernel[]: [326794.030065] ath10k_pci 0000:02:00.0: Cannot communicate with firmware, attempting to fake crash and restart firmware.
2016-12-26T11:23:01+01:00 err kernel[]: [326794.040814] ath10k_pci 0000:02:00.0: firmware crashed! (uuid n/a)
2016-12-26T11:23:01+01:00 info kernel[]: [326794.047024] ath10k_pci 0000:02:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
2016-12-26T11:23:01+01:00 info kernel[]: [326794.047030] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 1 testmode 0
2016-12-26T11:23:01+01:00 info kernel[]: [326794.048232] ath10k_pci 0000:02:00.0: firmware ver 10.1.467-ct-_fW- 018-3d8c23b api 2 features wmi-10.x,has-wmi-mgmt-tx,txstatus-noack,wmi-10.x-CT,ratemask-CT,regdump-CT,txrate-CT, flush-all-CT,pingpong-CT,ch-regs-CT,nop-CT,set-special-CT crc32 0920f3f9
2016-12-26T11:23:01+01:00 info kernel[]: [326794.048250] ath10k_pci 0000:02:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
2016-12-26T11:23:01+01:00 info kernel[]: [326794.048257] ath10k_pci 0000:02:00.0: htt-ver 2.1 wmi-op 2 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1
2016-12-26T11:23:01+01:00 err kernel[]: [326794.050292] ath10k_pci 0000:02:00.0: firmware register dump:
2016-12-26T11:23:01+01:00 err kernel[]: [326794.056056] ath10k_pci 0000:02:00.0: [00]: 0x00940750 0x00400C00 0x00980000 0x009B5A94
2016-12-26T11:23:01+01:00 err kernel[]: [326794.064099] ath10k_pci 0000:02:00.0: [04]: 0x009B5B04 0x009B5C28 0x00941B6C 0x00941B20
Yes, I read all posts. However, updater does not work in case of found collision. So, manual firmware change is needed in order not to get stuck with not working wifi. And again when new Omnia fw is out in order to be able to update. Which - in my eyes - is indeed annoying. So please stop reproving your rightfully complaining customers and provide the fix. Thank you and Merry Christmas
Man, maybe it seems like I’m part of Turris team (and you’re second who told me this), but I’m not.
Also I would prefer better forum system than Discourse, but I don’t think that it will gonna happen.
OK. We can be upset of many bugs, which are presented on Omnia and even on Turris 1.x (where all of us are under contract), but we also expect to get support for device, which cost nearly 300€, right?
They’re small team, I understand that, but they did fault, when they don’t communicate about theirs problem.
Hopefully they will get through it soon and they will start responding to our issues here on forum.
Meanwhile I have solution for you.
Switch to nightly branch and you will be covered, when there will be released TurrisOS 3.5 you can get back to stable branch. (and you won’t get email about collisions)
If you read it, you should see two posts, because they’re saying that TurrisOS will be switched again back to non-ct firmware. Unfortunately it will be included on TurrisOS 3.5, which is planned of course after New Year.
Surely you will get notification from your router (by email if you setup it correctly), you will see it it on this forum and also on Reddit. and also me and others people who bought Omnia are also on IRC #turris on freenode (with some Turris developers, too )
[details=Summary]Also many posts here are also complaining about collisions, when theyswitched it to non-CT firmware.
Maybe I was rude, sorry for that, but I can see: my post 137 where I said there was removed kmod-ath10k-ct (and link goes to their Gitlab), post 136, where he said that he received also collision. post 131 where he said that the next update of TurrisOS will be switch back to regular ath10k, post 129 reacting to post 127 about collisions.[/details]
So don’t tell me that you don’t read previous posts and also you could use search function. Sorry, but when everyone will do the same like you, when this forum isn’t really moderated then things will go bad.
Right. I guess I just had to express my imminent frustration having had my old folks visiting me today and felt so stupid finding out that crappy wifi was down again.
Sorry for the staff confusion and subsequent pissed reaction, don’t know why I had that feeling you were “one of 'em”
Had indeed read everything but haven’t found any serious solution - switching to nightly is just a workaround needed to be remembered of when switching back to stable in the future. Look at the length of this thread, this thing is serious, while the support team does what? I don’t feel like they are on the same page as for understanding the awkwardness of us - the backers - even having to undergo such ludicrous situations. Have they had for a real QA, things like this should never have happened. As you have stated, considering the price of the box, one would expect support on a whole different level.
Hopefully we all get there once but as for now, I feel more like a Guinea pig.
Cheers and no hard feelings
it produced very stable on the 5GHz wifi at my place (up and error free for 4.5 days now with 10+ android devices/windows laptops/smart tv, chromecast, ios devices)
tx rate is reported as 6mbps due to firmware limitation (no tx rate information in tx completions); instead see /sys/kernel/debug/ieee80211/phyX/ath10k/fw_stats , en:users:drivers:ath10k5 [Linux Wireless]
Just to say me too. Pretty much default config Omnia.
5GHz was capped to 25Mbit, no matter what. No packet loss or stability issues in either. 2.4GHz did not have this limit. Switched to master branch now and limit on 5GHz vanished, still no packet loss. Will see about stability. Thanks!
ok, switching to nightly (and then back to master) solved this specific problem for me as well. Unfortunately, the 5ghz wifi is still unusable since as soon as there is any half-serious load on it, I get a disconnects, see Very unstable WiFi
mozna tu nekdy nekdo ma/mel problemy s kartou Qualcomm Atheros QCA9880 ktera je soucasti balicku - musite nainstalovat firmware z balicku ath10k-firmware-qca988x smazat /etc/config/wireless a rebootovat
