WiFi 5GHz and 2.4GHz signal is barely usable

Omnia hardware Omnia HW problems
#1

Hi.

I needed a replacement for my Fritz!Box router and thought I’d do myself a favor and ordered a Turris Omnia 2020.

Sorry to say this, but after fiddling with it the last couple days it seems to me this device’s wifi is unusable.

Somehow, the first wifi adapter (which is set to 5GHz mode) does not show up at all when scanning. It looks like this in Luci:

image

The system logs shows:

Apr  6 10:58:50 turris kernel: [   11.958953] ath10k_pci 0000:02:00.0: enabling device (0140 -> 0142)
Apr  6 10:58:50 turris kernel: [   11.965527] ath10k_pci 0000:02:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
Apr  6 10:58:50 turris kernel: [   12.213974] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:02:00.0.bin failed with error -2
Apr  6 10:58:50 turris kernel: [   12.224716] ath10k_pci 0000:02:00.0: Falling back to user helper
Apr  6 10:58:50 turris kernel: [   12.585048] firmware ath10k!pre-cal-pci-0000:02:00.0.bin: firmware_loading_store: map pages failed
Apr  6 10:58:50 turris kernel: [   12.594230] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/cal-pci-0000:02:00.0.bin failed with error -2
Apr  6 10:58:50 turris kernel: [   12.604619] ath10k_pci 0000:02:00.0: Falling back to user helper
Apr  6 10:58:50 turris kernel: [   12.615294] firmware ath10k!cal-pci-0000:02:00.0.bin: firmware_loading_store: map pages failed
Apr  6 10:58:50 turris kernel: [   12.624096] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-6.bin failed with error -2
Apr  6 10:58:50 turris kernel: [   12.634834] ath10k_pci 0000:02:00.0: Falling back to user helper
Apr  6 10:58:50 turris kernel: [   12.645658] firmware ath10k!QCA988X!hw2.0!firmware-6.bin: firmware_loading_store: map pages failed
Apr  6 10:58:50 turris kernel: [   12.662953] ath10k_pci 0000:02:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
Apr  6 10:58:50 turris kernel: [   12.672212] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
Apr  6 10:58:50 turris kernel: [   12.681739] ath10k_pci 0000:02:00.0: firmware ver 10.2.4-1.0-00047 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 35bd9258
Apr  6 10:58:50 turris kernel: [   12.726526] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
Apr  6 10:58:50 turris kernel: [   12.736998] ath10k_pci 0000:02:00.0: Falling back to user helper
Apr  6 10:58:50 turris kernel: [   12.747773] firmware ath10k!QCA988X!hw2.0!board-2.bin: firmware_loading_store: map pages failed
Apr  6 10:58:50 turris kernel: [   12.757793] ath10k_pci 0000:02:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
Apr  6 10:58:50 turris kernel: [   13.896936] ath10k_pci 0000:02:00.0: htt-ver 2.1 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1
Apr  6 10:58:50 turris kernel: [   19.643064] ath10k_pci 0000:02:00.0: pdev param 0 not supported by firmware

Nonetheless, the card seems to be initialized, but I get no signal… EDIT: the problem was that I set the channel to “auto”, which – regardless of the country set to DE – choose channel 169. AFAICS, this channel is not something that is supported throughout Europe. Manually setting it to a 108, made the network appear when scanning… but has even worse signal quality than the second card.

The second adapater works, but has really sh*tty signal quality. Even the integrated AP of my printer has a better signal… And of course, the old Fritz!Box which I had planned to replace with the omnia also has better signal quality (but only does 2.4GHz).

I just cannot believe that people pay a premium for such mediocre set up. Does anyone have some tips what I could try (apart from replacing the wifi cards and antennas)? Everything in the router seems to be tightly connected and antennas are fixated properly.

I think I’ll have to return the omnia and get a different router… :frowning_face:

#2

Before that I’d (personally) at least look inside and check the antenna cabling.

#3

Thanks, already did that and just double checked again. Both cables from the larger card are connected to the right pins of the diplexer which are labelled as “5.3” and the cables from the smaller card are connected to the ones labelled “2.1”.

1 Like
#4

FTR:

Hostname
turris
Model
Turris Omnia
Architecture
ARMv7 Processor rev 1 (v7l)
Firmware Version
TurrisOS 5.1.10 a5672f6b96f393145070ad17c8eb1d15ef49ad2e / LuCI branch git-21.062.76689-a607f9c
Kernel Version
4.14.222
#5

Also when you set 5Ghz card there is something called DFS and its scanning for weather radars and stuff before turning the card on so you just have to wait a bit longer on certain channels. I have two Omnias and they cover the house pretty well. Maximum wifi power also depends on the country set.
Take a look at this page for reference:

#6

ad_DFS: https://openwrt.org/docs/guide-user/network/wifi/basic#dfsradar_detection
iw list will list info for each radio (where you can find which channels are using DFS).
iw reg get will show regulatory info for your country (if country is set correctly).

ad_HT/VHT: if you are using 2,4 and 5 together, do not use HT40 on 2.4 radio. for 5 one, consider to lower the VHT160 to VHT80 or even to 40 for a while.

Wi-Fi standard allows 10, 20, 22, 40, 80 and 160 MHz but 10MHz is not used anymore, the 80 and 160 can be used only with 5 GHz frequency, and certain devices not being able to connect to APs with channel widths more than 40Mhz.

#7

iw phy1 info
and
iw phy0 info

#8

I do own a MOX that - I think - has the same Atheros wireless card. Initially my MOX was in a corner of the home and I found wifi quite weak. I finally moved the MOX to a more central position and I am much happier. Also if you are in an area with many neighbours then there will be a lot of competition around 2.4GHz bands so you need to choose one with less possible interference.
This sensitivity might be linked to the type of antenna fitted on Turris devices.

#9 
root@turris:~# iw phy0 info
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 AP-side u-APSD.
	Available Antennas: TX 0x7 RX 0x7
	Configured Antennas: TX 0x7 RX 0x7
	Supported interface modes:
		 * managed
		 * AP
		 * monitor
		 * mesh point
	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-23
		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] (20.0 dBm)
			* 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-23
		VHT Capabilities (0x338001b2):
			Max MPDU length: 11454
			Supported Channel Width: neither 160 nor 80+80
			RX LDPC
			short GI (80 MHz)
			TX STBC
			RX antenna pattern consistency
			TX antenna pattern consistency
		VHT RX MCS set:
			1 streams: MCS 0-9
			2 streams: MCS 0-9
			3 streams: MCS 0-9
			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: MCS 0-9
			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
		Frequencies:
			* 5180 MHz [36] (23.0 dBm)
			* 5200 MHz [40] (23.0 dBm)
			* 5220 MHz [44] (23.0 dBm)
			* 5240 MHz [48] (23.0 dBm)
			* 5260 MHz [52] (20.0 dBm) (radar detection)
			* 5280 MHz [56] (20.0 dBm) (radar detection)
			* 5300 MHz [60] (20.0 dBm) (radar detection)
			* 5320 MHz [64] (20.0 dBm) (radar detection)
			* 5500 MHz [100] (26.0 dBm) (radar detection)
			* 5520 MHz [104] (26.0 dBm) (radar detection)
			* 5540 MHz [108] (26.0 dBm) (radar detection)
			* 5560 MHz [112] (26.0 dBm) (radar detection)
			* 5580 MHz [116] (26.0 dBm) (radar detection)
			* 5600 MHz [120] (26.0 dBm) (radar detection)
			* 5620 MHz [124] (26.0 dBm) (radar detection)
			* 5640 MHz [128] (26.0 dBm) (radar detection)
			* 5660 MHz [132] (26.0 dBm) (radar detection)
			* 5680 MHz [136] (26.0 dBm) (radar detection)
			* 5700 MHz [140] (26.0 dBm) (radar detection)
			* 5720 MHz [144] (disabled)
			* 5745 MHz [149] (13.0 dBm)
			* 5765 MHz [153] (13.0 dBm)
			* 5785 MHz [157] (13.0 dBm)
			* 5805 MHz [161] (13.0 dBm)
			* 5825 MHz [165] (13.0 dBm)
			* 5845 MHz [169] (13.0 dBm)
			* 5865 MHz [173] (13.0 dBm)
	valid interface combinations:
		 * #{ AP, mesh point } <= 8, #{ managed } <= 1,
		   total <= 8, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }

	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
	Supported extended features:
		* [ VHT_IBSS ]: VHT-IBSS
		* [ RRM ]: RRM
		* [ SET_SCAN_DWELL ]: scan dwell setting
		* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
		* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
		* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs

Wiphy phy1
	max # scan SSIDs: 4
	max scan IEs length: 2257 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 AP-side u-APSD.
	Device supports T-DLS.
	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
		 * outside context of a BSS
	Band 1:
		Capabilities: 0x11ee
			HT20/HT40
			SM Power Save disabled
			RX HT20 SGI
			RX HT40 SGI
			TX STBC
			RX STBC 1-stream
			Max AMSDU length: 3839 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
		Frequencies:
			* 2412 MHz [1] (19.0 dBm)
			* 2417 MHz [2] (19.0 dBm)
			* 2422 MHz [3] (19.0 dBm)
			* 2427 MHz [4] (19.0 dBm)
			* 2432 MHz [5] (19.0 dBm)
			* 2437 MHz [6] (19.0 dBm)
			* 2442 MHz [7] (19.0 dBm)
			* 2447 MHz [8] (19.0 dBm)
			* 2452 MHz [9] (19.0 dBm)
			* 2457 MHz [10] (19.0 dBm)
			* 2462 MHz [11] (19.0 dBm)
			* 2467 MHz [12] (19.0 dBm)
			* 2472 MHz [13] (19.0 dBm)
			* 2484 MHz [14] (disabled)
	valid interface combinations:
		 * #{ managed } <= 2048, #{ AP, mesh point } <= 8, #{ P2P-client, P2P-GO } <= 1, #{ IBSS } <= 1,
		   total <= 2048, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz }

	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
	Supported extended features:
		* [ RRM ]: RRM
		* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
		* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
		* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
#10

You can see maximal powers in dBm for specific channel and as well if its radar scanning. Make a choice depending on this.

#11

Hi Knut,
let me apologize for the inconvenience with our product. We are ready to help you.
Please be so kind and contact our Support - e-mail address is info@turris.cz. Please attach the diagnostics file from your device. [1]
[1] https://docs.turris.cz/basics/support/#getting-logs
I am looking forward to hearing of you.
Sincerely
Marcela from Turris Support Team