You are not logged in.

Pages: 1

#1 2017-02-05 15:06:36

gilbertw1
Member
Registered: 2016-04-27
Posts: 14

Killer 1535 Wireless Card - Extremely Poor Upload Speeds

I recently received a Dell XPS 15" Laptop (9560) containing a Killer wireless card and I've noticed abysmal file upload speeds. I have a AT&T gigabit fiber connection hooked up to a Nighthawk X6 router (also reproduced with AT&T provided wireless router). To compare against, I also have a 2015 Macbook Pro running arch linux as well wiith a broadcom wireless card.

Speed test results:
XPS w/ Killer - 390 Mbps down / 150 Mbps up
Macbook w/ Broadcom - 350 Mbps down / 330 Mbps up

The Macbook with the broadcom driver clearly has more symmetrical upload and download speeds, however the killer performance in this test seems somewhat reasonable although the upload speeds are a little on the low side. The real problem I experience is when uploading a file, the upload speed tops out at about 15 Mbps using the Killer card. I've done numerous tests uploading to EC2, S3, VPS, even a local computer connected via ethernet, and consistently the Killer card tops out around this 15 Mbps, while the Macbook easily hits 200-300 Mbps. I've verified that plugging the XPS directly into ethernet results in extremely high speeds in all of these scenarios. I don't know enough to understand why the disparity between the speeds achieved in the speedtest and the file upload speed exists.

I've tried using drivers from this repo, however this made no noticeable difference.

lspci output:

02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)

dmesg output:

[    2.001358] Bluetooth: HCI UART protocol ATH3K registered
[    2.095206] ath10k_pci 0000:02:00.0: enabling device (0000 -> 0002)
[    2.096415] ath10k_pci 0000:02:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[    2.355190] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:02:00.0.bin failed with error -2
[    2.355195] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/cal-pci-0000:02:00.0.bin failed with error -2
[    2.355361] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
[    2.355362] ath10k_pci 0000:02:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
[    2.356551] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
[    2.356552] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
[    2.356944] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5
[    2.419889] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7
[    4.652261] ath10k_pci 0000:02:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[    4.727442] ath: EEPROM regdomain: 0x69
[    4.727444] ath: EEPROM indicates we should expect a direct regpair map
[    4.727449] ath: Country alpha2 being used: 00
[    4.727450] ath: Regpair used: 0x69
[    4.733345] ath10k_pci 0000:02:00.0 wlp2s0: renamed from wlan0
[17053.869439]  nls_cp437 vfat fat rtsx_pci_ms memstick ath10k_pci ath10k_core ath mac80211 cfg80211 mei_me drm_kms_helper mei drm ip6t_REJECT idma64 nf_reject_ipv6 nf_log_ipv6 intel_lpss_pci intel_gtt syscopyarea sysfillrect sysimgblt fb_sys_fops i2c_algo_bit shpchp processor_thermal_device intel_soc_dts_iosf xt_hl ip6t_rt thermal i2c_hid hid nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG hci_uart xt_limit xt_tcpudp btbcm btqca btintel xt_addrtype bluetooth dell_smo8800 rfkill nf_conntrack_ipv4 nf_defrag_ipv4 intel_lpss_acpi video wmi intel_lpss xt_conntrack int3403_thermal battery int340x_thermal_zone int3400_thermal acpi_thermal_rel intel_hid sparse_keymap acpi_pad ac ip6table_filter button ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast acpi_als
[17053.869531]  [<ffffffff8107ec3d>] warn_slowpath_null+0x1d/0x20
[17053.869537]  [<ffffffffa0675e34>] ? ath10k_pci_interrupt_handler+0x74/0xd0 [ath10k_pci]

iw output:

Wiphy phy0
	max # scan SSIDs: 16
	max scan IEs length: 195 bytes
	max # sched scan SSIDs: 0
	max # match sets: 0
	max # scan plans: 1
	max scan plan interval: -1
	max scan plan iterations: 0
	Retry short limit: 7
	Retry long limit: 4
	Coverage class: 0 (up to 0m)
	Device supports RSN-IBSS.
	Device supports AP-side u-APSD.
	Device supports T-DLS.
	Supported Ciphers:
		* WEP40 (00-0f-ac:1)
		* WEP104 (00-0f-ac:5)
		* TKIP (00-0f-ac:2)
		* CCMP-128 (00-0f-ac:4)
		* CMAC (00-0f-ac:6)
	Available Antennas: TX 0x3 RX 0x3
	Configured Antennas: TX 0x3 RX 0x3
	Supported interface modes:
		 * IBSS
		 * managed
		 * AP
		 * AP/VLAN
		 * monitor
		 * mesh point
		 * P2P-client
		 * P2P-GO
		 * P2P-device
	Band 1:
		Capabilities: 0x19ef
			RX LDPC
			HT20/HT40
			SM Power Save disabled
			RX HT20 SGI
			RX HT40 SGI
			TX STBC
			RX STBC 1-stream
			Max AMSDU length: 7935 bytes
			DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: 8 usec (0x06)
		HT TX/RX MCS rate indexes supported: 0-15
		Bitrates (non-HT):
			* 1.0 Mbps
			* 2.0 Mbps (short preamble supported)
			* 5.5 Mbps (short preamble supported)
			* 11.0 Mbps (short preamble supported)
			* 6.0 Mbps
			* 9.0 Mbps
			* 12.0 Mbps
			* 18.0 Mbps
			* 24.0 Mbps
			* 36.0 Mbps
			* 48.0 Mbps
			* 54.0 Mbps
		Frequencies:
			* 2412 MHz [1] (20.0 dBm)
			* 2417 MHz [2] (20.0 dBm)
			* 2422 MHz [3] (20.0 dBm)
			* 2427 MHz [4] (20.0 dBm)
			* 2432 MHz [5] (20.0 dBm)
			* 2437 MHz [6] (20.0 dBm)
			* 2442 MHz [7] (20.0 dBm)
			* 2447 MHz [8] (20.0 dBm)
			* 2452 MHz [9] (20.0 dBm)
			* 2457 MHz [10] (20.0 dBm)
			* 2462 MHz [11] (20.0 dBm)
			* 2467 MHz [12] (20.0 dBm)
			* 2472 MHz [13] (disabled)
			* 2484 MHz [14] (disabled)
	Band 2:
		Capabilities: 0x19ef
			RX LDPC
			HT20/HT40
			SM Power Save disabled
			RX HT20 SGI
			RX HT40 SGI
			TX STBC
			RX STBC 1-stream
			Max AMSDU length: 7935 bytes
			DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: 8 usec (0x06)
		HT TX/RX MCS rate indexes supported: 0-15
		VHT Capabilities (0x339071b2):
			Max MPDU length: 11454
			Supported Channel Width: neither 160 nor 80+80
			RX LDPC
			short GI (80 MHz)
			TX STBC
			SU Beamformee
			MU Beamformee
			RX antenna pattern consistency
			TX antenna pattern consistency
		VHT RX MCS set:
			1 streams: MCS 0-9
			2 streams: MCS 0-9
			3 streams: not supported
			4 streams: not supported
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT RX highest supported: 0 Mbps
		VHT TX MCS set:
			1 streams: MCS 0-9
			2 streams: MCS 0-9
			3 streams: not supported
			4 streams: not supported
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT TX highest supported: 0 Mbps
		Bitrates (non-HT):
			* 6.0 Mbps
			* 9.0 Mbps
			* 12.0 Mbps
			* 18.0 Mbps
			* 24.0 Mbps
			* 36.0 Mbps
			* 48.0 Mbps
			* 54.0 Mbps
		Frequencies:
			* 5180 MHz [36] (30.0 dBm)
			* 5200 MHz [40] (30.0 dBm)
			* 5220 MHz [44] (30.0 dBm)
			* 5240 MHz [48] (30.0 dBm) (no IR)
			* 5260 MHz [52] (30.0 dBm) (no IR, radar detection)
			* 5280 MHz [56] (30.0 dBm) (no IR, radar detection)
			* 5300 MHz [60] (30.0 dBm) (no IR, radar detection)
			* 5320 MHz [64] (30.0 dBm) (no IR, radar detection)
			* 5500 MHz [100] (30.0 dBm) (no IR, radar detection)
			* 5520 MHz [104] (30.0 dBm) (no IR, radar detection)
			* 5540 MHz [108] (30.0 dBm) (no IR, radar detection)
			* 5560 MHz [112] (30.0 dBm) (no IR, radar detection)
			* 5580 MHz [116] (30.0 dBm) (no IR, radar detection)
			* 5600 MHz [120] (30.0 dBm) (no IR, radar detection)
			* 5620 MHz [124] (30.0 dBm) (no IR, radar detection)
			* 5640 MHz [128] (30.0 dBm) (no IR, radar detection)
			* 5660 MHz [132] (30.0 dBm) (no IR, radar detection)
			* 5680 MHz [136] (30.0 dBm) (no IR, radar detection)
			* 5700 MHz [140] (30.0 dBm) (no IR, radar detection)
			* 5720 MHz [144] (30.0 dBm) (no IR)
			* 5745 MHz [149] (30.0 dBm) (no IR)
			* 5765 MHz [153] (30.0 dBm)
			* 5785 MHz [157] (30.0 dBm)
			* 5805 MHz [161] (30.0 dBm) (no IR)
			* 5825 MHz [165] (30.0 dBm) (no IR)
	Supported commands:
		 * new_interface
		 * set_interface
		 * new_key
		 * start_ap
		 * new_station
		 * new_mpath
		 * set_mesh_config
		 * set_bss
		 * authenticate
		 * associate
		 * deauthenticate
		 * disassociate
		 * join_ibss
		 * join_mesh
		 * remain_on_channel
		 * set_tx_bitrate_mask
		 * frame
		 * frame_wait_cancel
		 * set_wiphy_netns
		 * set_channel
		 * set_wds_peer
		 * tdls_mgmt
		 * tdls_oper
		 * probe_client
		 * set_noack_map
		 * register_beacons
		 * start_p2p_device
		 * set_mcast_rate
		 * channel_switch
		 * set_qos_map
		 * connect
		 * disconnect
	Supported TX frame types:
		 * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
	Supported RX frame types:
		 * IBSS: 0x40 0xb0 0xc0 0xd0
		 * managed: 0x40 0xd0
		 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * mesh point: 0xb0 0xc0 0xd0
		 * P2P-client: 0x40 0xd0
		 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * P2P-device: 0x40 0xd0
	WoWLAN support:
		 * wake up on disconnect
		 * wake up on magic packet
		 * wake up on pattern match, up to 22 patterns of 1-148 bytes,
		   maximum packet offset 128 bytes
	software interface modes (can always be added):
		 * AP/VLAN
		 * monitor
	valid interface combinations:
		 * #{ managed } <= 2, #{ AP, mesh point, P2P-client, P2P-GO } <= 2, #{ P2P-device } <= 1,
		   total <= 4, #channels <= 1
		 * #{ managed } <= 2, #{ P2P-client } <= 2, #{ AP, mesh point, P2P-GO } <= 1, #{ P2P-device } <= 1,
		   total <= 4, #channels <= 2
		 * #{ managed } <= 1, #{ IBSS } <= 1,
		   total <= 2, #channels <= 1
	HT Capability overrides:
		 * MCS: ff ff ff ff ff ff ff ff ff ff
		 * maximum A-MSDU length
		 * supported channel width
		 * short GI for 40 MHz
		 * max A-MPDU length exponent
		 * min MPDU start spacing
	Device supports TX status socket option.
	Device supports HT-IBSS.
	Device supports SAE with AUTHENTICATE command
	Device supports scan flush.
	Device supports AP scan.
	Device supports per-vif TX power setting
	Driver supports full state transitions for AP/GO clients
	Driver supports a userspace MPM
	Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
	Device supports static SMPS
	Device supports configuring vdev MAC-addr on create.
	Device supports VHT-IBSS.

Has anyone had a better experience with this wireless card? Any assistance or pointers would be greatly appreciated!

Offline

#2 2017-02-05 16:21:22

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,347

Re: Killer 1535 Wireless Card - Extremely Poor Upload Speeds

What is the output of iw dev wlo1 link  ?

Replace wlo1 with what your card is called -- I did not see it in your output.
Is your regulatory domain set?  Check with iw reg get
Mine is not set.   I had to do some magic to achieve 480Mb/s on this Intel chip, but I don't remember what it was.  Let me poke around....

Edit:  The dev name was there.... wlp2s0

Last edited by ewaller (2017-02-05 16:22:17)

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#3 2017-02-05 22:12:40

gilbertw1
Member
Registered: 2016-04-27
Posts: 14

Re: Killer 1535 Wireless Card - Extremely Poor Upload Speeds

Hey, thanks for responding! the output of 'iw dev wlp2s0 link' is:

Connected to 10:da:43:cc:e0:e3 (on wlp2s0)
        SSID: GilbertManor-5G
        freq: 5765
        RX: 367230 bytes (1877 packets)
        TX: 104682 bytes (565 packets)
        signal: -37 dBm
        tx bitrate: 6.0 MBit/s

        bss flags:      short-slot-time
        dtim period:    2
        beacon int:     100

Also, 'iw reg get' results in:

global
country 00: DFS-UNSET
        (2402 - 2472 @ 40), (6, 20), (N/A)
        (2457 - 2482 @ 20), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN
        (2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN
        (5170 - 5250 @ 80), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN
        (5250 - 5330 @ 80), (6, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN
        (5490 - 5730 @ 160), (6, 20), (0 ms), DFS, PASSIVE-SCAN
        (5735 - 5835 @ 80), (6, 20), (N/A), PASSIVE-SCAN
        (57240 - 63720 @ 2160), (N/A, 0), (N/A)

I'm guessing 'DFS-UNSET' means that it is not set. What is the significance of this?

Thanks!

Offline

#4 2017-02-05 22:34:21

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,347

Re: Killer 1535 Wireless Card - Extremely Poor Upload Speeds

Dang.  

ewaller@turing ~ 1003 %iw dev wlo1 link
Connected to d0:17:c2:60:24:5c (on wlo1)
	SSID: Woodlyn-hi
	freq: 5180
	RX: 192418956 bytes (242374 packets)
	TX: 24537757 bytes (122842 packets)
	signal: -50 dBm
	tx bitrate: 433.3 MBit/s VHT-MCS 9 80MHz short GI VHT-NSS 1

	bss flags:	short-slot-time
	dtim period:	3
	beacon int:	100
ewaller@turing ~ 1004 %iw reg get
global
country 00: DFS-UNSET
	(2402 - 2472 @ 40), (N/A, 20), (N/A)
	(2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, NO-IR
	(2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, NO-IR
	(5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, NO-IR
	(5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, NO-IR
	(5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, NO-IR
	(5735 - 5835 @ 80), (N/A, 20), (N/A), NO-IR
	(57240 - 63720 @ 2160), (N/A, 0), (N/A)

ewaller@turing ~ 1005 %

Yeah, the regulatory environment is not set, but neither is mine.  I've I little higher Tx bit rate than do you.  It appears you are not in AC mode.
Edit:  and your bands/capabilities are different than mine.  Can you change the frequency of your router to be in the 5170 to 5250 GHz range?  Also, I note that all your channel bandwidths are 20MHz, no 40 or 80MHz.  Not great.

Last edited by ewaller (2017-02-05 22:39:27)

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#5 2017-02-05 23:00:09

gilbertw1
Member
Registered: 2016-04-27
Posts: 14

Re: Killer 1535 Wireless Card - Extremely Poor Upload Speeds

I couldn't find how to change the frequency, however I did connect to the wireless router that AT&T provided and it's frequency is at 5200:

Connected to f8:18:97:da:89:52 (on wlp2s0)
        SSID: ATT65rY4jA
        freq: 5200
        RX: 29611 bytes (189 packets)
        TX: 13036 bytes (103 packets)
        signal: -51 dBm
        tx bitrate: 6.0 MBit/s

        bss flags:      short-preamble short-slot-time
        dtim period:    2
        beacon int:     100

I experience the exact same upload issue on this network as well, unfortunately.

Offline

#6 2017-02-09 15:23:49

Psychokiller
Member
Registered: 2017-02-09
Posts: 1

Re: Killer 1535 Wireless Card - Extremely Poor Upload Speeds

Hi,

I had the same issue.  This appears to be an issue with the Ath10k driver. Try this patch in mac.c.  Once I did, I started see transmit rates of around 575mbps:
 
 
--- a/drivers/net/wireless/ath/ath10k/mac.c
+++ b/drivers/net/wireless/ath/ath10k/mac.c
@@ -3563,6 +3563,8 @@ static void ath10k_tx(struct ieee80211_hw *hw,
        struct ieee80211_hdr *hdr = (struct ieee80211_hdr *)skb->data;
        __le16 fc = hdr->frame_control;
 
+       skb_orphan(skb);
+
        /* We should disable CCK RATE due to P2P */
        if (info->flags & IEEE80211_TX_CTL_NO_CCK_RATE)

Offline

#7 2017-02-09 15:33:09

gilbertw1
Member
Registered: 2016-04-27
Posts: 14

Re: Killer 1535 Wireless Card - Extremely Poor Upload Speeds

Awesome, thanks for the reply! I gave up pretty quickly and purchased an Intel card replacement which has all around performed much better so far:

  https://www.amazon.com/gp/product/B0197 … UTF8&psc=1

I'll put the killer card back in and test this solution when I get a chance.

Offline

#8 2017-06-02 06:58:27

cookiemonster
Member
Registered: 2017-06-02
Posts: 4

Re: Killer 1535 Wireless Card - Extremely Poor Upload Speeds

Thanks a lot, the patch worked for my system.

Offline

#9 2018-02-09 15:21:00

idovitz
Member
Registered: 2011-08-24
Posts: 7

Re: Killer 1535 Wireless Card - Extremely Poor Upload Speeds

Same problem here on my new Clevo P775TM1 with Killer 1535, tried the latest firmwares from https://github.com/kvalo/ath10k-firmwar … er/QCA6174. Tried to patch the solution posted by PsychoKiller (see above).

result iperf between openwrt and laptop:
[  5] local XXX.XXX.XXX.118 port 54208 connected with XXX.XXX.XXX.1 port 5001
[  5]  0.0-10.1 sec  1.75 MBytes  1.46 Mbits/sec
[  4] local XXX.XXX.XXX.118 port 5001 connected with XXX.XXX.XXX.1 port 55412
[  4]  0.0-10.0 sec   398 MBytes   333 Mbits/sec

Is there any option left or is this HW related?

Offline

Pages: 1

Board footer

Powered by FluxBB