5GHz wifi doesn’t work on ZyXEL NBG6716 after upgrading to 22.03.0

Hi,

very similar post to: 21.02 same problem

I'm seeing the exact same behaviour with the 5G radio net coming up.


root@OpenWrt:/# dmesg | grep ath10k
[   15.798961] ath10k 5.15 driver, optimized for CT firmware, probing pci device: 0x3c.
[   15.808286] ath10k_pci 0000:00:00.0: enabling device (0000 -> 0002)
[   15.814828] ath10k_pci 0000:00:00.0: pci irq legacy oper_irq_mode 1 irq_mode 0 reset_mode 0
[   18.395894] ath10k_pci 0000:00:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
[   18.405315] ath10k_pci 0000:00:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
[   18.417233] ath10k_pci 0000:00:00.0: firmware ver 10.1-ct-8x-__fW-022-ecad3248 api 2 features wmi-10.x,has-wmi-mgmt-tx,mfp,txstatus-noack,wmi-10.x-CT,ratemask-CT,txrate-CT,get-temp-CT,tx-rc-CT,cust-stats-CT,retry-gt2-CT,txrate2-CT,beacon-cb-CT,wmi-block-ack-CT crc32 3e4cf97f
[   18.532136] ath10k_pci 0000:00:00.0: Loading BDF type 0
[   19.149088] ath10k_pci 0000:00:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[   20.094510] ath10k_pci 0000:00:00.0: 10.1 wmi init: vdevs: 16  peers: 127  tid: 256
[   25.142080] ath10k_pci 0000:00:00.0: wmi unified ready event not received
[   25.275386] ath10k_pci 0000:00:00.0: could not init core (-145)
[   25.281529] ath10k_pci 0000:00:00.0: could not probe fw (-145)

5Ghz worked fine under 19.07 (ar71xx)
any ideas on how to get it working with ath79 ?

thanks!

Just wanted to add that I also tried to regular driver/firmare (i.e. the non-ct variants) with pretty much the same result.

anyone out there still using this old thing?
thanks.

Did you reset wireless config to default. Restoring from a backup won't work.

Hej @Pilot6 ,
Yes, I upgraded via tftp which completely overwrites the existing installation.
AFAIK It's as "clean" as it gets.

Okay, found it!
Frustratingly this is an old bug resurfacing...

same bug in 17... series

fix is exactly the same too.

  • delete the cal data in /lib/firmware/ath10k
  • delete/modify the caldata script under /etc/hotplug.d/firmware 11-aath10k-caldata

five years to find the same bug again :man_facepalming:

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.