Can't even get my 5Ghz to come up on 21.02, so something's defo up.
It comes nicely up for me.
Check your settings, try first some basic simple wifi settings e.g. channel 36, width 40
(Note that there are no build specific WiFi settings in my build, so the possible issue should likely touch pretty widely the ath10k user space)
An update-it seems to work fine with those settings but it appears DFS is failing to initialize for.....some reason.
edit: and by that I mean
daemon.err hostapd: DFS start_dfs_cac() failed, -1
daemon.err hostapd: Interface initialization failed
Those DFS issues have been noticed already earlier. Possibly the semi-recent upgrades in ath10k-ct and/or mac80211 have caused something.
1 Like
Well, that would explain it. RIP.
I'll live.
@hnyman so, how do I go from 19.07 to 21.02? Normally via sysupgrade.bin file or...? I'd also like to keep my settings. 
Yes, quite normal sysupgrade.
Like I said yesterday, about 15 messages up...
2 Likes
@hnyman, I just installed the latest master (master-r15980-cc2d61edc3-20210226).
It ruined my iOS WiFi (slow, laggy, unresponsive).
Since you said your firmwares only come with the -ct variant, I manually installed the ath10k mainline.
Was this the correct way to do it:
- Install the actual firmware
- Upload the ath10k driver to /tmp via scp
- remove the -ct variant:
opkg remove kmod-ath10k-ct
opkg install /tmp/ath10k-blabla*.ipk
reboot
I'm asking because of this part:
"Note that both mainline and -ct havealso corresponding wifi "firmware" blobs that can be downloaded via opkg (after opkg update). They can / need to be installed separately from the driver itself. The blobs should be compatible, so it should be possible to also use the blob from the other variant. I haven't much played with them."
Typing "ath10k" in the Software part lists a bunch of "ath10k" files. Anything else I need installed via opkg after the mainline ath10k installation described above?
Thanks, and sorry in advance, I'm not an expert with driver changes... 
I.
That looks correct for the driver itself.
The separate WiFi firmware blobs are in
https://downloads.openwrt.org/snapshots/packages/arm_cortex-a15_neon-vfpv4/base/
Three -ct variants and one mainline for the QCA9984 WiFi chip that is in R7800
|ath10k-firmware-qca9984-ct-full-htt_2020-11-08-1_arm_cortex-a15_neon-vfpv4.ipk|457.9 KB|Sat Feb 27 08:43:48 2021|
|ath10k-firmware-qca9984-ct-htt_2020-11-08-1_arm_cortex-a15_neon-vfpv4.ipk|396.6 KB|Sat Feb 27 08:43:50 2021|
|ath10k-firmware-qca9984-ct_2020-11-08-1_arm_cortex-a15_neon-vfpv4.ipk|458.0 KB|Sat Feb 27 08:43:47 2021|
|ath10k-firmware-qca9984_20201118-3_arm_cortex-a15_neon-vfpv4.ipk|506.4 KB|Sat Feb 27 07:58:06 2021|
root@sh0dan:/tmp# opkg install /tmp/ath10k-firmware-qca9984_20201118-3_arm_corte
x-a15_neon-vfpv4.ipk
Installing ath10k-firmware-qca9984 (20201118-3) to root...
Downloading https://downloads.openwrt.org/snapshots/packages/arm_cortex-a15_neon -vfpv4/base/ath10k-firmware-qca9984_20201118-3_arm_cortex-a15_neon-vfpv4.ipk
Collected errors:
* check_data_file_clashes: Package ath10k-firmware-qca9984 wants to install fil e /lib/firmware/ath10k/QCA9984/hw1.0/firmware-5.bin
But that file is already provided by package * ath10k-firmware-qca9984- ct
* opkg_install_cmd: Cannot install package ath10k-firmware-qca9984.
um...it's already installed? O_o
Or am I doing something wrong?
You need to first opkg remove the -ct blob
(Opkg complains to you that you want to overwrite it with a file from another package)
OK. Did that, too.
I hope everything works now.
Btw. you should see the full version number loaded into your WLAN cards in dmesg after rebooting, e.g.:
ath10k_pci 0000:01:00.0: qca9984/qca9994 hw1.0 target 0x01000000 chip_id 0x00000000 sub 168c:cafe
ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
ath10k_pci 0000:01:00.0: firmware ver 10.4-3.9.0.2-00139 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate crc32 84f36f58
ath10k_pci 0000:01:00.0: board_file api 2 bmi_id 0:1 crc32 85498734
ath10k_pci 0000:01:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal pre-cal-file max-sta 512 raw 0 hwcrypto 1
1 Like
Been on master up until recently so i just sysupgraded every time i wanted to update the base,curious if now that i'm on the 21.02 branch its safe to just run a full update from opkg or if i should sysupgrade again to your build today.
edit: there is no build today, misread, but more of a general question i suppose
There is no safe "full update" with opkg.
Opkg is only suitable for upgrading selected individual packages. It can't upgrade kernel, and there are difficulties with low-level system packages.
Just use sysupgrade every now and then.
1 Like
Test-DSA-kernel510-master-r16135-7e7218d133-20210307
I have compiled a test version with kernel 5.10 and DSA switch config.
That is based on commits from @Ansuel in PR
https://github.com/openwrt/openwrt/pull/3954
Discussion and advice at
[WIP] [PR] ipq806x: kernel 5.10 bump code propose
I have been running 5.10 with DSA for a day, and so far no problems.
4 Likes
Hi hnyman,
does it mean you are going to use in your builds the code for NSS made by Ansuel (and others)?!? Uh hu!!! What a happy news!
nope... dsa is not nss 
it's just new kernel with new upstream driver
What has to be changed in config for using DSA? I'm only using VLAN on WAN for internet access.
all references to the hardware interfaces: eth0 eth1 eth.2 etc.
- wan interface is not eth0.2, but just "wan".
- lan is directly the 4 ports as 'lan1 lan2 lan3 lan4'
With default settings, only this change in the network config itself:
root@router1:~# diff -u /etc/config/network.normal /etc/config/network.hannu510
--- /etc/config/network.normal
+++ /etc/config/network.hannu510
@@ -10,35 +10,20 @@
config interface 'lan'
option type 'bridge'
- option ifname 'eth1.1'
+ option ifname 'lan1 lan2 lan3 lan4'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
config interface 'wan'
- option ifname 'eth0.2'
+ option ifname 'wan'
option proto 'dhcp'
config interface 'wan6'
- option ifname 'eth0.2'
+ option ifname 'wan'
option proto 'dhcpv6'
-config switch
- option name 'switch0'
- option reset '1'
- option enable_vlan '1'
-
-config switch_vlan
- option device 'switch0'
- option vlan '1'
- option ports '1 2 3 4 6t'
-
-config switch_vlan
- option device 'switch0'
- option vlan '2'
- option ports '5 0t'
-
config interface 'henet'
option proto '6in4'
option mtu '1424'
And the wan LED config:
root@router1:~# diff -u /etc/config/system.normal /etc/config/system.hannu510
--- /etc/config/system.normal
+++ /etc/config/system.hannu510
@@ -33,8 +33,9 @@
config led 'led_wan'
option name 'WAN'
option sysfs 'white:wan'
- option trigger 'switch0'
- option port_mask '0x20'
+ option trigger 'netdev'
+ option mode 'link tx rx'
+ option dev 'wan'
config led 'led_esata'
option name 'eSATA'
With those changes made before sysupgrade, I am able to sysupgrade with other settings intact. I do not use any VLANs.
But additionally, all stuff related to sqm, bcp38, whatever..., where references to the hardware interface names are used in config.
1 Like