5GHz AP on a QCA988x

[Jeroen Roovers]

When I set it to XZ (which is a work in progress) I get this output:

country XZ: DFS-UNSET
        (2402 - 2472 @ 40), (N/A, 20), (N/A)
        (2457 - 2482 @ 20), (N/A, 20), (N/A)
        (2474 - 2494 @ 20), (N/A, 20), (N/A)
        (5170 - 5250 @ 80), (N/A, 20), (N/A)
        (5250 - 5330 @ 80), (N/A, 20), (N/A)
        (5490 - 5730 @ 160), (N/A, 20), (N/A)
        (5735 - 5835 @ 80), (N/A, 20), (N/A)

[67530.824570] cfg80211: Regulatory domain changed to country: XZ
[67530.824573] cfg80211:  DFS Master region: unset
[67530.824577] cfg80211:   (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp), (dfs_cac_time)
[67530.824583] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz),
(N/A, 2000 mBm), (N/A)
[67530.824588] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz),
(N/A, 2000 mBm), (N/A)
[67530.824592] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz),
(N/A, 2000 mBm), (N/A)
[67530.824597] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz),
(N/A, 2000 mBm), (N/A)
[67530.824601] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz),
(N/A, 2000 mBm), (N/A)
[67530.824605] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz),
(N/A, 2000 mBm), (N/A)
[67530.824610] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz),
(N/A, 2000 mBm), (N/A)
[67590.826500] cfg80211: Verifying active interfaces after reg change



On 21 January 2016 at 10:15, Jeroen Roovers <jeroen.roovers at airfi.aero> wrote:
> country 00: DFS-UNSET
>         (2402 - 2472 @ 40), (6, 20), (N/A)
>         (2457 - 2482 @ 40), (6, 20), (N/A), PASSIVE-SCAN
>         (2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN
>         (5170 - 5250 @ 160), (6, 20), (N/A), PASSIVE-SCAN
>         (5250 - 5330 @ 160), (6, 20), (0 ms), DFS, 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)
>
> [   13.587870] ath10k_pci 0000:02:00.0: pci irq msi interrupts 1
> irq_mode 0 reset_mode 0
> [   14.062943] ath10k_pci 0000:02:00.0: Direct firmware load for
> ath10k/cal-pci-0000:02:00.0.bin failed with error -2
> [   14.327191] ath10k_pci 0000:02:00.0: Direct firmware load for
> ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
> [   15.625794] ath10k_pci 0000:02:00.0: qca988x hw2.0 (0x4100016c,
> 0x043202ff sub 0000:0000) fw 10.2.4.70.17-2 fwapi 5 bdapi 1 htt-ver
> 2.1 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1 features
> no-p2p,raw-mode
> [   15.625796] ath10k_pci 0000:02:00.0: debug 1 debugfs 1 tracing 1
> dfs 1 testmode 0
> [   15.686817] ath: EEPROM regdomain: 0x6a
> [   15.686818] ath: EEPROM indicates we should expect a direct regpair map
> [   15.686820] ath: Country alpha2 being used: 00
> [   15.686820] ath: Regpair used: 0x6a
> [67009.248697] ath10k_pci 0000:02:00.0: pci irq msi interrupts 1
> irq_mode 0 reset_mode 0
> [67009.379191] ath10k_pci 0000:02:00.0: Direct firmware load for
> ath10k/cal-pci-0000:02:00.0.bin failed with error -2
> [67009.435156] ath10k_pci 0000:02:00.0: Direct firmware load for
> ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
> [67010.635063] ath10k_pci 0000:02:00.0: qca988x hw2.0 (0x4100016c,
> 0x043202ff sub 0000:0000) fw 10.2.4.70.17-2 fwapi 5 bdapi 1 htt-ver
> 2.1 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1 features
> no-p2p,raw-mode
> [67010.635101] ath10k_pci 0000:02:00.0: debug 1 debugfs 1 tracing 1
> dfs 1 testmode 0
> [67010.695143] ath: EEPROM regdomain: 0x6a
> [67010.695150] ath: EEPROM indicates we should expect a direct regpair map
> [67010.695156] ath: Country alpha2 being used: 00
> [67010.695159] ath: Regpair used: 0x6a
>
> On 21 January 2016 at 09:52, Michal Kazior <michal.kazior at tieto.com> wrote:
>> On 21 January 2016 at 09:38, Jeroen Roovers <jeroen.roovers at airfi.aero> wrote:
>>> 02:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac
>>> Wireless Network Adapter
>>>         Flags: bus master, fast devsel, latency 0, IRQ 28
>>>         Memory at fe200000 (64-bit, non-prefetchable) [size=2M]
>>>         Expansion ROM at fe400000 [disabled] [size=64K]
>>>         Capabilities: [40] Power Management version 2
>>>         Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
>>>         Capabilities: [70] Express Endpoint, MSI 00
>>>         Capabilities: [100] Advanced Error Reporting
>>>         Capabilities: [140] Virtual Channel
>>>         Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
>>>         Kernel driver in use: ath10k_pci
>>>         Kernel modules: ath10k_pci
>>>
>>> Vendor/device ID: 168c:003c
>>>
>>> I am trying to get a 5GHZ AP working on the above device, using a
>>> Linux 4.4.0 kernel on a generic PC right now, in hopes of getting same
>>> to work on an embedded (ARM, but it's not important) system in the
>>> near future.
>>>
>>> Any attempt to get that up ends in a regulatory-based refusal to open
>>> IR on any 5GHz band frequency, even when I add "regulatory onus" and a
>>> new XZ region (hey, this is intended to work especially in
>>> "international waters") in a db.txt I define myself which should grant
>>> everything I ever wanted. Is there something the firmware is
>>> overriding here?
>>>
>>> Firmware as of the latest would be:
>>>
>>> /lib/firmware/ath10k/QCA988X/hw2.0/firmware-5.bin_10.2.4.70.17-2
>>>
>>> I could attach logs but I thought I might be missing something very obvious.
>>
>> "iw list" and "iw reg get" is very good start. Kernel log will be
>> useful as well to know device regulatory.
>>
>> Do you have other wifi cards on this system? I recall this could cause
>> problems. Not sure if that's still the case but may be worth
>> considering.
>>
>> In case you're not aware: channels rules are a result of intersected
>> system level regulatory and device (taken from eeprom) regulatory.
>> This can sometimes confuse because you think you're setting region XZ
>> which allows use of channel 36 but it remains unavailable due to the
>> device's regulatory.
>>
>>
>> Michał