Tp-link Archer C60 v2, 19.07.0-rc2-ath79 snapshot. Out of memory

I checked the opkg software list for ath10k-firmware and I found qca9887, qca9888 and qca988x. Since Archer C60 v2 has qca9882, shouldn't I use qca988x? In the notes for qca9888 it is written "Alternative ath10k firmware for QCA9886 and QCA9888 from Candela Technologies", not for qca9882.

Sorry, I was talking about version 1 of this model. It may be that with the non-CT driver the problem is solved like me.

According to this site they have the same WiFi hardware. I don't see that QCA9882 is used. But QCA9886 as the Archer C60 v1.

Why are there two different firmwares, then?
https://openwrt.org/toh/hwdata/tp-link/tp-link_archer_c60_v1
https://openwrt.org/toh/hwdata/tp-link/tp-link_archer_c60_v2
According to OpenWrt it uses QCA9882.

Different boards with the same chips aren't always ("seldom are") laid out the same or have their flash interpreted in the same way. Additionally, TP-Link requires some "special" headers on "factory" images to be flashed.

I have this in my kernel log

[    9.343624] ath10k 4.13 driver, optimized for CT firmware, probing pci device: 0x56.
[    9.360799] PCI: Enabling device 0000:00:00.0 (0000 -> 0002)
[    9.366960] ath10k_pci 0000:00:00.0: pci irq legacy oper_irq_mode 1 irq_mode 0 reset_mode 0
[    9.570130] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/fwcfg-pci-0000:00:00.0.txt failed with error -2
[    9.581039] ath10k_pci 0000:00:00.0: Falling back to user helper
[    9.658574] firmware ath10k!fwcfg-pci-0000:00:00.0.txt: firmware_loading_store: map pages failed
[    9.743845] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/QCA9888/hw2.0/ct-firmware-5.bin failed with error -2
[    9.755213] ath10k_pci 0000:00:00.0: Falling back to user helper
[    9.823730] firmware ath10k!QCA9888!hw2.0!ct-firmware-5.bin: firmware_loading_store: map pages failed
[    9.833544] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/QCA9888/hw2.0/ct-firmware-2.bin failed with error -2
[    9.844892] ath10k_pci 0000:00:00.0: Falling back to user helper
[    9.975035] firmware ath10k!QCA9888!hw2.0!ct-firmware-2.bin: firmware_loading_store: map pages failed
[    9.984843] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/QCA9888/hw2.0/firmware-6.bin failed with error -2
[    9.995922] ath10k_pci 0000:00:00.0: Falling back to user helper
[   10.126246] firmware ath10k!QCA9888!hw2.0!firmware-6.bin: firmware_loading_store: map pages failed
[   10.671625] ath10k_pci 0000:00:00.0: qca9888 hw2.0 target 0x01000000 chip_id 0x00000000 sub 0000:0000
[   10.681183] ath10k_pci 0000:00:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
[   10.700595] ath10k_pci 0000:00:00.0: firmware ver 10.4-ct-9888-fW-011-cf79c7f api 5 features peer-flow-ctrl,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,cust-stats-CT crc32 0f624b45
[   11.028256] ath10k_pci 0000:00:00.0: failed to fetch board data for bus=pci,bmi-chip-id=0,bmi-board-id=20 from ath10k/QCA9888/hw2.0/board-2.bin
[   11.042337] ath10k_pci 0000:00:00.0: board_file api 1 bmi_id 0:20 crc32 83440407
[   13.033364] ath10k_pci 0000:00:00.0: 10.4 wmi init: vdevs: 16  peers: 48  tid: 96
[   13.041139] ath10k_pci 0000:00:00.0: msdu-desc: 2500  skid: 32
[   13.070865] ath10k_pci 0000:00:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186  msdu-desc: 2500  sw-crypt: 0'
[   13.081318] ath10k_pci 0000:00:00.0: wmi print 'free: 133328 iram: 16804 sram: 39400'
[   13.204316] ath10k_pci 0000:00:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal pre-cal-file max-sta 32 raw 0 hwcrypto 1

In the "wireless overview" 5ghz is listed as "Generic MAC80211 802.11nac"but I had to reinstall 18.06.5 to get a working router using 5ghz ...

So it seems to be a QCA9888 in there to what matters (the driver and firmware). What is rendered in the UI is somewhat immaterial.

This is consistent with the build

define Device/tplink_archer-c60-v2
  $(Device/tplink-safeloader-uimage)
  ATH_SOC := qca9561
  IMAGE_SIZE := 7808k
  DEVICE_MODEL := Archer C60
  DEVICE_VARIANT := v2
  TPLINK_BOARD_ID := ARCHER-C60-V2
  DEVICE_PACKAGES := kmod-ath10k-ct ath10k-firmware-qca9888-ct
  SUPPORTED_DEVICES += archer-c60-v2
endef
TARGET_DEVICES += tplink_archer-c60-v2

From "menu config help":
CONFIG_PACKAGE_ath10k-firmware-qca9888-ct: Alternative ath10k firmware for QCA9886 and QCA9888 from Candela Technologies.
So the firmware "firmware ver 10.4-ct-9888-fW-011-cf79c7f" is the same for 9886 and 9888?
My guess is that on Archer C60 V2 there is a 9886...

It's like the other controllers (like ath9k) that includes several chipsets.

Having the same issue with 5Ghz wifi. My temporary solution is to use Image Builder to build an image with zram and include this custom config file, one attempt to avoid OOM killer:

root@OpenWrt:~# cat /etc/sysctl.conf
vm.swappiness=100
vm.min_free_kbytes=512

I have some archer c60 v2 as wifi AP at home. Funny thing is, the one with more client connected and handle more traffic usually has more free memory. I have no idea why.

The top one carry some heavy duty, the bottom one is barely used:

looks like there is a memory leak in rpcd or ubus, at least on r11086. no idea if it has been fixed later

Hi.

@flavioweb

I have the same problem with my router.
Try to compile using "ath10k-ct-smallbuffers" instead "ath10k-ct", it worked for me.

Regards.
Juliano

2 Likes

Good news... looks like is enabled by default now =)
I give a try and let you know!


19 hours and still alive and kicking =)

Seems all fine now!

3 Likes

Did you try the 19.07.0 or 18.06.6 ? Please report back, I did not get around to compiling it myself and since I share the wifi with my flatmates I get very little window to experiment on this as work takes priority.

I've tested 19.07.0.
In a few days, as far as i can know, the release version should be available.
19.07.0 is tagged now.

2 Likes

19.07.0 is being built already and is available. when all targets finish building there should be an announcement about release

2 Likes

I'm testing 19.07.0 with 5 GHz turned on since yesterday. So far it's working flawlessly.
Thank you very much.