Comment 68 for bug 1520343

Revision history for this message
s (sendmeloadsofjunk) wrote :

I'm using a Killer 1535 on kernel 4.5.0 and the updated files as per post #1, and I get the same dmesg as Dennis posted in #66 after initialisation:

[ 2986.987057] ath10k_pci 0000:01:00.0: pci irq msi interrupts 1 irq_mode 0 reset_mode 0
[ 2987.223913] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/cal-pci-0000:01:00.0.bin failed with error -2
[ 2987.223924] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
[ 2987.223926] ath10k_pci 0000:01:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
[ 2987.224344] ath10k_pci 0000:01:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
[ 2987.224346] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[ 2987.224836] ath10k_pci 0000:01:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5
[ 2987.288654] ath10k_pci 0000:01:00.0: board_file api 2 bmi_id N/A crc32 46b57247
[ 2989.447728] ath10k_pci 0000:01:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[ 2989.513801] ath: EEPROM regdomain: 0x69
[ 2989.513804] ath: EEPROM indicates we should expect a direct regpair map
[ 2989.513806] ath: Country alpha2 being used: 00
[ 2989.513807] ath: Regpair used: 0x69
[ 2989.517364] ath10k_pci 0000:01:00.0 wlan3: renamed from wlan0

I can connect to 5GHz SSIDs, however I see very unstable ping and high packet loss even when the link is otherwise idle:

526 packets transmitted, 221 received, +9 errors, 57% packet loss, time 525820ms
rtt min/avg/max/mdev = 2.244/93.484/1691.704/201.948 ms, pipe 3

Using the same SSID but using Windows 7, or a 2.4GHz SSID on , normal performance is seen, >1% packet loss and >3ms ping.

Any ideas here, have I missed something?