* 5GHz AP on a QCA988x
@ 2016-01-21 8:38 Jeroen Roovers
2016-01-21 8:52 ` Michal Kazior
0 siblings, 1 reply; 8+ messages in thread
From: Jeroen Roovers @ 2016-01-21 8:38 UTC (permalink / raw)
To: ath10k
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.
Kind regards,
jer
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: 5GHz AP on a QCA988x 2016-01-21 8:38 5GHz AP on a QCA988x Jeroen Roovers @ 2016-01-21 8:52 ` Michal Kazior 2016-01-21 9:15 ` Jeroen Roovers 0 siblings, 1 reply; 8+ messages in thread From: Michal Kazior @ 2016-01-21 8:52 UTC (permalink / raw) To: Jeroen Roovers; +Cc: ath10k@lists.infradead.org On 21 January 2016 at 09:38, Jeroen Roovers <jeroen.roovers@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ł _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: 5GHz AP on a QCA988x 2016-01-21 8:52 ` Michal Kazior @ 2016-01-21 9:15 ` Jeroen Roovers 2016-01-21 9:20 ` Jeroen Roovers 2016-01-22 8:26 ` Michal Kazior 0 siblings, 2 replies; 8+ messages in thread From: Jeroen Roovers @ 2016-01-21 9:15 UTC (permalink / raw) To: Michal Kazior; +Cc: ath10k@lists.infradead.org [-- Attachment #1: Type: text/plain, Size: 4555 bytes --] 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@tieto.com> wrote: > On 21 January 2016 at 09:38, Jeroen Roovers <jeroen.roovers@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ł [-- Attachment #2: iw-list.txt --] [-- Type: text/plain, Size: 8132 bytes --] Wiphy phy0 max # scan SSIDs: 16 max scan IEs length: 195 bytes Retry short limit: 7 Retry long limit: 4 Coverage class: 0 (up to 0m) Device supports RSN-IBSS. Device supports AP-side u-APSD. Supported Ciphers: * WEP40 (00-0f-ac:1) * WEP104 (00-0f-ac:5) * TKIP (00-0f-ac:2) * CCMP (00-0f-ac:4) * CMAC (00-0f-ac:6) Available Antennas: TX 0x7 RX 0x7 Configured Antennas: TX 0x7 RX 0x7 Supported interface modes: * managed * AP * AP/VLAN * monitor * mesh point Band 1: Capabilities: 0x19e3 RX LDPC HT20/HT40 Static SM Power Save 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 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) (no IR) * 2472 MHz [13] (20.0 dBm) (no IR) * 2484 MHz [14] (disabled) Band 2: Capabilities: 0x19e3 RX LDPC HT20/HT40 Static SM Power Save 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 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] (20.0 dBm) (no IR) * 5200 MHz [40] (20.0 dBm) (no IR) * 5220 MHz [44] (20.0 dBm) (no IR) * 5240 MHz [48] (20.0 dBm) (no IR) * 5260 MHz [52] (20.0 dBm) (no IR, radar detection) DFS state: usable (for 55 sec) DFS CAC time: 60000 ms * 5280 MHz [56] (20.0 dBm) (no IR, radar detection) DFS state: usable (for 55 sec) DFS CAC time: 60000 ms * 5300 MHz [60] (20.0 dBm) (no IR, radar detection) DFS state: usable (for 55 sec) DFS CAC time: 60000 ms * 5320 MHz [64] (20.0 dBm) (no IR, radar detection) DFS state: usable (for 55 sec) DFS CAC time: 60000 ms * 5500 MHz [100] (20.0 dBm) (no IR, radar detection) DFS state: usable (for 55 sec) DFS CAC time: 60000 ms * 5520 MHz [104] (20.0 dBm) (no IR, radar detection) DFS state: usable (for 55 sec) DFS CAC time: 60000 ms * 5540 MHz [108] (20.0 dBm) (no IR, radar detection) DFS state: usable (for 55 sec) DFS CAC time: 60000 ms * 5560 MHz [112] (20.0 dBm) (no IR, radar detection) DFS state: usable (for 55 sec) DFS CAC time: 60000 ms * 5580 MHz [116] (20.0 dBm) (no IR, radar detection) DFS state: usable (for 55 sec) DFS CAC time: 60000 ms * 5600 MHz [120] (20.0 dBm) (no IR, radar detection) DFS state: usable (for 55 sec) DFS CAC time: 60000 ms * 5620 MHz [124] (20.0 dBm) (no IR, radar detection) DFS state: usable (for 55 sec) DFS CAC time: 60000 ms * 5640 MHz [128] (20.0 dBm) (no IR, radar detection) DFS state: usable (for 55 sec) DFS CAC time: 60000 ms * 5660 MHz [132] (20.0 dBm) (no IR, radar detection) DFS state: usable (for 55 sec) DFS CAC time: 60000 ms * 5680 MHz [136] (20.0 dBm) (no IR, radar detection) DFS state: usable (for 55 sec) DFS CAC time: 60000 ms * 5700 MHz [140] (20.0 dBm) (no IR, radar detection) DFS state: usable (for 55 sec) DFS CAC time: 60000 ms * 5720 MHz [144] (20.0 dBm) (no IR) * 5745 MHz [149] (20.0 dBm) (no IR) * 5765 MHz [153] (20.0 dBm) (no IR) * 5785 MHz [157] (20.0 dBm) (no IR) * 5805 MHz [161] (20.0 dBm) (no IR) * 5825 MHz [165] (20.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 * probe_client * set_noack_map * register_beacons * start_p2p_device * set_mcast_rate * channel_switch * Unknown command (104) * 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 software interface modes (can always be added): * AP/VLAN * monitor valid interface combinations: * #{ AP, mesh point } <= 8, 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 Device supports TX status socket option. Device supports HT-IBSS. Device supports SAE with AUTHENTICATE command Device supports scan flush. Device supports per-vif TX power setting Driver supports a userspace MPM Driver/device bandwidth changes during BSS lifetime (AP/GO mode) Device supports static SMPS [-- Attachment #3: Type: text/plain, Size: 146 bytes --] _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: 5GHz AP on a QCA988x 2016-01-21 9:15 ` Jeroen Roovers @ 2016-01-21 9:20 ` Jeroen Roovers 2016-01-22 8:26 ` Michal Kazior 1 sibling, 0 replies; 8+ messages in thread From: Jeroen Roovers @ 2016-01-21 9:20 UTC (permalink / raw) To: Michal Kazior; +Cc: ath10k@lists.infradead.org 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@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@tieto.com> wrote: >> On 21 January 2016 at 09:38, Jeroen Roovers <jeroen.roovers@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ł _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: 5GHz AP on a QCA988x 2016-01-21 9:15 ` Jeroen Roovers 2016-01-21 9:20 ` Jeroen Roovers @ 2016-01-22 8:26 ` Michal Kazior 2016-01-22 10:11 ` Jeroen Roovers 1 sibling, 1 reply; 8+ messages in thread From: Michal Kazior @ 2016-01-22 8:26 UTC (permalink / raw) To: Jeroen Roovers; +Cc: ath10k@lists.infradead.org On 21 January 2016 at 10:15, Jeroen Roovers <jeroen.roovers@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 If I'm this right it says your regulatory for the card is world regulatory. This means 5GHz is pretty much locked out - at least for APs (which initiate radiation, NO-IR flag on all channels). For comparison, one of my QCA99X0's says: [ 4450.629243] ath: EEPROM regdomain: 0x0 [ 4450.629248] ath: EEPROM indicates default country code should be used [ 4450.629250] ath: doing EEPROM country->regdmn map search [ 4450.629252] ath: country maps to regdmn code: 0x3a [ 4450.629254] ath: Country alpha2 being used: US [ 4450.629256] ath: Regpair used: 0x3a Here's a command snippet from my system for comparison: ; uname -a Linux bob-0-ec-vm 4.4.0-wt-ath+ #21 SMP Thu Jan 21 13:20:41 CET 2016 x86_64 GNU/Linux ; iw --version iw version 4.1-1-g182ef7d07a61-dirty ; iw reg get global country US: DFS-FCC (2402 - 2472 @ 40), (N/A, 30), (N/A) (5170 - 5250 @ 80), (N/A, 17), (N/A), AUTO-BW (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS (5735 - 5835 @ 80), (N/A, 30), (N/A) (57240 - 63720 @ 2160), (N/A, 40), (N/A) phy#0 country US: DFS-FCC (2402 - 2472 @ 40), (N/A, 30), (N/A) (5170 - 5250 @ 80), (N/A, 17), (N/A), AUTO-BW (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS (5735 - 5835 @ 80), (N/A, 30), (N/A) (57240 - 63720 @ 2160), (N/A, 40), (N/A) ; iw list | grep -F 'MHz [' * 5180 MHz [36] (17.0 dBm) * 5200 MHz [40] (17.0 dBm) * 5220 MHz [44] (17.0 dBm) * 5240 MHz [48] (17.0 dBm) * 5260 MHz [52] (23.0 dBm) (no IR, radar detection) * 5280 MHz [56] (23.0 dBm) (no IR, radar detection) * 5300 MHz [60] (23.0 dBm) (no IR, radar detection) * 5320 MHz [64] (23.0 dBm) (no IR, radar detection) * 5500 MHz [100] (23.0 dBm) (no IR, radar detection) * 5520 MHz [104] (23.0 dBm) (no IR, radar detection) * 5540 MHz [108] (23.0 dBm) (no IR, radar detection) * 5560 MHz [112] (23.0 dBm) (no IR, radar detection) * 5580 MHz [116] (23.0 dBm) (no IR, radar detection) * 5600 MHz [120] (23.0 dBm) (no IR, radar detection) * 5620 MHz [124] (23.0 dBm) (no IR, radar detection) * 5640 MHz [128] (23.0 dBm) (no IR, radar detection) * 5660 MHz [132] (23.0 dBm) (no IR, radar detection) * 5680 MHz [136] (23.0 dBm) (no IR, radar detection) * 5700 MHz [140] (23.0 dBm) (no IR, radar detection) * 5720 MHz [144] (23.0 dBm) (radar detection) * 5745 MHz [149] (30.0 dBm) * 5765 MHz [153] (30.0 dBm) * 5785 MHz [157] (30.0 dBm) * 5805 MHz [161] (30.0 dBm) * 5825 MHz [165] (30.0 dBm) Michał _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: 5GHz AP on a QCA988x 2016-01-22 8:26 ` Michal Kazior @ 2016-01-22 10:11 ` Jeroen Roovers 2016-01-22 14:43 ` Ben Greear 0 siblings, 1 reply; 8+ messages in thread From: Jeroen Roovers @ 2016-01-22 10:11 UTC (permalink / raw) To: Michal Kazior; +Cc: ath10k@lists.infradead.org So I would somehow need to fix the EEPROM, then? :) On 22 January 2016 at 09:26, Michal Kazior <michal.kazior@tieto.com> wrote: > On 21 January 2016 at 10:15, Jeroen Roovers <jeroen.roovers@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 > > If I'm this right it says your regulatory for the card is world > regulatory. This means 5GHz is pretty much locked out - at least for > APs (which initiate radiation, NO-IR flag on all channels). > > For comparison, one of my QCA99X0's says: > > [ 4450.629243] ath: EEPROM regdomain: 0x0 > [ 4450.629248] ath: EEPROM indicates default country code should be used > [ 4450.629250] ath: doing EEPROM country->regdmn map search > [ 4450.629252] ath: country maps to regdmn code: 0x3a > [ 4450.629254] ath: Country alpha2 being used: US > [ 4450.629256] ath: Regpair used: 0x3a > > Here's a command snippet from my system for comparison: > > ; uname -a > Linux bob-0-ec-vm 4.4.0-wt-ath+ #21 SMP Thu Jan 21 13:20:41 CET 2016 > x86_64 GNU/Linux > ; iw --version > iw version 4.1-1-g182ef7d07a61-dirty > ; iw reg get > global > country US: DFS-FCC > (2402 - 2472 @ 40), (N/A, 30), (N/A) > (5170 - 5250 @ 80), (N/A, 17), (N/A), AUTO-BW > (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW > (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS > (5735 - 5835 @ 80), (N/A, 30), (N/A) > (57240 - 63720 @ 2160), (N/A, 40), (N/A) > > phy#0 > country US: DFS-FCC > (2402 - 2472 @ 40), (N/A, 30), (N/A) > (5170 - 5250 @ 80), (N/A, 17), (N/A), AUTO-BW > (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW > (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS > (5735 - 5835 @ 80), (N/A, 30), (N/A) > (57240 - 63720 @ 2160), (N/A, 40), (N/A) > > ; iw list | grep -F 'MHz [' > * 5180 MHz [36] (17.0 dBm) > * 5200 MHz [40] (17.0 dBm) > * 5220 MHz [44] (17.0 dBm) > * 5240 MHz [48] (17.0 dBm) > * 5260 MHz [52] (23.0 dBm) (no IR, radar detection) > * 5280 MHz [56] (23.0 dBm) (no IR, radar detection) > * 5300 MHz [60] (23.0 dBm) (no IR, radar detection) > * 5320 MHz [64] (23.0 dBm) (no IR, radar detection) > * 5500 MHz [100] (23.0 dBm) (no IR, radar detection) > * 5520 MHz [104] (23.0 dBm) (no IR, radar detection) > * 5540 MHz [108] (23.0 dBm) (no IR, radar detection) > * 5560 MHz [112] (23.0 dBm) (no IR, radar detection) > * 5580 MHz [116] (23.0 dBm) (no IR, radar detection) > * 5600 MHz [120] (23.0 dBm) (no IR, radar detection) > * 5620 MHz [124] (23.0 dBm) (no IR, radar detection) > * 5640 MHz [128] (23.0 dBm) (no IR, radar detection) > * 5660 MHz [132] (23.0 dBm) (no IR, radar detection) > * 5680 MHz [136] (23.0 dBm) (no IR, radar detection) > * 5700 MHz [140] (23.0 dBm) (no IR, radar detection) > * 5720 MHz [144] (23.0 dBm) (radar detection) > * 5745 MHz [149] (30.0 dBm) > * 5765 MHz [153] (30.0 dBm) > * 5785 MHz [157] (30.0 dBm) > * 5805 MHz [161] (30.0 dBm) > * 5825 MHz [165] (30.0 dBm) > > > Michał _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: 5GHz AP on a QCA988x 2016-01-22 10:11 ` Jeroen Roovers @ 2016-01-22 14:43 ` Ben Greear 2016-01-22 16:42 ` Jeroen Roovers 0 siblings, 1 reply; 8+ messages in thread From: Ben Greear @ 2016-01-22 14:43 UTC (permalink / raw) To: Jeroen Roovers, Michal Kazior; +Cc: ath10k@lists.infradead.org On 01/22/2016 02:11 AM, Jeroen Roovers wrote: > So I would somehow need to fix the EEPROM, then? :) You just need to hack the driver to change the regulatory domain. You do not need to muck with the firmware or eeprom or anything like that. http://dmz2.candelatech.com/?p=linux-4.0.dev.y/.git;a=commitdiff;h=6f8337e5380a59fe498cea96d096bef4c60b4201;hp=f936faa45dc793704ff35f135473f1c390054f4d Thanks, Ben -- Ben Greear <greearb@candelatech.com> Candela Technologies Inc http://www.candelatech.com _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: 5GHz AP on a QCA988x 2016-01-22 14:43 ` Ben Greear @ 2016-01-22 16:42 ` Jeroen Roovers 0 siblings, 0 replies; 8+ messages in thread From: Jeroen Roovers @ 2016-01-22 16:42 UTC (permalink / raw) To: Ben Greear; +Cc: Michal Kazior, ath10k@lists.infradead.org On 22 January 2016 at 15:43, Ben Greear <greearb@candelatech.com> wrote: > http://dmz2.candelatech.com/?p=linux-4.0.dev.y/.git;a=commitdiff;h=6f8337e5380a59fe498cea96d096bef4c60b4201;hp=f936faa45dc793704ff35f135473f1c390054f4d That looks promising, thanks. Regards, jer _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2016-01-22 16:42 UTC | newest] Thread overview: 8+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2016-01-21 8:38 5GHz AP on a QCA988x Jeroen Roovers 2016-01-21 8:52 ` Michal Kazior 2016-01-21 9:15 ` Jeroen Roovers 2016-01-21 9:20 ` Jeroen Roovers 2016-01-22 8:26 ` Michal Kazior 2016-01-22 10:11 ` Jeroen Roovers 2016-01-22 14:43 ` Ben Greear 2016-01-22 16:42 ` Jeroen Roovers
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.