Skip to contentSkip to conversation

Support for QCA6174 [168c:003e]

DISCUSSION Michael Krupp 2 participants 8 messages Oct 25, 2015 – Oct 29, 2015 Qualcomm Atheros ATH10K wireless driver

lore
Share & tools
lore
#0 lore raw

Hello,

I just bought a Aspire VN7-792G, but so far I was not able to get wireless working. The chip reports as QCA6174 [168c:003e] and it looks like the board.bin cannot be loaded:

    Oct 25 04:27:05 debian kernel: [ 4833.902454] ath10k_pci 
0000:07:00.0: limiting irq mode to: 1
    Oct 25 04:27:05 debian kernel: [ 4833.902461] ath10k_pci 
0000:07:00.0: pci irq legacy interrupts 0 irq_mode 1 reset_mode 0
    Oct 25 04:27:05 debian kernel: [ 4834.162236] ath10k_pci 
0000:07:00.0: Direct firmware load for ath10k/cal-pci-0000:07:00.0.bin failed with error -2
    Oct 25 04:27:05 debian kernel: [ 4834.162250] ath10k_pci 
0000:07:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/board-pci-168c:003e:11ad:0807.bin failed with error -2
    Oct 25 04:27:05 debian kernel: [ 4834.162253] ath10k_pci 
0000:07:00.0: failed to load spec board file, falling back to generic: -2
    Oct 25 04:27:05 debian kernel: [ 4834.162283] ath10k_pci 
0000:07:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
    Oct 25 04:27:05 debian kernel: [ 4834.162286] ath10k_pci 
0000:07:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
    Oct 25 04:27:07 debian kernel: [ 4836.280409] ath10k_pci 
0000:07:00.0: qca6174 hw3.2 (0x05030000, 0x00340aff, 168c:003e:11ad:0807 fallback) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 htt 3.26 wmi 4 cal otp max_sta 32
    Oct 25 04:27:07 debian kernel: [ 4836.280413] ath10k_pci 
0000:07:00.0: debug 0 debugfs 0 tracing 0 dfs 0 testmode 0
    Oct 25 04:27:08 debian kernel: [ 4837.278508] ath10k_pci 
0000:07:00.0: suspend timed out - target pause event never came
    Oct 25 04:27:08 debian systemd[1]: Starting Load/Save RF Kill 
Switch Status...
    Oct 25 04:27:08 debian kernel: [ 4837.367302] ath: EEPROM 
regdomain: 0x6c
    Oct 25 04:27:08 debian kernel: [ 4837.367304] ath: EEPROM indicates 
we should expect a direct regpair map
    Oct 25 04:27:08 debian kernel: [ 4837.367306] ath: Country alpha2 
being used: 00
    Oct 25 04:27:08 debian kernel: [ 4837.367307] ath: Regpair used: 0x6c
    Oct 25 04:27:08 debian kernel: [ 4837.369008] ath10k_pci 
0000:07:00.0 wlp7s0: renamed from wlan0
    Oct 25 04:27:08 debian systemd[1]: Started Load/Save RF Kill Switch 

Status.

I also tried renaming / symlinking the firmware-4.bin to firmware-5.bin, but that does not seem to have any effect, other than getting rid of the error message on lines 6 and 7.

Also followed the 'qca6164 support' discussion, but still could not get it working:
* http://lists.infradead.org/pipermail/ath10k/2015-August/005752.html

I tried several kernel versions, starting from 4.2.0 (debian) up to latest 4.2.4 (kernel.org). All of them seem to include the patch mentioned in the thread i linked erlier:
* http://lists.infradead.org/pipermail/ath10k/2015-August/005775.html

When trying to 'up' the device via 'ifconfig wlp7s0 up':

    Oct 25 04:31:36 debian kernel: [ 5104.570092] ath10k_pci 
0000:07:00.0: failed to enable adaptive qcs: -11
    Oct 25 04:31:39 debian kernel: [ 5107.569748] ath10k_pci 

0000:07:00.0: could not suspend target (-11)

I tired the following firmware images:
* https://github.com/kvalo/ath10k-firmware
* https://github.com/sumdog/ath10k-firmware
*
https://github.com/kvalo/ath10k-firmware/tree/b247aca880e2b228dddc647eb853e36a0627b189/ath10k/QCA6174/hw3.0
*
https://github.com/atondwal/ath10k-firmware/commit/88fca85ef59d708b9874e5b7885416b58aef9ee7

--

    # uname -a
    Linux debian 4.2.4 #2 SMP Sat Oct 24 23:56:33 CEST 2015 x86_64 
GNU/Linux
    # lspci
    00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM 
Registers (rev 07)
    00:01.0 PCI bridge: Intel Corporation Sky Lake PCIe Controller 
(x16) (rev 07)
    00:02.0 VGA compatible controller: Intel Corporation Device 191b 
(rev 06)
    00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 
xHCI Controller (rev 31)
    00:14.2 Signal processing controller: Intel Corporation Sunrise 
Point-H Thermal subsystem (rev 31)
    00:15.0 Signal processing controller: Intel Corporation Sunrise 
Point-H LPSS I2C Controller #0 (rev 31)
    00:15.1 Signal processing controller: Intel Corporation Sunrise 
Point-H LPSS I2C Controller #1 (rev 31)
    00:16.0 Communication controller: Intel Corporation Sunrise Point-H 
CSME HECI #1 (rev 31)
    00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA 
Controller [AHCI mode] (rev 31)
    00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express 
Root Port #3 (rev f1)
    00:1c.3 PCI bridge: Intel Corporation Sunrise Point-H PCI Express 
Root Port #4 (rev f1)
    00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC 
Controller (rev 31)
    00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC 
(rev 31)
    00:1f.3 Multimedia audio controller: Intel Corporation Sunrise 
Point-H HD Audio (rev 31)
    00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
    01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 950M] 
(rev a2)
    07:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac 
Wireless Network Adapter (rev 32)
    08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
    # lshw -c network
      *-network UNCLAIMED
           description: Network controller
           product: QCA6174 802.11ac Wireless Network Adapter
           vendor: Qualcomm Atheros
           physical id: 0
           bus info: pci@0000:07:00.0
           version: 32
           width: 64 bits
           clock: 33MHz
           capabilities: pm msi pciexpress cap_list
           configuration: latency=0
           resources: memory:54000000-541fffff

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

#1 lore raw
Quoted 43 lines · Michael Krupp

Hello,

I just bought a Aspire VN7-792G, but so far I was not able to get wireless working.
The chip reports as QCA6174 [168c:003e] and it looks like the board.bin cannot be loaded:

    Oct 25 04:27:05 debian kernel: [ 4833.902454] ath10k_pci 0000:07:00.0:
limiting irq mode to: 1
    Oct 25 04:27:05 debian kernel: [ 4833.902461] ath10k_pci 0000:07:00.0:
pci irq legacy interrupts 0 irq_mode 1 reset_mode 0
    Oct 25 04:27:05 debian kernel: [ 4834.162236] ath10k_pci 0000:07:00.0:
Direct firmware load for ath10k/cal-pci-0000:07:00.0.bin failed with error
-2
    Oct 25 04:27:05 debian kernel: [ 4834.162250] ath10k_pci 0000:07:00.0:
Direct firmware load for
ath10k/QCA6174/hw3.0/board-pci-168c:003e:11ad:0807.bin failed with error -2
    Oct 25 04:27:05 debian kernel: [ 4834.162253] ath10k_pci 0000:07:00.0:
failed to load spec board file, falling back to generic: -2
    Oct 25 04:27:05 debian kernel: [ 4834.162283] ath10k_pci 0000:07:00.0:
Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with
error -2
    Oct 25 04:27:05 debian kernel: [ 4834.162286] ath10k_pci 0000:07:00.0:
could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
    Oct 25 04:27:07 debian kernel: [ 4836.280409] ath10k_pci 0000:07:00.0:
qca6174 hw3.2 (0x05030000, 0x00340aff, 168c:003e:11ad:0807 fallback) fw
WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 htt 3.26 wmi 4 cal otp max_sta 32
    Oct 25 04:27:07 debian kernel: [ 4836.280413] ath10k_pci 0000:07:00.0:
debug 0 debugfs 0 tracing 0 dfs 0 testmode 0
    Oct 25 04:27:08 debian kernel: [ 4837.278508] ath10k_pci 0000:07:00.0:
suspend timed out - target pause event never came
    Oct 25 04:27:08 debian systemd[1]: Starting Load/Save RF Kill Switch
Status...
    Oct 25 04:27:08 debian kernel: [ 4837.367302] ath: EEPROM regdomain:
0x6c
    Oct 25 04:27:08 debian kernel: [ 4837.367304] ath: EEPROM indicates we
should expect a direct regpair map
    Oct 25 04:27:08 debian kernel: [ 4837.367306] ath: Country alpha2 being
used: 00
    Oct 25 04:27:08 debian kernel: [ 4837.367307] ath: Regpair used: 0x6c
    Oct 25 04:27:08 debian kernel: [ 4837.369008] ath10k_pci 0000:07:00.0
wlp7s0: renamed from wlan0
    Oct 25 04:27:08 debian systemd[1]: Started Load/Save RF Kill Switch
Quoted 6 lines

Status.

I also tried renaming / symlinking the firmware-4.bin to firmware-5.bin, but that does not seem to have any effect,
other than getting rid of the error message on lines 6 and 7.

ath10k keeps backward compatibility with userspace and it has a fallback mechanism when trying to find firmware files. That why you see these "error" messages.

It does load the board.bin. If it didn't find any board.bin it would not register a wiphy and you would not see a wireless interface on your system.

Quoted 12 lines

Also followed the 'qca6164 support' discussion, but still could not get it working:
* http://lists.infradead.org/pipermail/ath10k/2015-August/005752.html

I tried several kernel versions, starting from 4.2.0 (debian) up to latest 4.2.4 (kernel.org).
All of them seem to include the patch mentioned in the thread i linked erlier:
* http://lists.infradead.org/pipermail/ath10k/2015-August/005775.html

Quoted 6 lines

When trying to 'up' the device via 'ifconfig wlp7s0 up':

    Oct 25 04:31:36 debian kernel: [ 5104.570092] ath10k_pci 0000:07:00.0:
failed to enable adaptive qcs: -11
    Oct 25 04:31:39 debian kernel: [ 5107.569748] ath10k_pci 0000:07:00.0:

could not suspend target (-11)

This suggests you have an invalid board.bin. From the logs it looks like you have one of the newer qca6174 chips (hw3.2 instead of hw2.x). If you want it to get it working asap you'll need to look into windows driver for the device and extract an adequate eeprom/board file which matches your device's subsystem product/vendor ids.

Michał

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

#2 lore raw

Hello,

I managed to get it (sort of) working with the eeprom extracted from the windows driversand thefirmware from kvalo's ath10k-repo on GitHub.See more details below.

Unfortunately I only get a bandwidth of about 2Mb/s connected to a 54Mb/s AP.Is this a known limitation to ath10k right now, or may there be a way to get it working at full speed?

Also, thank You Michał for pointing me the right direction and helping make it usable, at least.

--

Loading the kernel modules:

[ 1399.912769] cfg80211: World regulatory domain updated:
[ 1399.912772] cfg80211:  DFS Master region: unset
[ 1399.912772] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 1399.912774] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 1399.912775] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 1399.912776] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[ 1399.912777] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 1399.912778] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[ 1399.912779] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[ 1399.912780] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[ 1399.912781] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[ 1399.914523] ath10k_pci 0000:07:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0
[ 1400.101020] ath10k_pci 0000:07:00.0: firmware: failed to load ath10k/cal-pci-0000:07:00.0.bin (-2)
[ 1400.101029] ath10k_pci 0000:07:00.0: Direct firmware load for ath10k/cal-pci-0000:07:00.0.bin failed with error -2
[ 1400.101047] ath10k_pci 0000:07:00.0: firmware: failed to load ath10k/QCA6174/hw3.0/board-pci-168c:003e:11ad:0807.bin (-2)
[ 1400.101051] ath10k_pci 0000:07:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/board-pci-168c:003e:11ad:0807.bin failed with error -2
[ 1400.101055] ath10k_pci 0000:07:00.0: failed to load spec board file, falling back to generic: -2
[ 1400.101109] ath10k_pci 0000:07:00.0: firmware: direct-loading firmware ath10k/QCA6174/hw3.0/board.bin
[ 1400.101125] ath10k_pci 0000:07:00.0: firmware: failed to load ath10k/QCA6174/hw3.0/firmware-5.bin (-2)
[ 1400.101129] ath10k_pci 0000:07:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
[ 1400.101133] ath10k_pci 0000:07:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
[ 1400.101409] ath10k_pci 0000:07:00.0: firmware: direct-loading firmware ath10k/QCA6174/hw3.0/firmware-4.bin
[ 1402.218360] ath10k_pci 0000:07:00.0: qca6174 hw3.2 (0x05030000, 0x00340aff, 168c:003e:11ad:0807 fallback) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 htt 3.26 wmi 4 cal otp max_sta 32
[ 1402.218364] ath10k_pci 0000:07:00.0: debug 0 debugfs 0 tracing 0 dfs 0 testmode 0
[ 1402.293000] ath: EEPROM regdomain: 0x6c
[ 1402.293005] ath: EEPROM indicates we should expect a direct regpair map
[ 1402.293009] ath: Country alpha2 being used: 00
[ 1402.293011] ath: Regpair used: 0x6c
[ 1402.295714] ath10k_pci 0000:07:00.0 wlp7s0: renamed from wlan0

And connecting via wpa_supplicant:

[ 1473.897941] wlp7s0: authenticate with 00:24:fe:a8:2c:55
[ 1473.961257] wlp7s0: send auth to 00:24:fe:a8:2c:55 (try 1/3)
[ 1473.963499] wlp7s0: authenticated
[ 1473.963841] wlp7s0: associate with 00:24:fe:a8:2c:55 (try 1/3)
[ 1473.971386] wlp7s0: RX AssocResp from 00:24:fe:a8:2c:55 (capab=0x411 status=0 aid=2)
[ 1473.974978] wlp7s0: associated
[ 1473.975015] IPv6: ADDRCONF(NETDEV_CHANGE): wlp7s0: link becomes ready

Firmware used:
* eeprom_ar6320_3p0_NFA344a.bin
- extracte from Windows 10 Driver via InstallShield/UniExtract
- MD5: 956bec86376ef28615dd8493048fafb1
* firmware-4.bin
-
https://github.com/kvalo/ath10k-firmware/blob/master/ath10k/QCA6174/hw3.0/firmware-4.bin

# iwconfig wlp7s0:

wlp7s0 IEEE 802.11abgn ESSID:"[REMOVED]"
Mode:Managed Frequency:2.457 GHz Access Point:
00:24:FE:A8:2C:55
Bit Rate=1 Mb/s Tx-Power=20 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
Link Quality=69/70 Signal level=-41 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:32 Missed beacon:0

# uname -a:
Linux debian 4.2.0-1-amd64 #1 SMP Debian 4.2.3-2 (2015-10-14) x86_64 GNU/Linux

Michael

Quoted 84 lines · Michal Kazior
Quoted 43 lines · Michael Krupp

Hello,

I just bought a Aspire VN7-792G, but so far I was not able to get wireless working.
The chip reports as QCA6174 [168c:003e] and it looks like the board.bin cannot be loaded:

     Oct 25 04:27:05 debian kernel: [ 4833.902454] ath10k_pci 0000:07:00.0:
limiting irq mode to: 1
     Oct 25 04:27:05 debian kernel: [ 4833.902461] ath10k_pci 0000:07:00.0:
pci irq legacy interrupts 0 irq_mode 1 reset_mode 0
     Oct 25 04:27:05 debian kernel: [ 4834.162236] ath10k_pci 0000:07:00.0:
Direct firmware load for ath10k/cal-pci-0000:07:00.0.bin failed with error
-2
     Oct 25 04:27:05 debian kernel: [ 4834.162250] ath10k_pci 0000:07:00.0:
Direct firmware load for
ath10k/QCA6174/hw3.0/board-pci-168c:003e:11ad:0807.bin failed with error -2
     Oct 25 04:27:05 debian kernel: [ 4834.162253] ath10k_pci 0000:07:00.0:
failed to load spec board file, falling back to generic: -2
     Oct 25 04:27:05 debian kernel: [ 4834.162283] ath10k_pci 0000:07:00.0:
Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with
error -2
     Oct 25 04:27:05 debian kernel: [ 4834.162286] ath10k_pci 0000:07:00.0:
could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
     Oct 25 04:27:07 debian kernel: [ 4836.280409] ath10k_pci 0000:07:00.0:
qca6174 hw3.2 (0x05030000, 0x00340aff, 168c:003e:11ad:0807 fallback) fw
WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 htt 3.26 wmi 4 cal otp max_sta 32
     Oct 25 04:27:07 debian kernel: [ 4836.280413] ath10k_pci 0000:07:00.0:
debug 0 debugfs 0 tracing 0 dfs 0 testmode 0
     Oct 25 04:27:08 debian kernel: [ 4837.278508] ath10k_pci 0000:07:00.0:
suspend timed out - target pause event never came
     Oct 25 04:27:08 debian systemd[1]: Starting Load/Save RF Kill Switch
Status...
     Oct 25 04:27:08 debian kernel: [ 4837.367302] ath: EEPROM regdomain:
0x6c
     Oct 25 04:27:08 debian kernel: [ 4837.367304] ath: EEPROM indicates we
should expect a direct regpair map
     Oct 25 04:27:08 debian kernel: [ 4837.367306] ath: Country alpha2 being
used: 00
     Oct 25 04:27:08 debian kernel: [ 4837.367307] ath: Regpair used: 0x6c
     Oct 25 04:27:08 debian kernel: [ 4837.369008] ath10k_pci 0000:07:00.0
wlp7s0: renamed from wlan0
     Oct 25 04:27:08 debian systemd[1]: Started Load/Save RF Kill Switch
Quoted 6 lines

Status.

I also tried renaming / symlinking the firmware-4.bin to firmware-5.bin, but that does not seem to have any effect,
other than getting rid of the error message on lines 6 and 7.

ath10k keeps backward compatibility with userspace and it has a fallback mechanism when trying to find firmware files. That why you see these "error" messages.

It does load the board.bin. If it didn't find any board.bin it would not register a wiphy and you would not see a wireless interface on your system.

Quoted 12 lines

Also followed the 'qca6164 support' discussion, but still could not get it working:
* http://lists.infradead.org/pipermail/ath10k/2015-August/005752.html

I tried several kernel versions, starting from 4.2.0 (debian) up to latest 4.2.4 (kernel.org).
All of them seem to include the patch mentioned in the thread i linked erlier:
* http://lists.infradead.org/pipermail/ath10k/2015-August/005775.html

Quoted 6 lines

When trying to 'up' the device via 'ifconfig wlp7s0 up':

     Oct 25 04:31:36 debian kernel: [ 5104.570092] ath10k_pci 0000:07:00.0:
failed to enable adaptive qcs: -11
     Oct 25 04:31:39 debian kernel: [ 5107.569748] ath10k_pci 0000:07:00.0:

could not suspend target (-11)

This suggests you have an invalid board.bin. From the logs it looks like you have one of the newer qca6174 chips (hw3.2 instead of hw2.x). If you want it to get it working asap you'll need to look into windows driver for the device and extract an adequate eeprom/board file which matches your device's subsystem product/vendor ids.

Quoted 6 lines

Michał

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

#3 lore raw
Quoted 19 lines · Michael Krupp

Hello,

I managed to get it (sort of) working with the eeprom extracted from the windows
driversand thefirmware from kvalo's ath10k-repo on GitHub.See more details below.

Unfortunately I only get a bandwidth of about 2Mb/s connected to a 54Mb/s AP.Is
this a known limitation to ath10k right now, or may there be a way to get it working at full speed?

Also, thank You Michał for pointing me the right direction and helping make it
usable, at least.

--

[...]

Quoted 11 lines
# iwconfig wlp7s0:

wlp7s0 IEEE 802.11abgn ESSID:"[REMOVED]"
Mode:Managed Frequency:2.457 GHz Access Point: 00:24:FE:A8:2C:55
Bit Rate=1 Mb/s Tx-Power=20 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
Link Quality=69/70 Signal level=-41 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:32 Missed beacon:0

Did you actually check the performance? The driver doesn't report tx rate properly due to firmware limitation so it always reports 1mbps or 6mbps to userspace tools.

Sidenote: iwconfig is deprecated. iw is the go-to wireless tool now.

Michał

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

#4 lore raw

Hello Michał

yes, I checked the actual performance via netcat, scp and rsync. I'll report back once I have tested against another AP.

Michael

Quoted 40 lines · Michal Kazior
Quoted 19 lines · Michael Krupp

Hello,

I managed to get it (sort of) working with the eeprom extracted from the windows
driversand thefirmware from kvalo's ath10k-repo on GitHub.See more details below.

Unfortunately I only get a bandwidth of about 2Mb/s connected to a 54Mb/s AP.Is
this a known limitation to ath10k right now, or may there be a way to get it working at full speed?

Also, thank You Michał for pointing me the right direction and helping make it
usable, at least.

--

[...]

Quoted 11 lines
# iwconfig wlp7s0:

wlp7s0 IEEE 802.11abgn ESSID:"[REMOVED]"
Mode:Managed Frequency:2.457 GHz Access Point: 00:24:FE:A8:2C:55
Bit Rate=1 Mb/s Tx-Power=20 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
Link Quality=69/70 Signal level=-41 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:32 Missed beacon:0

Did you actually check the performance? The driver doesn't report tx rate properly due to firmware limitation so it always reports 1mbps or 6mbps to userspace tools.

Sidenote: iwconfig is deprecated. iw is the go-to wireless tool now.

Quoted 7 lines

Michał

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

#5 lore raw
Quoted 4 lines · Michael Krupp

Hello Michał

yes, I checked the actual performance via netcat, scp and rsync. I'll report back once I have tested against another AP.

TCP performance is known to be tricky/poor in various scenarios. There were some discussions in the past:

- http://lists.infradead.org/pipermail/ath10k/2015-October/006160.html
- http://thread.gmane.org/gmane.linux.network/348420

Michał

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

#6 lore raw

Hello Michał,

thank you for pointing me to those discussions.

I will repeat my tests using iperf to also cover UDP, and will also try some older kernel releases, pre-dating 3.19. Also I'll try another AP as mentioned earlier.

Michael

Quoted 13 lines · Michal Kazior
Quoted 4 lines · Michael Krupp

Hello Michał

yes, I checked the actual performance via netcat, scp and rsync. I'll report back once I have tested against another AP.

TCP performance is known to be tricky/poor in various scenarios. There were some discussions in the past:

- http://lists.infradead.org/pipermail/ath10k/2015-October/006160.html
- http://thread.gmane.org/gmane.linux.network/348420

Quoted 7 lines

Michał

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

#7 lore raw

Hello Michał,

I did some more testing with iperf, two different APs:
* TP-Link TL-WR941ND
* Speedport W 723V B

I'm using my old notebook WiFi (AR9285, ath9k) as reference here. All of the results below are reliably repeatable, with minimal deviation. Kernel versions do not seem to have any meaningful impact, neither does setting the TCP/CC algorithm. The following tests were run on 4.2 using "reno".

The numbers I get look very strange to me. I tried playing around with buffer sizes, but with no effect (http://lists.infradead.org/pipermail/ath10k/2015-October/006160.html)

I also noted, that the QCA6174 does not seem to like close proximity to the AP. When I get any closer than about 3m to the AP, connection drops to less than 1Mbit/s average. Same result with both APs vs the QCA6174 (TCP):

[ ID] Interval       Transfer     Bandwidth
[  3]  0.0- 1.0 sec   128 KBytes  1.05 Mbits/sec
[  3]  1.0- 2.0 sec   128 KBytes  1.05 Mbits/sec
[  3]  2.0- 3.0 sec  0.00 Bytes  0.00 bits/sec
[  3]  3.0- 4.0 sec  0.00 Bytes  0.00 bits/sec
[  3]  4.0- 5.0 sec   128 KBytes  1.05 Mbits/sec
[  3]  5.0- 6.0 sec  0.00 Bytes  0.00 bits/sec
[  3]  6.0- 7.0 sec   384 KBytes  3.15 Mbits/sec
[  3]  7.0- 8.0 sec   128 KBytes  1.05 Mbits/sec
[  3]  8.0- 9.0 sec   256 KBytes  2.10 Mbits/sec
[  3]  9.0-10.0 sec  0.00 Bytes  0.00 bits/sec
[  3] 10.0-11.0 sec  0.00 Bytes  0.00 bits/sec
[  3] 11.0-12.0 sec  0.00 Bytes  0.00 bits/sec
[  3] 12.0-13.0 sec  0.00 Bytes  0.00 bits/sec
[  3] 13.0-14.0 sec   128 KBytes  1.05 Mbits/sec
[  3] 14.0-15.0 sec   256 KBytes  2.10 Mbits/sec

UDP traffic at first is more or less stable around 40Mbit/s, but also randomly drops down to zero, quickly ramps up to 100M, drops again and finally stabilizes at around 100M again (log cropped):

[ ID] Interval       Transfer     Bandwidth
[  3]  0.0- 1.0 sec  5.16 MBytes  43.3 Mbits/sec
[  3]  1.0- 2.0 sec  4.74 MBytes  39.8 Mbits/sec
[  3]  2.0- 3.0 sec  5.70 MBytes  47.8 Mbits/sec
[  3]  3.0- 4.0 sec  4.59 MBytes  38.5 Mbits/sec
[  3]  4.0- 5.0 sec  4.63 MBytes  38.8 Mbits/sec
... // seems stable at first, then drops and quickly ramps up
[  3] 53.0-54.0 sec  4.48 MBytes  37.6 Mbits/sec
[  3] 54.0-55.0 sec  2.67 MBytes  22.4 Mbits/sec
[  3] 55.0-56.0 sec   294 KBytes  2.41 Mbits/sec
[  3] 56.0-57.0 sec  2.13 MBytes  17.9 Mbits/sec
[  3] 57.0-58.0 sec  8.09 MBytes  67.9 Mbits/sec
[  3] 58.0-59.0 sec  12.2 MBytes   102 Mbits/sec
[  3] 59.0-60.0 sec  13.2 MBytes   110 Mbits/sec
... // stable for a couple of seconds, then drops again
[  3] 65.0-66.0 sec  13.2 MBytes   111 Mbits/sec
[  3] 66.0-67.0 sec  7.11 MBytes  59.7 Mbits/sec
[  3] 67.0-68.0 sec  4.24 MBytes  35.6 Mbits/sec
[  3] 68.0-69.0 sec  2.30 MBytes  19.3 Mbits/sec
[  3] 69.0-70.0 sec  3.20 MBytes  26.8 Mbits/sec
[  3] 70.0-71.0 sec  1.93 MBytes  16.2 Mbits/sec
[  3] 71.0-72.0 sec  1.92 MBytes  16.1 Mbits/sec
[  3] 72.0-73.0 sec  2.80 MBytes  23.5 Mbits/sec
[  3] 73.0-74.0 sec  4.11 MBytes  34.5 Mbits/sec
[  3] 74.0-75.0 sec  3.11 MBytes  26.1 Mbits/sec
[  3] 75.0-76.0 sec  2.47 MBytes  20.7 Mbits/sec
[  3] 76.0-77.0 sec   678 KBytes  5.55 Mbits/sec
[  3] 77.0-78.0 sec   589 KBytes  4.82 Mbits/sec
[  3] 78.0-79.0 sec  68.9 KBytes   564 Kbits/sec
[  3] 79.0-80.0 sec  0.00 Bytes  0.00 bits/sec
[  3] 80.0-81.0 sec  68.9 KBytes   564 Kbits/sec
... // peaks and drops between 0 and around 580k
[  3] 107.0-108.0 sec   138 KBytes  1.13 Mbits/sec
[  3] 108.0-109.0 sec   586 KBytes  4.80 Mbits/sec
[  3] 109.0-110.0 sec   597 KBytes  4.89 Mbits/sec
[  3] 110.0-111.0 sec   350 KBytes  2.87 Mbits/sec
[  3] 111.0-112.0 sec   212 KBytes  1.74 Mbits/sec
[  3] 112.0-113.0 sec   741 KBytes  6.07 Mbits/sec
[  3] 113.0-114.0 sec  1.48 MBytes  12.4 Mbits/sec
[  3] 114.0-115.0 sec  2.19 MBytes  18.4 Mbits/sec
... // now slowly ramps up again
[  3] 131.0-132.0 sec  5.06 MBytes  42.4 Mbits/sec
[  3] 132.0-133.0 sec  9.00 MBytes  75.5 Mbits/sec
[  3] 133.0-134.0 sec  10.8 MBytes  90.7 Mbits/sec
[  3] 134.0-135.0 sec  12.8 MBytes   108 Mbits/sec
... // and stabilizes
[  3] 169.0-170.0 sec  11.1 MBytes  93.2 Mbits/sec
[  3] 170.0-171.0 sec  11.6 MBytes  97.3 Mbits/sec
[  3] 171.0-172.0 sec  10.4 MBytes  87.6 Mbits/sec
[  3] 172.0-173.0 sec  11.7 MBytes  97.9 Mbits/sec

This behavior is reproducible with both APs. Only difference is that the W 723V B only reaches about 45Mbit/s.

My old AR9285 remains stable between 40 and 50Mbit/s, with both APs.

I'm really reaching a point here, where I do not know enough about WiFi to debug this any further... Would more test data (maybe nstat, tcpdump, etc...) be of any use for you or someone else to help fix this problem?

Greetings,
Michael

---

Some more TCP-tests with iperf. Parallelization (ipef -P X) does not seem to have any effect on total average throughput. I cropped the logs for better clarity, when there were no significant changes anymore.

1) TL-WR941ND <-> AR9285 (TCP):

It slowly ramps up and stabilizes around 45Mbit/s:

[ ID] Interval       Transfer     Bandwidth
[  3]  0.0- 1.0 sec  2.50 MBytes  21.0 Mbits/sec
[  3]  1.0- 2.0 sec  2.38 MBytes  19.9 Mbits/sec
[  3]  2.0- 3.0 sec  2.38 MBytes  19.9 Mbits/sec
[  3]  3.0- 4.0 sec  1.75 MBytes  14.7 Mbits/sec
[  3]  4.0- 5.0 sec  2.00 MBytes  16.8 Mbits/sec
[  3]  5.0- 6.0 sec  1.88 MBytes  15.7 Mbits/sec
[  3]  6.0- 7.0 sec  1.25 MBytes  10.5 Mbits/sec
[  3]  7.0- 8.0 sec  2.75 MBytes  23.1 Mbits/sec
[  3]  8.0- 9.0 sec  2.38 MBytes  19.9 Mbits/sec
[  3]  9.0-10.0 sec  2.25 MBytes  18.9 Mbits/sec
[  3] 10.0-11.0 sec  2.00 MBytes  16.8 Mbits/sec
[  3] 11.0-12.0 sec  2.62 MBytes  22.0 Mbits/sec
[  3] 12.0-13.0 sec  2.50 MBytes  21.0 Mbits/sec
[  3] 13.0-14.0 sec  2.88 MBytes  24.1 Mbits/sec
[  3] 14.0-15.0 sec  2.62 MBytes  22.0 Mbits/sec
[  3] 15.0-16.0 sec  2.62 MBytes  22.0 Mbits/sec
[  3] 16.0-17.0 sec  2.62 MBytes  22.0 Mbits/sec
[  3] 17.0-18.0 sec  2.62 MBytes  22.0 Mbits/sec
[  3] 18.0-19.0 sec  2.88 MBytes  24.1 Mbits/sec
[  3] 19.0-20.0 sec  2.75 MBytes  23.1 Mbits/sec
[  3] 20.0-21.0 sec  4.25 MBytes  35.7 Mbits/sec
[  3] 21.0-22.0 sec  5.25 MBytes  44.0 Mbits/sec
[  3] 22.0-23.0 sec  5.25 MBytes  44.0 Mbits/sec
[  3] 23.0-24.0 sec  5.12 MBytes  43.0 Mbits/sec
[  3] 24.0-25.0 sec  5.38 MBytes  45.1 Mbits/sec
[  3] 25.0-26.0 sec  5.25 MBytes  44.0 Mbits/sec
[  3] 26.0-27.0 sec  5.12 MBytes  43.0 Mbits/sec
[  3] 27.0-28.0 sec  5.25 MBytes  44.0 Mbits/sec
[  3] 28.0-29.0 sec  5.12 MBytes  43.0 Mbits/sec
[  3] 29.0-30.0 sec  5.25 MBytes  44.0 Mbits/sec
[  3] 30.0-31.0 sec  5.38 MBytes  45.1 Mbits/sec

...

2) TL-WR941ND <-> QCA6174 (TCP):

Connection is mostly stable around 5.2Mbit/s, but seems to randomy drop to 1.05Mbit/s.

[ ID] Interval       Transfer     Bandwidth
[  3]  0.0- 1.0 sec  1.00 MBytes  8.39 Mbits/sec
[  3]  1.0- 2.0 sec   640 KBytes  5.24 Mbits/sec
[  3]  2.0- 3.0 sec   768 KBytes  6.29 Mbits/sec
[  3]  3.0- 4.0 sec   640 KBytes  5.24 Mbits/sec
[  3]  4.0- 5.0 sec   768 KBytes  6.29 Mbits/sec
[  3]  5.0- 6.0 sec   768 KBytes  6.29 Mbits/sec
[  3]  6.0- 7.0 sec   768 KBytes  6.29 Mbits/sec
[  3]  7.0- 8.0 sec   768 KBytes  6.29 Mbits/sec
[  3]  8.0- 9.0 sec   640 KBytes  5.24 Mbits/sec
[  3]  9.0-10.0 sec   768 KBytes  6.29 Mbits/sec
[  3] 10.0-11.0 sec   768 KBytes  6.29 Mbits/sec
[  3] 11.0-12.0 sec   768 KBytes  6.29 Mbits/sec
[  3] 12.0-13.0 sec   640 KBytes  5.24 Mbits/sec
[  3] 13.0-14.0 sec   768 KBytes  6.29 Mbits/sec
[  3] 14.0-15.0 sec   640 KBytes  5.24 Mbits/sec
[  3] 15.0-16.0 sec   768 KBytes  6.29 Mbits/sec
[  3] 16.0-17.0 sec   384 KBytes  3.15 Mbits/sec
[  3] 17.0-18.0 sec   384 KBytes  3.15 Mbits/sec
[  3] 18.0-19.0 sec   128 KBytes  1.05 Mbits/sec
[  3] 19.0-20.0 sec   128 KBytes  1.05 Mbits/sec
[  3] 20.0-21.0 sec   128 KBytes  1.05 Mbits/sec
[  3] 21.0-22.0 sec   256 KBytes  2.10 Mbits/sec
[  3] 22.0-23.0 sec   256 KBytes  2.10 Mbits/sec
[  3] 23.0-24.0 sec   640 KBytes  5.24 Mbits/sec
[  3] 24.0-25.0 sec   768 KBytes  6.29 Mbits/sec
[  3] 25.0-26.0 sec   640 KBytes  5.24 Mbits/sec
[  3] 26.0-27.0 sec   640 KBytes  5.24 Mbits/sec
[  3] 27.0-28.0 sec   512 KBytes  4.19 Mbits/sec
[  3] 28.0-29.0 sec   640 KBytes  5.24 Mbits/sec
[  3] 29.0-30.0 sec   768 KBytes  6.29 Mbits/sec
[  3] 30.0-31.0 sec   640 KBytes  5.24 Mbits/sec
[  3] 31.0-32.0 sec   768 KBytes  6.29 Mbits/sec
[  3] 32.0-33.0 sec   640 KBytes  5.24 Mbits/sec
[  3] 33.0-34.0 sec   640 KBytes  5.24 Mbits/sec
[  3] 34.0-35.0 sec   640 KBytes  5.24 Mbits/sec
[  3] 35.0-36.0 sec   640 KBytes  5.24 Mbits/sec
[  3] 36.0-37.0 sec   640 KBytes  5.24 Mbits/sec
[  3] 37.0-38.0 sec   640 KBytes  5.24 Mbits/sec
[  3] 38.0-39.0 sec   768 KBytes  6.29 Mbits/sec
[  3] 39.0-40.0 sec   640 KBytes  5.24 Mbits/sec
[  3] 40.0-41.0 sec   640 KBytes  5.24 Mbits/sec

...

3) W 723V B <-> AR9285 (TCP):

Almost immediately reaches max throughput of around 35Mbit/s, then drops repeatedly, and finally stabilizes at around 35Mbit/s:

[ 3] local 192.168.1.153 port 39623 connected with 192.168.1.2 port 5001

[ ID] Interval       Transfer     Bandwidth
[  3]  0.0- 1.0 sec  3.50 MBytes  29.4 Mbits/sec
[  3]  1.0- 2.0 sec  3.00 MBytes  25.2 Mbits/sec
[  3]  2.0- 3.0 sec  3.12 MBytes  26.2 Mbits/sec
[  3]  3.0- 4.0 sec  1.62 MBytes  13.6 Mbits/sec
[  3]  4.0- 5.0 sec  4.12 MBytes  34.6 Mbits/sec
[  3]  5.0- 6.0 sec  4.12 MBytes  34.6 Mbits/sec
[  3]  6.0- 7.0 sec  4.38 MBytes  36.7 Mbits/sec
[  3]  7.0- 8.0 sec  2.38 MBytes  19.9 Mbits/sec
[  3]  8.0- 9.0 sec  4.00 MBytes  33.6 Mbits/sec
[  3]  9.0-10.0 sec  4.00 MBytes  33.6 Mbits/sec
[  3] 10.0-11.0 sec  4.38 MBytes  36.7 Mbits/sec
[  3] 11.0-12.0 sec  4.38 MBytes  36.7 Mbits/sec
[  3] 12.0-13.0 sec  4.62 MBytes  38.8 Mbits/sec
[  3] 13.0-14.0 sec  4.50 MBytes  37.7 Mbits/sec
[  3] 14.0-15.0 sec  4.50 MBytes  37.7 Mbits/sec
[  3] 15.0-16.0 sec  4.62 MBytes  38.8 Mbits/sec
[  3] 16.0-17.0 sec  4.25 MBytes  35.7 Mbits/sec
[  3] 17.0-18.0 sec  4.25 MBytes  35.7 Mbits/sec
[  3] 18.0-19.0 sec  4.00 MBytes  33.6 Mbits/sec
[  3] 19.0-20.0 sec  3.88 MBytes  32.5 Mbits/sec
[  3] 20.0-21.0 sec  4.12 MBytes  34.6 Mbits/sec
[  3] 21.0-22.0 sec  4.12 MBytes  34.6 Mbits/sec
[  3] 22.0-23.0 sec  4.38 MBytes  36.7 Mbits/sec
[  3] 23.0-24.0 sec  4.25 MBytes  35.7 Mbits/sec
[  3] 24.0-25.0 sec  4.25 MBytes  35.7 Mbits/sec
[  3] 25.0-26.0 sec  4.12 MBytes  34.6 Mbits/sec
[  3] 26.0-27.0 sec  4.25 MBytes  35.7 Mbits/sec
[  3] 27.0-28.0 sec  4.12 MBytes  34.6 Mbits/sec
[  3] 28.0-29.0 sec  4.00 MBytes  33.6 Mbits/sec
[  3] 29.0-30.0 sec  4.25 MBytes  35.7 Mbits/sec
[  3] 30.0-31.0 sec  4.12 MBytes  34.6 Mbits/sec
[  3] 31.0-32.0 sec  4.12 MBytes  34.6 Mbits/sec
[  3] 32.0-33.0 sec  4.25 MBytes  35.7 Mbits/sec
[  3] 33.0-34.0 sec  4.38 MBytes  36.7 Mbits/sec
[  3] 34.0-35.0 sec  4.25 MBytes  35.7 Mbits/sec
[  3] 35.0-36.0 sec  4.25 MBytes  35.7 Mbits/sec
[  3] 36.0-37.0 sec  4.25 MBytes  35.7 Mbits/sec
[  3] 37.0-38.0 sec  4.12 MBytes  34.6 Mbits/sec
[  3] 38.0-39.0 sec  4.12 MBytes  34.6 Mbits/sec
[  3] 39.0-40.0 sec  4.12 MBytes  34.6 Mbits/sec
[  3] 40.0-41.0 sec  4.25 MBytes  35.7 Mbits/sec
[  3] 41.0-42.0 sec  4.62 MBytes  38.8 Mbits/sec
[  3] 42.0-43.0 sec  4.38 MBytes  36.7 Mbits/sec
[  3] 43.0-44.0 sec  3.88 MBytes  32.5 Mbits/sec
[  3] 44.0-45.0 sec  3.12 MBytes  26.2 Mbits/sec
[  3] 45.0-46.0 sec  3.12 MBytes  26.2 Mbits/sec
[  3] 46.0-47.0 sec  2.75 MBytes  23.1 Mbits/sec
[  3] 47.0-48.0 sec  4.12 MBytes  34.6 Mbits/sec
[  3] 48.0-49.0 sec  3.75 MBytes  31.5 Mbits/sec
[  3] 49.0-50.0 sec  4.12 MBytes  34.6 Mbits/sec
[  3] 50.0-51.0 sec  4.38 MBytes  36.7 Mbits/sec
[  3] 51.0-52.0 sec  4.38 MBytes  36.7 Mbits/sec
[  3] 52.0-53.0 sec  4.25 MBytes  35.7 Mbits/sec
[  3] 53.0-54.0 sec  4.00 MBytes  33.6 Mbits/sec
[  3] 54.0-55.0 sec  4.12 MBytes  34.6 Mbits/sec
[  3] 55.0-56.0 sec  4.12 MBytes  34.6 Mbits/sec
[  3] 56.0-57.0 sec  4.25 MBytes  35.7 Mbits/sec
[  3] 57.0-58.0 sec  4.38 MBytes  36.7 Mbits/sec
[  3] 58.0-59.0 sec  4.25 MBytes  35.7 Mbits/sec
[  3] 59.0-60.0 sec  4.25 MBytes  35.7 Mbits/sec

...

4) W 723V B <-> QCA6174 (TCP):

Connection seems stable at around 14Mbit/s at first, then starts jumping between 7 and 14 Mbit/s:

[ ID] Interval       Transfer     Bandwidth
[  3]  0.0- 1.0 sec  1.62 MBytes  13.6 Mbits/sec
[  3]  1.0- 2.0 sec  1.75 MBytes  14.7 Mbits/sec
[  3]  2.0- 3.0 sec  1.62 MBytes  13.6 Mbits/sec
[  3]  3.0- 4.0 sec  1.75 MBytes  14.7 Mbits/sec
[  3]  4.0- 5.0 sec  1.75 MBytes  14.7 Mbits/sec
[  3]  5.0- 6.0 sec  1.75 MBytes  14.7 Mbits/sec
[  3]  6.0- 7.0 sec  1.75 MBytes  14.7 Mbits/sec
[  3]  7.0- 8.0 sec  1.75 MBytes  14.7 Mbits/sec
[  3]  8.0- 9.0 sec  1.88 MBytes  15.7 Mbits/sec
[  3]  9.0-10.0 sec  1.62 MBytes  13.6 Mbits/sec
[  3] 10.0-11.0 sec  1.75 MBytes  14.7 Mbits/sec
[  3] 11.0-12.0 sec  1.75 MBytes  14.7 Mbits/sec
[  3] 12.0-13.0 sec  1.75 MBytes  14.7 Mbits/sec
[  3] 13.0-14.0 sec  1.75 MBytes  14.7 Mbits/sec
[  3] 14.0-15.0 sec  1.75 MBytes  14.7 Mbits/sec
[  3] 15.0-16.0 sec  1.75 MBytes  14.7 Mbits/sec
[  3] 16.0-17.0 sec  1.75 MBytes  14.7 Mbits/sec
[  3] 17.0-18.0 sec  1.75 MBytes  14.7 Mbits/sec
[  3] 18.0-19.0 sec  1.62 MBytes  13.6 Mbits/sec
[  3] 19.0-20.0 sec  1.88 MBytes  15.7 Mbits/sec
[  3] 20.0-21.0 sec  1.75 MBytes  14.7 Mbits/sec
[  3] 21.0-22.0 sec  1.75 MBytes  14.7 Mbits/sec
[  3] 22.0-23.0 sec  1.62 MBytes  13.6 Mbits/sec
[  3] 23.0-24.0 sec  1.75 MBytes  14.7 Mbits/sec
[  3] 24.0-25.0 sec  1.88 MBytes  15.7 Mbits/sec
[  3] 25.0-26.0 sec  1.25 MBytes  10.5 Mbits/sec
[  3] 26.0-27.0 sec  1.38 MBytes  11.5 Mbits/sec
[  3] 27.0-28.0 sec   896 KBytes  7.34 Mbits/sec
[  3] 28.0-29.0 sec   768 KBytes  6.29 Mbits/sec
[  3] 29.0-30.0 sec  1.12 MBytes  9.44 Mbits/sec
[  3] 30.0-31.0 sec  1.12 MBytes  9.44 Mbits/sec
[  3] 31.0-32.0 sec  1.00 MBytes  8.39 Mbits/sec
[  3] 32.0-33.0 sec  1.00 MBytes  8.39 Mbits/sec
[  3] 33.0-34.0 sec  1.12 MBytes  9.44 Mbits/sec
[  3] 34.0-35.0 sec  1.00 MBytes  8.39 Mbits/sec
[  3] 35.0-36.0 sec  1.38 MBytes  11.5 Mbits/sec
[  3] 36.0-37.0 sec   896 KBytes  7.34 Mbits/sec
[  3] 37.0-38.0 sec  1.12 MBytes  9.44 Mbits/sec
[  3] 38.0-39.0 sec  1.50 MBytes  12.6 Mbits/sec
[  3] 39.0-40.0 sec  1.50 MBytes  12.6 Mbits/sec
[  3] 40.0-41.0 sec  1.50 MBytes  12.6 Mbits/sec
[  3] 41.0-42.0 sec  1.38 MBytes  11.5 Mbits/sec
[  3] 42.0-43.0 sec  1.62 MBytes  13.6 Mbits/sec
[  3] 43.0-44.0 sec  1.38 MBytes  11.5 Mbits/sec
[  3] 44.0-45.0 sec  1.50 MBytes  12.6 Mbits/sec
[  3] 45.0-46.0 sec  1.38 MBytes  11.5 Mbits/sec
[  3] 46.0-47.0 sec  1.38 MBytes  11.5 Mbits/sec
[  3] 47.0-48.0 sec  1.38 MBytes  11.5 Mbits/sec
[  3] 48.0-49.0 sec  1.25 MBytes  10.5 Mbits/sec
[  3] 49.0-50.0 sec  1.12 MBytes  9.44 Mbits/sec
[  3] 50.0-51.0 sec   896 KBytes  7.34 Mbits/sec
[  3] 51.0-52.0 sec  1.25 MBytes  10.5 Mbits/sec
[  3] 52.0-53.0 sec  1.25 MBytes  10.5 Mbits/sec
[  3] 53.0-54.0 sec  1.12 MBytes  9.44 Mbits/sec
[  3] 54.0-55.0 sec  1.25 MBytes  10.5 Mbits/sec
[  3] 55.0-56.0 sec  1.25 MBytes  10.5 Mbits/sec
[  3] 56.0-57.0 sec  1.00 MBytes  8.39 Mbits/sec
[  3] 57.0-58.0 sec  1.00 MBytes  8.39 Mbits/sec
[  3] 58.0-59.0 sec  1.00 MBytes  8.39 Mbits/sec
[  3] 59.0-60.0 sec   896 KBytes  7.34 Mbits/sec
[  3] 60.0-61.0 sec   896 KBytes  7.34 Mbits/sec
[  3] 61.0-62.0 sec  1.12 MBytes  9.44 Mbits/sec
[  3] 62.0-63.0 sec  1.75 MBytes  14.7 Mbits/sec
[  3] 63.0-64.0 sec  1.88 MBytes  15.7 Mbits/sec
[  3] 64.0-65.0 sec  1.88 MBytes  15.7 Mbits/sec
[  3] 65.0-66.0 sec  1.88 MBytes  15.7 Mbits/sec
[  3] 66.0-67.0 sec  1.88 MBytes  15.7 Mbits/sec
[  3] 67.0-68.0 sec  1.75 MBytes  14.7 Mbits/sec
[  3] 68.0-69.0 sec  1.88 MBytes  15.7 Mbits/sec
[  3] 69.0-70.0 sec  1.88 MBytes  15.7 Mbits/sec
[  3] 70.0-71.0 sec  1.75 MBytes  14.7 Mbits/sec
[  3] 71.0-72.0 sec  1.88 MBytes  15.7 Mbits/sec
[  3] 72.0-73.0 sec  1.88 MBytes  15.7 Mbits/sec
[  3] 73.0-74.0 sec  1.75 MBytes  14.7 Mbits/sec
[  3] 74.0-75.0 sec  1.88 MBytes  15.7 Mbits/sec
[  3] 75.0-76.0 sec  1.88 MBytes  15.7 Mbits/sec
[  3] 76.0-77.0 sec  1.75 MBytes  14.7 Mbits/sec
[  3] 77.0-78.0 sec  1.12 MBytes  9.44 Mbits/sec
[  3] 78.0-79.0 sec  1.50 MBytes  12.6 Mbits/sec
[  3] 79.0-80.0 sec  1.25 MBytes  10.5 Mbits/sec
[  3] 80.0-81.0 sec   896 KBytes  7.34 Mbits/sec
[  3] 81.0-82.0 sec   896 KBytes  7.34 Mbits/sec
[  3] 82.0-83.0 sec   896 KBytes  7.34 Mbits/sec
[  3] 83.0-84.0 sec  1.00 MBytes  8.39 Mbits/sec
[  3] 84.0-85.0 sec   896 KBytes  7.34 Mbits/sec
[  3] 85.0-86.0 sec   896 KBytes  7.34 Mbits/sec
[  3] 86.0-87.0 sec   896 KBytes  7.34 Mbits/sec
[  3] 87.0-88.0 sec  1.00 MBytes  8.39 Mbits/sec
[  3] 88.0-89.0 sec   768 KBytes  6.29 Mbits/sec
[  3] 89.0-90.0 sec   896 KBytes  7.34 Mbits/sec
[  3] 90.0-91.0 sec   896 KBytes  7.34 Mbits/sec
[  3] 91.0-92.0 sec  1.12 MBytes  9.44 Mbits/sec
[  3] 92.0-93.0 sec  1.12 MBytes  9.44 Mbits/sec
[  3] 93.0-94.0 sec  1.00 MBytes  8.39 Mbits/sec
[  3] 94.0-95.0 sec  1.25 MBytes  10.5 Mbits/sec
[  3] 95.0-96.0 sec  1.12 MBytes  9.44 Mbits/sec
[  3] 96.0-97.0 sec  1.00 MBytes  8.39 Mbits/sec

...

Quoted 36 lines · Michael Krupp

Hello Michał,

thank you for pointing me to those discussions.

I will repeat my tests using iperf to also cover UDP, and will also try some older kernel releases, pre-dating 3.19. Also I'll try another AP as mentioned earlier.

Michael

Quoted 13 lines · Michal Kazior
Quoted 4 lines · Michael Krupp

Hello Michał

yes, I checked the actual performance via netcat, scp and rsync. I'll report back once I have tested against another AP.

TCP performance is known to be tricky/poor in various scenarios. There were some discussions in the past:

- http://lists.infradead.org/pipermail/ath10k/2015-October/006160.html
- http://thread.gmane.org/gmane.linux.network/348420

Quoted 7 lines

Michał

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

Quoted 5 lines

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k