* RE: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
[not found] <mailman.7.1667674802.1691884.ath11k@lists.infradead.org>
@ 2022-11-07 16:07 ` Nagarajan Maran (QUIC)
2022-11-07 18:57 ` Mariusz
[not found] ` <CAJrE-q73Jt8MfGn4bbyPs_VEb5DcjLMb7BWBp5MjMDjhZ2g5Wg@mail.gmail.com>
0 siblings, 2 replies; 18+ messages in thread
From: Nagarajan Maran (QUIC) @ 2022-11-07 16:07 UTC (permalink / raw)
To: enebeo; +Cc: ath11k
Hi Mariusz,
We are looking into this issue. It seems that this error can occur when the given frequency is not present or when the given frequency is disabled.
To further analyze the issue, could you kindly let us know the output of the below commands during failure case.
1) iw dev
2) iw phyX channels
Also, could you kindly send the WiFi driver boot up logs with "debug_mask=0x212" enabled during insmod of ath11k.ko module.
Thanks,
Nagarajan M.
-----Original Message-----
From: Mariusz <enebeo@gmail.com>
To: ath11k@lists.infradead.org
Subject: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
Message-ID:
<CAJrE-q6NVEF4sNW1s4Zz7Pb2ryzCi69e+_vLQswBWm747DHYDw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hi,
As support for QCN9074 got better I went ahead and built a 6E linux based AP. Dell R720 server x86 running Linux s4 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64
x86_64 x86_64 GNU/Linux.
My issue is that I cannot get it working on 6GHz bands but it works fine on 5GHz. I bought 6E version and since this is a single band module it cannot be both 5G & 6G and linux driver does not agree with it being 6E version:
[71914.038562] ath11k_pci 0000:03:00.0: BAR 0: assigned [mem 0xdf800000-0xdf9fffff 64bit] [71914.038840] ath11k_pci 0000:03:00.0: MSI vectors: 16 [71914.038852] ath11k_pci 0000:03:00.0: qcn9074 hw1.0 [71914.194459] mhi mhi0: Requested to power ON [71914.194712] mhi mhi0: Power on setup success [71914.297749] mhi mhi0: Wait for device to enter SBL or Mission mode [71914.647118] ath11k_pci 0000:03:00.0: chip_id 0x0 chip_family 0x0 board_id 0xff soc_id 0xffffffff [71914.647134] ath11k_pci 0000:03:00.0: fw_version 0x250a04b8 fw_build_timestamp 2021-12-20 06:41 fw_build_id [71916.310787] ath11k_pci 0000:03:00.0 wlp3s0: renamed from wlan0
HE PHY Capabilities: (0x1c604c88ffdb839c110c00):
HE40/HE80/5GHz
HE160/5GHz
HE160/HE80+80/5GHz
iw dev wlp3s0 set freq 6195 160MHz
kernel reports: Channel is disabled
command failed: Invalid argument (-22)
I am using the latest firmware files from ath11k tree. Is there any special firmware to force this to 6GHz? I read somewhere board_id determines which one it is and 255 disables 6GHz but I miss more data on that.
phy#2 (self-managed)
country US: DFS-FCC
(2402 - 2472 @ 40), (6, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 30), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS, AUTO-BW
(5735 - 5895 @ 160), (N/A, 30), (N/A), AUTO-BW
(5945 - 7125 @ 160), (N/A, 30), (N/A), NO-OUTDOOR, AUTO-BW
It works fine in 5GHz but this is not what I purchased it for, so I am puzzled if this is something in software or I was sold wrong hardware.Is there a specific board-2.bin for 6GHz? Since the 9074 chip is the same in all versions perhaps this is a software hiccup.
Any clues are welcome.
Regards,
Mario
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
2022-11-07 16:07 ` Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band Nagarajan Maran (QUIC)
@ 2022-11-07 18:57 ` Mariusz
2022-11-08 21:03 ` Mariusz
[not found] ` <CAJrE-q73Jt8MfGn4bbyPs_VEb5DcjLMb7BWBp5MjMDjhZ2g5Wg@mail.gmail.com>
1 sibling, 1 reply; 18+ messages in thread
From: Mariusz @ 2022-11-07 18:57 UTC (permalink / raw)
To: Nagarajan Maran (QUIC); +Cc: ath11k
Hi!
To start I am trying to use it as SoftAP not a 6E client. I did some
research and in part this issue appears to be due to a wrong board_id.
It is set to 0xff = 255 which is not loading 6GHz firmware but a
default 255 firmware from board-2.bin blob. I extracted from
board-2.bin firmware for board 162 and renamed it to board.bin. Now
the module is loading firmware with Band 4 and 6GHz channels. But it
would be too beautiful that it works right away, so it is pretending
to be working but when set to mode master (SoftAP) in hostapd, none of
my Intel AX210 160Mhz client is able to see this ssid. I am attaching
what I have collected so far.
1.
root@s4:/usr/lib/modules/5.19.
0-23-generic/kernel/drivers/net/wireless/ath/ath11k#
rmmod ath11k_pci
root@s4:/usr/lib/modules/5.19.0-23-generic/kernel/drivers/net/wireless/ath/ath11k#
rmmod ath11k
root@s4:/usr/lib/modules/5.19.0-23-generic/kernel/drivers/net/wireless/ath/ath11k#
insmod ath11k.ko debug_mask=0x212
root@s4:/usr/lib/modules/5.19.0-23-generic/kernel/drivers/net/wireless/ath/ath11k#
insmod ath11k_pci.ko
2.
Nov 7 18:01:08 s4 systemd[1]: systemd-rfkill.service: Deactivated successfully.
Nov 7 18:01:29 s4 kernel: [ 3734.630406] ath11k_pci 0000:01:00.0: BAR
0: assigned [mem 0xf7c00000-0xf7dfffff 64bit]
Nov 7 18:01:29 s4 kernel: [ 3734.630515] ath11k_pci 0000:01:00.0: MSI
vectors: 1
Nov 7 18:01:29 s4 kernel: [ 3734.630522] ath11k_pci 0000:01:00.0: qcn9074 hw1.0
Nov 7 18:01:29 s4 kernel: [ 3734.784909] mhi mhi0: Requested to power ON
Nov 7 18:01:29 s4 kernel: [ 3734.785124] mhi mhi0: Power on setup success
Nov 7 18:01:29 s4 kernel: [ 3734.886704] mhi mhi0: Wait for device to
enter SBL or Mission mode
Nov 7 18:01:29 s4 kernel: [ 3735.257623] ath11k_pci 0000:01:00.0:
chip_id 0x0 chip_family 0x0 board_id 0xff soc_id 0xffffffff
Nov 7 18:01:29 s4 kernel: [ 3735.257638] ath11k_pci 0000:01:00.0:
fw_version 0x250a04b8 fw_build_timestamp 2021-12-20 06:41 fw_build_id
Nov 7 18:01:31 s4 kernel: [ 3736.587053] ath11k_pci 0000:01:00.0:
leaving PCI ASPM disabled to avoid MHI M2 problems
Nov 7 18:01:31 s4 kernel: [ 3736.933304] ath11k_pci 0000:01:00.0
wlp1s0: renamed from wlan0
Nov 7 18:01:31 s4 systemd[1]: Starting Load/Save RF Kill Switch Status...
Nov 7 18:01:31 s4 systemd[1]: Started Load/Save RF Kill Switch Status.
Nov 7 18:01:31 s4 systemd-networkd[711]: wlan0: Interface name change
detected, renamed to wlp1s0.
Nov 7 18:01:34 s4 ModemManager[824]: <info> [base-manager] couldn't
check support for device
'/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0': not supported by
any plugin
Nov 7 18:01:36 s4 systemd[1]: systemd-rfkill.service: Deactivated successfully.
Nov 7 18:10:08 s4 systemd-networkd[711]: wlp1s0: Link UP
Nov 7 18:10:11 s4 systemd-networkd[711]: wlp1s0: Gained carrier
Nov 7 18:10:11 s4 kernel: [ 4257.237326] IPv6:
ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
Nov 7 18:10:13 s4 systemd-networkd[711]: wlp1s0: Gained IPv6LL
Nov 7 18:11:32 s4 systemd-networkd[711]: wlp1s0: Lost carrier
Nov 7 18:11:32 s4 systemd-networkd[711]: wlp1s0: Link DOWN
Nov 7 18:11:37 s4 systemd-networkd[711]: wlp1s0: Link UP
Nov 7 18:11:40 s4 systemd-networkd[711]: wlp1s0: Gained carrier
Nov 7 18:11:40 s4 kernel: [ 4346.125158] IPv6:
ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
Nov 7 18:11:42 s4 systemd-networkd[711]: wlp1s0: Gained IPv6LL
3.
root@s4:/home/angel/hostapd-2.10/hostapd# iw dev
phy#2
Interface wlp1s0
ifindex 7
wdev 0x200000001
addr c4:4b:d1:d0:00:7e
ssid test
type AP
channel 33 (6115 MHz), width: 80 MHz, center1: 6145 MHz
txpower 30.00 dBm
root@s4:/usr/lib/modules/5.19.0-23-generic/kernel/drivers/net/wireless/ath/ath11k#
iw phy2 channels
Band 4:
* 5955 MHz [1]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 5975 MHz [5]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 5995 MHz [9]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6015 MHz [13]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6035 MHz [17]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6055 MHz [21]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6075 MHz [25]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6095 MHz [29]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6115 MHz [33]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6135 MHz [37]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6155 MHz [41]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6175 MHz [45]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6195 MHz [49]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6215 MHz [53]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6235 MHz [57]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6255 MHz [61]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6275 MHz [65]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6295 MHz [69]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6315 MHz [73]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6335 MHz [77]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6355 MHz [81]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6375 MHz [85]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6395 MHz [89]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6415 MHz [93]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6435 MHz [97]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6455 MHz [101]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6475 MHz [105]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6495 MHz [109]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6515 MHz [113]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6535 MHz [117]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6555 MHz [121]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6575 MHz [125]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6595 MHz [129]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6615 MHz [133]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6635 MHz [137]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6655 MHz [141]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6675 MHz [145]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6695 MHz [149]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6715 MHz [153]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6735 MHz [157]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6755 MHz [161]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6775 MHz [165]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6795 MHz [169]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6815 MHz [173]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6835 MHz [177]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6855 MHz [181]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6875 MHz [185]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6895 MHz [189]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6915 MHz [193]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6935 MHz [197]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6955 MHz [201]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6975 MHz [205]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 6995 MHz [209]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 7015 MHz [213]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 7035 MHz [217]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 7055 MHz [221]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 7075 MHz [225]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 7095 MHz [229]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 7115 MHz [233]
Maximum TX power: 30.0 dBm
Channel widths: 20MHz
* 5935 MHz [2] (disabled)
4.
Now with hostapd pretending to work, it does not error out on 6GHz
freq anymore, it starts on channel 33 but no client can see it
root@s4:/home/angel/hostapd-2.10/hostapd# ./hostapd hostapd.conf&
[1] 2008
root@s4:/home/angel/hostapd-2.10/hostapd# wlp1s0: interface state
UNINITIALIZED->COUNTRY_UPDATE
ACS: Automatic channel selection started, this may take a bit
wlp1s0: interface state COUNTRY_UPDATE->ACS
wlp1s0: ACS-STARTED
wlp1s0: ACS-COMPLETED freq=6115 channel=33
wlp1s0: interface state ACS->ENABLED
wlp1s0: AP-ENABLED
Should work, no?
5. and the config
root@s4:/home/angel/hostapd-2.10/hostapd# cat hostapd.conf | grep -v
'^#' | grep . | more
interface=wlp1s0
driver=nl80211
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
ssid=test
country_code=BE
ieee80211d=1
ieee80211h=1
hw_mode=a
channel=0
op_class=133
acs_num_scans=1
beacon_int=100
dtim_period=2
max_num_sta=255
rts_threshold=-1
fragm_threshold=-1
macaddr_acl=0
ieee80211w=2
auth_algs=3
ignore_broadcast_ssid=0
wmm_enabled=1
wmm_ac_bk_cwmin=4
wmm_ac_bk_cwmax=10
wmm_ac_bk_aifs=7
wmm_ac_bk_txop_limit=0
wmm_ac_bk_acm=0
wmm_ac_be_aifs=3
wmm_ac_be_cwmin=4
wmm_ac_be_cwmax=10
wmm_ac_be_txop_limit=0
wmm_ac_be_acm=0
wmm_ac_vi_aifs=2
wmm_ac_vi_cwmin=3
wmm_ac_vi_cwmax=4
wmm_ac_vi_txop_limit=94
wmm_ac_vi_acm=0
wmm_ac_vo_aifs=2
wmm_ac_vo_cwmin=2
wmm_ac_vo_cwmax=3
wmm_ac_vo_txop_limit=47
wmm_ac_vo_acm=0
ieee80211ax=1
eapol_key_index_workaround=0
eap_server=0
own_ip_addr=127.0.0.1
wpa=2
wpa_key_mgmt=SAE
rsn_pairwise=CCMP
group_cipher=CCMP
sae_password=testtest
sae_require_mfp=1
sae_pwe=1
Client, windows 11, country BE, lower 6E bands are approved for use
per regulatory domain, Intel AX210 160MHz, latest driver:22.170.0.
Physically external 5V power is connected as well as 4x antenna
pigtails and external antennas (5dbi).
Any light on this welcome & thanks for taking the time! There's
nothing else in the logs past this point.
M
On Mon, 7 Nov 2022 at 17:07, Nagarajan Maran (QUIC)
<quic_nmaran@quicinc.com> wrote:
>
> Hi Mariusz,
>
> We are looking into this issue. It seems that this error can occur when the given frequency is not present or when the given frequency is disabled.
> To further analyze the issue, could you kindly let us know the output of the below commands during failure case.
> 1) iw dev
> 2) iw phyX channels
>
> Also, could you kindly send the WiFi driver boot up logs with "debug_mask=0x212" enabled during insmod of ath11k.ko module.
>
> Thanks,
> Nagarajan M.
>
> -----Original Message-----
>
> From: Mariusz <enebeo@gmail.com>
> To: ath11k@lists.infradead.org
> Subject: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
> Message-ID:
> <CAJrE-q6NVEF4sNW1s4Zz7Pb2ryzCi69e+_vLQswBWm747DHYDw@mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Hi,
>
> As support for QCN9074 got better I went ahead and built a 6E linux based AP. Dell R720 server x86 running Linux s4 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64
> x86_64 x86_64 GNU/Linux.
>
> My issue is that I cannot get it working on 6GHz bands but it works fine on 5GHz. I bought 6E version and since this is a single band module it cannot be both 5G & 6G and linux driver does not agree with it being 6E version:
>
> [71914.038562] ath11k_pci 0000:03:00.0: BAR 0: assigned [mem 0xdf800000-0xdf9fffff 64bit] [71914.038840] ath11k_pci 0000:03:00.0: MSI vectors: 16 [71914.038852] ath11k_pci 0000:03:00.0: qcn9074 hw1.0 [71914.194459] mhi mhi0: Requested to power ON [71914.194712] mhi mhi0: Power on setup success [71914.297749] mhi mhi0: Wait for device to enter SBL or Mission mode [71914.647118] ath11k_pci 0000:03:00.0: chip_id 0x0 chip_family 0x0 board_id 0xff soc_id 0xffffffff [71914.647134] ath11k_pci 0000:03:00.0: fw_version 0x250a04b8 fw_build_timestamp 2021-12-20 06:41 fw_build_id [71916.310787] ath11k_pci 0000:03:00.0 wlp3s0: renamed from wlan0
>
> HE PHY Capabilities: (0x1c604c88ffdb839c110c00):
> HE40/HE80/5GHz
> HE160/5GHz
> HE160/HE80+80/5GHz
>
> iw dev wlp3s0 set freq 6195 160MHz
> kernel reports: Channel is disabled
> command failed: Invalid argument (-22)
>
> I am using the latest firmware files from ath11k tree. Is there any special firmware to force this to 6GHz? I read somewhere board_id determines which one it is and 255 disables 6GHz but I miss more data on that.
>
> phy#2 (self-managed)
> country US: DFS-FCC
> (2402 - 2472 @ 40), (6, 30), (N/A)
> (5170 - 5250 @ 80), (N/A, 30), (N/A), AUTO-BW
> (5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
> (5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS, AUTO-BW
> (5735 - 5895 @ 160), (N/A, 30), (N/A), AUTO-BW
> (5945 - 7125 @ 160), (N/A, 30), (N/A), NO-OUTDOOR, AUTO-BW
>
> It works fine in 5GHz but this is not what I purchased it for, so I am puzzled if this is something in software or I was sold wrong hardware.Is there a specific board-2.bin for 6GHz? Since the 9074 chip is the same in all versions perhaps this is a software hiccup.
>
> Any clues are welcome.
>
> Regards,
> Mario
>
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
2022-11-07 18:57 ` Mariusz
@ 2022-11-08 21:03 ` Mariusz
0 siblings, 0 replies; 18+ messages in thread
From: Mariusz @ 2022-11-08 21:03 UTC (permalink / raw)
To: ath11k
Another interesting finding is that while no client can see my test
6GHz network to connect to, there is in fact something happening over
the air. QCN9074 is transmitting beacon frames on the right frequency
which a remote AX210 client running on ubuntu can see and decode with
help of tshark & airodump. beacon counter is also increasing and
signal strength and AP up time look correct. That would mean QCN9074
switched the frequency correctly to 6GHz and attempts to work as an AP
but something is missing. I checked again regulatory domains and intel
picks up country but self-managed is within the scopeglobalcountry BE:
DFS-ETSI
phy#3 (self-managed)
country EU: DFS-UNSET
from airodump:
airodump-ng -C 6115 -i wlan0mon --bssid C4:4B:D1:D0:00:7E
Freq 6115 ][ Elapsed: 0 s ][ 2022-11-08 19:48
BSSID PWR Beacons #Data, #/s CH MB ENC CIPHER AUTH ESSID
C4:4B:D1:D0:00:7E -46 12 0 0 33 54e WPA3 CCMP SAE dupa
from tshark
802.11 radio information
PHY type: 802.11a (OFDM) (5)
Turbo type: Non-turbo (0)
Data rate: 6.0 Mb/s
Channel: 33
Frequency: 6115MHz
Signal strength (dBm): -47 dBm
TSF timestamp: 1826096995
[Duration: 312µs]
[Preamble: 20µs]
[IFS: 204488µs]
[Start: 1826096683µs]
[End: 1826096995µs]
Why it mentions OFDM not OFDMA?
Other than that it gets SSID, operating class (I played with
20/80/160MHz hence 134 instead of 133), got the country code from the
AP so it is receiving something.
Tagged parameters (175 bytes)
Tag: SSID parameter set: dupa
Tag Number: SSID parameter set (0)
Tag length: 4
SSID: dupa
Tag: Supported Rates 6(B), 9, 12(B), 18, 24(B), 36, 48, 54, [Mbit/sec]
Tag Number: Supported Rates (1)
Tag length: 8
Supported Rates: 6(B) (0x8c)
Supported Rates: 9 (0x12)
Supported Rates: 12(B) (0x98)
Supported Rates: 18 (0x24)
Supported Rates: 24(B) (0xb0)
Supported Rates: 36 (0x48)
Supported Rates: 48 (0x60)
Supported Rates: 54 (0x6c)
Tag: DS Parameter set: Current Channel: 33
Tag Number: DS Parameter set (3)
Tag length: 1
Current Channel: 33
Tag: Traffic Indication Map (TIM): DTIM 1 of 2 bitmap
Tag Number: Traffic Indication Map (TIM) (5)
Tag length: 4
DTIM count: 1
DTIM period: 2
Bitmap control: 0x00
.... ...0 = Multicast: False
0000 000. = Bitmap Offset: 0x00
Partial Virtual Bitmap: 00
Tag: Country Information: Country Code BE, Environment 0x04
Tag Number: Country Information (7)
Tag length: 6
Code: BE
Environment: 4
Country Info: Operating Extension Identifier: 201,
Operating Class: 134, Coverage Class: 0
Operating Extension Identifier: 201
Operating Class: 134
Coverage Class: 0
Tag: RSN Information
Tag Number: RSN Information (48)
Tag length: 20
RSN Version: 1
Group Cipher Suite: 00:0f:ac (Ieee 802.11) AES (CCM)
Group Cipher Suite OUI: 00:0f:ac (Ieee 802.11)
Group Cipher Suite type: AES (CCM) (4)
Pairwise Cipher Suite Count: 1
Pairwise Cipher Suite List 00:0f:ac (Ieee 802.11) AES (CCM)
Pairwise Cipher Suite: 00:0f:ac (Ieee 802.11) AES (CCM)
Pairwise Cipher Suite OUI: 00:0f:ac (Ieee 802.11)
Pairwise Cipher Suite type: AES (CCM) (4)
Auth Key Management (AKM) Suite Count: 1
Auth Key Management (AKM) List 00:0f:ac (Ieee 802.11) SAE (SHA256)
Auth Key Management (AKM) Suite: 00:0f:ac (Ieee
802.11) SAE (SHA256)
Auth Key Management (AKM) OUI: 00:0f:ac (Ieee 802.11)
Auth Key Management (AKM) type: SAE (SHA256) (8)
RSN Capabilities: 0x00cc
.... .... .... ...0 = RSN Pre-Auth capabilities:
Transmitter does not support pre-authentication
.... .... .... ..0. = RSN No Pairwise capabilities:
Transmitter can support WEP default key 0 simultaneously with Pairwise
key
.... .... .... 11.. = RSN PTKSA Replay Counter
capabilities: 16 replay counters per PTKSA/GTKSA/STAKeySA (0x3)
.... .... ..00 .... = RSN GTKSA Replay Counter
capabilities: 1 replay counter per PTKSA/GTKSA/STAKeySA (0x0)
.... .... .1.. .... = Management Frame Protection Required: True
.... .... 1... .... = Management Frame Protection Capable: True
.... ...0 .... .... = Joint Multi-band RSNA: False
.... ..0. .... .... = PeerKey Enabled: False
..0. .... .... .... = Extended Key ID for Individually
On Mon, 7 Nov 2022 at 19:57, Mariusz <enebeo@gmail.com> wrote:
>
> Hi!
>
> To start I am trying to use it as SoftAP not a 6E client. I did some
> research and in part this issue appears to be due to a wrong board_id.
> It is set to 0xff = 255 which is not loading 6GHz firmware but a
> default 255 firmware from board-2.bin blob. I extracted from
> board-2.bin firmware for board 162 and renamed it to board.bin. Now
> the module is loading firmware with Band 4 and 6GHz channels. But it
> would be too beautiful that it works right away, so it is pretending
> to be working but when set to mode master (SoftAP) in hostapd, none of
> my Intel AX210 160Mhz client is able to see this ssid. I am attaching
> what I have collected so far.
>
> 1.
> root@s4:/usr/lib/modules/5.19.
> 0-23-generic/kernel/drivers/net/wireless/ath/ath11k#
> rmmod ath11k_pci
> root@s4:/usr/lib/modules/5.19.0-23-generic/kernel/drivers/net/wireless/ath/ath11k#
> rmmod ath11k
> root@s4:/usr/lib/modules/5.19.0-23-generic/kernel/drivers/net/wireless/ath/ath11k#
> insmod ath11k.ko debug_mask=0x212
> root@s4:/usr/lib/modules/5.19.0-23-generic/kernel/drivers/net/wireless/ath/ath11k#
> insmod ath11k_pci.ko
>
> 2.
> Nov 7 18:01:08 s4 systemd[1]: systemd-rfkill.service: Deactivated successfully.
> Nov 7 18:01:29 s4 kernel: [ 3734.630406] ath11k_pci 0000:01:00.0: BAR
> 0: assigned [mem 0xf7c00000-0xf7dfffff 64bit]
> Nov 7 18:01:29 s4 kernel: [ 3734.630515] ath11k_pci 0000:01:00.0: MSI
> vectors: 1
> Nov 7 18:01:29 s4 kernel: [ 3734.630522] ath11k_pci 0000:01:00.0: qcn9074 hw1.0
> Nov 7 18:01:29 s4 kernel: [ 3734.784909] mhi mhi0: Requested to power ON
> Nov 7 18:01:29 s4 kernel: [ 3734.785124] mhi mhi0: Power on setup success
> Nov 7 18:01:29 s4 kernel: [ 3734.886704] mhi mhi0: Wait for device to
> enter SBL or Mission mode
> Nov 7 18:01:29 s4 kernel: [ 3735.257623] ath11k_pci 0000:01:00.0:
> chip_id 0x0 chip_family 0x0 board_id 0xff soc_id 0xffffffff
> Nov 7 18:01:29 s4 kernel: [ 3735.257638] ath11k_pci 0000:01:00.0:
> fw_version 0x250a04b8 fw_build_timestamp 2021-12-20 06:41 fw_build_id
> Nov 7 18:01:31 s4 kernel: [ 3736.587053] ath11k_pci 0000:01:00.0:
> leaving PCI ASPM disabled to avoid MHI M2 problems
> Nov 7 18:01:31 s4 kernel: [ 3736.933304] ath11k_pci 0000:01:00.0
> wlp1s0: renamed from wlan0
> Nov 7 18:01:31 s4 systemd[1]: Starting Load/Save RF Kill Switch Status...
> Nov 7 18:01:31 s4 systemd[1]: Started Load/Save RF Kill Switch Status.
> Nov 7 18:01:31 s4 systemd-networkd[711]: wlan0: Interface name change
> detected, renamed to wlp1s0.
> Nov 7 18:01:34 s4 ModemManager[824]: <info> [base-manager] couldn't
> check support for device
> '/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0': not supported by
> any plugin
> Nov 7 18:01:36 s4 systemd[1]: systemd-rfkill.service: Deactivated successfully.
> Nov 7 18:10:08 s4 systemd-networkd[711]: wlp1s0: Link UP
> Nov 7 18:10:11 s4 systemd-networkd[711]: wlp1s0: Gained carrier
> Nov 7 18:10:11 s4 kernel: [ 4257.237326] IPv6:
> ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
> Nov 7 18:10:13 s4 systemd-networkd[711]: wlp1s0: Gained IPv6LL
> Nov 7 18:11:32 s4 systemd-networkd[711]: wlp1s0: Lost carrier
> Nov 7 18:11:32 s4 systemd-networkd[711]: wlp1s0: Link DOWN
> Nov 7 18:11:37 s4 systemd-networkd[711]: wlp1s0: Link UP
> Nov 7 18:11:40 s4 systemd-networkd[711]: wlp1s0: Gained carrier
> Nov 7 18:11:40 s4 kernel: [ 4346.125158] IPv6:
> ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
> Nov 7 18:11:42 s4 systemd-networkd[711]: wlp1s0: Gained IPv6LL
>
>
> 3.
>
> root@s4:/home/angel/hostapd-2.10/hostapd# iw dev
> phy#2
> Interface wlp1s0
> ifindex 7
> wdev 0x200000001
> addr c4:4b:d1:d0:00:7e
> ssid test
> type AP
> channel 33 (6115 MHz), width: 80 MHz, center1: 6145 MHz
> txpower 30.00 dBm
>
> root@s4:/usr/lib/modules/5.19.0-23-generic/kernel/drivers/net/wireless/ath/ath11k#
> iw phy2 channels
> Band 4:
> * 5955 MHz [1]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 5975 MHz [5]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 5995 MHz [9]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6015 MHz [13]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6035 MHz [17]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6055 MHz [21]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6075 MHz [25]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6095 MHz [29]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6115 MHz [33]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6135 MHz [37]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6155 MHz [41]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6175 MHz [45]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6195 MHz [49]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6215 MHz [53]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6235 MHz [57]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6255 MHz [61]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6275 MHz [65]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6295 MHz [69]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6315 MHz [73]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6335 MHz [77]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6355 MHz [81]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6375 MHz [85]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6395 MHz [89]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6415 MHz [93]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6435 MHz [97]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6455 MHz [101]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6475 MHz [105]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6495 MHz [109]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6515 MHz [113]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6535 MHz [117]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6555 MHz [121]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6575 MHz [125]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6595 MHz [129]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6615 MHz [133]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6635 MHz [137]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6655 MHz [141]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6675 MHz [145]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6695 MHz [149]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6715 MHz [153]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6735 MHz [157]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6755 MHz [161]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6775 MHz [165]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6795 MHz [169]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6815 MHz [173]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6835 MHz [177]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6855 MHz [181]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6875 MHz [185]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6895 MHz [189]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6915 MHz [193]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6935 MHz [197]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6955 MHz [201]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6975 MHz [205]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6995 MHz [209]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 7015 MHz [213]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 7035 MHz [217]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 7055 MHz [221]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 7075 MHz [225]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 7095 MHz [229]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 7115 MHz [233]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 5935 MHz [2] (disabled)
>
> 4.
> Now with hostapd pretending to work, it does not error out on 6GHz
> freq anymore, it starts on channel 33 but no client can see it
>
> root@s4:/home/angel/hostapd-2.10/hostapd# ./hostapd hostapd.conf&
> [1] 2008
> root@s4:/home/angel/hostapd-2.10/hostapd# wlp1s0: interface state
> UNINITIALIZED->COUNTRY_UPDATE
> ACS: Automatic channel selection started, this may take a bit
> wlp1s0: interface state COUNTRY_UPDATE->ACS
> wlp1s0: ACS-STARTED
> wlp1s0: ACS-COMPLETED freq=6115 channel=33
> wlp1s0: interface state ACS->ENABLED
> wlp1s0: AP-ENABLED
>
> Should work, no?
>
> 5. and the config
> root@s4:/home/angel/hostapd-2.10/hostapd# cat hostapd.conf | grep -v
> '^#' | grep . | more
> interface=wlp1s0
> driver=nl80211
> logger_syslog=-1
> logger_syslog_level=2
> logger_stdout=-1
> logger_stdout_level=2
> ctrl_interface=/var/run/hostapd
> ctrl_interface_group=0
> ssid=test
> country_code=BE
> ieee80211d=1
> ieee80211h=1
> hw_mode=a
> channel=0
> op_class=133
> acs_num_scans=1
> beacon_int=100
> dtim_period=2
> max_num_sta=255
> rts_threshold=-1
> fragm_threshold=-1
> macaddr_acl=0
> ieee80211w=2
> auth_algs=3
> ignore_broadcast_ssid=0
> wmm_enabled=1
> wmm_ac_bk_cwmin=4
> wmm_ac_bk_cwmax=10
> wmm_ac_bk_aifs=7
> wmm_ac_bk_txop_limit=0
> wmm_ac_bk_acm=0
> wmm_ac_be_aifs=3
> wmm_ac_be_cwmin=4
> wmm_ac_be_cwmax=10
> wmm_ac_be_txop_limit=0
> wmm_ac_be_acm=0
> wmm_ac_vi_aifs=2
> wmm_ac_vi_cwmin=3
> wmm_ac_vi_cwmax=4
> wmm_ac_vi_txop_limit=94
> wmm_ac_vi_acm=0
> wmm_ac_vo_aifs=2
> wmm_ac_vo_cwmin=2
> wmm_ac_vo_cwmax=3
> wmm_ac_vo_txop_limit=47
> wmm_ac_vo_acm=0
> ieee80211ax=1
> eapol_key_index_workaround=0
> eap_server=0
> own_ip_addr=127.0.0.1
> wpa=2
> wpa_key_mgmt=SAE
> rsn_pairwise=CCMP
> group_cipher=CCMP
> sae_password=testtest
> sae_require_mfp=1
> sae_pwe=1
>
> Client, windows 11, country BE, lower 6E bands are approved for use
> per regulatory domain, Intel AX210 160MHz, latest driver:22.170.0.
>
> Physically external 5V power is connected as well as 4x antenna
> pigtails and external antennas (5dbi).
>
> Any light on this welcome & thanks for taking the time! There's
> nothing else in the logs past this point.
>
> M
>
> On Mon, 7 Nov 2022 at 17:07, Nagarajan Maran (QUIC)
> <quic_nmaran@quicinc.com> wrote:
> >
> > Hi Mariusz,
> >
> > We are looking into this issue. It seems that this error can occur when the given frequency is not present or when the given frequency is disabled.
> > To further analyze the issue, could you kindly let us know the output of the below commands during failure case.
> > 1) iw dev
> > 2) iw phyX channels
> >
> > Also, could you kindly send the WiFi driver boot up logs with "debug_mask=0x212" enabled during insmod of ath11k.ko module.
> >
> > Thanks,
> > Nagarajan M.
> >
> > -----Original Message-----
> >
> > From: Mariusz <enebeo@gmail.com>
> > To: ath11k@lists.infradead.org
> > Subject: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
> > Message-ID:
> > <CAJrE-q6NVEF4sNW1s4Zz7Pb2ryzCi69e+_vLQswBWm747DHYDw@mail.gmail.com>
> > Content-Type: text/plain; charset="UTF-8"
> >
> > Hi,
> >
> > As support for QCN9074 got better I went ahead and built a 6E linux based AP. Dell R720 server x86 running Linux s4 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64
> > x86_64 x86_64 GNU/Linux.
> >
> > My issue is that I cannot get it working on 6GHz bands but it works fine on 5GHz. I bought 6E version and since this is a single band module it cannot be both 5G & 6G and linux driver does not agree with it being 6E version:
> >
> > [71914.038562] ath11k_pci 0000:03:00.0: BAR 0: assigned [mem 0xdf800000-0xdf9fffff 64bit] [71914.038840] ath11k_pci 0000:03:00.0: MSI vectors: 16 [71914.038852] ath11k_pci 0000:03:00.0: qcn9074 hw1.0 [71914.194459] mhi mhi0: Requested to power ON [71914.194712] mhi mhi0: Power on setup success [71914.297749] mhi mhi0: Wait for device to enter SBL or Mission mode [71914.647118] ath11k_pci 0000:03:00.0: chip_id 0x0 chip_family 0x0 board_id 0xff soc_id 0xffffffff [71914.647134] ath11k_pci 0000:03:00.0: fw_version 0x250a04b8 fw_build_timestamp 2021-12-20 06:41 fw_build_id [71916.310787] ath11k_pci 0000:03:00.0 wlp3s0: renamed from wlan0
> >
> > HE PHY Capabilities: (0x1c604c88ffdb839c110c00):
> > HE40/HE80/5GHz
> > HE160/5GHz
> > HE160/HE80+80/5GHz
> >
> > iw dev wlp3s0 set freq 6195 160MHz
> > kernel reports: Channel is disabled
> > command failed: Invalid argument (-22)
> >
> > I am using the latest firmware files from ath11k tree. Is there any special firmware to force this to 6GHz? I read somewhere board_id determines which one it is and 255 disables 6GHz but I miss more data on that.
> >
> > phy#2 (self-managed)
> > country US: DFS-FCC
> > (2402 - 2472 @ 40), (6, 30), (N/A)
> > (5170 - 5250 @ 80), (N/A, 30), (N/A), AUTO-BW
> > (5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
> > (5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS, AUTO-BW
> > (5735 - 5895 @ 160), (N/A, 30), (N/A), AUTO-BW
> > (5945 - 7125 @ 160), (N/A, 30), (N/A), NO-OUTDOOR, AUTO-BW
> >
> > It works fine in 5GHz but this is not what I purchased it for, so I am puzzled if this is something in software or I was sold wrong hardware.Is there a specific board-2.bin for 6GHz? Since the 9074 chip is the same in all versions perhaps this is a software hiccup.
> >
> > Any clues are welcome.
> >
> > Regards,
> > Mario
> >
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
[not found] ` <MW2PR02MB38992059ED67678172D6604DED059@MW2PR02MB3899.namprd02.prod.outlook.com>
@ 2022-11-15 10:02 ` Mariusz
2022-11-15 18:29 ` walde
2022-11-17 16:51 ` Mariusz
0 siblings, 2 replies; 18+ messages in thread
From: Mariusz @ 2022-11-15 10:02 UTC (permalink / raw)
To: ath11k
Hi,
I have asked the manufacturer to confirm. It has the 6E sticker on it
but I have no lower level tools to read e-fuses if any. Regarding
board_id they say normally on non-x86 this is set by bootloader so it
is not hardcoded in eeprom.
For the HW side, on the PCB there are two markings, 5G (top) and 6E
(bottom), none of them was bridged from the factory. I bridged the 6E
one but that did not change anything. In the meantime I also deployed
aircrack-ng on AX210 client since I have no 6GHz equipment to do other
testing.
On the client:
iw wlp1s0 del
airmon-ng start wlan0mon
tshark -i wlan0mon -T text -V > log.wifi
airodump-ng -C 6115 -i wlan0mon --bssid C4:4B:D1:D0:00:7E
Checking available frequencies, this could take few seconds.
Freq 6115 ][ Elapsed: 0 s ][ 2022-11-08 19:48
BSSID PWR Beacons #Data, #/s CH MB ENC CIPHER AUTH ESSID
C4:4B:D1:D0:00:7E -46 12 0 0 33 54e WPA3 CCMP SAE dupa
So the client is seeing signal strength and beacon packets which are
increasing continuously. It has concluded SSID, MAC and encryption
details correctly on 6E freq - 6115MHz and it is also seeing op class
134 = 160Mhz channel as set. Then I assume electronics at least TX on
QCN9074 is working fine as the remote client is picking up something
but whatever is not right as there's no handshake. I tried to
pre-setup SSID so it auto connects without SSID discovery on Win
client but no juice. So I dumped packet details, not sure if I read
all flags right but there's a mix of it mentioning 6GHz supported &
enabled but in other places OFDM is listed instead of OFDMA. Now which
part of it is due aircrack-ng having all updates to support/decode 6E
don't know, it is another variable here.
802.11 radio information
PHY type: 802.11a (OFDM) (5)
Turbo type: Non-turbo (0)
Data rate: 6.0 Mb/s
Channel: 33
Frequency: 6115MHz
Signal strength (dBm): -47 dBm
TSF timestamp: 1826096995
[Duration: 312µs]
[Preamble: 20µs]
[IFS: 204488µs]
[Start: 1826096683µs]
[End: 1826096995µs]
IEEE 802.11 Beacon frame, Flags: ........C
Type/Subtype: Beacon frame (0x0008)
Frame Control Field: 0x8000
.... ..00 = Version: 0
.... 00.. = Type: Management frame (0)
1000 .... = Subtype: 8
Flags: 0x00
.... ..00 = DS status: Not leaving DS or network is
operating in AD-HOC mode (To DS: 0 From DS: 0) (0x0)
.... .0.. = More Fragments: This is the last fragment
.... 0... = Retry: Frame is not being retransmitted
...0 .... = PWR MGT: STA will stay up
..0. .... = More Data: No data buffered
.0.. .... = Protected flag: Data is not protected
0... .... = +HTC/Order flag: Not strictly ordered
.000 0000 0000 0000 = Duration: 0 microseconds
Receiver address: Broadcast (ff:ff:ff:ff:ff:ff)
Destination address: Broadcast (ff:ff:ff:ff:ff:ff)
Transmitter address: WallysCo_d0:00:7e (c4:4b:d1:d0:00:7e)
Source address: WallysCo_d0:00:7e (c4:4b:d1:d0:00:7e)
BSS Id: WallysCo_d0:00:7e (c4:4b:d1:d0:00:7e)
.... .... .... 0000 = Fragment number: 0
0100 0100 0101 .... = Sequence number: 1093
Frame check sequence: 0xcf64d100 [unverified]
[FCS Status: Unverified]
IEEE 802.11 Wireless Management
Fixed parameters (12 bytes)
Timestamp: 4349132798
Beacon Interval: 0.204800 [Seconds]
Capabilities Information: 0x1011
.... .... .... ...1 = ESS capabilities: Transmitter is an AP
.... .... .... ..0. = IBSS status: Transmitter belongs to a BSS
.... ..0. .... 00.. = CFP participation capabilities: No
point coordinator at AP (0x00)
.... .... ...1 .... = Privacy: AP/STA can support WEP
.... .... ..0. .... = Short Preamble: Not Allowed
.... .... .0.. .... = PBCC: Not Allowed
.... .... 0... .... = Channel Agility: Not in use
.... ...0 .... .... = Spectrum Management: Not Implemented
.... .0.. .... .... = Short Slot Time: Not in use
.... 0... .... .... = Automatic Power Save Delivery: Not Implemented
...1 .... .... .... = Radio Measurement: Implemented
..0. .... .... .... = DSSS-OFDM: Not Allowed
.0.. .... .... .... = Delayed Block Ack: Not Implemented
0... .... .... .... = Immediate Block Ack: Not Implemented
Tagged parameters (175 bytes)
Tag: SSID parameter set: dupa
Tag Number: SSID parameter set (0)
Tag length: 4
SSID: dupa
Tag: Supported Rates 6(B), 9, 12(B), 18, 24(B), 36, 48, 54, [Mbit/sec]
Tag Number: Supported Rates (1)
Tag length: 8
Supported Rates: 6(B) (0x8c)
Supported Rates: 9 (0x12)
Supported Rates: 12(B) (0x98)
Supported Rates: 18 (0x24)
Supported Rates: 24(B) (0xb0)
Supported Rates: 36 (0x48)
Supported Rates: 48 (0x60)
Supported Rates: 54 (0x6c)
Tag: DS Parameter set: Current Channel: 33
Tag Number: DS Parameter set (3)
Tag length: 1
Current Channel: 33
Tag: Traffic Indication Map (TIM): DTIM 1 of 2 bitmap
Tag Number: Traffic Indication Map (TIM) (5)
Tag length: 4
DTIM count: 1
DTIM period: 2
Bitmap control: 0x00
.... ...0 = Multicast: False
0000 000. = Bitmap Offset: 0x00
Partial Virtual Bitmap: 00
Tag: Country Information: Country Code BE, Environment 0x04
Tag Number: Country Information (7)
Tag length: 6
Code: BE
Environment: 4
Country Info: Operating Extension Identifier: 201,
Operating Class: 134, Coverage Class: 0
Operating Extension Identifier: 201
Operating Class: 134
Coverage Class: 0
Tag: RSN Information
Tag Number: RSN Information (48)
Tag length: 20
RSN Version: 1
Group Cipher Suite: 00:0f:ac (Ieee 802.11) AES (CCM)
Group Cipher Suite OUI: 00:0f:ac (Ieee 802.11)
Group Cipher Suite type: AES (CCM) (4)
Pairwise Cipher Suite Count: 1
Pairwise Cipher Suite List 00:0f:ac (Ieee 802.11) AES (CCM)
Pairwise Cipher Suite: 00:0f:ac (Ieee 802.11) AES (CCM)
Pairwise Cipher Suite OUI: 00:0f:ac (Ieee 802.11)
Pairwise Cipher Suite type: AES (CCM) (4)
Auth Key Management (AKM) Suite Count: 1
Auth Key Management (AKM) List 00:0f:ac (Ieee 802.11) SAE (SHA256)
Auth Key Management (AKM) Suite: 00:0f:ac (Ieee
802.11) SAE (SHA256)
Auth Key Management (AKM) OUI: 00:0f:ac (Ieee 802.11)
Auth Key Management (AKM) type: SAE (SHA256) (8)
RSN Capabilities: 0x00cc
.... .... .... ...0 = RSN Pre-Auth capabilities:
Transmitter does not support pre-authentication
.... .... .... ..0. = RSN No Pairwise capabilities:
Transmitter can support WEP default key 0 simultaneously with Pairwise
key
.... .... .... 11.. = RSN PTKSA Replay Counter
capabilities: 16 replay counters per PTKSA/GTKSA/STAKeySA (0x3)
.... .... ..00 .... = RSN GTKSA Replay Counter
capabilities: 1 replay counter per PTKSA/GTKSA/STAKeySA (0x0)
.... .... .1.. .... = Management Frame Protection Required: True
.... .... 1... .... = Management Frame Protection Capable: True
.... ...0 .... .... = Joint Multi-band RSNA: False
.... ..0. .... .... = PeerKey Enabled: False
..0. .... .... .... = Extended Key ID for Individually
Addressed Frames: Not supported
Tag: RM Enabled Capabilities (5 octets)
Tag Number: RM Enabled Capabilities (70)
Tag length: 5
RM Capabilities: 0x72 (octet 1)
.... ...0 = Link Measurement: Disabled
.... ..1. = Neighbor Report: Enabled
.... .0.. = Parallel Measurements: Disabled
.... 0... = Repeated Measurements: Disabled
...1 .... = Beacon Passive Measurement: Enabled
..1. .... = Beacon Active Measurement: Enabled
.1.. .... = Beacon Table Measurement: Supported
0... .... = Beacon Measurement Reporting Conditions: Disabled
RM Capabilities: 0x00 (octet 2)
.... ...0 = Frame Measurement: Disabled
.... ..0. = Channel Load Measurement: Disabled
.... .0.. = Noise Histogram Measurement: Disabled
.... 0... = Statistics Measurement: Disabled
...0 .... = LCI Measurement: Disabled
..0. .... = LCI Azimuth capability: Disabled
.0.. .... = Transmit Stream/Category Measurement: Not supported
0... .... = Triggered Transmit Stream/Category
Measurement: Disabled
RM Capabilities: 0x00 (octet 3)
.... ...0 = AP Channel Report capability: Disabled
.... ..0. = RM MIB capability: Disabled
...0 00.. = Operating Channel Max Measurement Duration: 0
000. .... = Nonoperating Channel Max Measurement Duration: 0
RM Capabilities: 0x00 (octet 4)
.... .000 = Measurement Pilotcapability: 0
.... 0... = Measurement Pilot Transmission Information: Disabled
...0 .... = Neighbor Report TSF Offset: Disabled
..0. .... = RCPI Measurement capability: Disabled
.0.. .... = RSNI Measurement capability: Not supported
0... .... = BSS Average Access Delay capability: Disabled
RM Capabilities: 0x00 (octet 5)
.... ...0 = BSS Available Admission Capacity
capability: Disabled
.... ..0. = Antenna capability: Disabled
.... .0.. = FTM Range Report Capability: Disabled
.... 0... = Civic Location Measurement Capability: Disabled
0000 .... = Reserved: 0x0
Tag: Supported Operating Classes
Tag Number: Supported Operating Classes (59)
Tag length: 2
Current Operating Class: 134
Tag: Extended Capabilities (10 octets)
Tag Number: Extended Capabilities (127)
Tag length: 10
Extended Capabilities: 0x04 (octet 1)
.... ...0 = 20/40 BSS Coexistence Management Support:
Not supported
.... ..0. = Reserved (was On-demand beacon): 0x0
.... .1.. = Extended Channel Switching: Supported
.... 0... = Reserved (was WAVE indication): 0x0
...0 .... = PSMP Capability: Not supported
..0. .... = Reserved: 0x0
.0.. .... = S-PSMP Support: Not supported
0... .... = Event: Not supported
Extended Capabilities: 0x00 (octet 2)
.... ...0 = Diagnostics: Not supported
.... ..0. = Multicast Diagnostics: Not supported
.... .0.. = Location Tracking: Not supported
.... 0... = FMS: Not supported
...0 .... = Proxy ARP Service: Not supported
..0. .... = Collocated Interference Reporting: Not supported
.0.. .... = Civic Location: Not supported
0... .... = Geospatial Location: Not supported
Extended Capabilities: 0x00 (octet 3)
.... ...0 = TFS: Not supported
.... ..0. = WNM Sleep Mode: Not supported
.... .0.. = TIM Broadcast: Not supported
.... 0... = BSS Transition: Not supported
...0 .... = QoS Traffic Capability: Not supported
..0. .... = AC Station Count: Not supported
.0.. .... = Multiple BSSID: Not supported
0... .... = Timing Measurement: Not supported
Extended Capabilities: 0x00 (octet 4)
.... ...0 = Channel Usage: Not supported
.... ..0. = SSID List: Not supported
.... .0.. = DMS: Not supported
.... 0... = UTC TSF Offset: Not supported
...0 .... = TPU Buffer STA Support: Not supported
..0. .... = TDLS Peer PSM Support: Not supported
.0.. .... = TDLS channel switching: Not supported
0... .... = Interworking: Not supported
Extended Capabilities: 0x00 (octet 5)
.... ...0 = QoS Map: Not supported
.... ..0. = EBR: Not supported
.... .0.. = SSPN Interface: Not supported
.... 0... = Reserved: 0x0
...0 .... = MSGCF Capability: Not supported
..0. .... = TDLS Support: Not supported
.0.. .... = TDLS Prohibited: Not supported
0... .... = TDLS Channel Switching Prohibited: Not supported
Extended Capabilities: 0x00 (octet 6)
.... ...0 = Reject Unadmitted Frame: Not supported
.... 000. = Service Interval Granularity: 5 ms (0)
...0 .... = Identifier Location: Not supported
..0. .... = U-APSD Coexistence: Not supported
.0.. .... = WNM Notification: Not supported
0... .... = QAB Capability: 0x0
Extended Capabilities: 0x00 (octet 7)
.... ...0 = UTF-8 SSID: Not supported
.... ..0. = QMF Activated: False
.... .0.. = QMF Reconfiguration Activated: False
.... 0... = Robust AV Streaming: False
...0 .... = Advanced GCR: False
..0. .... = Mesh GCR: False
.0.. .... = SCS: False
0... .... = QLoad Report: False
Extended Capabilities: 0x0040 (octets 8 & 9)
.... .... .... ...0 = Alternate EDCA: False
.... .... .... ..0. = Unprotected TXOP Negotiation: False
.... .... .... .0.. = Protected TXOP Negotiation: False
.... .... .... 0... = Reserved: 0x0
.... .... ...0 .... = Protected QLoad Report: False
.... .... ..0. .... = TDLS Wider Bandwidth: Not supported
.... .... .1.. .... = Operating Mode Notification: Supported
.... ...0 0... .... = Max Number Of MSDUs In A-MSDU:
No limit (0)
.... ..0. .... .... = Channel Schedule Management: False
.... .0.. .... .... = Geodatabase Inband Enabling Signal: False
.... 0... .... .... = Network Channel Control: False
...0 .... .... .... = White Space Map: False
..0. .... .... .... = Channel Availability Query: False
.0.. .... .... .... = Fine Timing Measurement Responder: False
0... .... .... .... = Fine Timing Measurement Initiator: False
Extended Capabilities: 0x40 (octet 10)
.... ...0 = FILS Capable: False
.... ..0. = Extended Spectrum Management Capable: False
.... .0.. = Future Channel Capable: False
.... 0... = Reserved: 0x0
...0 .... = Reserved: 0x0
..0. .... = TWT Requester Support: False
.1.. .... = TWT Responder Support: True
0... .... = OBSS Narrow Bandwidth RU in UL OFDMA
Tolerance Support: False
Tag: Tx Power Envelope
Tag Number: Tx Power Envelope (195)
Tag length: 2
Tx Pwr Info: 0x18
.... .000 = Max Tx Pwr Count: 0
..01 1... = Max Tx Pwr Unit Interpretation: Unknown (3)
00.. .... = Reserved: 0
Local Max Tx Pwr Constraint 20MHz: -1.0 dBm
Tag: Tx Power Envelope
Tag Number: Tx Power Envelope (195)
Tag length: 2
Tx Pwr Info: 0x58
.... .000 = Max Tx Pwr Count: 0
..01 1... = Max Tx Pwr Unit Interpretation: Unknown (3)
01.. .... = Reserved: 1
Local Max Tx Pwr Constraint 20MHz: 5.0 dBm
Tag: RSN eXtension (1 octet)
Tag Number: RSN eXtension (244)
Tag length: 1
RSNX: 0x20 (octet 1)
.... 0000 = RSNX Length: 0
...0 .... = Protected TWT Operations Support: 0
..1. .... = SAE Hash to element: 1
00.. .... = Reserved: 0x0
Ext Tag: HE Capabilities
Tag Number: Element ID Extension (255)
Ext Tag length: 38
Ext Tag Number: HE Capabilities (35)
HE MAC Capabilities Information: 0x10409a18000d
.... .... .... .... .... .... .... .... .... .... ....
...1 = +HTC HE Support: Supported
.... .... .... .... .... .... .... .... .... .... ....
..0. = TWT Requester Support: Not supported
.... .... .... .... .... .... .... .... .... .... ....
.1.. = TWT Responder Support: Supported
.... .... .... .... .... .... .... .... .... .... ...0
1... = Dynamic Fragmentation Support: Level 1 dynamic fragmentation
support (1)
.... .... .... .... .... .... .... .... .... .... 000.
.... = Maximum Number of Fragmented MSDUs: 1
.... .... .... .... .... .... .... .... .... ..00 ....
.... = Minimum Fragment Size: No restriction on minimum payload size
(0)
.... .... .... .... .... .... .... .... .... 00.. ....
.... = Trigger Frame MAC Padding Duration: 0 (0)
.... .... .... .... .... .... .... .... .000 .... ....
.... = Multi-TID Aggregation Rx Support: 0
.... .... .... .... .... .... .... ...0 0... .... ....
.... = HE Link Adaptation Support: No feedback if the STA does not
provide HE MFB (0)
.... .... .... .... .... .... .... ..0. .... .... ....
.... = All Ack Support: Not supported
.... .... .... .... .... .... .... .0.. .... .... ....
.... = TRS Support: Not supported
.... .... .... .... .... .... .... 1... .... .... ....
.... = BSR Support: Supported
.... .... .... .... .... .... ...1 .... .... .... ....
.... = Broadcast TWT Support: Supported
.... .... .... .... .... .... ..0. .... .... .... ....
.... = 32-bit BA Bitmap Support: Not supported
.... .... .... .... .... .... .0.. .... .... .... ....
.... = MU Cascading Support: Not supported
.... .... .... .... .... .... 0... .... .... .... ....
.... = Ack-Enabled Aggregation Support: Not supported
.... .... .... .... .... ...0 .... .... .... .... ....
.... = Reserved: 0x0
.... .... .... .... .... ..1. .... .... .... .... ....
.... = OM Control Support: Supported
.... .... .... .... .... .0.. .... .... .... .... ....
.... = OFDMA RA Support: Not supported
.... .... .... .... ...1 1... .... .... .... .... ....
.... = Maximum A-MPDU Length Exponent Extension: 3
.... .... .... .... ..0. .... .... .... .... .... ....
.... = A-MSDU Fragmentation Support: Not supported
.... .... .... .... .0.. .... .... .... .... .... ....
.... = Flexible TWT Schedule Support: Not supported
.... .... .... .... 1... .... .... .... .... .... ....
.... = Rx Control Frame to MultiBSS: Supported
.... .... .... ...0 .... .... .... .... .... .... ....
.... = BSRP BQRP A-MPDU Aggregation: Not supported
.... .... .... ..0. .... .... .... .... .... .... ....
.... = QTP Support: Not supported
.... .... .... .0.. .... .... .... .... .... .... ....
.... = BQR Support: Not supported
.... .... .... 0... .... .... .... .... .... .... ....
.... = PSR Responder: Not supported
.... .... ...0 .... .... .... .... .... .... .... ....
.... = NDP Feedback Report Support: Not supported
.... .... ..0. .... .... .... .... .... .... .... ....
.... = OPS Support: Not supported
.... .... .1.. .... .... .... .... .... .... .... ....
.... = A-MSDU Not Under BA in Ack-Enabled A-MPDU Support: Supported
.... ..00 0... .... .... .... .... .... .... .... ....
.... = Multi-TID Aggregation Tx Support: 0
.... .0.. .... .... .... .... .... .... .... .... ....
.... = HE Subchannel Selective Transmission Support: Not supported
.... 0... .... .... .... .... .... .... .... .... ....
.... = UL 2x996-tone RU Support: Not supported
...1 .... .... .... .... .... .... .... .... .... ....
.... = OM Control UL MU Data Disable RX Support: Supported
..0. .... .... .... .... .... .... .... .... .... ....
.... = HE Dynamic SM Power Save: Not supported
.0.. .... .... .... .... .... .... .... .... .... ....
.... = Punctured Sounding Support: Not supported
0... .... .... .... .... .... .... .... .... .... ....
.... = HT And VHT Trigger Frame RX Support: Not supported
HE PHY Capabilities Information
.... ...0 = Reserved: 0x0
.... ...0 = Reserved: 0x0
0000 110. = Channel Width Set: 0x06
.... ..0. = Reserved: 0x0
.... .1.. = 40 & 80 MHz in the 5 GHz and 6 GHz
bands: Supported
.... 1... = 160 MHz in the 5 GHz and 6 GHz bands: Supported
...0 .... = 160/80+80 MHz in the 5 GHz and 6 GHz
bands: Not supported
..0. .... = Reserved: 0x0
.0.. .... = 242 tone RUs in the 5 GHz and 6 GHz
bands: Not supported
0... .... = Reserved: 0x0
Bits 8 to 23: 0x4c60
.... .... .... 0000 = Punctured Preamble Rx: 0x0
.... .... ...0 .... = Device Class: Class B Device (0x0)
.... .... ..1. .... = LDPC Coding In Payload: Supported
.... .... .1.. .... = HE SU PPDU With 1x HE-LTF
And 0.8us GI: Supported
.... ...0 0... .... = Midamble Tx/Rx Max NSTS: 1
Space-Time Stream (0x0)
.... ..0. .... .... = NDP With 4x HE-LTF and 3.2us
GI: Not supported
.... .1.. .... .... = STBC Tx <= 80 MHz: Supported
.... 1... .... .... = STBC Rx <= 80 MHz: Supported
...0 .... .... .... = Doppler Tx: Not supported
..0. .... .... .... = Doppler Rx: Not supported
.1.. .... .... .... = Full Bandwidth UL MU-MIMO: Supported
0... .... .... .... = Partial Bandwidth UL
MU-MIMO: Not supported
Bits 24 to 39: 0xfc08
.... .... .... ..00 = DCM Max Constellation Tx:
DCM is not supported (0x0)
.... .... .... .0.. = DCM Max NSS Tx: 1 Spatial Stream (0x0)
.... .... ...0 1... = DCM Max Constellation Rx: BPSK (0x1)
.... .... ..0. .... = DCM Max NSS Rx: 1 Spatial Stream (0x0)
.... .... .0.. .... = Rx Partial BW SU In 20 MHz
HE MU PPDU: Not supported
.... .... 0... .... = SU Beamformer: Not supported
.... ...0 .... .... = SU Beamformee: Not supported
.... ..0. .... .... = MU Beamformer: Not supported
...1 11.. .... .... = Beamformee STS <= 80 MHz: 0x7
111. .... .... .... = Beamformee STS > 80 MHz: 0x7
Bits 40 to 55: 0x83db
.... .... .... .011 = Number Of Sounding
Dimensions <= 80 MHz: 3
.... .... ..01 1... = Number Of Sounding
Dimensions > 80 MHz: 3
.... .... .1.. .... = Ng = 16 SU Feedback: Supported
.... .... 1... .... = Ng = 16 MU Feedback: Supported
.... ...1 .... .... = Codebook Size SU Feedback: Supported
.... ..1. .... .... = Codebook Size MU Feedback: Supported
.... .0.. .... .... = Triggered SU Beamforming
Feedback: Not supported
.... 0... .... .... = Triggered MU Beamforming
Feedback: Not supported
...0 .... .... .... = Triggered CQI Feedback: Not supported
..0. .... .... .... = Partial Bandwidth Extended
Range: Not supported
.0.. .... .... .... = Partial Bandwidth DL
MU-MIMO: Not supported
1... .... .... .... = PPE Thresholds Present: True
Bits 56 to 71: 0x119c
.... .... .... ...0 = PSR-based SR Support: Not supported
.... .... .... ..0. = Power Boost Factor ar
Support: Not supported
.... .... .... .1.. = HE SU PPDU And HE MU PPDU
With 4x HE-LTF And 0.8us GI: Supported
.... .... ..01 1... = Max Nc: Supported
.... .... .0.. .... = STBC Tx > 80 MHz: Not supported
.... .... 1... .... = STBC Rx > 80 MHz: Supported
.... ...1 .... .... = HE ER SU PPDU With 4x HE-LTF
And 0.8us GI: Supported
.... ..0. .... .... = 20 MHz In 40 MHz HE PPDU In
2.4 GHz Band: Not supported
.... .0.. .... .... = 20 MHz In 160/80+80 MHz HE
PPDU: Not supported
.... 0... .... .... = 80 MHz In 160/80+80 MHz HE
PPDU: Not supported
...1 .... .... .... = HE ER SU PPDU With 1x HE-LTF
And 0.8us GI: Supported
..0. .... .... .... = Midamble Tx/Rx 2x And 1x
HE-LTF: Not supported
00.. .... .... .... = DCM Max RU: 242-tone RU (0x0)
Bits 72 to 87: 0x000c
.... .... .... ...0 = Longer Than 16 HE SIG-B OFDM
Symbols Support: Not supported
.... .... .... ..0. = Non-Triggered CQI Feedback:
Not supported
.... .... .... .1.. = Tx 1024-QAM Support <
242-tone RU Support: Supported
.... .... .... 1... = Rx 1024-QAM Support <
242-tone RU Support: Supported
.... .... ...0 .... = Rx Full BW SU Using HE MU
PPDU With Compressed HE-SIG-B: Not supported
.... .... ..0. .... = Rx Full BW SU Using HE MU
PPDU With Non-Compressed HE-SIG-B: Not supported
.... .... 00.. .... = Nominal Packet Padding: 0 µs
for all constellations, Nss and RU allocations (0)
.... ...0 .... .... = HE MU PPDU With More Than
One RU Rx Max N_HE-LTF: 0
0000 000. .... .... = Reserved: 0x00
Supported HE-MCS and NSS Set
Rx and Tx MCS Maps <= 80 MHz
Rx HE-MCS Map <= 80 MHz: 0xffaa
.... .... .... ..10 = Max HE-MCS for 1 SS:
Support for HE-MCS 0-11 (0x2)
.... .... .... 10.. = Max HE-MCS for 2 SS:
Support for HE-MCS 0-11 (0x2)
.... .... ..10 .... = Max HE-MCS for 3 SS:
Support for HE-MCS 0-11 (0x2)
.... .... 10.. .... = Max HE-MCS for 4 SS:
Support for HE-MCS 0-11 (0x2)
.... ..11 .... .... = Max HE-MCS for 5 SS: Not
supported for HE PPDUs (0x3)
.... 11.. .... .... = Max HE-MCS for 6 SS: Not
supported for HE PPDUs (0x3)
..11 .... .... .... = Max HE-MCS for 7 SS: Not
supported for HE PPDUs (0x3)
11.. .... .... .... = Max HE-MCS for 8 SS: Not
supported for HE PPDUs (0x3)
Tx HE-MCS Map <= 80 MHz: 0xffaa
.... .... .... ..10 = Max HE-MCS for 1 SS:
Support for HE-MCS 0-11 (0x2)
.... .... .... 10.. = Max HE-MCS for 2 SS:
Support for HE-MCS 0-11 (0x2)
.... .... ..10 .... = Max HE-MCS for 3 SS:
Support for HE-MCS 0-11 (0x2)
.... .... 10.. .... = Max HE-MCS for 4 SS:
Support for HE-MCS 0-11 (0x2)
.... ..11 .... .... = Max HE-MCS for 5 SS: Not
supported for HE PPDUs (0x3)
.... 11.. .... .... = Max HE-MCS for 6 SS: Not
supported for HE PPDUs (0x3)
..11 .... .... .... = Max HE-MCS for 7 SS: Not
supported for HE PPDUs (0x3)
11.. .... .... .... = Max HE-MCS for 8 SS: Not
supported for HE PPDUs (0x3)
Rx and Tx MCS Maps 160 MHz
Rx HE-MCS Map 160 MHz: 0xffaa
.... .... .... ..10 = Max HE-MCS for 1 SS:
Support for HE-MCS 0-11 (0x2)
.... .... .... 10.. = Max HE-MCS for 2 SS:
Support for HE-MCS 0-11 (0x2)
.... .... ..10 .... = Max HE-MCS for 3 SS:
Support for HE-MCS 0-11 (0x2)
.... .... 10.. .... = Max HE-MCS for 4 SS:
Support for HE-MCS 0-11 (0x2)
.... ..11 .... .... = Max HE-MCS for 5 SS: Not
supported for HE PPDUs (0x3)
.... 11.. .... .... = Max HE-MCS for 6 SS: Not
supported for HE PPDUs (0x3)
..11 .... .... .... = Max HE-MCS for 7 SS: Not
supported for HE PPDUs (0x3)
11.. .... .... .... = Max HE-MCS for 8 SS: Not
supported for HE PPDUs (0x3)
Tx HE-MCS Map 160 MHz: 0xffaa
.... .... .... ..10 = Max HE-MCS for 1 SS:
Support for HE-MCS 0-11 (0x2)
.... .... .... 10.. = Max HE-MCS for 2 SS:
Support for HE-MCS 0-11 (0x2)
.... .... ..10 .... = Max HE-MCS for 3 SS:
Support for HE-MCS 0-11 (0x2)
.... .... 10.. .... = Max HE-MCS for 4 SS:
Support for HE-MCS 0-11 (0x2)
.... ..11 .... .... = Max HE-MCS for 5 SS: Not
supported for HE PPDUs (0x3)
.... 11.. .... .... = Max HE-MCS for 6 SS: Not
supported for HE PPDUs (0x3)
..11 .... .... .... = Max HE-MCS for 7 SS: Not
supported for HE PPDUs (0x3)
11.. .... .... .... = Max HE-MCS for 8 SS: Not
supported for HE PPDUs (0x3)
PPE Thresholds
.... .011 = NSS: 3
.111 1... = RU Index Bitmask: 0xf
NSS 0
RU allocation: 242
PPET16: BPSK (0x00)
PPET8: None (0x07)
RU allocation: 484
PPET16: BPSK (0x00)
PPET8: None (0x07)
RU allocation: 996
PPET16: BPSK (0x00)
PPET8: None (0x07)
RU allocation: 2x996
PPET16: BPSK (0x00)
PPET8: None (0x07)
NSS 1
RU allocation: 242
PPET16: BPSK (0x00)
PPET8: None (0x07)
RU allocation: 484
PPET16: BPSK (0x00)
PPET8: None (0x07)
RU allocation: 996
PPET16: BPSK (0x00)
PPET8: None (0x07)
RU allocation: 2x996
PPET16: BPSK (0x00)
PPET8: None (0x07)
NSS 2
RU allocation: 242
PPET16: BPSK (0x00)
PPET8: None (0x07)
RU allocation: 484
PPET16: BPSK (0x00)
PPET8: None (0x07)
RU allocation: 996
PPET16: BPSK (0x00)
PPET8: None (0x07)
RU allocation: 2x996
PPET16: BPSK (0x00)
PPET8: None (0x07)
NSS 3
RU allocation: 242
PPET16: BPSK (0x00)
PPET8: None (0x07)
RU allocation: 484
PPET16: BPSK (0x00)
PPET8: None (0x07)
RU allocation: 996
PPET16: BPSK (0x00)
PPET8: None (0x07)
RU allocation: 2x996
PPET16: BPSK (0x00)
PPET8: None (0x07)
Ext Tag: HE Operation
Tag Number: Element ID Extension (255)
Ext Tag length: 11
Ext Tag Number: HE Operation (36)
HE Operation Parameters: 0x023ff0
.... .... .... .... .... .000 = Default PE Duration: 0
.... .... .... .... .... 0... = TWT Required: Not required
.... .... ..11 1111 1111 .... = TXOP Duration RTS
Threshold: 1023
.... .... .0.. .... .... .... = VHT Operation
Information Present: False
.... .... 0... .... .... .... = Co-Hosted BSS: False
.... ...0 .... .... .... .... = ER SU Disable: False
.... ..1. .... .... .... .... = 6 GHz Operation
Information Present: True
0000 00.. .... .... .... .... = Reserved: 0x00
BSS Color Information: 0x92
..01 0010 = BSS Color: 0x12
.0.. .... = Partial BSS Color: False
1... .... = BSS Color Disabled: True
Basic HE-MCS and NSS Set: 0xfffc
.... .... .... ..00 = Max HE-MCS for 1 SS: Support for
HE-MCS 0-7 (0)
.... .... .... 11.. = Max HE-MCS for 2 SS: Not
supported for HE PPDUs (3)
.... .... ..11 .... = Max HE-MCS for 3 SS: Not
supported for HE PPDUs (3)
.... .... 11.. .... = Max HE-MCS for 4 SS: Not
supported for HE PPDUs (3)
.... ..11 .... .... = Max HE-MCS for 5 SS: Not
supported for HE PPDUs (3)
.... 11.. .... .... = Max HE-MCS for 6 SS: Not
supported for HE PPDUs (3)
..11 .... .... .... = Max HE-MCS for 7 SS: Not
supported for HE PPDUs (3)
11.. .... .... .... = Max HE-MCS for 8 SS: Not
supported for HE PPDUs (3)
6 GHz Operation Information
Primary Channel: 33
Control: 0x03
.... ..11 = Channel Width: 160MHz or 80MHz+80MHz (3)
.... .0.. = Duplicate Beacon: False
..00 0... = Regulatory Info: 0
00.. .... = Reserved: 0
Channel Center Frequency Segment 0: 39
Channel Center Frequency Segment 1: 47
Minimum Rate: 6
Ext Tag: HE 6 GHz Band Capabilities
Tag Number: Element ID Extension (255)
Ext Tag length: 2
Ext Tag Number: HE 6 GHz Band Capabilities (59)
Capabilities Information: 0x36b8
.... .... .... .000 = Minimum MPDU Start Spacing: No
restriction (0x0)
.... .... ..11 1... = Maximum A-MPDU Length Exponent:
1 048 575 (0x7)
.... .... 10.. .... = Maximum MPDU Length: 11 454 (0x2)
.... ...0 .... .... = Reserved: 0x0
.... .11. .... .... = SM Power Save: SM Power Save
disabled (0x3)
.... 0... .... .... = RD Responder: Not supported
...1 .... .... .... = Rx Antenna Pattern Consistency: Supported
..1. .... .... .... = Tx Antenna Pattern Consistency: Supported
00.. .... .... .... = Reserved: 0x0
Tag: Vendor Specific: Microsoft Corp.: WMM/WME: Parameter Element
Tag Number: Vendor Specific (221)
Tag length: 24
OUI: 00:50:f2 (Microsoft Corp.)
Vendor Specific OUI Type: 2
Type: WMM/WME (0x02)
WME Subtype: Parameter Element (1)
WME Version: 1
WME QoS Info: 0x01
0... .... = U-APSD: Disabled
.... 0001 = Parameter Set Count: 0x1
.000 .... = Reserved: 0x0
Reserved: 00
Ac Parameters ACI 0 (Best Effort), ACM no, AIFSN 3,
ECWmin/max 4/10 (CWmin/max 15/1023), TXOP 0
ACI / AIFSN Field: 0x03
.... 0011 = AIFSN: 3
...0 .... = Admission Control Mandatory: No
.00. .... = ACI: Best Effort (0)
0... .... = Reserved: 0
ECW: 0xa4
1010 .... = ECW Max: 10
.... 0100 = ECW Min: 4
CW Max: 1023
CW Min: 15
TXOP Limit: 0
Ac Parameters ACI 1 (Background), ACM no, AIFSN 7,
ECWmin/max 4/10 (CWmin/max 15/1023), TXOP 0
ACI / AIFSN Field: 0x27
.... 0111 = AIFSN: 7
...0 .... = Admission Control Mandatory: No
.01. .... = ACI: Background (1)
0... .... = Reserved: 0
ECW: 0xa4
1010 .... = ECW Max: 10
.... 0100 = ECW Min: 4
CW Max: 1023
CW Min: 15
TXOP Limit: 0
Ac Parameters ACI 2 (Video), ACM no, AIFSN 2, ECWmin/max
3/4 (CWmin/max 7/15), TXOP 94
ACI / AIFSN Field: 0x42
.... 0010 = AIFSN: 2
...0 .... = Admission Control Mandatory: No
.10. .... = ACI: Video (2)
0... .... = Reserved: 0
ECW: 0x43
0100 .... = ECW Max: 4
.... 0011 = ECW Min: 3
CW Max: 15
CW Min: 7
TXOP Limit: 94
Ac Parameters ACI 3 (Voice), ACM no, AIFSN 2, ECWmin/max
2/3 (CWmin/max 3/7), TXOP 47
ACI / AIFSN Field: 0x62
.... 0010 = AIFSN: 2
...0 .... = Admission Control Mandatory: No
.11. .... = ACI: Voice (3)
0... .... = Reserved: 0
ECW: 0x32
0011 .... = ECW Max: 3
.... 0010 = ECW Min: 2
CW Max: 7
CW Min: 3
If I can check anyhing in between pls. let me know.
OpenWRT is known to have some tuning for these things but ath11k was
not included by default hence also QCN9074. So I am now also working
with 5.15 master, compiled custom OpenWRT with enabled ath11k and
included *.bin firmware into OpenWRT. Resolved MSI issues to VT-D but
so far this is still work in progress as the card does not error out
but never responds to power on command. MHI keeps waiting for power
on. This is however secondary topic I started looking into due lack of
progress on a regular distro. Tried also latest 6.1 rc4 kernel on
ubuntu with no change.
Regards,
Mariusz
On Mon, 14 Nov 2022 at 14:19, Nagarajan Maran (QUIC)
<quic_nmaran@quicinc.com> wrote:
>
> Hi Mariusz,
>
>
>
> We checked the upstream driver code and firmware bins similar to your setup environment and it seems to work well.
>
> Could you kindly check whether your Wi-Fi card has been OTP fused for 6Ghz?
>
>
>
> -Thanks
>
> Nagarajan M.
>
>
>
> From: Mariusz <enebeo@gmail.com>
> Sent: Tuesday, November 8, 2022 8:25 PM
> To: Nagarajan Maran (QUIC) <quic_nmaran@quicinc.com>
> Cc: ath11k@lists.infradead.org
> Subject: Re: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
>
>
>
> Perhaps also something interesting, I apply reg domain of Belgium/BE. It has lower 6GHz channels allowed.
>
>
>
> iw reg get
> global
> country BE: DFS-ETSI
> (2400 - 2483 @ 40), (N/A, 20), (N/A)
> (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
> (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
> (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
> (5725 - 5875 @ 80), (N/A, 13), (N/A)
> (5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
> (57000 - 66000 @ 2160), (N/A, 40), (N/A)
>
> phy#3 (self-managed)
> country US: DFS-FCC
> (2402 - 2472 @ 40), (6, 30), (N/A)
> (5170 - 5250 @ 80), (N/A, 30), (N/A), AUTO-BW
> (5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
> (5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS, AUTO-BW
> (5735 - 5895 @ 160), (N/A, 30), (N/A), AUTO-BW
> (5945 - 7125 @ 160), (N/A, 30), (N/A), NO-OUTDOOR, AUTO-BW
>
>
>
> When I start hostapd with acs_survey or channel=0 it starts but pretends to work, no other client can connect to this ssid.
>
>
>
> When I disable acs in hostapd.conf and set channel=1 (freq 5955 in 6GHz range) so allowed per reg domain it refuses to start:
>
>
>
> Mode: IEEE 802.11a Channel: 1 Frequency: 5955 MHz
> nl80211: Set freq 5955 (ht_enabled=0, vht_enabled=0, he_enabled=1, eht_enabled=0, bandwidth=160 MHz, cf1=5955 MHz, cf2=0 MHz)
> * freq=5955
> * eht_enabled=0
> * he_enabled=1
> * vht_enabled=0
> * ht_enabled=0
> * radar_background=0
> * bandwidth=160
> * channel_width=5
> * center_freq1=5955
> * center_freq2=0
> nl80211: kernel reports: invalid channel definition
> nl80211: Failed to set channel (freq=5955): -22 (Invalid argument)
>
>
>
> reg domain BE is more restrictive than US so channel 1 should be enabled in both cases
>
> Previous country code BE, new country code BE
> nl80211: Regulatory information - country=US (DFS-FCC)
> nl80211: 2402-2472 @ 40 MHz 30 mBm
> nl80211: 5170-5250 @ 80 MHz 30 mBm
> nl80211: 5250-5330 @ 80 MHz 24 mBm (DFS)
> nl80211: 5490-5730 @ 160 MHz 24 mBm (DFS)
> nl80211: 5735-5895 @ 160 MHz 30 mBm
> nl80211: 5945-7125 @ 160 MHz 30 mBm (no outdoor)
> nl80211: Mode IEEE 802.11a: 5955 5975 5995 6015 6035 6055 6075 6095 6115 6135 6155 6175 6195 6215 6235 6255 6275 6295 6315 6335 6355 6375 6395 6415 6435 6455 6475 6495 6515 6535 6555 6575 6595 6615 6635 6655 6675 6695 6715 6735 6755 6775 6795 6815 6835 6855 6875 6895 6915 6935 6955 6975 6995 7015 7035 7055 7075 7095 7115 5935[DISABLED]
>
>
>
> for op_class=134 = 160MHz valid channels are 1-29, 33-61, 65-93, 97-125, 129-157, 161-189, 193-221
>
>
>
>
>
> phy: phy3
> BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
> wlp1s0: interface state UNINITIALIZED->COUNTRY_UPDATE
> Previous country code BE, new country code BE
> nl80211: Regulatory information - country=US (DFS-FCC)
> nl80211: 2402-2472 @ 40 MHz 30 mBm
> nl80211: 5170-5250 @ 80 MHz 30 mBm
> nl80211: 5250-5330 @ 80 MHz 24 mBm (DFS)
> nl80211: 5490-5730 @ 160 MHz 24 mBm (DFS)
> nl80211: 5735-5895 @ 160 MHz 30 mBm
> nl80211: 5945-7125 @ 160 MHz 30 mBm (no outdoor)
> nl80211: Mode IEEE 802.11a: 5955 5975 5995 6015 6035 6055 6075 6095 6115 6135 6155 6175 6195 6215 6235 6255 6275 6295 6315 6335 6355 6375 6395 6415 6435 6455 6475 6495 6515 6535 6555 6575 6595 6615 6635 6655 6675 6695 6715 6735 6755 6775 6795 6815 6835 6855 6875 6895 6915 6935 6955 6975 6995 7015 7035 7055 7075 7095 7115 5935[DISABLED]
> Completing interface initialization
> Mode: IEEE 802.11a Channel: 33 Frequency: 6115 MHz
> nl80211: Set freq 6115 (ht_enabled=0, vht_enabled=0, he_enabled=1, eht_enabled=0, bandwidth=160 MHz, cf1=6115 MHz, cf2=0 MHz)
> * freq=6115
> * eht_enabled=0
> * he_enabled=1
> * vht_enabled=0
> * ht_enabled=0
> * radar_background=0
> * bandwidth=160
> * channel_width=5
> * center_freq1=6115
> * center_freq2=0
> nl80211: kernel reports: invalid channel definition
> nl80211: Failed to set channel (freq=6115): -22 (Invalid argument)
> Could not set channel for kernel driver
> Interface initialization failed
>
>
>
>
>
>
>
> How is this invalid channel?
>
>
>
> root@s4:/home/angel/hostap/hostapd# iw phy3 channels
> Band 4:
> * 5955 MHz [1]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 5975 MHz [5]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 5995 MHz [9]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6015 MHz [13]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6035 MHz [17]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6055 MHz [21]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6075 MHz [25]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6095 MHz [29]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6115 MHz [33]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6135 MHz [37]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6155 MHz [41]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6175 MHz [45]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6195 MHz [49]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6215 MHz [53]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6235 MHz [57]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6255 MHz [61]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6275 MHz [65]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6295 MHz [69]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6315 MHz [73]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6335 MHz [77]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6355 MHz [81]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6375 MHz [85]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6395 MHz [89]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6415 MHz [93]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6435 MHz [97]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6455 MHz [101]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6475 MHz [105]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6495 MHz [109]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6515 MHz [113]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6535 MHz [117]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6555 MHz [121]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6575 MHz [125]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6595 MHz [129]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6615 MHz [133]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6635 MHz [137]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6655 MHz [141]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6675 MHz [145]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6695 MHz [149]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6715 MHz [153]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6735 MHz [157]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6755 MHz [161]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6775 MHz [165]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6795 MHz [169]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6815 MHz [173]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6835 MHz [177]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6855 MHz [181]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6875 MHz [185]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6895 MHz [189]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6915 MHz [193]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6935 MHz [197]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6955 MHz [201]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6975 MHz [205]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 6995 MHz [209]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 7015 MHz [213]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 7035 MHz [217]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 7055 MHz [221]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 7075 MHz [225]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 7095 MHz [229]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 7115 MHz [233]
> Maximum TX power: 30.0 dBm
> Channel widths: 20MHz
> * 5935 MHz [2] (disabled)
>
>
>
>
>
>
>
>
>
> On Mon, 7 Nov 2022 at 17:07, Nagarajan Maran (QUIC) <quic_nmaran@quicinc.com> wrote:
>
> Hi Mariusz,
>
> We are looking into this issue. It seems that this error can occur when the given frequency is not present or when the given frequency is disabled.
> To further analyze the issue, could you kindly let us know the output of the below commands during failure case.
> 1) iw dev
> 2) iw phyX channels
>
> Also, could you kindly send the WiFi driver boot up logs with "debug_mask=0x212" enabled during insmod of ath11k.ko module.
>
> Thanks,
> Nagarajan M.
>
> -----Original Message-----
>
> From: Mariusz <enebeo@gmail.com>
> To: ath11k@lists.infradead.org
> Subject: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
> Message-ID:
> <CAJrE-q6NVEF4sNW1s4Zz7Pb2ryzCi69e+_vLQswBWm747DHYDw@mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Hi,
>
> As support for QCN9074 got better I went ahead and built a 6E linux based AP. Dell R720 server x86 running Linux s4 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64
> x86_64 x86_64 GNU/Linux.
>
> My issue is that I cannot get it working on 6GHz bands but it works fine on 5GHz. I bought 6E version and since this is a single band module it cannot be both 5G & 6G and linux driver does not agree with it being 6E version:
>
> [71914.038562] ath11k_pci 0000:03:00.0: BAR 0: assigned [mem 0xdf800000-0xdf9fffff 64bit] [71914.038840] ath11k_pci 0000:03:00.0: MSI vectors: 16 [71914.038852] ath11k_pci 0000:03:00.0: qcn9074 hw1.0 [71914.194459] mhi mhi0: Requested to power ON [71914.194712] mhi mhi0: Power on setup success [71914.297749] mhi mhi0: Wait for device to enter SBL or Mission mode [71914.647118] ath11k_pci 0000:03:00.0: chip_id 0x0 chip_family 0x0 board_id 0xff soc_id 0xffffffff [71914.647134] ath11k_pci 0000:03:00.0: fw_version 0x250a04b8 fw_build_timestamp 2021-12-20 06:41 fw_build_id [71916.310787] ath11k_pci 0000:03:00.0 wlp3s0: renamed from wlan0
>
> HE PHY Capabilities: (0x1c604c88ffdb839c110c00):
> HE40/HE80/5GHz
> HE160/5GHz
> HE160/HE80+80/5GHz
>
> iw dev wlp3s0 set freq 6195 160MHz
> kernel reports: Channel is disabled
> command failed: Invalid argument (-22)
>
> I am using the latest firmware files from ath11k tree. Is there any special firmware to force this to 6GHz? I read somewhere board_id determines which one it is and 255 disables 6GHz but I miss more data on that.
>
> phy#2 (self-managed)
> country US: DFS-FCC
> (2402 - 2472 @ 40), (6, 30), (N/A)
> (5170 - 5250 @ 80), (N/A, 30), (N/A), AUTO-BW
> (5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
> (5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS, AUTO-BW
> (5735 - 5895 @ 160), (N/A, 30), (N/A), AUTO-BW
> (5945 - 7125 @ 160), (N/A, 30), (N/A), NO-OUTDOOR, AUTO-BW
>
> It works fine in 5GHz but this is not what I purchased it for, so I am puzzled if this is something in software or I was sold wrong hardware.Is there a specific board-2.bin for 6GHz? Since the 9074 chip is the same in all versions perhaps this is a software hiccup.
>
> Any clues are welcome.
>
> Regards,
> Mario
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
2022-11-15 10:02 ` Mariusz
@ 2022-11-15 18:29 ` walde
2022-11-15 19:18 ` Mariusz
2022-11-18 11:26 ` Sven Eckelmann
2022-11-17 16:51 ` Mariusz
1 sibling, 2 replies; 18+ messages in thread
From: walde @ 2022-11-15 18:29 UTC (permalink / raw)
To: Mariusz, ath11k
Hi,
we probably have the same problem.
We have two Pinapple 6 Wifi 6 cards from the manufacturer 8devices that
we want to operate at 6 GHz. The modules have the QCN 9074 chipset and
are also certified for the 6E standard. The modules work very well at 5
GHZ. However the option to transmit on 6 GHz is not available. The board
ID is also defined as 0xff. If there is any information you could share
to enable the modules for 6 GHz, we would appreciate it.
Regards,
Waldemar S.
Am 15.11.2022 um 11:02 schrieb Mariusz:
> Hi,
>
> I have asked the manufacturer to confirm. It has the 6E sticker on it
> but I have no lower level tools to read e-fuses if any. Regarding
> board_id they say normally on non-x86 this is set by bootloader so it
> is not hardcoded in eeprom.
> For the HW side, on the PCB there are two markings, 5G (top) and 6E
> (bottom), none of them was bridged from the factory. I bridged the 6E
> one but that did not change anything. In the meantime I also deployed
> aircrack-ng on AX210 client since I have no 6GHz equipment to do other
> testing.
>
> On the client:
> iw wlp1s0 del
> airmon-ng start wlan0mon
> tshark -i wlan0mon -T text -V > log.wifi
> airodump-ng -C 6115 -i wlan0mon --bssid C4:4B:D1:D0:00:7E
>
> Checking available frequencies, this could take few seconds.
> Freq 6115 ][ Elapsed: 0 s ][ 2022-11-08 19:48
> BSSID PWR Beacons #Data, #/s CH MB ENC CIPHER AUTH ESSID
> C4:4B:D1:D0:00:7E -46 12 0 0 33 54e WPA3 CCMP SAE dupa
>
> So the client is seeing signal strength and beacon packets which are
> increasing continuously. It has concluded SSID, MAC and encryption
> details correctly on 6E freq - 6115MHz and it is also seeing op class
> 134 = 160Mhz channel as set. Then I assume electronics at least TX on
> QCN9074 is working fine as the remote client is picking up something
> but whatever is not right as there's no handshake. I tried to
> pre-setup SSID so it auto connects without SSID discovery on Win
> client but no juice. So I dumped packet details, not sure if I read
> all flags right but there's a mix of it mentioning 6GHz supported &
> enabled but in other places OFDM is listed instead of OFDMA. Now which
> part of it is due aircrack-ng having all updates to support/decode 6E
> don't know, it is another variable here.
>
> 802.11 radio information
> PHY type: 802.11a (OFDM) (5)
> Turbo type: Non-turbo (0)
> Data rate: 6.0 Mb/s
> Channel: 33
> Frequency: 6115MHz
> Signal strength (dBm): -47 dBm
> TSF timestamp: 1826096995
> [Duration: 312µs]
> [Preamble: 20µs]
> [IFS: 204488µs]
> [Start: 1826096683µs]
> [End: 1826096995µs]
>
>
> IEEE 802.11 Beacon frame, Flags: ........C
> Type/Subtype: Beacon frame (0x0008)
> Frame Control Field: 0x8000
> .... ..00 = Version: 0
> .... 00.. = Type: Management frame (0)
> 1000 .... = Subtype: 8
> Flags: 0x00
> .... ..00 = DS status: Not leaving DS or network is
> operating in AD-HOC mode (To DS: 0 From DS: 0) (0x0)
> .... .0.. = More Fragments: This is the last fragment
> .... 0... = Retry: Frame is not being retransmitted
> ...0 .... = PWR MGT: STA will stay up
> ..0. .... = More Data: No data buffered
> .0.. .... = Protected flag: Data is not protected
> 0... .... = +HTC/Order flag: Not strictly ordered
> .000 0000 0000 0000 = Duration: 0 microseconds
> Receiver address: Broadcast (ff:ff:ff:ff:ff:ff)
> Destination address: Broadcast (ff:ff:ff:ff:ff:ff)
> Transmitter address: WallysCo_d0:00:7e (c4:4b:d1:d0:00:7e)
> Source address: WallysCo_d0:00:7e (c4:4b:d1:d0:00:7e)
> BSS Id: WallysCo_d0:00:7e (c4:4b:d1:d0:00:7e)
> .... .... .... 0000 = Fragment number: 0
> 0100 0100 0101 .... = Sequence number: 1093
> Frame check sequence: 0xcf64d100 [unverified]
> [FCS Status: Unverified]
>
> IEEE 802.11 Wireless Management
> Fixed parameters (12 bytes)
> Timestamp: 4349132798
> Beacon Interval: 0.204800 [Seconds]
> Capabilities Information: 0x1011
> .... .... .... ...1 = ESS capabilities: Transmitter is an AP
> .... .... .... ..0. = IBSS status: Transmitter belongs to a BSS
> .... ..0. .... 00.. = CFP participation capabilities: No
> point coordinator at AP (0x00)
> .... .... ...1 .... = Privacy: AP/STA can support WEP
> .... .... ..0. .... = Short Preamble: Not Allowed
> .... .... .0.. .... = PBCC: Not Allowed
> .... .... 0... .... = Channel Agility: Not in use
> .... ...0 .... .... = Spectrum Management: Not Implemented
> .... .0.. .... .... = Short Slot Time: Not in use
> .... 0... .... .... = Automatic Power Save Delivery: Not Implemented
> ...1 .... .... .... = Radio Measurement: Implemented
> ..0. .... .... .... = DSSS-OFDM: Not Allowed
> .0.. .... .... .... = Delayed Block Ack: Not Implemented
> 0... .... .... .... = Immediate Block Ack: Not Implemented
> Tagged parameters (175 bytes)
> Tag: SSID parameter set: dupa
> Tag Number: SSID parameter set (0)
> Tag length: 4
> SSID: dupa
> Tag: Supported Rates 6(B), 9, 12(B), 18, 24(B), 36, 48, 54, [Mbit/sec]
> Tag Number: Supported Rates (1)
> Tag length: 8
> Supported Rates: 6(B) (0x8c)
> Supported Rates: 9 (0x12)
> Supported Rates: 12(B) (0x98)
> Supported Rates: 18 (0x24)
> Supported Rates: 24(B) (0xb0)
> Supported Rates: 36 (0x48)
> Supported Rates: 48 (0x60)
> Supported Rates: 54 (0x6c)
> Tag: DS Parameter set: Current Channel: 33
> Tag Number: DS Parameter set (3)
> Tag length: 1
> Current Channel: 33
> Tag: Traffic Indication Map (TIM): DTIM 1 of 2 bitmap
> Tag Number: Traffic Indication Map (TIM) (5)
> Tag length: 4
> DTIM count: 1
> DTIM period: 2
> Bitmap control: 0x00
> .... ...0 = Multicast: False
> 0000 000. = Bitmap Offset: 0x00
> Partial Virtual Bitmap: 00
> Tag: Country Information: Country Code BE, Environment 0x04
> Tag Number: Country Information (7)
> Tag length: 6
> Code: BE
> Environment: 4
> Country Info: Operating Extension Identifier: 201,
> Operating Class: 134, Coverage Class: 0
> Operating Extension Identifier: 201
> Operating Class: 134
> Coverage Class: 0
> Tag: RSN Information
> Tag Number: RSN Information (48)
> Tag length: 20
> RSN Version: 1
> Group Cipher Suite: 00:0f:ac (Ieee 802.11) AES (CCM)
> Group Cipher Suite OUI: 00:0f:ac (Ieee 802.11)
> Group Cipher Suite type: AES (CCM) (4)
> Pairwise Cipher Suite Count: 1
> Pairwise Cipher Suite List 00:0f:ac (Ieee 802.11) AES (CCM)
> Pairwise Cipher Suite: 00:0f:ac (Ieee 802.11) AES (CCM)
> Pairwise Cipher Suite OUI: 00:0f:ac (Ieee 802.11)
> Pairwise Cipher Suite type: AES (CCM) (4)
> Auth Key Management (AKM) Suite Count: 1
> Auth Key Management (AKM) List 00:0f:ac (Ieee 802.11) SAE (SHA256)
> Auth Key Management (AKM) Suite: 00:0f:ac (Ieee
> 802.11) SAE (SHA256)
> Auth Key Management (AKM) OUI: 00:0f:ac (Ieee 802.11)
> Auth Key Management (AKM) type: SAE (SHA256) (8)
> RSN Capabilities: 0x00cc
> .... .... .... ...0 = RSN Pre-Auth capabilities:
> Transmitter does not support pre-authentication
> .... .... .... ..0. = RSN No Pairwise capabilities:
> Transmitter can support WEP default key 0 simultaneously with Pairwise
> key
> .... .... .... 11.. = RSN PTKSA Replay Counter
> capabilities: 16 replay counters per PTKSA/GTKSA/STAKeySA (0x3)
> .... .... ..00 .... = RSN GTKSA Replay Counter
> capabilities: 1 replay counter per PTKSA/GTKSA/STAKeySA (0x0)
> .... .... .1.. .... = Management Frame Protection Required: True
> .... .... 1... .... = Management Frame Protection Capable: True
> .... ...0 .... .... = Joint Multi-band RSNA: False
> .... ..0. .... .... = PeerKey Enabled: False
> ..0. .... .... .... = Extended Key ID for Individually
> Addressed Frames: Not supported
> Tag: RM Enabled Capabilities (5 octets)
> Tag Number: RM Enabled Capabilities (70)
> Tag length: 5
> RM Capabilities: 0x72 (octet 1)
> .... ...0 = Link Measurement: Disabled
> .... ..1. = Neighbor Report: Enabled
> .... .0.. = Parallel Measurements: Disabled
> .... 0... = Repeated Measurements: Disabled
> ...1 .... = Beacon Passive Measurement: Enabled
> ..1. .... = Beacon Active Measurement: Enabled
> .1.. .... = Beacon Table Measurement: Supported
> 0... .... = Beacon Measurement Reporting Conditions: Disabled
> RM Capabilities: 0x00 (octet 2)
> .... ...0 = Frame Measurement: Disabled
> .... ..0. = Channel Load Measurement: Disabled
> .... .0.. = Noise Histogram Measurement: Disabled
> .... 0... = Statistics Measurement: Disabled
> ...0 .... = LCI Measurement: Disabled
> ..0. .... = LCI Azimuth capability: Disabled
> .0.. .... = Transmit Stream/Category Measurement: Not supported
> 0... .... = Triggered Transmit Stream/Category
> Measurement: Disabled
> RM Capabilities: 0x00 (octet 3)
> .... ...0 = AP Channel Report capability: Disabled
> .... ..0. = RM MIB capability: Disabled
> ...0 00.. = Operating Channel Max Measurement Duration: 0
> 000. .... = Nonoperating Channel Max Measurement Duration: 0
> RM Capabilities: 0x00 (octet 4)
> .... .000 = Measurement Pilotcapability: 0
> .... 0... = Measurement Pilot Transmission Information: Disabled
> ...0 .... = Neighbor Report TSF Offset: Disabled
> ..0. .... = RCPI Measurement capability: Disabled
> .0.. .... = RSNI Measurement capability: Not supported
> 0... .... = BSS Average Access Delay capability: Disabled
> RM Capabilities: 0x00 (octet 5)
> .... ...0 = BSS Available Admission Capacity
> capability: Disabled
> .... ..0. = Antenna capability: Disabled
> .... .0.. = FTM Range Report Capability: Disabled
> .... 0... = Civic Location Measurement Capability: Disabled
> 0000 .... = Reserved: 0x0
> Tag: Supported Operating Classes
> Tag Number: Supported Operating Classes (59)
> Tag length: 2
> Current Operating Class: 134
> Tag: Extended Capabilities (10 octets)
> Tag Number: Extended Capabilities (127)
> Tag length: 10
> Extended Capabilities: 0x04 (octet 1)
> .... ...0 = 20/40 BSS Coexistence Management Support:
> Not supported
> .... ..0. = Reserved (was On-demand beacon): 0x0
> .... .1.. = Extended Channel Switching: Supported
> .... 0... = Reserved (was WAVE indication): 0x0
> ...0 .... = PSMP Capability: Not supported
> ..0. .... = Reserved: 0x0
> .0.. .... = S-PSMP Support: Not supported
> 0... .... = Event: Not supported
> Extended Capabilities: 0x00 (octet 2)
> .... ...0 = Diagnostics: Not supported
> .... ..0. = Multicast Diagnostics: Not supported
> .... .0.. = Location Tracking: Not supported
> .... 0... = FMS: Not supported
> ...0 .... = Proxy ARP Service: Not supported
> ..0. .... = Collocated Interference Reporting: Not supported
> .0.. .... = Civic Location: Not supported
> 0... .... = Geospatial Location: Not supported
> Extended Capabilities: 0x00 (octet 3)
> .... ...0 = TFS: Not supported
> .... ..0. = WNM Sleep Mode: Not supported
> .... .0.. = TIM Broadcast: Not supported
> .... 0... = BSS Transition: Not supported
> ...0 .... = QoS Traffic Capability: Not supported
> ..0. .... = AC Station Count: Not supported
> .0.. .... = Multiple BSSID: Not supported
> 0... .... = Timing Measurement: Not supported
> Extended Capabilities: 0x00 (octet 4)
> .... ...0 = Channel Usage: Not supported
> .... ..0. = SSID List: Not supported
> .... .0.. = DMS: Not supported
> .... 0... = UTC TSF Offset: Not supported
> ...0 .... = TPU Buffer STA Support: Not supported
> ..0. .... = TDLS Peer PSM Support: Not supported
> .0.. .... = TDLS channel switching: Not supported
> 0... .... = Interworking: Not supported
> Extended Capabilities: 0x00 (octet 5)
> .... ...0 = QoS Map: Not supported
> .... ..0. = EBR: Not supported
> .... .0.. = SSPN Interface: Not supported
> .... 0... = Reserved: 0x0
> ...0 .... = MSGCF Capability: Not supported
> ..0. .... = TDLS Support: Not supported
> .0.. .... = TDLS Prohibited: Not supported
> 0... .... = TDLS Channel Switching Prohibited: Not supported
> Extended Capabilities: 0x00 (octet 6)
> .... ...0 = Reject Unadmitted Frame: Not supported
> .... 000. = Service Interval Granularity: 5 ms (0)
> ...0 .... = Identifier Location: Not supported
> ..0. .... = U-APSD Coexistence: Not supported
> .0.. .... = WNM Notification: Not supported
> 0... .... = QAB Capability: 0x0
> Extended Capabilities: 0x00 (octet 7)
> .... ...0 = UTF-8 SSID: Not supported
> .... ..0. = QMF Activated: False
> .... .0.. = QMF Reconfiguration Activated: False
> .... 0... = Robust AV Streaming: False
> ...0 .... = Advanced GCR: False
> ..0. .... = Mesh GCR: False
> .0.. .... = SCS: False
> 0... .... = QLoad Report: False
> Extended Capabilities: 0x0040 (octets 8 & 9)
> .... .... .... ...0 = Alternate EDCA: False
> .... .... .... ..0. = Unprotected TXOP Negotiation: False
> .... .... .... .0.. = Protected TXOP Negotiation: False
> .... .... .... 0... = Reserved: 0x0
> .... .... ...0 .... = Protected QLoad Report: False
> .... .... ..0. .... = TDLS Wider Bandwidth: Not supported
> .... .... .1.. .... = Operating Mode Notification: Supported
> .... ...0 0... .... = Max Number Of MSDUs In A-MSDU:
> No limit (0)
> .... ..0. .... .... = Channel Schedule Management: False
> .... .0.. .... .... = Geodatabase Inband Enabling Signal: False
> .... 0... .... .... = Network Channel Control: False
> ...0 .... .... .... = White Space Map: False
> ..0. .... .... .... = Channel Availability Query: False
> .0.. .... .... .... = Fine Timing Measurement Responder: False
> 0... .... .... .... = Fine Timing Measurement Initiator: False
> Extended Capabilities: 0x40 (octet 10)
> .... ...0 = FILS Capable: False
> .... ..0. = Extended Spectrum Management Capable: False
> .... .0.. = Future Channel Capable: False
> .... 0... = Reserved: 0x0
> ...0 .... = Reserved: 0x0
> ..0. .... = TWT Requester Support: False
> .1.. .... = TWT Responder Support: True
> 0... .... = OBSS Narrow Bandwidth RU in UL OFDMA
> Tolerance Support: False
> Tag: Tx Power Envelope
> Tag Number: Tx Power Envelope (195)
> Tag length: 2
> Tx Pwr Info: 0x18
> .... .000 = Max Tx Pwr Count: 0
> ..01 1... = Max Tx Pwr Unit Interpretation: Unknown (3)
> 00.. .... = Reserved: 0
> Local Max Tx Pwr Constraint 20MHz: -1.0 dBm
> Tag: Tx Power Envelope
> Tag Number: Tx Power Envelope (195)
> Tag length: 2
> Tx Pwr Info: 0x58
> .... .000 = Max Tx Pwr Count: 0
> ..01 1... = Max Tx Pwr Unit Interpretation: Unknown (3)
> 01.. .... = Reserved: 1
> Local Max Tx Pwr Constraint 20MHz: 5.0 dBm
> Tag: RSN eXtension (1 octet)
> Tag Number: RSN eXtension (244)
> Tag length: 1
> RSNX: 0x20 (octet 1)
> .... 0000 = RSNX Length: 0
> ...0 .... = Protected TWT Operations Support: 0
> ..1. .... = SAE Hash to element: 1
> 00.. .... = Reserved: 0x0
> Ext Tag: HE Capabilities
> Tag Number: Element ID Extension (255)
> Ext Tag length: 38
> Ext Tag Number: HE Capabilities (35)
> HE MAC Capabilities Information: 0x10409a18000d
> .... .... .... .... .... .... .... .... .... .... ....
> ...1 = +HTC HE Support: Supported
> .... .... .... .... .... .... .... .... .... .... ....
> ..0. = TWT Requester Support: Not supported
> .... .... .... .... .... .... .... .... .... .... ....
> .1.. = TWT Responder Support: Supported
> .... .... .... .... .... .... .... .... .... .... ...0
> 1... = Dynamic Fragmentation Support: Level 1 dynamic fragmentation
> support (1)
> .... .... .... .... .... .... .... .... .... .... 000.
> .... = Maximum Number of Fragmented MSDUs: 1
> .... .... .... .... .... .... .... .... .... ..00 ....
> .... = Minimum Fragment Size: No restriction on minimum payload size
> (0)
> .... .... .... .... .... .... .... .... .... 00.. ....
> .... = Trigger Frame MAC Padding Duration: 0 (0)
> .... .... .... .... .... .... .... .... .000 .... ....
> .... = Multi-TID Aggregation Rx Support: 0
> .... .... .... .... .... .... .... ...0 0... .... ....
> .... = HE Link Adaptation Support: No feedback if the STA does not
> provide HE MFB (0)
> .... .... .... .... .... .... .... ..0. .... .... ....
> .... = All Ack Support: Not supported
> .... .... .... .... .... .... .... .0.. .... .... ....
> .... = TRS Support: Not supported
> .... .... .... .... .... .... .... 1... .... .... ....
> .... = BSR Support: Supported
> .... .... .... .... .... .... ...1 .... .... .... ....
> .... = Broadcast TWT Support: Supported
> .... .... .... .... .... .... ..0. .... .... .... ....
> .... = 32-bit BA Bitmap Support: Not supported
> .... .... .... .... .... .... .0.. .... .... .... ....
> .... = MU Cascading Support: Not supported
> .... .... .... .... .... .... 0... .... .... .... ....
> .... = Ack-Enabled Aggregation Support: Not supported
> .... .... .... .... .... ...0 .... .... .... .... ....
> .... = Reserved: 0x0
> .... .... .... .... .... ..1. .... .... .... .... ....
> .... = OM Control Support: Supported
> .... .... .... .... .... .0.. .... .... .... .... ....
> .... = OFDMA RA Support: Not supported
> .... .... .... .... ...1 1... .... .... .... .... ....
> .... = Maximum A-MPDU Length Exponent Extension: 3
> .... .... .... .... ..0. .... .... .... .... .... ....
> .... = A-MSDU Fragmentation Support: Not supported
> .... .... .... .... .0.. .... .... .... .... .... ....
> .... = Flexible TWT Schedule Support: Not supported
> .... .... .... .... 1... .... .... .... .... .... ....
> .... = Rx Control Frame to MultiBSS: Supported
> .... .... .... ...0 .... .... .... .... .... .... ....
> .... = BSRP BQRP A-MPDU Aggregation: Not supported
> .... .... .... ..0. .... .... .... .... .... .... ....
> .... = QTP Support: Not supported
> .... .... .... .0.. .... .... .... .... .... .... ....
> .... = BQR Support: Not supported
> .... .... .... 0... .... .... .... .... .... .... ....
> .... = PSR Responder: Not supported
> .... .... ...0 .... .... .... .... .... .... .... ....
> .... = NDP Feedback Report Support: Not supported
> .... .... ..0. .... .... .... .... .... .... .... ....
> .... = OPS Support: Not supported
> .... .... .1.. .... .... .... .... .... .... .... ....
> .... = A-MSDU Not Under BA in Ack-Enabled A-MPDU Support: Supported
> .... ..00 0... .... .... .... .... .... .... .... ....
> .... = Multi-TID Aggregation Tx Support: 0
> .... .0.. .... .... .... .... .... .... .... .... ....
> .... = HE Subchannel Selective Transmission Support: Not supported
> .... 0... .... .... .... .... .... .... .... .... ....
> .... = UL 2x996-tone RU Support: Not supported
> ...1 .... .... .... .... .... .... .... .... .... ....
> .... = OM Control UL MU Data Disable RX Support: Supported
> ..0. .... .... .... .... .... .... .... .... .... ....
> .... = HE Dynamic SM Power Save: Not supported
> .0.. .... .... .... .... .... .... .... .... .... ....
> .... = Punctured Sounding Support: Not supported
> 0... .... .... .... .... .... .... .... .... .... ....
> .... = HT And VHT Trigger Frame RX Support: Not supported
> HE PHY Capabilities Information
> .... ...0 = Reserved: 0x0
> .... ...0 = Reserved: 0x0
> 0000 110. = Channel Width Set: 0x06
> .... ..0. = Reserved: 0x0
> .... .1.. = 40 & 80 MHz in the 5 GHz and 6 GHz
> bands: Supported
> .... 1... = 160 MHz in the 5 GHz and 6 GHz bands: Supported
> ...0 .... = 160/80+80 MHz in the 5 GHz and 6 GHz
> bands: Not supported
> ..0. .... = Reserved: 0x0
> .0.. .... = 242 tone RUs in the 5 GHz and 6 GHz
> bands: Not supported
> 0... .... = Reserved: 0x0
> Bits 8 to 23: 0x4c60
> .... .... .... 0000 = Punctured Preamble Rx: 0x0
> .... .... ...0 .... = Device Class: Class B Device (0x0)
> .... .... ..1. .... = LDPC Coding In Payload: Supported
> .... .... .1.. .... = HE SU PPDU With 1x HE-LTF
> And 0.8us GI: Supported
> .... ...0 0... .... = Midamble Tx/Rx Max NSTS: 1
> Space-Time Stream (0x0)
> .... ..0. .... .... = NDP With 4x HE-LTF and 3.2us
> GI: Not supported
> .... .1.. .... .... = STBC Tx <= 80 MHz: Supported
> .... 1... .... .... = STBC Rx <= 80 MHz: Supported
> ...0 .... .... .... = Doppler Tx: Not supported
> ..0. .... .... .... = Doppler Rx: Not supported
> .1.. .... .... .... = Full Bandwidth UL MU-MIMO: Supported
> 0... .... .... .... = Partial Bandwidth UL
> MU-MIMO: Not supported
> Bits 24 to 39: 0xfc08
> .... .... .... ..00 = DCM Max Constellation Tx:
> DCM is not supported (0x0)
> .... .... .... .0.. = DCM Max NSS Tx: 1 Spatial Stream (0x0)
> .... .... ...0 1... = DCM Max Constellation Rx: BPSK (0x1)
> .... .... ..0. .... = DCM Max NSS Rx: 1 Spatial Stream (0x0)
> .... .... .0.. .... = Rx Partial BW SU In 20 MHz
> HE MU PPDU: Not supported
> .... .... 0... .... = SU Beamformer: Not supported
> .... ...0 .... .... = SU Beamformee: Not supported
> .... ..0. .... .... = MU Beamformer: Not supported
> ...1 11.. .... .... = Beamformee STS <= 80 MHz: 0x7
> 111. .... .... .... = Beamformee STS > 80 MHz: 0x7
> Bits 40 to 55: 0x83db
> .... .... .... .011 = Number Of Sounding
> Dimensions <= 80 MHz: 3
> .... .... ..01 1... = Number Of Sounding
> Dimensions > 80 MHz: 3
> .... .... .1.. .... = Ng = 16 SU Feedback: Supported
> .... .... 1... .... = Ng = 16 MU Feedback: Supported
> .... ...1 .... .... = Codebook Size SU Feedback: Supported
> .... ..1. .... .... = Codebook Size MU Feedback: Supported
> .... .0.. .... .... = Triggered SU Beamforming
> Feedback: Not supported
> .... 0... .... .... = Triggered MU Beamforming
> Feedback: Not supported
> ...0 .... .... .... = Triggered CQI Feedback: Not supported
> ..0. .... .... .... = Partial Bandwidth Extended
> Range: Not supported
> .0.. .... .... .... = Partial Bandwidth DL
> MU-MIMO: Not supported
> 1... .... .... .... = PPE Thresholds Present: True
> Bits 56 to 71: 0x119c
> .... .... .... ...0 = PSR-based SR Support: Not supported
> .... .... .... ..0. = Power Boost Factor ar
> Support: Not supported
> .... .... .... .1.. = HE SU PPDU And HE MU PPDU
> With 4x HE-LTF And 0.8us GI: Supported
> .... .... ..01 1... = Max Nc: Supported
> .... .... .0.. .... = STBC Tx > 80 MHz: Not supported
> .... .... 1... .... = STBC Rx > 80 MHz: Supported
> .... ...1 .... .... = HE ER SU PPDU With 4x HE-LTF
> And 0.8us GI: Supported
> .... ..0. .... .... = 20 MHz In 40 MHz HE PPDU In
> 2.4 GHz Band: Not supported
> .... .0.. .... .... = 20 MHz In 160/80+80 MHz HE
> PPDU: Not supported
> .... 0... .... .... = 80 MHz In 160/80+80 MHz HE
> PPDU: Not supported
> ...1 .... .... .... = HE ER SU PPDU With 1x HE-LTF
> And 0.8us GI: Supported
> ..0. .... .... .... = Midamble Tx/Rx 2x And 1x
> HE-LTF: Not supported
> 00.. .... .... .... = DCM Max RU: 242-tone RU (0x0)
> Bits 72 to 87: 0x000c
> .... .... .... ...0 = Longer Than 16 HE SIG-B OFDM
> Symbols Support: Not supported
> .... .... .... ..0. = Non-Triggered CQI Feedback:
> Not supported
> .... .... .... .1.. = Tx 1024-QAM Support <
> 242-tone RU Support: Supported
> .... .... .... 1... = Rx 1024-QAM Support <
> 242-tone RU Support: Supported
> .... .... ...0 .... = Rx Full BW SU Using HE MU
> PPDU With Compressed HE-SIG-B: Not supported
> .... .... ..0. .... = Rx Full BW SU Using HE MU
> PPDU With Non-Compressed HE-SIG-B: Not supported
> .... .... 00.. .... = Nominal Packet Padding: 0 µs
> for all constellations, Nss and RU allocations (0)
> .... ...0 .... .... = HE MU PPDU With More Than
> One RU Rx Max N_HE-LTF: 0
> 0000 000. .... .... = Reserved: 0x00
> Supported HE-MCS and NSS Set
> Rx and Tx MCS Maps <= 80 MHz
> Rx HE-MCS Map <= 80 MHz: 0xffaa
> .... .... .... ..10 = Max HE-MCS for 1 SS:
> Support for HE-MCS 0-11 (0x2)
> .... .... .... 10.. = Max HE-MCS for 2 SS:
> Support for HE-MCS 0-11 (0x2)
> .... .... ..10 .... = Max HE-MCS for 3 SS:
> Support for HE-MCS 0-11 (0x2)
> .... .... 10.. .... = Max HE-MCS for 4 SS:
> Support for HE-MCS 0-11 (0x2)
> .... ..11 .... .... = Max HE-MCS for 5 SS: Not
> supported for HE PPDUs (0x3)
> .... 11.. .... .... = Max HE-MCS for 6 SS: Not
> supported for HE PPDUs (0x3)
> ..11 .... .... .... = Max HE-MCS for 7 SS: Not
> supported for HE PPDUs (0x3)
> 11.. .... .... .... = Max HE-MCS for 8 SS: Not
> supported for HE PPDUs (0x3)
> Tx HE-MCS Map <= 80 MHz: 0xffaa
> .... .... .... ..10 = Max HE-MCS for 1 SS:
> Support for HE-MCS 0-11 (0x2)
> .... .... .... 10.. = Max HE-MCS for 2 SS:
> Support for HE-MCS 0-11 (0x2)
> .... .... ..10 .... = Max HE-MCS for 3 SS:
> Support for HE-MCS 0-11 (0x2)
> .... .... 10.. .... = Max HE-MCS for 4 SS:
> Support for HE-MCS 0-11 (0x2)
> .... ..11 .... .... = Max HE-MCS for 5 SS: Not
> supported for HE PPDUs (0x3)
> .... 11.. .... .... = Max HE-MCS for 6 SS: Not
> supported for HE PPDUs (0x3)
> ..11 .... .... .... = Max HE-MCS for 7 SS: Not
> supported for HE PPDUs (0x3)
> 11.. .... .... .... = Max HE-MCS for 8 SS: Not
> supported for HE PPDUs (0x3)
> Rx and Tx MCS Maps 160 MHz
> Rx HE-MCS Map 160 MHz: 0xffaa
> .... .... .... ..10 = Max HE-MCS for 1 SS:
> Support for HE-MCS 0-11 (0x2)
> .... .... .... 10.. = Max HE-MCS for 2 SS:
> Support for HE-MCS 0-11 (0x2)
> .... .... ..10 .... = Max HE-MCS for 3 SS:
> Support for HE-MCS 0-11 (0x2)
> .... .... 10.. .... = Max HE-MCS for 4 SS:
> Support for HE-MCS 0-11 (0x2)
> .... ..11 .... .... = Max HE-MCS for 5 SS: Not
> supported for HE PPDUs (0x3)
> .... 11.. .... .... = Max HE-MCS for 6 SS: Not
> supported for HE PPDUs (0x3)
> ..11 .... .... .... = Max HE-MCS for 7 SS: Not
> supported for HE PPDUs (0x3)
> 11.. .... .... .... = Max HE-MCS for 8 SS: Not
> supported for HE PPDUs (0x3)
> Tx HE-MCS Map 160 MHz: 0xffaa
> .... .... .... ..10 = Max HE-MCS for 1 SS:
> Support for HE-MCS 0-11 (0x2)
> .... .... .... 10.. = Max HE-MCS for 2 SS:
> Support for HE-MCS 0-11 (0x2)
> .... .... ..10 .... = Max HE-MCS for 3 SS:
> Support for HE-MCS 0-11 (0x2)
> .... .... 10.. .... = Max HE-MCS for 4 SS:
> Support for HE-MCS 0-11 (0x2)
> .... ..11 .... .... = Max HE-MCS for 5 SS: Not
> supported for HE PPDUs (0x3)
> .... 11.. .... .... = Max HE-MCS for 6 SS: Not
> supported for HE PPDUs (0x3)
> ..11 .... .... .... = Max HE-MCS for 7 SS: Not
> supported for HE PPDUs (0x3)
> 11.. .... .... .... = Max HE-MCS for 8 SS: Not
> supported for HE PPDUs (0x3)
> PPE Thresholds
> .... .011 = NSS: 3
> .111 1... = RU Index Bitmask: 0xf
> NSS 0
> RU allocation: 242
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> RU allocation: 484
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> RU allocation: 996
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> RU allocation: 2x996
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> NSS 1
> RU allocation: 242
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> RU allocation: 484
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> RU allocation: 996
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> RU allocation: 2x996
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> NSS 2
> RU allocation: 242
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> RU allocation: 484
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> RU allocation: 996
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> RU allocation: 2x996
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> NSS 3
> RU allocation: 242
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> RU allocation: 484
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> RU allocation: 996
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> RU allocation: 2x996
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> Ext Tag: HE Operation
> Tag Number: Element ID Extension (255)
> Ext Tag length: 11
> Ext Tag Number: HE Operation (36)
> HE Operation Parameters: 0x023ff0
> .... .... .... .... .... .000 = Default PE Duration: 0
> .... .... .... .... .... 0... = TWT Required: Not required
> .... .... ..11 1111 1111 .... = TXOP Duration RTS
> Threshold: 1023
> .... .... .0.. .... .... .... = VHT Operation
> Information Present: False
> .... .... 0... .... .... .... = Co-Hosted BSS: False
> .... ...0 .... .... .... .... = ER SU Disable: False
> .... ..1. .... .... .... .... = 6 GHz Operation
> Information Present: True
> 0000 00.. .... .... .... .... = Reserved: 0x00
> BSS Color Information: 0x92
> ..01 0010 = BSS Color: 0x12
> .0.. .... = Partial BSS Color: False
> 1... .... = BSS Color Disabled: True
> Basic HE-MCS and NSS Set: 0xfffc
> .... .... .... ..00 = Max HE-MCS for 1 SS: Support for
> HE-MCS 0-7 (0)
> .... .... .... 11.. = Max HE-MCS for 2 SS: Not
> supported for HE PPDUs (3)
> .... .... ..11 .... = Max HE-MCS for 3 SS: Not
> supported for HE PPDUs (3)
> .... .... 11.. .... = Max HE-MCS for 4 SS: Not
> supported for HE PPDUs (3)
> .... ..11 .... .... = Max HE-MCS for 5 SS: Not
> supported for HE PPDUs (3)
> .... 11.. .... .... = Max HE-MCS for 6 SS: Not
> supported for HE PPDUs (3)
> ..11 .... .... .... = Max HE-MCS for 7 SS: Not
> supported for HE PPDUs (3)
> 11.. .... .... .... = Max HE-MCS for 8 SS: Not
> supported for HE PPDUs (3)
> 6 GHz Operation Information
> Primary Channel: 33
> Control: 0x03
> .... ..11 = Channel Width: 160MHz or 80MHz+80MHz (3)
> .... .0.. = Duplicate Beacon: False
> ..00 0... = Regulatory Info: 0
> 00.. .... = Reserved: 0
> Channel Center Frequency Segment 0: 39
> Channel Center Frequency Segment 1: 47
> Minimum Rate: 6
> Ext Tag: HE 6 GHz Band Capabilities
> Tag Number: Element ID Extension (255)
> Ext Tag length: 2
> Ext Tag Number: HE 6 GHz Band Capabilities (59)
> Capabilities Information: 0x36b8
> .... .... .... .000 = Minimum MPDU Start Spacing: No
> restriction (0x0)
> .... .... ..11 1... = Maximum A-MPDU Length Exponent:
> 1 048 575 (0x7)
> .... .... 10.. .... = Maximum MPDU Length: 11 454 (0x2)
> .... ...0 .... .... = Reserved: 0x0
> .... .11. .... .... = SM Power Save: SM Power Save
> disabled (0x3)
> .... 0... .... .... = RD Responder: Not supported
> ...1 .... .... .... = Rx Antenna Pattern Consistency: Supported
> ..1. .... .... .... = Tx Antenna Pattern Consistency: Supported
> 00.. .... .... .... = Reserved: 0x0
> Tag: Vendor Specific: Microsoft Corp.: WMM/WME: Parameter Element
> Tag Number: Vendor Specific (221)
> Tag length: 24
> OUI: 00:50:f2 (Microsoft Corp.)
> Vendor Specific OUI Type: 2
> Type: WMM/WME (0x02)
> WME Subtype: Parameter Element (1)
> WME Version: 1
> WME QoS Info: 0x01
> 0... .... = U-APSD: Disabled
> .... 0001 = Parameter Set Count: 0x1
> .000 .... = Reserved: 0x0
> Reserved: 00
> Ac Parameters ACI 0 (Best Effort), ACM no, AIFSN 3,
> ECWmin/max 4/10 (CWmin/max 15/1023), TXOP 0
> ACI / AIFSN Field: 0x03
> .... 0011 = AIFSN: 3
> ...0 .... = Admission Control Mandatory: No
> .00. .... = ACI: Best Effort (0)
> 0... .... = Reserved: 0
> ECW: 0xa4
> 1010 .... = ECW Max: 10
> .... 0100 = ECW Min: 4
> CW Max: 1023
> CW Min: 15
> TXOP Limit: 0
> Ac Parameters ACI 1 (Background), ACM no, AIFSN 7,
> ECWmin/max 4/10 (CWmin/max 15/1023), TXOP 0
> ACI / AIFSN Field: 0x27
> .... 0111 = AIFSN: 7
> ...0 .... = Admission Control Mandatory: No
> .01. .... = ACI: Background (1)
> 0... .... = Reserved: 0
> ECW: 0xa4
> 1010 .... = ECW Max: 10
> .... 0100 = ECW Min: 4
> CW Max: 1023
> CW Min: 15
> TXOP Limit: 0
> Ac Parameters ACI 2 (Video), ACM no, AIFSN 2, ECWmin/max
> 3/4 (CWmin/max 7/15), TXOP 94
> ACI / AIFSN Field: 0x42
> .... 0010 = AIFSN: 2
> ...0 .... = Admission Control Mandatory: No
> .10. .... = ACI: Video (2)
> 0... .... = Reserved: 0
> ECW: 0x43
> 0100 .... = ECW Max: 4
> .... 0011 = ECW Min: 3
> CW Max: 15
> CW Min: 7
> TXOP Limit: 94
> Ac Parameters ACI 3 (Voice), ACM no, AIFSN 2, ECWmin/max
> 2/3 (CWmin/max 3/7), TXOP 47
> ACI / AIFSN Field: 0x62
> .... 0010 = AIFSN: 2
> ...0 .... = Admission Control Mandatory: No
> .11. .... = ACI: Voice (3)
> 0... .... = Reserved: 0
> ECW: 0x32
> 0011 .... = ECW Max: 3
> .... 0010 = ECW Min: 2
> CW Max: 7
> CW Min: 3
>
>
> If I can check anyhing in between pls. let me know.
> OpenWRT is known to have some tuning for these things but ath11k was
> not included by default hence also QCN9074. So I am now also working
> with 5.15 master, compiled custom OpenWRT with enabled ath11k and
> included *.bin firmware into OpenWRT. Resolved MSI issues to VT-D but
> so far this is still work in progress as the card does not error out
> but never responds to power on command. MHI keeps waiting for power
> on. This is however secondary topic I started looking into due lack of
> progress on a regular distro. Tried also latest 6.1 rc4 kernel on
> ubuntu with no change.
>
> Regards,
> Mariusz
>
>
> On Mon, 14 Nov 2022 at 14:19, Nagarajan Maran (QUIC)
> <quic_nmaran@quicinc.com> wrote:
>> Hi Mariusz,
>>
>>
>>
>> We checked the upstream driver code and firmware bins similar to your setup environment and it seems to work well.
>>
>> Could you kindly check whether your Wi-Fi card has been OTP fused for 6Ghz?
>>
>>
>>
>> -Thanks
>>
>> Nagarajan M.
>>
>>
>>
>> From: Mariusz <enebeo@gmail.com>
>> Sent: Tuesday, November 8, 2022 8:25 PM
>> To: Nagarajan Maran (QUIC) <quic_nmaran@quicinc.com>
>> Cc: ath11k@lists.infradead.org
>> Subject: Re: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
>>
>>
>>
>> Perhaps also something interesting, I apply reg domain of Belgium/BE. It has lower 6GHz channels allowed.
>>
>>
>>
>> iw reg get
>> global
>> country BE: DFS-ETSI
>> (2400 - 2483 @ 40), (N/A, 20), (N/A)
>> (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
>> (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
>> (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
>> (5725 - 5875 @ 80), (N/A, 13), (N/A)
>> (5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
>> (57000 - 66000 @ 2160), (N/A, 40), (N/A)
>>
>> phy#3 (self-managed)
>> country US: DFS-FCC
>> (2402 - 2472 @ 40), (6, 30), (N/A)
>> (5170 - 5250 @ 80), (N/A, 30), (N/A), AUTO-BW
>> (5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
>> (5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS, AUTO-BW
>> (5735 - 5895 @ 160), (N/A, 30), (N/A), AUTO-BW
>> (5945 - 7125 @ 160), (N/A, 30), (N/A), NO-OUTDOOR, AUTO-BW
>>
>>
>>
>> When I start hostapd with acs_survey or channel=0 it starts but pretends to work, no other client can connect to this ssid.
>>
>>
>>
>> When I disable acs in hostapd.conf and set channel=1 (freq 5955 in 6GHz range) so allowed per reg domain it refuses to start:
>>
>>
>>
>> Mode: IEEE 802.11a Channel: 1 Frequency: 5955 MHz
>> nl80211: Set freq 5955 (ht_enabled=0, vht_enabled=0, he_enabled=1, eht_enabled=0, bandwidth=160 MHz, cf1=5955 MHz, cf2=0 MHz)
>> * freq=5955
>> * eht_enabled=0
>> * he_enabled=1
>> * vht_enabled=0
>> * ht_enabled=0
>> * radar_background=0
>> * bandwidth=160
>> * channel_width=5
>> * center_freq1=5955
>> * center_freq2=0
>> nl80211: kernel reports: invalid channel definition
>> nl80211: Failed to set channel (freq=5955): -22 (Invalid argument)
>>
>>
>>
>> reg domain BE is more restrictive than US so channel 1 should be enabled in both cases
>>
>> Previous country code BE, new country code BE
>> nl80211: Regulatory information - country=US (DFS-FCC)
>> nl80211: 2402-2472 @ 40 MHz 30 mBm
>> nl80211: 5170-5250 @ 80 MHz 30 mBm
>> nl80211: 5250-5330 @ 80 MHz 24 mBm (DFS)
>> nl80211: 5490-5730 @ 160 MHz 24 mBm (DFS)
>> nl80211: 5735-5895 @ 160 MHz 30 mBm
>> nl80211: 5945-7125 @ 160 MHz 30 mBm (no outdoor)
>> nl80211: Mode IEEE 802.11a: 5955 5975 5995 6015 6035 6055 6075 6095 6115 6135 6155 6175 6195 6215 6235 6255 6275 6295 6315 6335 6355 6375 6395 6415 6435 6455 6475 6495 6515 6535 6555 6575 6595 6615 6635 6655 6675 6695 6715 6735 6755 6775 6795 6815 6835 6855 6875 6895 6915 6935 6955 6975 6995 7015 7035 7055 7075 7095 7115 5935[DISABLED]
>>
>>
>>
>> for op_class=134 = 160MHz valid channels are 1-29, 33-61, 65-93, 97-125, 129-157, 161-189, 193-221
>>
>>
>>
>>
>>
>> phy: phy3
>> BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
>> wlp1s0: interface state UNINITIALIZED->COUNTRY_UPDATE
>> Previous country code BE, new country code BE
>> nl80211: Regulatory information - country=US (DFS-FCC)
>> nl80211: 2402-2472 @ 40 MHz 30 mBm
>> nl80211: 5170-5250 @ 80 MHz 30 mBm
>> nl80211: 5250-5330 @ 80 MHz 24 mBm (DFS)
>> nl80211: 5490-5730 @ 160 MHz 24 mBm (DFS)
>> nl80211: 5735-5895 @ 160 MHz 30 mBm
>> nl80211: 5945-7125 @ 160 MHz 30 mBm (no outdoor)
>> nl80211: Mode IEEE 802.11a: 5955 5975 5995 6015 6035 6055 6075 6095 6115 6135 6155 6175 6195 6215 6235 6255 6275 6295 6315 6335 6355 6375 6395 6415 6435 6455 6475 6495 6515 6535 6555 6575 6595 6615 6635 6655 6675 6695 6715 6735 6755 6775 6795 6815 6835 6855 6875 6895 6915 6935 6955 6975 6995 7015 7035 7055 7075 7095 7115 5935[DISABLED]
>> Completing interface initialization
>> Mode: IEEE 802.11a Channel: 33 Frequency: 6115 MHz
>> nl80211: Set freq 6115 (ht_enabled=0, vht_enabled=0, he_enabled=1, eht_enabled=0, bandwidth=160 MHz, cf1=6115 MHz, cf2=0 MHz)
>> * freq=6115
>> * eht_enabled=0
>> * he_enabled=1
>> * vht_enabled=0
>> * ht_enabled=0
>> * radar_background=0
>> * bandwidth=160
>> * channel_width=5
>> * center_freq1=6115
>> * center_freq2=0
>> nl80211: kernel reports: invalid channel definition
>> nl80211: Failed to set channel (freq=6115): -22 (Invalid argument)
>> Could not set channel for kernel driver
>> Interface initialization failed
>>
>>
>>
>>
>>
>>
>>
>> How is this invalid channel?
>>
>>
>>
>> root@s4:/home/angel/hostap/hostapd# iw phy3 channels
>> Band 4:
>> * 5955 MHz [1]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 5975 MHz [5]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 5995 MHz [9]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6015 MHz [13]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6035 MHz [17]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6055 MHz [21]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6075 MHz [25]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6095 MHz [29]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6115 MHz [33]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6135 MHz [37]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6155 MHz [41]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6175 MHz [45]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6195 MHz [49]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6215 MHz [53]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6235 MHz [57]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6255 MHz [61]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6275 MHz [65]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6295 MHz [69]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6315 MHz [73]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6335 MHz [77]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6355 MHz [81]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6375 MHz [85]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6395 MHz [89]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6415 MHz [93]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6435 MHz [97]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6455 MHz [101]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6475 MHz [105]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6495 MHz [109]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6515 MHz [113]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6535 MHz [117]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6555 MHz [121]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6575 MHz [125]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6595 MHz [129]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6615 MHz [133]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6635 MHz [137]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6655 MHz [141]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6675 MHz [145]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6695 MHz [149]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6715 MHz [153]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6735 MHz [157]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6755 MHz [161]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6775 MHz [165]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6795 MHz [169]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6815 MHz [173]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6835 MHz [177]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6855 MHz [181]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6875 MHz [185]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6895 MHz [189]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6915 MHz [193]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6935 MHz [197]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6955 MHz [201]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6975 MHz [205]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 6995 MHz [209]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 7015 MHz [213]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 7035 MHz [217]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 7055 MHz [221]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 7075 MHz [225]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 7095 MHz [229]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 7115 MHz [233]
>> Maximum TX power: 30.0 dBm
>> Channel widths: 20MHz
>> * 5935 MHz [2] (disabled)
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Mon, 7 Nov 2022 at 17:07, Nagarajan Maran (QUIC) <quic_nmaran@quicinc.com> wrote:
>>
>> Hi Mariusz,
>>
>> We are looking into this issue. It seems that this error can occur when the given frequency is not present or when the given frequency is disabled.
>> To further analyze the issue, could you kindly let us know the output of the below commands during failure case.
>> 1) iw dev
>> 2) iw phyX channels
>>
>> Also, could you kindly send the WiFi driver boot up logs with "debug_mask=0x212" enabled during insmod of ath11k.ko module.
>>
>> Thanks,
>> Nagarajan M.
>>
>> -----Original Message-----
>>
>> From: Mariusz <enebeo@gmail.com>
>> To: ath11k@lists.infradead.org
>> Subject: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
>> Message-ID:
>> <CAJrE-q6NVEF4sNW1s4Zz7Pb2ryzCi69e+_vLQswBWm747DHYDw@mail.gmail.com>
>> Content-Type: text/plain; charset="UTF-8"
>>
>> Hi,
>>
>> As support for QCN9074 got better I went ahead and built a 6E linux based AP. Dell R720 server x86 running Linux s4 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64
>> x86_64 x86_64 GNU/Linux.
>>
>> My issue is that I cannot get it working on 6GHz bands but it works fine on 5GHz. I bought 6E version and since this is a single band module it cannot be both 5G & 6G and linux driver does not agree with it being 6E version:
>>
>> [71914.038562] ath11k_pci 0000:03:00.0: BAR 0: assigned [mem 0xdf800000-0xdf9fffff 64bit] [71914.038840] ath11k_pci 0000:03:00.0: MSI vectors: 16 [71914.038852] ath11k_pci 0000:03:00.0: qcn9074 hw1.0 [71914.194459] mhi mhi0: Requested to power ON [71914.194712] mhi mhi0: Power on setup success [71914.297749] mhi mhi0: Wait for device to enter SBL or Mission mode [71914.647118] ath11k_pci 0000:03:00.0: chip_id 0x0 chip_family 0x0 board_id 0xff soc_id 0xffffffff [71914.647134] ath11k_pci 0000:03:00.0: fw_version 0x250a04b8 fw_build_timestamp 2021-12-20 06:41 fw_build_id [71916.310787] ath11k_pci 0000:03:00.0 wlp3s0: renamed from wlan0
>>
>> HE PHY Capabilities: (0x1c604c88ffdb839c110c00):
>> HE40/HE80/5GHz
>> HE160/5GHz
>> HE160/HE80+80/5GHz
>>
>> iw dev wlp3s0 set freq 6195 160MHz
>> kernel reports: Channel is disabled
>> command failed: Invalid argument (-22)
>>
>> I am using the latest firmware files from ath11k tree. Is there any special firmware to force this to 6GHz? I read somewhere board_id determines which one it is and 255 disables 6GHz but I miss more data on that.
>>
>> phy#2 (self-managed)
>> country US: DFS-FCC
>> (2402 - 2472 @ 40), (6, 30), (N/A)
>> (5170 - 5250 @ 80), (N/A, 30), (N/A), AUTO-BW
>> (5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
>> (5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS, AUTO-BW
>> (5735 - 5895 @ 160), (N/A, 30), (N/A), AUTO-BW
>> (5945 - 7125 @ 160), (N/A, 30), (N/A), NO-OUTDOOR, AUTO-BW
>>
>> It works fine in 5GHz but this is not what I purchased it for, so I am puzzled if this is something in software or I was sold wrong hardware.Is there a specific board-2.bin for 6GHz? Since the 9074 chip is the same in all versions perhaps this is a software hiccup.
>>
>> Any clues are welcome.
>>
>> Regards,
>> Mario
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
2022-11-15 18:29 ` walde
@ 2022-11-15 19:18 ` Mariusz
2022-11-18 11:26 ` Sven Eckelmann
1 sibling, 0 replies; 18+ messages in thread
From: Mariusz @ 2022-11-15 19:18 UTC (permalink / raw)
To: walde; +Cc: ath11k
Hi,
Not a problem however I have not achieved working configuration yet so
what I do is not bulletproof.
Support for my board which is likely just PCB guys stated board_id is
not encoded in eeprom, they mention driver modification but I still
miss details what they modify. Is it just to ignore board_id or other
things to circumvent whatever are added... did not get that far.
For the firmware, it is a bit clearer. What you can do is extract
firmware for board_id 162 from board-2.bin blob and place it in the
firmware folder as board.bin.
1. You need the swiss army knife tool for ath11: ath11k-bdencoder, it
is on github.(git clone
https://github.com/qca/qca-swiss-army-knife.git)
2. There's a script there to split board-2.bin firmware. You
can/should get the latest firmware from github as well since older
ones have reg domain issues. Not to attest this one does not but older
ones do report all 6E frequencies as disabled.
3. Run the tool/script ./ath11k-bdencoder -e
/home/angel/target/firmware/board-2.bin (adjust your path :) )
4. From extracted list of bin files cp
bus\=pci\,qmi-chip-id\=0\,qmi-board-id\=162.bin
/lib/firmware/ath11k/QCN9074/hw1.0/board.bin
5. Delete board-2.bin blob from /lib/firmware/ath11k/QCN9074/hw1.0 ,
only keep board.bin (one renamed in copy process from 162).
6. either reboot or rmmod ath11k_pci rmmod ath11k modprobe ath11k_pci,
this will load the new FW.
7. iw phy should list all 6E freq with 30dbm power
For drivers, they sent me some ko files but even for same 5.17.0
kernel magic does not match. I modified ko files to match symbol
tables of my kernel but it resulted in more errors. Still waiting for
source files to replace & compile with my kernel.
This is where my story ends... for now at least. I am now trying to
get openwrt seeing this over pci bus (not integrated soc) to leverage
some extra options.
On Tue, 15 Nov 2022 at 19:29, walde <waldemar.stroh@uni-siegen.de> wrote:
>
> Hi,
>
> we probably have the same problem.
> We have two Pinapple 6 Wifi 6 cards from the manufacturer 8devices that
> we want to operate at 6 GHz. The modules have the QCN 9074 chipset and
> are also certified for the 6E standard. The modules work very well at 5
> GHZ. However the option to transmit on 6 GHz is not available. The board
> ID is also defined as 0xff. If there is any information you could share
> to enable the modules for 6 GHz, we would appreciate it.
>
> Regards,
>
> Waldemar S.
>
> Am 15.11.2022 um 11:02 schrieb Mariusz:
>
> > Hi,
> >
> > I have asked the manufacturer to confirm. It has the 6E sticker on it
> > but I have no lower level tools to read e-fuses if any. Regarding
> > board_id they say normally on non-x86 this is set by bootloader so it
> > is not hardcoded in eeprom.
> > For the HW side, on the PCB there are two markings, 5G (top) and 6E
> > (bottom), none of them was bridged from the factory. I bridged the 6E
> > one but that did not change anything. In the meantime I also deployed
> > aircrack-ng on AX210 client since I have no 6GHz equipment to do other
> > testing.
> >
> > On the client:
> > iw wlp1s0 del
> > airmon-ng start wlan0mon
> > tshark -i wlan0mon -T text -V > log.wifi
> > airodump-ng -C 6115 -i wlan0mon --bssid C4:4B:D1:D0:00:7E
> >
> > Checking available frequencies, this could take few seconds.
> > Freq 6115 ][ Elapsed: 0 s ][ 2022-11-08 19:48
> > BSSID PWR Beacons #Data, #/s CH MB ENC CIPHER AUTH ESSID
> > C4:4B:D1:D0:00:7E -46 12 0 0 33 54e WPA3 CCMP SAE dupa
> >
> > So the client is seeing signal strength and beacon packets which are
> > increasing continuously. It has concluded SSID, MAC and encryption
> > details correctly on 6E freq - 6115MHz and it is also seeing op class
> > 134 = 160Mhz channel as set. Then I assume electronics at least TX on
> > QCN9074 is working fine as the remote client is picking up something
> > but whatever is not right as there's no handshake. I tried to
> > pre-setup SSID so it auto connects without SSID discovery on Win
> > client but no juice. So I dumped packet details, not sure if I read
> > all flags right but there's a mix of it mentioning 6GHz supported &
> > enabled but in other places OFDM is listed instead of OFDMA. Now which
> > part of it is due aircrack-ng having all updates to support/decode 6E
> > don't know, it is another variable here.
> >
> > 802.11 radio information
> > PHY type: 802.11a (OFDM) (5)
> > Turbo type: Non-turbo (0)
> > Data rate: 6.0 Mb/s
> > Channel: 33
> > Frequency: 6115MHz
> > Signal strength (dBm): -47 dBm
> > TSF timestamp: 1826096995
> > [Duration: 312µs]
> > [Preamble: 20µs]
> > [IFS: 204488µs]
> > [Start: 1826096683µs]
> > [End: 1826096995µs]
> >
> >
> > IEEE 802.11 Beacon frame, Flags: ........C
> > Type/Subtype: Beacon frame (0x0008)
> > Frame Control Field: 0x8000
> > .... ..00 = Version: 0
> > .... 00.. = Type: Management frame (0)
> > 1000 .... = Subtype: 8
> > Flags: 0x00
> > .... ..00 = DS status: Not leaving DS or network is
> > operating in AD-HOC mode (To DS: 0 From DS: 0) (0x0)
> > .... .0.. = More Fragments: This is the last fragment
> > .... 0... = Retry: Frame is not being retransmitted
> > ...0 .... = PWR MGT: STA will stay up
> > ..0. .... = More Data: No data buffered
> > .0.. .... = Protected flag: Data is not protected
> > 0... .... = +HTC/Order flag: Not strictly ordered
> > .000 0000 0000 0000 = Duration: 0 microseconds
> > Receiver address: Broadcast (ff:ff:ff:ff:ff:ff)
> > Destination address: Broadcast (ff:ff:ff:ff:ff:ff)
> > Transmitter address: WallysCo_d0:00:7e (c4:4b:d1:d0:00:7e)
> > Source address: WallysCo_d0:00:7e (c4:4b:d1:d0:00:7e)
> > BSS Id: WallysCo_d0:00:7e (c4:4b:d1:d0:00:7e)
> > .... .... .... 0000 = Fragment number: 0
> > 0100 0100 0101 .... = Sequence number: 1093
> > Frame check sequence: 0xcf64d100 [unverified]
> > [FCS Status: Unverified]
> >
> > IEEE 802.11 Wireless Management
> > Fixed parameters (12 bytes)
> > Timestamp: 4349132798
> > Beacon Interval: 0.204800 [Seconds]
> > Capabilities Information: 0x1011
> > .... .... .... ...1 = ESS capabilities: Transmitter is an AP
> > .... .... .... ..0. = IBSS status: Transmitter belongs to a BSS
> > .... ..0. .... 00.. = CFP participation capabilities: No
> > point coordinator at AP (0x00)
> > .... .... ...1 .... = Privacy: AP/STA can support WEP
> > .... .... ..0. .... = Short Preamble: Not Allowed
> > .... .... .0.. .... = PBCC: Not Allowed
> > .... .... 0... .... = Channel Agility: Not in use
> > .... ...0 .... .... = Spectrum Management: Not Implemented
> > .... .0.. .... .... = Short Slot Time: Not in use
> > .... 0... .... .... = Automatic Power Save Delivery: Not Implemented
> > ...1 .... .... .... = Radio Measurement: Implemented
> > ..0. .... .... .... = DSSS-OFDM: Not Allowed
> > .0.. .... .... .... = Delayed Block Ack: Not Implemented
> > 0... .... .... .... = Immediate Block Ack: Not Implemented
> > Tagged parameters (175 bytes)
> > Tag: SSID parameter set: dupa
> > Tag Number: SSID parameter set (0)
> > Tag length: 4
> > SSID: dupa
> > Tag: Supported Rates 6(B), 9, 12(B), 18, 24(B), 36, 48, 54, [Mbit/sec]
> > Tag Number: Supported Rates (1)
> > Tag length: 8
> > Supported Rates: 6(B) (0x8c)
> > Supported Rates: 9 (0x12)
> > Supported Rates: 12(B) (0x98)
> > Supported Rates: 18 (0x24)
> > Supported Rates: 24(B) (0xb0)
> > Supported Rates: 36 (0x48)
> > Supported Rates: 48 (0x60)
> > Supported Rates: 54 (0x6c)
> > Tag: DS Parameter set: Current Channel: 33
> > Tag Number: DS Parameter set (3)
> > Tag length: 1
> > Current Channel: 33
> > Tag: Traffic Indication Map (TIM): DTIM 1 of 2 bitmap
> > Tag Number: Traffic Indication Map (TIM) (5)
> > Tag length: 4
> > DTIM count: 1
> > DTIM period: 2
> > Bitmap control: 0x00
> > .... ...0 = Multicast: False
> > 0000 000. = Bitmap Offset: 0x00
> > Partial Virtual Bitmap: 00
> > Tag: Country Information: Country Code BE, Environment 0x04
> > Tag Number: Country Information (7)
> > Tag length: 6
> > Code: BE
> > Environment: 4
> > Country Info: Operating Extension Identifier: 201,
> > Operating Class: 134, Coverage Class: 0
> > Operating Extension Identifier: 201
> > Operating Class: 134
> > Coverage Class: 0
> > Tag: RSN Information
> > Tag Number: RSN Information (48)
> > Tag length: 20
> > RSN Version: 1
> > Group Cipher Suite: 00:0f:ac (Ieee 802.11) AES (CCM)
> > Group Cipher Suite OUI: 00:0f:ac (Ieee 802.11)
> > Group Cipher Suite type: AES (CCM) (4)
> > Pairwise Cipher Suite Count: 1
> > Pairwise Cipher Suite List 00:0f:ac (Ieee 802.11) AES (CCM)
> > Pairwise Cipher Suite: 00:0f:ac (Ieee 802.11) AES (CCM)
> > Pairwise Cipher Suite OUI: 00:0f:ac (Ieee 802.11)
> > Pairwise Cipher Suite type: AES (CCM) (4)
> > Auth Key Management (AKM) Suite Count: 1
> > Auth Key Management (AKM) List 00:0f:ac (Ieee 802.11) SAE (SHA256)
> > Auth Key Management (AKM) Suite: 00:0f:ac (Ieee
> > 802.11) SAE (SHA256)
> > Auth Key Management (AKM) OUI: 00:0f:ac (Ieee 802.11)
> > Auth Key Management (AKM) type: SAE (SHA256) (8)
> > RSN Capabilities: 0x00cc
> > .... .... .... ...0 = RSN Pre-Auth capabilities:
> > Transmitter does not support pre-authentication
> > .... .... .... ..0. = RSN No Pairwise capabilities:
> > Transmitter can support WEP default key 0 simultaneously with Pairwise
> > key
> > .... .... .... 11.. = RSN PTKSA Replay Counter
> > capabilities: 16 replay counters per PTKSA/GTKSA/STAKeySA (0x3)
> > .... .... ..00 .... = RSN GTKSA Replay Counter
> > capabilities: 1 replay counter per PTKSA/GTKSA/STAKeySA (0x0)
> > .... .... .1.. .... = Management Frame Protection Required: True
> > .... .... 1... .... = Management Frame Protection Capable: True
> > .... ...0 .... .... = Joint Multi-band RSNA: False
> > .... ..0. .... .... = PeerKey Enabled: False
> > ..0. .... .... .... = Extended Key ID for Individually
> > Addressed Frames: Not supported
> > Tag: RM Enabled Capabilities (5 octets)
> > Tag Number: RM Enabled Capabilities (70)
> > Tag length: 5
> > RM Capabilities: 0x72 (octet 1)
> > .... ...0 = Link Measurement: Disabled
> > .... ..1. = Neighbor Report: Enabled
> > .... .0.. = Parallel Measurements: Disabled
> > .... 0... = Repeated Measurements: Disabled
> > ...1 .... = Beacon Passive Measurement: Enabled
> > ..1. .... = Beacon Active Measurement: Enabled
> > .1.. .... = Beacon Table Measurement: Supported
> > 0... .... = Beacon Measurement Reporting Conditions: Disabled
> > RM Capabilities: 0x00 (octet 2)
> > .... ...0 = Frame Measurement: Disabled
> > .... ..0. = Channel Load Measurement: Disabled
> > .... .0.. = Noise Histogram Measurement: Disabled
> > .... 0... = Statistics Measurement: Disabled
> > ...0 .... = LCI Measurement: Disabled
> > ..0. .... = LCI Azimuth capability: Disabled
> > .0.. .... = Transmit Stream/Category Measurement: Not supported
> > 0... .... = Triggered Transmit Stream/Category
> > Measurement: Disabled
> > RM Capabilities: 0x00 (octet 3)
> > .... ...0 = AP Channel Report capability: Disabled
> > .... ..0. = RM MIB capability: Disabled
> > ...0 00.. = Operating Channel Max Measurement Duration: 0
> > 000. .... = Nonoperating Channel Max Measurement Duration: 0
> > RM Capabilities: 0x00 (octet 4)
> > .... .000 = Measurement Pilotcapability: 0
> > .... 0... = Measurement Pilot Transmission Information: Disabled
> > ...0 .... = Neighbor Report TSF Offset: Disabled
> > ..0. .... = RCPI Measurement capability: Disabled
> > .0.. .... = RSNI Measurement capability: Not supported
> > 0... .... = BSS Average Access Delay capability: Disabled
> > RM Capabilities: 0x00 (octet 5)
> > .... ...0 = BSS Available Admission Capacity
> > capability: Disabled
> > .... ..0. = Antenna capability: Disabled
> > .... .0.. = FTM Range Report Capability: Disabled
> > .... 0... = Civic Location Measurement Capability: Disabled
> > 0000 .... = Reserved: 0x0
> > Tag: Supported Operating Classes
> > Tag Number: Supported Operating Classes (59)
> > Tag length: 2
> > Current Operating Class: 134
> > Tag: Extended Capabilities (10 octets)
> > Tag Number: Extended Capabilities (127)
> > Tag length: 10
> > Extended Capabilities: 0x04 (octet 1)
> > .... ...0 = 20/40 BSS Coexistence Management Support:
> > Not supported
> > .... ..0. = Reserved (was On-demand beacon): 0x0
> > .... .1.. = Extended Channel Switching: Supported
> > .... 0... = Reserved (was WAVE indication): 0x0
> > ...0 .... = PSMP Capability: Not supported
> > ..0. .... = Reserved: 0x0
> > .0.. .... = S-PSMP Support: Not supported
> > 0... .... = Event: Not supported
> > Extended Capabilities: 0x00 (octet 2)
> > .... ...0 = Diagnostics: Not supported
> > .... ..0. = Multicast Diagnostics: Not supported
> > .... .0.. = Location Tracking: Not supported
> > .... 0... = FMS: Not supported
> > ...0 .... = Proxy ARP Service: Not supported
> > ..0. .... = Collocated Interference Reporting: Not supported
> > .0.. .... = Civic Location: Not supported
> > 0... .... = Geospatial Location: Not supported
> > Extended Capabilities: 0x00 (octet 3)
> > .... ...0 = TFS: Not supported
> > .... ..0. = WNM Sleep Mode: Not supported
> > .... .0.. = TIM Broadcast: Not supported
> > .... 0... = BSS Transition: Not supported
> > ...0 .... = QoS Traffic Capability: Not supported
> > ..0. .... = AC Station Count: Not supported
> > .0.. .... = Multiple BSSID: Not supported
> > 0... .... = Timing Measurement: Not supported
> > Extended Capabilities: 0x00 (octet 4)
> > .... ...0 = Channel Usage: Not supported
> > .... ..0. = SSID List: Not supported
> > .... .0.. = DMS: Not supported
> > .... 0... = UTC TSF Offset: Not supported
> > ...0 .... = TPU Buffer STA Support: Not supported
> > ..0. .... = TDLS Peer PSM Support: Not supported
> > .0.. .... = TDLS channel switching: Not supported
> > 0... .... = Interworking: Not supported
> > Extended Capabilities: 0x00 (octet 5)
> > .... ...0 = QoS Map: Not supported
> > .... ..0. = EBR: Not supported
> > .... .0.. = SSPN Interface: Not supported
> > .... 0... = Reserved: 0x0
> > ...0 .... = MSGCF Capability: Not supported
> > ..0. .... = TDLS Support: Not supported
> > .0.. .... = TDLS Prohibited: Not supported
> > 0... .... = TDLS Channel Switching Prohibited: Not supported
> > Extended Capabilities: 0x00 (octet 6)
> > .... ...0 = Reject Unadmitted Frame: Not supported
> > .... 000. = Service Interval Granularity: 5 ms (0)
> > ...0 .... = Identifier Location: Not supported
> > ..0. .... = U-APSD Coexistence: Not supported
> > .0.. .... = WNM Notification: Not supported
> > 0... .... = QAB Capability: 0x0
> > Extended Capabilities: 0x00 (octet 7)
> > .... ...0 = UTF-8 SSID: Not supported
> > .... ..0. = QMF Activated: False
> > .... .0.. = QMF Reconfiguration Activated: False
> > .... 0... = Robust AV Streaming: False
> > ...0 .... = Advanced GCR: False
> > ..0. .... = Mesh GCR: False
> > .0.. .... = SCS: False
> > 0... .... = QLoad Report: False
> > Extended Capabilities: 0x0040 (octets 8 & 9)
> > .... .... .... ...0 = Alternate EDCA: False
> > .... .... .... ..0. = Unprotected TXOP Negotiation: False
> > .... .... .... .0.. = Protected TXOP Negotiation: False
> > .... .... .... 0... = Reserved: 0x0
> > .... .... ...0 .... = Protected QLoad Report: False
> > .... .... ..0. .... = TDLS Wider Bandwidth: Not supported
> > .... .... .1.. .... = Operating Mode Notification: Supported
> > .... ...0 0... .... = Max Number Of MSDUs In A-MSDU:
> > No limit (0)
> > .... ..0. .... .... = Channel Schedule Management: False
> > .... .0.. .... .... = Geodatabase Inband Enabling Signal: False
> > .... 0... .... .... = Network Channel Control: False
> > ...0 .... .... .... = White Space Map: False
> > ..0. .... .... .... = Channel Availability Query: False
> > .0.. .... .... .... = Fine Timing Measurement Responder: False
> > 0... .... .... .... = Fine Timing Measurement Initiator: False
> > Extended Capabilities: 0x40 (octet 10)
> > .... ...0 = FILS Capable: False
> > .... ..0. = Extended Spectrum Management Capable: False
> > .... .0.. = Future Channel Capable: False
> > .... 0... = Reserved: 0x0
> > ...0 .... = Reserved: 0x0
> > ..0. .... = TWT Requester Support: False
> > .1.. .... = TWT Responder Support: True
> > 0... .... = OBSS Narrow Bandwidth RU in UL OFDMA
> > Tolerance Support: False
> > Tag: Tx Power Envelope
> > Tag Number: Tx Power Envelope (195)
> > Tag length: 2
> > Tx Pwr Info: 0x18
> > .... .000 = Max Tx Pwr Count: 0
> > ..01 1... = Max Tx Pwr Unit Interpretation: Unknown (3)
> > 00.. .... = Reserved: 0
> > Local Max Tx Pwr Constraint 20MHz: -1.0 dBm
> > Tag: Tx Power Envelope
> > Tag Number: Tx Power Envelope (195)
> > Tag length: 2
> > Tx Pwr Info: 0x58
> > .... .000 = Max Tx Pwr Count: 0
> > ..01 1... = Max Tx Pwr Unit Interpretation: Unknown (3)
> > 01.. .... = Reserved: 1
> > Local Max Tx Pwr Constraint 20MHz: 5.0 dBm
> > Tag: RSN eXtension (1 octet)
> > Tag Number: RSN eXtension (244)
> > Tag length: 1
> > RSNX: 0x20 (octet 1)
> > .... 0000 = RSNX Length: 0
> > ...0 .... = Protected TWT Operations Support: 0
> > ..1. .... = SAE Hash to element: 1
> > 00.. .... = Reserved: 0x0
> > Ext Tag: HE Capabilities
> > Tag Number: Element ID Extension (255)
> > Ext Tag length: 38
> > Ext Tag Number: HE Capabilities (35)
> > HE MAC Capabilities Information: 0x10409a18000d
> > .... .... .... .... .... .... .... .... .... .... ....
> > ...1 = +HTC HE Support: Supported
> > .... .... .... .... .... .... .... .... .... .... ....
> > ..0. = TWT Requester Support: Not supported
> > .... .... .... .... .... .... .... .... .... .... ....
> > .1.. = TWT Responder Support: Supported
> > .... .... .... .... .... .... .... .... .... .... ...0
> > 1... = Dynamic Fragmentation Support: Level 1 dynamic fragmentation
> > support (1)
> > .... .... .... .... .... .... .... .... .... .... 000.
> > .... = Maximum Number of Fragmented MSDUs: 1
> > .... .... .... .... .... .... .... .... .... ..00 ....
> > .... = Minimum Fragment Size: No restriction on minimum payload size
> > (0)
> > .... .... .... .... .... .... .... .... .... 00.. ....
> > .... = Trigger Frame MAC Padding Duration: 0 (0)
> > .... .... .... .... .... .... .... .... .000 .... ....
> > .... = Multi-TID Aggregation Rx Support: 0
> > .... .... .... .... .... .... .... ...0 0... .... ....
> > .... = HE Link Adaptation Support: No feedback if the STA does not
> > provide HE MFB (0)
> > .... .... .... .... .... .... .... ..0. .... .... ....
> > .... = All Ack Support: Not supported
> > .... .... .... .... .... .... .... .0.. .... .... ....
> > .... = TRS Support: Not supported
> > .... .... .... .... .... .... .... 1... .... .... ....
> > .... = BSR Support: Supported
> > .... .... .... .... .... .... ...1 .... .... .... ....
> > .... = Broadcast TWT Support: Supported
> > .... .... .... .... .... .... ..0. .... .... .... ....
> > .... = 32-bit BA Bitmap Support: Not supported
> > .... .... .... .... .... .... .0.. .... .... .... ....
> > .... = MU Cascading Support: Not supported
> > .... .... .... .... .... .... 0... .... .... .... ....
> > .... = Ack-Enabled Aggregation Support: Not supported
> > .... .... .... .... .... ...0 .... .... .... .... ....
> > .... = Reserved: 0x0
> > .... .... .... .... .... ..1. .... .... .... .... ....
> > .... = OM Control Support: Supported
> > .... .... .... .... .... .0.. .... .... .... .... ....
> > .... = OFDMA RA Support: Not supported
> > .... .... .... .... ...1 1... .... .... .... .... ....
> > .... = Maximum A-MPDU Length Exponent Extension: 3
> > .... .... .... .... ..0. .... .... .... .... .... ....
> > .... = A-MSDU Fragmentation Support: Not supported
> > .... .... .... .... .0.. .... .... .... .... .... ....
> > .... = Flexible TWT Schedule Support: Not supported
> > .... .... .... .... 1... .... .... .... .... .... ....
> > .... = Rx Control Frame to MultiBSS: Supported
> > .... .... .... ...0 .... .... .... .... .... .... ....
> > .... = BSRP BQRP A-MPDU Aggregation: Not supported
> > .... .... .... ..0. .... .... .... .... .... .... ....
> > .... = QTP Support: Not supported
> > .... .... .... .0.. .... .... .... .... .... .... ....
> > .... = BQR Support: Not supported
> > .... .... .... 0... .... .... .... .... .... .... ....
> > .... = PSR Responder: Not supported
> > .... .... ...0 .... .... .... .... .... .... .... ....
> > .... = NDP Feedback Report Support: Not supported
> > .... .... ..0. .... .... .... .... .... .... .... ....
> > .... = OPS Support: Not supported
> > .... .... .1.. .... .... .... .... .... .... .... ....
> > .... = A-MSDU Not Under BA in Ack-Enabled A-MPDU Support: Supported
> > .... ..00 0... .... .... .... .... .... .... .... ....
> > .... = Multi-TID Aggregation Tx Support: 0
> > .... .0.. .... .... .... .... .... .... .... .... ....
> > .... = HE Subchannel Selective Transmission Support: Not supported
> > .... 0... .... .... .... .... .... .... .... .... ....
> > .... = UL 2x996-tone RU Support: Not supported
> > ...1 .... .... .... .... .... .... .... .... .... ....
> > .... = OM Control UL MU Data Disable RX Support: Supported
> > ..0. .... .... .... .... .... .... .... .... .... ....
> > .... = HE Dynamic SM Power Save: Not supported
> > .0.. .... .... .... .... .... .... .... .... .... ....
> > .... = Punctured Sounding Support: Not supported
> > 0... .... .... .... .... .... .... .... .... .... ....
> > .... = HT And VHT Trigger Frame RX Support: Not supported
> > HE PHY Capabilities Information
> > .... ...0 = Reserved: 0x0
> > .... ...0 = Reserved: 0x0
> > 0000 110. = Channel Width Set: 0x06
> > .... ..0. = Reserved: 0x0
> > .... .1.. = 40 & 80 MHz in the 5 GHz and 6 GHz
> > bands: Supported
> > .... 1... = 160 MHz in the 5 GHz and 6 GHz bands: Supported
> > ...0 .... = 160/80+80 MHz in the 5 GHz and 6 GHz
> > bands: Not supported
> > ..0. .... = Reserved: 0x0
> > .0.. .... = 242 tone RUs in the 5 GHz and 6 GHz
> > bands: Not supported
> > 0... .... = Reserved: 0x0
> > Bits 8 to 23: 0x4c60
> > .... .... .... 0000 = Punctured Preamble Rx: 0x0
> > .... .... ...0 .... = Device Class: Class B Device (0x0)
> > .... .... ..1. .... = LDPC Coding In Payload: Supported
> > .... .... .1.. .... = HE SU PPDU With 1x HE-LTF
> > And 0.8us GI: Supported
> > .... ...0 0... .... = Midamble Tx/Rx Max NSTS: 1
> > Space-Time Stream (0x0)
> > .... ..0. .... .... = NDP With 4x HE-LTF and 3.2us
> > GI: Not supported
> > .... .1.. .... .... = STBC Tx <= 80 MHz: Supported
> > .... 1... .... .... = STBC Rx <= 80 MHz: Supported
> > ...0 .... .... .... = Doppler Tx: Not supported
> > ..0. .... .... .... = Doppler Rx: Not supported
> > .1.. .... .... .... = Full Bandwidth UL MU-MIMO: Supported
> > 0... .... .... .... = Partial Bandwidth UL
> > MU-MIMO: Not supported
> > Bits 24 to 39: 0xfc08
> > .... .... .... ..00 = DCM Max Constellation Tx:
> > DCM is not supported (0x0)
> > .... .... .... .0.. = DCM Max NSS Tx: 1 Spatial Stream (0x0)
> > .... .... ...0 1... = DCM Max Constellation Rx: BPSK (0x1)
> > .... .... ..0. .... = DCM Max NSS Rx: 1 Spatial Stream (0x0)
> > .... .... .0.. .... = Rx Partial BW SU In 20 MHz
> > HE MU PPDU: Not supported
> > .... .... 0... .... = SU Beamformer: Not supported
> > .... ...0 .... .... = SU Beamformee: Not supported
> > .... ..0. .... .... = MU Beamformer: Not supported
> > ...1 11.. .... .... = Beamformee STS <= 80 MHz: 0x7
> > 111. .... .... .... = Beamformee STS > 80 MHz: 0x7
> > Bits 40 to 55: 0x83db
> > .... .... .... .011 = Number Of Sounding
> > Dimensions <= 80 MHz: 3
> > .... .... ..01 1... = Number Of Sounding
> > Dimensions > 80 MHz: 3
> > .... .... .1.. .... = Ng = 16 SU Feedback: Supported
> > .... .... 1... .... = Ng = 16 MU Feedback: Supported
> > .... ...1 .... .... = Codebook Size SU Feedback: Supported
> > .... ..1. .... .... = Codebook Size MU Feedback: Supported
> > .... .0.. .... .... = Triggered SU Beamforming
> > Feedback: Not supported
> > .... 0... .... .... = Triggered MU Beamforming
> > Feedback: Not supported
> > ...0 .... .... .... = Triggered CQI Feedback: Not supported
> > ..0. .... .... .... = Partial Bandwidth Extended
> > Range: Not supported
> > .0.. .... .... .... = Partial Bandwidth DL
> > MU-MIMO: Not supported
> > 1... .... .... .... = PPE Thresholds Present: True
> > Bits 56 to 71: 0x119c
> > .... .... .... ...0 = PSR-based SR Support: Not supported
> > .... .... .... ..0. = Power Boost Factor ar
> > Support: Not supported
> > .... .... .... .1.. = HE SU PPDU And HE MU PPDU
> > With 4x HE-LTF And 0.8us GI: Supported
> > .... .... ..01 1... = Max Nc: Supported
> > .... .... .0.. .... = STBC Tx > 80 MHz: Not supported
> > .... .... 1... .... = STBC Rx > 80 MHz: Supported
> > .... ...1 .... .... = HE ER SU PPDU With 4x HE-LTF
> > And 0.8us GI: Supported
> > .... ..0. .... .... = 20 MHz In 40 MHz HE PPDU In
> > 2.4 GHz Band: Not supported
> > .... .0.. .... .... = 20 MHz In 160/80+80 MHz HE
> > PPDU: Not supported
> > .... 0... .... .... = 80 MHz In 160/80+80 MHz HE
> > PPDU: Not supported
> > ...1 .... .... .... = HE ER SU PPDU With 1x HE-LTF
> > And 0.8us GI: Supported
> > ..0. .... .... .... = Midamble Tx/Rx 2x And 1x
> > HE-LTF: Not supported
> > 00.. .... .... .... = DCM Max RU: 242-tone RU (0x0)
> > Bits 72 to 87: 0x000c
> > .... .... .... ...0 = Longer Than 16 HE SIG-B OFDM
> > Symbols Support: Not supported
> > .... .... .... ..0. = Non-Triggered CQI Feedback:
> > Not supported
> > .... .... .... .1.. = Tx 1024-QAM Support <
> > 242-tone RU Support: Supported
> > .... .... .... 1... = Rx 1024-QAM Support <
> > 242-tone RU Support: Supported
> > .... .... ...0 .... = Rx Full BW SU Using HE MU
> > PPDU With Compressed HE-SIG-B: Not supported
> > .... .... ..0. .... = Rx Full BW SU Using HE MU
> > PPDU With Non-Compressed HE-SIG-B: Not supported
> > .... .... 00.. .... = Nominal Packet Padding: 0 µs
> > for all constellations, Nss and RU allocations (0)
> > .... ...0 .... .... = HE MU PPDU With More Than
> > One RU Rx Max N_HE-LTF: 0
> > 0000 000. .... .... = Reserved: 0x00
> > Supported HE-MCS and NSS Set
> > Rx and Tx MCS Maps <= 80 MHz
> > Rx HE-MCS Map <= 80 MHz: 0xffaa
> > .... .... .... ..10 = Max HE-MCS for 1 SS:
> > Support for HE-MCS 0-11 (0x2)
> > .... .... .... 10.. = Max HE-MCS for 2 SS:
> > Support for HE-MCS 0-11 (0x2)
> > .... .... ..10 .... = Max HE-MCS for 3 SS:
> > Support for HE-MCS 0-11 (0x2)
> > .... .... 10.. .... = Max HE-MCS for 4 SS:
> > Support for HE-MCS 0-11 (0x2)
> > .... ..11 .... .... = Max HE-MCS for 5 SS: Not
> > supported for HE PPDUs (0x3)
> > .... 11.. .... .... = Max HE-MCS for 6 SS: Not
> > supported for HE PPDUs (0x3)
> > ..11 .... .... .... = Max HE-MCS for 7 SS: Not
> > supported for HE PPDUs (0x3)
> > 11.. .... .... .... = Max HE-MCS for 8 SS: Not
> > supported for HE PPDUs (0x3)
> > Tx HE-MCS Map <= 80 MHz: 0xffaa
> > .... .... .... ..10 = Max HE-MCS for 1 SS:
> > Support for HE-MCS 0-11 (0x2)
> > .... .... .... 10.. = Max HE-MCS for 2 SS:
> > Support for HE-MCS 0-11 (0x2)
> > .... .... ..10 .... = Max HE-MCS for 3 SS:
> > Support for HE-MCS 0-11 (0x2)
> > .... .... 10.. .... = Max HE-MCS for 4 SS:
> > Support for HE-MCS 0-11 (0x2)
> > .... ..11 .... .... = Max HE-MCS for 5 SS: Not
> > supported for HE PPDUs (0x3)
> > .... 11.. .... .... = Max HE-MCS for 6 SS: Not
> > supported for HE PPDUs (0x3)
> > ..11 .... .... .... = Max HE-MCS for 7 SS: Not
> > supported for HE PPDUs (0x3)
> > 11.. .... .... .... = Max HE-MCS for 8 SS: Not
> > supported for HE PPDUs (0x3)
> > Rx and Tx MCS Maps 160 MHz
> > Rx HE-MCS Map 160 MHz: 0xffaa
> > .... .... .... ..10 = Max HE-MCS for 1 SS:
> > Support for HE-MCS 0-11 (0x2)
> > .... .... .... 10.. = Max HE-MCS for 2 SS:
> > Support for HE-MCS 0-11 (0x2)
> > .... .... ..10 .... = Max HE-MCS for 3 SS:
> > Support for HE-MCS 0-11 (0x2)
> > .... .... 10.. .... = Max HE-MCS for 4 SS:
> > Support for HE-MCS 0-11 (0x2)
> > .... ..11 .... .... = Max HE-MCS for 5 SS: Not
> > supported for HE PPDUs (0x3)
> > .... 11.. .... .... = Max HE-MCS for 6 SS: Not
> > supported for HE PPDUs (0x3)
> > ..11 .... .... .... = Max HE-MCS for 7 SS: Not
> > supported for HE PPDUs (0x3)
> > 11.. .... .... .... = Max HE-MCS for 8 SS: Not
> > supported for HE PPDUs (0x3)
> > Tx HE-MCS Map 160 MHz: 0xffaa
> > .... .... .... ..10 = Max HE-MCS for 1 SS:
> > Support for HE-MCS 0-11 (0x2)
> > .... .... .... 10.. = Max HE-MCS for 2 SS:
> > Support for HE-MCS 0-11 (0x2)
> > .... .... ..10 .... = Max HE-MCS for 3 SS:
> > Support for HE-MCS 0-11 (0x2)
> > .... .... 10.. .... = Max HE-MCS for 4 SS:
> > Support for HE-MCS 0-11 (0x2)
> > .... ..11 .... .... = Max HE-MCS for 5 SS: Not
> > supported for HE PPDUs (0x3)
> > .... 11.. .... .... = Max HE-MCS for 6 SS: Not
> > supported for HE PPDUs (0x3)
> > ..11 .... .... .... = Max HE-MCS for 7 SS: Not
> > supported for HE PPDUs (0x3)
> > 11.. .... .... .... = Max HE-MCS for 8 SS: Not
> > supported for HE PPDUs (0x3)
> > PPE Thresholds
> > .... .011 = NSS: 3
> > .111 1... = RU Index Bitmask: 0xf
> > NSS 0
> > RU allocation: 242
> > PPET16: BPSK (0x00)
> > PPET8: None (0x07)
> > RU allocation: 484
> > PPET16: BPSK (0x00)
> > PPET8: None (0x07)
> > RU allocation: 996
> > PPET16: BPSK (0x00)
> > PPET8: None (0x07)
> > RU allocation: 2x996
> > PPET16: BPSK (0x00)
> > PPET8: None (0x07)
> > NSS 1
> > RU allocation: 242
> > PPET16: BPSK (0x00)
> > PPET8: None (0x07)
> > RU allocation: 484
> > PPET16: BPSK (0x00)
> > PPET8: None (0x07)
> > RU allocation: 996
> > PPET16: BPSK (0x00)
> > PPET8: None (0x07)
> > RU allocation: 2x996
> > PPET16: BPSK (0x00)
> > PPET8: None (0x07)
> > NSS 2
> > RU allocation: 242
> > PPET16: BPSK (0x00)
> > PPET8: None (0x07)
> > RU allocation: 484
> > PPET16: BPSK (0x00)
> > PPET8: None (0x07)
> > RU allocation: 996
> > PPET16: BPSK (0x00)
> > PPET8: None (0x07)
> > RU allocation: 2x996
> > PPET16: BPSK (0x00)
> > PPET8: None (0x07)
> > NSS 3
> > RU allocation: 242
> > PPET16: BPSK (0x00)
> > PPET8: None (0x07)
> > RU allocation: 484
> > PPET16: BPSK (0x00)
> > PPET8: None (0x07)
> > RU allocation: 996
> > PPET16: BPSK (0x00)
> > PPET8: None (0x07)
> > RU allocation: 2x996
> > PPET16: BPSK (0x00)
> > PPET8: None (0x07)
> > Ext Tag: HE Operation
> > Tag Number: Element ID Extension (255)
> > Ext Tag length: 11
> > Ext Tag Number: HE Operation (36)
> > HE Operation Parameters: 0x023ff0
> > .... .... .... .... .... .000 = Default PE Duration: 0
> > .... .... .... .... .... 0... = TWT Required: Not required
> > .... .... ..11 1111 1111 .... = TXOP Duration RTS
> > Threshold: 1023
> > .... .... .0.. .... .... .... = VHT Operation
> > Information Present: False
> > .... .... 0... .... .... .... = Co-Hosted BSS: False
> > .... ...0 .... .... .... .... = ER SU Disable: False
> > .... ..1. .... .... .... .... = 6 GHz Operation
> > Information Present: True
> > 0000 00.. .... .... .... .... = Reserved: 0x00
> > BSS Color Information: 0x92
> > ..01 0010 = BSS Color: 0x12
> > .0.. .... = Partial BSS Color: False
> > 1... .... = BSS Color Disabled: True
> > Basic HE-MCS and NSS Set: 0xfffc
> > .... .... .... ..00 = Max HE-MCS for 1 SS: Support for
> > HE-MCS 0-7 (0)
> > .... .... .... 11.. = Max HE-MCS for 2 SS: Not
> > supported for HE PPDUs (3)
> > .... .... ..11 .... = Max HE-MCS for 3 SS: Not
> > supported for HE PPDUs (3)
> > .... .... 11.. .... = Max HE-MCS for 4 SS: Not
> > supported for HE PPDUs (3)
> > .... ..11 .... .... = Max HE-MCS for 5 SS: Not
> > supported for HE PPDUs (3)
> > .... 11.. .... .... = Max HE-MCS for 6 SS: Not
> > supported for HE PPDUs (3)
> > ..11 .... .... .... = Max HE-MCS for 7 SS: Not
> > supported for HE PPDUs (3)
> > 11.. .... .... .... = Max HE-MCS for 8 SS: Not
> > supported for HE PPDUs (3)
> > 6 GHz Operation Information
> > Primary Channel: 33
> > Control: 0x03
> > .... ..11 = Channel Width: 160MHz or 80MHz+80MHz (3)
> > .... .0.. = Duplicate Beacon: False
> > ..00 0... = Regulatory Info: 0
> > 00.. .... = Reserved: 0
> > Channel Center Frequency Segment 0: 39
> > Channel Center Frequency Segment 1: 47
> > Minimum Rate: 6
> > Ext Tag: HE 6 GHz Band Capabilities
> > Tag Number: Element ID Extension (255)
> > Ext Tag length: 2
> > Ext Tag Number: HE 6 GHz Band Capabilities (59)
> > Capabilities Information: 0x36b8
> > .... .... .... .000 = Minimum MPDU Start Spacing: No
> > restriction (0x0)
> > .... .... ..11 1... = Maximum A-MPDU Length Exponent:
> > 1 048 575 (0x7)
> > .... .... 10.. .... = Maximum MPDU Length: 11 454 (0x2)
> > .... ...0 .... .... = Reserved: 0x0
> > .... .11. .... .... = SM Power Save: SM Power Save
> > disabled (0x3)
> > .... 0... .... .... = RD Responder: Not supported
> > ...1 .... .... .... = Rx Antenna Pattern Consistency: Supported
> > ..1. .... .... .... = Tx Antenna Pattern Consistency: Supported
> > 00.. .... .... .... = Reserved: 0x0
> > Tag: Vendor Specific: Microsoft Corp.: WMM/WME: Parameter Element
> > Tag Number: Vendor Specific (221)
> > Tag length: 24
> > OUI: 00:50:f2 (Microsoft Corp.)
> > Vendor Specific OUI Type: 2
> > Type: WMM/WME (0x02)
> > WME Subtype: Parameter Element (1)
> > WME Version: 1
> > WME QoS Info: 0x01
> > 0... .... = U-APSD: Disabled
> > .... 0001 = Parameter Set Count: 0x1
> > .000 .... = Reserved: 0x0
> > Reserved: 00
> > Ac Parameters ACI 0 (Best Effort), ACM no, AIFSN 3,
> > ECWmin/max 4/10 (CWmin/max 15/1023), TXOP 0
> > ACI / AIFSN Field: 0x03
> > .... 0011 = AIFSN: 3
> > ...0 .... = Admission Control Mandatory: No
> > .00. .... = ACI: Best Effort (0)
> > 0... .... = Reserved: 0
> > ECW: 0xa4
> > 1010 .... = ECW Max: 10
> > .... 0100 = ECW Min: 4
> > CW Max: 1023
> > CW Min: 15
> > TXOP Limit: 0
> > Ac Parameters ACI 1 (Background), ACM no, AIFSN 7,
> > ECWmin/max 4/10 (CWmin/max 15/1023), TXOP 0
> > ACI / AIFSN Field: 0x27
> > .... 0111 = AIFSN: 7
> > ...0 .... = Admission Control Mandatory: No
> > .01. .... = ACI: Background (1)
> > 0... .... = Reserved: 0
> > ECW: 0xa4
> > 1010 .... = ECW Max: 10
> > .... 0100 = ECW Min: 4
> > CW Max: 1023
> > CW Min: 15
> > TXOP Limit: 0
> > Ac Parameters ACI 2 (Video), ACM no, AIFSN 2, ECWmin/max
> > 3/4 (CWmin/max 7/15), TXOP 94
> > ACI / AIFSN Field: 0x42
> > .... 0010 = AIFSN: 2
> > ...0 .... = Admission Control Mandatory: No
> > .10. .... = ACI: Video (2)
> > 0... .... = Reserved: 0
> > ECW: 0x43
> > 0100 .... = ECW Max: 4
> > .... 0011 = ECW Min: 3
> > CW Max: 15
> > CW Min: 7
> > TXOP Limit: 94
> > Ac Parameters ACI 3 (Voice), ACM no, AIFSN 2, ECWmin/max
> > 2/3 (CWmin/max 3/7), TXOP 47
> > ACI / AIFSN Field: 0x62
> > .... 0010 = AIFSN: 2
> > ...0 .... = Admission Control Mandatory: No
> > .11. .... = ACI: Voice (3)
> > 0... .... = Reserved: 0
> > ECW: 0x32
> > 0011 .... = ECW Max: 3
> > .... 0010 = ECW Min: 2
> > CW Max: 7
> > CW Min: 3
> >
> >
> > If I can check anyhing in between pls. let me know.
> > OpenWRT is known to have some tuning for these things but ath11k was
> > not included by default hence also QCN9074. So I am now also working
> > with 5.15 master, compiled custom OpenWRT with enabled ath11k and
> > included *.bin firmware into OpenWRT. Resolved MSI issues to VT-D but
> > so far this is still work in progress as the card does not error out
> > but never responds to power on command. MHI keeps waiting for power
> > on. This is however secondary topic I started looking into due lack of
> > progress on a regular distro. Tried also latest 6.1 rc4 kernel on
> > ubuntu with no change.
> >
> > Regards,
> > Mariusz
> >
> >
> > On Mon, 14 Nov 2022 at 14:19, Nagarajan Maran (QUIC)
> > <quic_nmaran@quicinc.com> wrote:
> >> Hi Mariusz,
> >>
> >>
> >>
> >> We checked the upstream driver code and firmware bins similar to your setup environment and it seems to work well.
> >>
> >> Could you kindly check whether your Wi-Fi card has been OTP fused for 6Ghz?
> >>
> >>
> >>
> >> -Thanks
> >>
> >> Nagarajan M.
> >>
> >>
> >>
> >> From: Mariusz <enebeo@gmail.com>
> >> Sent: Tuesday, November 8, 2022 8:25 PM
> >> To: Nagarajan Maran (QUIC) <quic_nmaran@quicinc.com>
> >> Cc: ath11k@lists.infradead.org
> >> Subject: Re: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
> >>
> >>
> >>
> >> Perhaps also something interesting, I apply reg domain of Belgium/BE. It has lower 6GHz channels allowed.
> >>
> >>
> >>
> >> iw reg get
> >> global
> >> country BE: DFS-ETSI
> >> (2400 - 2483 @ 40), (N/A, 20), (N/A)
> >> (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
> >> (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
> >> (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
> >> (5725 - 5875 @ 80), (N/A, 13), (N/A)
> >> (5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
> >> (57000 - 66000 @ 2160), (N/A, 40), (N/A)
> >>
> >> phy#3 (self-managed)
> >> country US: DFS-FCC
> >> (2402 - 2472 @ 40), (6, 30), (N/A)
> >> (5170 - 5250 @ 80), (N/A, 30), (N/A), AUTO-BW
> >> (5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
> >> (5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS, AUTO-BW
> >> (5735 - 5895 @ 160), (N/A, 30), (N/A), AUTO-BW
> >> (5945 - 7125 @ 160), (N/A, 30), (N/A), NO-OUTDOOR, AUTO-BW
> >>
> >>
> >>
> >> When I start hostapd with acs_survey or channel=0 it starts but pretends to work, no other client can connect to this ssid.
> >>
> >>
> >>
> >> When I disable acs in hostapd.conf and set channel=1 (freq 5955 in 6GHz range) so allowed per reg domain it refuses to start:
> >>
> >>
> >>
> >> Mode: IEEE 802.11a Channel: 1 Frequency: 5955 MHz
> >> nl80211: Set freq 5955 (ht_enabled=0, vht_enabled=0, he_enabled=1, eht_enabled=0, bandwidth=160 MHz, cf1=5955 MHz, cf2=0 MHz)
> >> * freq=5955
> >> * eht_enabled=0
> >> * he_enabled=1
> >> * vht_enabled=0
> >> * ht_enabled=0
> >> * radar_background=0
> >> * bandwidth=160
> >> * channel_width=5
> >> * center_freq1=5955
> >> * center_freq2=0
> >> nl80211: kernel reports: invalid channel definition
> >> nl80211: Failed to set channel (freq=5955): -22 (Invalid argument)
> >>
> >>
> >>
> >> reg domain BE is more restrictive than US so channel 1 should be enabled in both cases
> >>
> >> Previous country code BE, new country code BE
> >> nl80211: Regulatory information - country=US (DFS-FCC)
> >> nl80211: 2402-2472 @ 40 MHz 30 mBm
> >> nl80211: 5170-5250 @ 80 MHz 30 mBm
> >> nl80211: 5250-5330 @ 80 MHz 24 mBm (DFS)
> >> nl80211: 5490-5730 @ 160 MHz 24 mBm (DFS)
> >> nl80211: 5735-5895 @ 160 MHz 30 mBm
> >> nl80211: 5945-7125 @ 160 MHz 30 mBm (no outdoor)
> >> nl80211: Mode IEEE 802.11a: 5955 5975 5995 6015 6035 6055 6075 6095 6115 6135 6155 6175 6195 6215 6235 6255 6275 6295 6315 6335 6355 6375 6395 6415 6435 6455 6475 6495 6515 6535 6555 6575 6595 6615 6635 6655 6675 6695 6715 6735 6755 6775 6795 6815 6835 6855 6875 6895 6915 6935 6955 6975 6995 7015 7035 7055 7075 7095 7115 5935[DISABLED]
> >>
> >>
> >>
> >> for op_class=134 = 160MHz valid channels are 1-29, 33-61, 65-93, 97-125, 129-157, 161-189, 193-221
> >>
> >>
> >>
> >>
> >>
> >> phy: phy3
> >> BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
> >> wlp1s0: interface state UNINITIALIZED->COUNTRY_UPDATE
> >> Previous country code BE, new country code BE
> >> nl80211: Regulatory information - country=US (DFS-FCC)
> >> nl80211: 2402-2472 @ 40 MHz 30 mBm
> >> nl80211: 5170-5250 @ 80 MHz 30 mBm
> >> nl80211: 5250-5330 @ 80 MHz 24 mBm (DFS)
> >> nl80211: 5490-5730 @ 160 MHz 24 mBm (DFS)
> >> nl80211: 5735-5895 @ 160 MHz 30 mBm
> >> nl80211: 5945-7125 @ 160 MHz 30 mBm (no outdoor)
> >> nl80211: Mode IEEE 802.11a: 5955 5975 5995 6015 6035 6055 6075 6095 6115 6135 6155 6175 6195 6215 6235 6255 6275 6295 6315 6335 6355 6375 6395 6415 6435 6455 6475 6495 6515 6535 6555 6575 6595 6615 6635 6655 6675 6695 6715 6735 6755 6775 6795 6815 6835 6855 6875 6895 6915 6935 6955 6975 6995 7015 7035 7055 7075 7095 7115 5935[DISABLED]
> >> Completing interface initialization
> >> Mode: IEEE 802.11a Channel: 33 Frequency: 6115 MHz
> >> nl80211: Set freq 6115 (ht_enabled=0, vht_enabled=0, he_enabled=1, eht_enabled=0, bandwidth=160 MHz, cf1=6115 MHz, cf2=0 MHz)
> >> * freq=6115
> >> * eht_enabled=0
> >> * he_enabled=1
> >> * vht_enabled=0
> >> * ht_enabled=0
> >> * radar_background=0
> >> * bandwidth=160
> >> * channel_width=5
> >> * center_freq1=6115
> >> * center_freq2=0
> >> nl80211: kernel reports: invalid channel definition
> >> nl80211: Failed to set channel (freq=6115): -22 (Invalid argument)
> >> Could not set channel for kernel driver
> >> Interface initialization failed
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> How is this invalid channel?
> >>
> >>
> >>
> >> root@s4:/home/angel/hostap/hostapd# iw phy3 channels
> >> Band 4:
> >> * 5955 MHz [1]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 5975 MHz [5]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 5995 MHz [9]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6015 MHz [13]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6035 MHz [17]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6055 MHz [21]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6075 MHz [25]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6095 MHz [29]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6115 MHz [33]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6135 MHz [37]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6155 MHz [41]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6175 MHz [45]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6195 MHz [49]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6215 MHz [53]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6235 MHz [57]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6255 MHz [61]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6275 MHz [65]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6295 MHz [69]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6315 MHz [73]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6335 MHz [77]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6355 MHz [81]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6375 MHz [85]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6395 MHz [89]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6415 MHz [93]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6435 MHz [97]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6455 MHz [101]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6475 MHz [105]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6495 MHz [109]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6515 MHz [113]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6535 MHz [117]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6555 MHz [121]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6575 MHz [125]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6595 MHz [129]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6615 MHz [133]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6635 MHz [137]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6655 MHz [141]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6675 MHz [145]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6695 MHz [149]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6715 MHz [153]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6735 MHz [157]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6755 MHz [161]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6775 MHz [165]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6795 MHz [169]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6815 MHz [173]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6835 MHz [177]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6855 MHz [181]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6875 MHz [185]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6895 MHz [189]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6915 MHz [193]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6935 MHz [197]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6955 MHz [201]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6975 MHz [205]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 6995 MHz [209]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 7015 MHz [213]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 7035 MHz [217]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 7055 MHz [221]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 7075 MHz [225]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 7095 MHz [229]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 7115 MHz [233]
> >> Maximum TX power: 30.0 dBm
> >> Channel widths: 20MHz
> >> * 5935 MHz [2] (disabled)
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> On Mon, 7 Nov 2022 at 17:07, Nagarajan Maran (QUIC) <quic_nmaran@quicinc.com> wrote:
> >>
> >> Hi Mariusz,
> >>
> >> We are looking into this issue. It seems that this error can occur when the given frequency is not present or when the given frequency is disabled.
> >> To further analyze the issue, could you kindly let us know the output of the below commands during failure case.
> >> 1) iw dev
> >> 2) iw phyX channels
> >>
> >> Also, could you kindly send the WiFi driver boot up logs with "debug_mask=0x212" enabled during insmod of ath11k.ko module.
> >>
> >> Thanks,
> >> Nagarajan M.
> >>
> >> -----Original Message-----
> >>
> >> From: Mariusz <enebeo@gmail.com>
> >> To: ath11k@lists.infradead.org
> >> Subject: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
> >> Message-ID:
> >> <CAJrE-q6NVEF4sNW1s4Zz7Pb2ryzCi69e+_vLQswBWm747DHYDw@mail.gmail.com>
> >> Content-Type: text/plain; charset="UTF-8"
> >>
> >> Hi,
> >>
> >> As support for QCN9074 got better I went ahead and built a 6E linux based AP. Dell R720 server x86 running Linux s4 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64
> >> x86_64 x86_64 GNU/Linux.
> >>
> >> My issue is that I cannot get it working on 6GHz bands but it works fine on 5GHz. I bought 6E version and since this is a single band module it cannot be both 5G & 6G and linux driver does not agree with it being 6E version:
> >>
> >> [71914.038562] ath11k_pci 0000:03:00.0: BAR 0: assigned [mem 0xdf800000-0xdf9fffff 64bit] [71914.038840] ath11k_pci 0000:03:00.0: MSI vectors: 16 [71914.038852] ath11k_pci 0000:03:00.0: qcn9074 hw1.0 [71914.194459] mhi mhi0: Requested to power ON [71914.194712] mhi mhi0: Power on setup success [71914.297749] mhi mhi0: Wait for device to enter SBL or Mission mode [71914.647118] ath11k_pci 0000:03:00.0: chip_id 0x0 chip_family 0x0 board_id 0xff soc_id 0xffffffff [71914.647134] ath11k_pci 0000:03:00.0: fw_version 0x250a04b8 fw_build_timestamp 2021-12-20 06:41 fw_build_id [71916.310787] ath11k_pci 0000:03:00.0 wlp3s0: renamed from wlan0
> >>
> >> HE PHY Capabilities: (0x1c604c88ffdb839c110c00):
> >> HE40/HE80/5GHz
> >> HE160/5GHz
> >> HE160/HE80+80/5GHz
> >>
> >> iw dev wlp3s0 set freq 6195 160MHz
> >> kernel reports: Channel is disabled
> >> command failed: Invalid argument (-22)
> >>
> >> I am using the latest firmware files from ath11k tree. Is there any special firmware to force this to 6GHz? I read somewhere board_id determines which one it is and 255 disables 6GHz but I miss more data on that.
> >>
> >> phy#2 (self-managed)
> >> country US: DFS-FCC
> >> (2402 - 2472 @ 40), (6, 30), (N/A)
> >> (5170 - 5250 @ 80), (N/A, 30), (N/A), AUTO-BW
> >> (5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
> >> (5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS, AUTO-BW
> >> (5735 - 5895 @ 160), (N/A, 30), (N/A), AUTO-BW
> >> (5945 - 7125 @ 160), (N/A, 30), (N/A), NO-OUTDOOR, AUTO-BW
> >>
> >> It works fine in 5GHz but this is not what I purchased it for, so I am puzzled if this is something in software or I was sold wrong hardware.Is there a specific board-2.bin for 6GHz? Since the 9074 chip is the same in all versions perhaps this is a software hiccup.
> >>
> >> Any clues are welcome.
> >>
> >> Regards,
> >> Mario
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
2022-11-15 10:02 ` Mariusz
2022-11-15 18:29 ` walde
@ 2022-11-17 16:51 ` Mariusz
1 sibling, 0 replies; 18+ messages in thread
From: Mariusz @ 2022-11-17 16:51 UTC (permalink / raw)
To: ath11k
I am still waiting for feedback, I have recompiled the kernel with
testing options CERT_TESTING & CONFIGURATION_ONUS to see if there is
something else at play. I also loaded ath11k module with
debug_mask=0x16
Upon starting hostapd I start seeing a repetitive rx completion error:
[ 998.115392] ath11k_pci 0000:07:00.0: txpower from firmware 48,
reported 24 dBm
[ 998.115494] ath11k_pci 0000:07:00.0: mac chanctx add freq 5955
width 2 ptr ffff921153c0d058
[ 998.115497] ath11k_pci 0000:07:00.0: mac chanctx assign ptr
ffff921153c0d058 vdev_id 0
[ 998.115500] ath11k_pci 0000:07:00.0: WMI vdev id 0x0 set param
32770 value 123
[ 998.115502] ath11k_pci 0000:07:00.0: WMI vdev id 0x0 set param 135 value 9
[ 998.115503] ath11k_pci 0000:07:00.0: mac vdev 0 start center_freq
5955 phymode 11ax-he40
[ 998.115505] ath11k_pci 0000:07:00.0: vdev start id 0x0 freq 0x1743 mode 0x11
[ 998.161183] ath11k_pci 0000:07:00.0: htc rx completion ep 2 skb
pK-error
[ 998.161190] ath11k_pci 0000:07:00.0: Unknown eventid: 0x4028
[ 998.161194] ath11k_pci 0000:07:00.0: htc rx completion ep 2 skb
pK-error
[ 998.161196] ath11k_pci 0000:07:00.0: Unknown eventid: 0x4028
[ 998.166883] ath11k_pci 0000:07:00.0: htc rx completion ep 2 skb
pK-error
[ 998.166892] ath11k_pci 0000:07:00.0: pdev ctl failsafe check ev status 0
[ 998.172504] ath11k_pci 0000:07:00.0: htc rx completion ep 2 skb
pK-error
[ 998.172518] ath11k_pci 0000:07:00.0: vdev start resp for vdev id 0
[ 998.172664] ath11k_pci 0000:07:00.0: vdev c4:4b:d1:d0:00:7e
started, vdev_id 0
[ 998.172675] ath11k_pci 0000:07:00.0: WMI vdev id 0x0 set param 45 value 829
[ 998.172688] ath11k_pci 0000:07:00.0: WMI vdev id 0x0 set param 3 value 100
[ 998.172691] ath11k_pci 0000:07:00.0: Beacon interval: 100 set for VDEV: 0
[ 998.172694] ath11k_pci 0000:07:00.0: WMI pdev set param 7 pdev id 1 value 0
[ 998.172697] ath11k_pci 0000:07:00.0: Set staggered beacon mode for VDEV: 0
[ 998.172705] ath11k_pci 0000:07:00.0: WMI vdev id 0x0 set param 126 value 3
[ 998.172707] ath11k_pci 0000:07:00.0: Set BA BUFFER SIZE 256 for VDEV: 0
[ 998.172710] ath11k_pci 0000:07:00.0: WMI vdev id 0x0 set param 13 value 2
[ 998.172712] ath11k_pci 0000:07:00.0: DTIM period: 2 set for VDEV: 0
[ 998.172717] ath11k_pci 0000:07:00.0: WMI mgmt vdev up id 0x0 assoc
id 0 bssid c4:4b:d1:d0:00:7e
[ 998.172720] ath11k_pci 0000:07:00.0: mac vdev 0 up
[ 998.172722] ath11k_pci 0000:07:00.0: mac vdev_id 0 txpower 30
[ 998.172724] ath11k_pci 0000:07:00.0: txpower to set in hw 30
[ 998.172728] ath11k_pci 0000:07:00.0: mac obss pd sr_ctrl 0
non_srg_thres 0 srg_max 0
[ 998.172732] ath11k_pci 0000:07:00.0: WMI pdev set param 188 pdev id
1 value -1610612542
[ 998.172736] ath11k_pci 0000:07:00.0: WMI pdev set param 190 pdev id
1 value 15
[ 998.172739] ath11k_pci 0000:07:00.0: WMI pdev set param 198 pdev id 1 value 0
[ 998.172742] ath11k_pci 0000:07:00.0: obss pd pdev_id 1 bss color
bitmap 00000000 00000000
[ 998.172747] ath11k_pci 0000:07:00.0: obss pd pdev_id 1 partial
bssid bitmap 00000000 00000000
[ 998.172750] ath11k_pci 0000:07:00.0: obss pd srg pdev_id 1 bss
color enable bitmap ffffffff ffffffff
[ 998.172754] ath11k_pci 0000:07:00.0: obss pd srg pdev_id 1 bssid
enable bitmap ffffffff ffffffff
[ 998.172757] ath11k_pci 0000:07:00.0: obss pd non_srg pdev_id 1 bss
color enable bitmap ffffffff ffffffff
[ 998.172761] ath11k_pci 0000:07:00.0: obss pd non_srg pdev_id 1
bssid enable bitmap ffffffff ffffffff
[ 998.172885] ath11k_pci 0000:07:00.0: WMI vdev id 0x0 set param 26 value 0
[ 998.172888] ath11k_pci 0000:07:00.0: Set CTS prot: 0 for VDEV: 0
[ 998.172891] ath11k_pci 0000:07:00.0: WMI vdev id 0x0 set param 8 value 2
[ 998.172893] ath11k_pci 0000:07:00.0: Set preamble: 2 for VDEV: 0
[ 998.172896] ath11k_pci 0000:07:00.0: WMI vdev id 0x0 set param 25
value 268435459
[ 998.172900] ath11k_pci 0000:07:00.0: WMI vdev id 0x0 set param 94
value 268435459
[ 998.177740] ath11k_pci 0000:07:00.0: htc rx completion ep 2 skb
pK-error
[ 998.177748] ath11k_pci 0000:07:00.0: ignoring unsupported event 0x7008
[ 998.180598] ath11k_pci 0000:07:00.0: htc rx completion ep 2 skb
pK-error
[ 998.180600] ath11k_pci 0000:07:00.0: ignoring unsupported event 0x3e001
[ 998.195042] ath11k_pci 0000:07:00.0: WMI vdev install key idx 1
cipher 4 len 16
[ 998.196269] ath11k_pci 0000:07:00.0: htc rx completion ep 2 skb
pK-error
[ 998.196274] ath11k_pci 0000:07:00.0: vdev install key ev idx 1
flags 00000001 macaddr c4:4b:d1:d0:00:7e status 0
[ 998.218911] ath11k_pci 0000:07:00.0: htc rx completion ep 2 skb
pK-error
[ 998.219007] ath11k_pci 0000:07:00.0: htc rx completion ep 1 skb
pK-error
[ 998.219167] ath11k_pci 0000:07:00.0: wmi wmm set ac 0 aifs 3 cwmin
15 cwmax 63 txop 0 acm 0 no_ack 0
[ 998.219172] ath11k_pci 0000:07:00.0: wmi wmm set ac 1 aifs 7 cwmin
15 cwmax 1023 txop 0 acm 0 no_ack 0
[ 998.219176] ath11k_pci 0000:07:00.0: wmi wmm set ac 2 aifs 1 cwmin
7 cwmax 15 txop 94 acm 0 no_ack 0
[ 998.219180] ath11k_pci 0000:07:00.0: wmi wmm set ac 3 aifs 1 cwmin
3 cwmax 7 txop 47 acm 0 no_ack 0
[ 998.219207] ath11k_pci 0000:07:00.0: wmi wmm set ac 0 aifs 3 cwmin
15 cwmax 63 txop 0 acm 0 no_ack 0
[ 998.219211] ath11k_pci 0000:07:00.0: wmi wmm set ac 1 aifs 7 cwmin
15 cwmax 1023 txop 0 acm 0 no_ack 0
[ 998.219214] ath11k_pci 0000:07:00.0: wmi wmm set ac 2 aifs 1 cwmin
7 cwmax 15 txop 94 acm 0 no_ack 0
[ 998.219217] ath11k_pci 0000:07:00.0: wmi wmm set ac 3 aifs 1 cwmin
3 cwmax 7 txop 47 acm 0 no_ack 0
[ 998.219241] ath11k_pci 0000:07:00.0: wmi wmm set ac 0 aifs 3 cwmin
15 cwmax 63 txop 0 acm 0 no_ack 0
[ 998.219244] ath11k_pci 0000:07:00.0: wmi wmm set ac 1 aifs 7 cwmin
15 cwmax 1023 txop 0 acm 0 no_ack 0
[ 998.219247] ath11k_pci 0000:07:00.0: wmi wmm set ac 2 aifs 1 cwmin
7 cwmax 15 txop 94 acm 0 no_ack 0
[ 998.219250] ath11k_pci 0000:07:00.0: wmi wmm set ac 3 aifs 1 cwmin
3 cwmax 7 txop 47 acm 0 no_ack 0
[ 998.219272] ath11k_pci 0000:07:00.0: wmi wmm set ac 0 aifs 3 cwmin
15 cwmax 63 txop 0 acm 0 no_ack 0
[ 998.219275] ath11k_pci 0000:07:00.0: wmi wmm set ac 1 aifs 7 cwmin
15 cwmax 1023 txop 0 acm 0 no_ack 0
[ 998.219277] ath11k_pci 0000:07:00.0: wmi wmm set ac 2 aifs 1 cwmin
7 cwmax 15 txop 94 acm 0 no_ack 0
[ 998.219280] ath11k_pci 0000:07:00.0: wmi wmm set ac 3 aifs 1 cwmin
3 cwmax 7 txop 47 acm 0 no_ack 0
[ 998.320920] ath11k_pci 0000:07:00.0: htc rx completion ep 1 skb
pK-error
[ 998.422872] ath11k_pci 0000:07:00.0: htc rx completion ep 1 skb
pK-error
[ 998.525099] ath11k_pci 0000:07:00.0: htc rx completion ep 1 skb
pK-error
[ 998.627328] ath11k_pci 0000:07:00.0: htc rx completion ep 1 skb
pK-error
[ 998.729962] ath11k_pci 0000:07:00.0: htc rx completion ep 1 skb
pK-error
[ 998.832893] ath11k_pci 0000:07:00.0: htc rx completion ep 1 skb
pK-error
[ 998.934766] ath11k_pci 0000:07:00.0: htc rx completion ep 1 skb
pK-error
[ 999.037387] ath11k_pci 0000:07:00.0: htc rx completion ep 1 skb
pK-error
[ 999.139589] ath11k_pci 0000:07:00.0: htc rx completion ep 1 skb
pK-error
[ 999.242822] ath11k_pci 0000:07:00.0: htc rx completion ep 1 skb
pK-error
[ 999.344918] ath11k_pci 0000:07:00.0: htc rx completion ep 1 skb
pK-error
[ 999.446812] ath11k_pci 0000:07:00.0: htc rx completion ep 1 skb
pK-error
[ 999.549138] ath11k_pci 0000:07:00.0: htc rx completion ep 1 skb
pK-error
[ 999.651586] ath11k_pci 0000:07:00.0: htc rx completion ep 1 skb
pK-error
[ 999.754795] ath11k_pci 0000:07:00.0: htc rx completion ep 1 skb
pK-error
[ 999.856897] ath11k_pci 0000:07:00.0: htc rx completion ep 1 skb
pK-error
[ 999.958910] ath11k_pci 0000:07:00.0: htc rx completion ep 1 skb
pK-error
[ 1000.061380] ath11k_pci 0000:07:00.0: htc rx completion ep 1 skb
pK-error
[ 1000.163549] ath11k_pci 0000:07:00.0: htc rx completion ep 1 skb
pK-error
[ 1000.266791] ath11k_pci 0000:07:00.0: htc rx completion ep 1 skb
pK-error
[ 1000.368367] ath11k_pci 0000:07:00.0: htc rx completion ep 1 skb
pK-error
[ 1000.470888] ath11k_pci 0000:07:00.0: htc rx completion ep 1 skb
pK-error
[ 1000.573401] ath11k_pci 0000:07:00.0: htc rx completion ep 1 skb
pK-error
On Tue, 15 Nov 2022 at 11:02, Mariusz <enebeo@gmail.com> wrote:
>
> Hi,
>
> I have asked the manufacturer to confirm. It has the 6E sticker on it
> but I have no lower level tools to read e-fuses if any. Regarding
> board_id they say normally on non-x86 this is set by bootloader so it
> is not hardcoded in eeprom.
> For the HW side, on the PCB there are two markings, 5G (top) and 6E
> (bottom), none of them was bridged from the factory. I bridged the 6E
> one but that did not change anything. In the meantime I also deployed
> aircrack-ng on AX210 client since I have no 6GHz equipment to do other
> testing.
>
> On the client:
> iw wlp1s0 del
> airmon-ng start wlan0mon
> tshark -i wlan0mon -T text -V > log.wifi
> airodump-ng -C 6115 -i wlan0mon --bssid C4:4B:D1:D0:00:7E
>
> Checking available frequencies, this could take few seconds.
> Freq 6115 ][ Elapsed: 0 s ][ 2022-11-08 19:48
> BSSID PWR Beacons #Data, #/s CH MB ENC CIPHER AUTH ESSID
> C4:4B:D1:D0:00:7E -46 12 0 0 33 54e WPA3 CCMP SAE dupa
>
> So the client is seeing signal strength and beacon packets which are
> increasing continuously. It has concluded SSID, MAC and encryption
> details correctly on 6E freq - 6115MHz and it is also seeing op class
> 134 = 160Mhz channel as set. Then I assume electronics at least TX on
> QCN9074 is working fine as the remote client is picking up something
> but whatever is not right as there's no handshake. I tried to
> pre-setup SSID so it auto connects without SSID discovery on Win
> client but no juice. So I dumped packet details, not sure if I read
> all flags right but there's a mix of it mentioning 6GHz supported &
> enabled but in other places OFDM is listed instead of OFDMA. Now which
> part of it is due aircrack-ng having all updates to support/decode 6E
> don't know, it is another variable here.
>
> 802.11 radio information
> PHY type: 802.11a (OFDM) (5)
> Turbo type: Non-turbo (0)
> Data rate: 6.0 Mb/s
> Channel: 33
> Frequency: 6115MHz
> Signal strength (dBm): -47 dBm
> TSF timestamp: 1826096995
> [Duration: 312µs]
> [Preamble: 20µs]
> [IFS: 204488µs]
> [Start: 1826096683µs]
> [End: 1826096995µs]
>
>
> IEEE 802.11 Beacon frame, Flags: ........C
> Type/Subtype: Beacon frame (0x0008)
> Frame Control Field: 0x8000
> .... ..00 = Version: 0
> .... 00.. = Type: Management frame (0)
> 1000 .... = Subtype: 8
> Flags: 0x00
> .... ..00 = DS status: Not leaving DS or network is
> operating in AD-HOC mode (To DS: 0 From DS: 0) (0x0)
> .... .0.. = More Fragments: This is the last fragment
> .... 0... = Retry: Frame is not being retransmitted
> ...0 .... = PWR MGT: STA will stay up
> ..0. .... = More Data: No data buffered
> .0.. .... = Protected flag: Data is not protected
> 0... .... = +HTC/Order flag: Not strictly ordered
> .000 0000 0000 0000 = Duration: 0 microseconds
> Receiver address: Broadcast (ff:ff:ff:ff:ff:ff)
> Destination address: Broadcast (ff:ff:ff:ff:ff:ff)
> Transmitter address: WallysCo_d0:00:7e (c4:4b:d1:d0:00:7e)
> Source address: WallysCo_d0:00:7e (c4:4b:d1:d0:00:7e)
> BSS Id: WallysCo_d0:00:7e (c4:4b:d1:d0:00:7e)
> .... .... .... 0000 = Fragment number: 0
> 0100 0100 0101 .... = Sequence number: 1093
> Frame check sequence: 0xcf64d100 [unverified]
> [FCS Status: Unverified]
>
> IEEE 802.11 Wireless Management
> Fixed parameters (12 bytes)
> Timestamp: 4349132798
> Beacon Interval: 0.204800 [Seconds]
> Capabilities Information: 0x1011
> .... .... .... ...1 = ESS capabilities: Transmitter is an AP
> .... .... .... ..0. = IBSS status: Transmitter belongs to a BSS
> .... ..0. .... 00.. = CFP participation capabilities: No
> point coordinator at AP (0x00)
> .... .... ...1 .... = Privacy: AP/STA can support WEP
> .... .... ..0. .... = Short Preamble: Not Allowed
> .... .... .0.. .... = PBCC: Not Allowed
> .... .... 0... .... = Channel Agility: Not in use
> .... ...0 .... .... = Spectrum Management: Not Implemented
> .... .0.. .... .... = Short Slot Time: Not in use
> .... 0... .... .... = Automatic Power Save Delivery: Not Implemented
> ...1 .... .... .... = Radio Measurement: Implemented
> ..0. .... .... .... = DSSS-OFDM: Not Allowed
> .0.. .... .... .... = Delayed Block Ack: Not Implemented
> 0... .... .... .... = Immediate Block Ack: Not Implemented
> Tagged parameters (175 bytes)
> Tag: SSID parameter set: dupa
> Tag Number: SSID parameter set (0)
> Tag length: 4
> SSID: dupa
> Tag: Supported Rates 6(B), 9, 12(B), 18, 24(B), 36, 48, 54, [Mbit/sec]
> Tag Number: Supported Rates (1)
> Tag length: 8
> Supported Rates: 6(B) (0x8c)
> Supported Rates: 9 (0x12)
> Supported Rates: 12(B) (0x98)
> Supported Rates: 18 (0x24)
> Supported Rates: 24(B) (0xb0)
> Supported Rates: 36 (0x48)
> Supported Rates: 48 (0x60)
> Supported Rates: 54 (0x6c)
> Tag: DS Parameter set: Current Channel: 33
> Tag Number: DS Parameter set (3)
> Tag length: 1
> Current Channel: 33
> Tag: Traffic Indication Map (TIM): DTIM 1 of 2 bitmap
> Tag Number: Traffic Indication Map (TIM) (5)
> Tag length: 4
> DTIM count: 1
> DTIM period: 2
> Bitmap control: 0x00
> .... ...0 = Multicast: False
> 0000 000. = Bitmap Offset: 0x00
> Partial Virtual Bitmap: 00
> Tag: Country Information: Country Code BE, Environment 0x04
> Tag Number: Country Information (7)
> Tag length: 6
> Code: BE
> Environment: 4
> Country Info: Operating Extension Identifier: 201,
> Operating Class: 134, Coverage Class: 0
> Operating Extension Identifier: 201
> Operating Class: 134
> Coverage Class: 0
> Tag: RSN Information
> Tag Number: RSN Information (48)
> Tag length: 20
> RSN Version: 1
> Group Cipher Suite: 00:0f:ac (Ieee 802.11) AES (CCM)
> Group Cipher Suite OUI: 00:0f:ac (Ieee 802.11)
> Group Cipher Suite type: AES (CCM) (4)
> Pairwise Cipher Suite Count: 1
> Pairwise Cipher Suite List 00:0f:ac (Ieee 802.11) AES (CCM)
> Pairwise Cipher Suite: 00:0f:ac (Ieee 802.11) AES (CCM)
> Pairwise Cipher Suite OUI: 00:0f:ac (Ieee 802.11)
> Pairwise Cipher Suite type: AES (CCM) (4)
> Auth Key Management (AKM) Suite Count: 1
> Auth Key Management (AKM) List 00:0f:ac (Ieee 802.11) SAE (SHA256)
> Auth Key Management (AKM) Suite: 00:0f:ac (Ieee
> 802.11) SAE (SHA256)
> Auth Key Management (AKM) OUI: 00:0f:ac (Ieee 802.11)
> Auth Key Management (AKM) type: SAE (SHA256) (8)
> RSN Capabilities: 0x00cc
> .... .... .... ...0 = RSN Pre-Auth capabilities:
> Transmitter does not support pre-authentication
> .... .... .... ..0. = RSN No Pairwise capabilities:
> Transmitter can support WEP default key 0 simultaneously with Pairwise
> key
> .... .... .... 11.. = RSN PTKSA Replay Counter
> capabilities: 16 replay counters per PTKSA/GTKSA/STAKeySA (0x3)
> .... .... ..00 .... = RSN GTKSA Replay Counter
> capabilities: 1 replay counter per PTKSA/GTKSA/STAKeySA (0x0)
> .... .... .1.. .... = Management Frame Protection Required: True
> .... .... 1... .... = Management Frame Protection Capable: True
> .... ...0 .... .... = Joint Multi-band RSNA: False
> .... ..0. .... .... = PeerKey Enabled: False
> ..0. .... .... .... = Extended Key ID for Individually
> Addressed Frames: Not supported
> Tag: RM Enabled Capabilities (5 octets)
> Tag Number: RM Enabled Capabilities (70)
> Tag length: 5
> RM Capabilities: 0x72 (octet 1)
> .... ...0 = Link Measurement: Disabled
> .... ..1. = Neighbor Report: Enabled
> .... .0.. = Parallel Measurements: Disabled
> .... 0... = Repeated Measurements: Disabled
> ...1 .... = Beacon Passive Measurement: Enabled
> ..1. .... = Beacon Active Measurement: Enabled
> .1.. .... = Beacon Table Measurement: Supported
> 0... .... = Beacon Measurement Reporting Conditions: Disabled
> RM Capabilities: 0x00 (octet 2)
> .... ...0 = Frame Measurement: Disabled
> .... ..0. = Channel Load Measurement: Disabled
> .... .0.. = Noise Histogram Measurement: Disabled
> .... 0... = Statistics Measurement: Disabled
> ...0 .... = LCI Measurement: Disabled
> ..0. .... = LCI Azimuth capability: Disabled
> .0.. .... = Transmit Stream/Category Measurement: Not supported
> 0... .... = Triggered Transmit Stream/Category
> Measurement: Disabled
> RM Capabilities: 0x00 (octet 3)
> .... ...0 = AP Channel Report capability: Disabled
> .... ..0. = RM MIB capability: Disabled
> ...0 00.. = Operating Channel Max Measurement Duration: 0
> 000. .... = Nonoperating Channel Max Measurement Duration: 0
> RM Capabilities: 0x00 (octet 4)
> .... .000 = Measurement Pilotcapability: 0
> .... 0... = Measurement Pilot Transmission Information: Disabled
> ...0 .... = Neighbor Report TSF Offset: Disabled
> ..0. .... = RCPI Measurement capability: Disabled
> .0.. .... = RSNI Measurement capability: Not supported
> 0... .... = BSS Average Access Delay capability: Disabled
> RM Capabilities: 0x00 (octet 5)
> .... ...0 = BSS Available Admission Capacity
> capability: Disabled
> .... ..0. = Antenna capability: Disabled
> .... .0.. = FTM Range Report Capability: Disabled
> .... 0... = Civic Location Measurement Capability: Disabled
> 0000 .... = Reserved: 0x0
> Tag: Supported Operating Classes
> Tag Number: Supported Operating Classes (59)
> Tag length: 2
> Current Operating Class: 134
> Tag: Extended Capabilities (10 octets)
> Tag Number: Extended Capabilities (127)
> Tag length: 10
> Extended Capabilities: 0x04 (octet 1)
> .... ...0 = 20/40 BSS Coexistence Management Support:
> Not supported
> .... ..0. = Reserved (was On-demand beacon): 0x0
> .... .1.. = Extended Channel Switching: Supported
> .... 0... = Reserved (was WAVE indication): 0x0
> ...0 .... = PSMP Capability: Not supported
> ..0. .... = Reserved: 0x0
> .0.. .... = S-PSMP Support: Not supported
> 0... .... = Event: Not supported
> Extended Capabilities: 0x00 (octet 2)
> .... ...0 = Diagnostics: Not supported
> .... ..0. = Multicast Diagnostics: Not supported
> .... .0.. = Location Tracking: Not supported
> .... 0... = FMS: Not supported
> ...0 .... = Proxy ARP Service: Not supported
> ..0. .... = Collocated Interference Reporting: Not supported
> .0.. .... = Civic Location: Not supported
> 0... .... = Geospatial Location: Not supported
> Extended Capabilities: 0x00 (octet 3)
> .... ...0 = TFS: Not supported
> .... ..0. = WNM Sleep Mode: Not supported
> .... .0.. = TIM Broadcast: Not supported
> .... 0... = BSS Transition: Not supported
> ...0 .... = QoS Traffic Capability: Not supported
> ..0. .... = AC Station Count: Not supported
> .0.. .... = Multiple BSSID: Not supported
> 0... .... = Timing Measurement: Not supported
> Extended Capabilities: 0x00 (octet 4)
> .... ...0 = Channel Usage: Not supported
> .... ..0. = SSID List: Not supported
> .... .0.. = DMS: Not supported
> .... 0... = UTC TSF Offset: Not supported
> ...0 .... = TPU Buffer STA Support: Not supported
> ..0. .... = TDLS Peer PSM Support: Not supported
> .0.. .... = TDLS channel switching: Not supported
> 0... .... = Interworking: Not supported
> Extended Capabilities: 0x00 (octet 5)
> .... ...0 = QoS Map: Not supported
> .... ..0. = EBR: Not supported
> .... .0.. = SSPN Interface: Not supported
> .... 0... = Reserved: 0x0
> ...0 .... = MSGCF Capability: Not supported
> ..0. .... = TDLS Support: Not supported
> .0.. .... = TDLS Prohibited: Not supported
> 0... .... = TDLS Channel Switching Prohibited: Not supported
> Extended Capabilities: 0x00 (octet 6)
> .... ...0 = Reject Unadmitted Frame: Not supported
> .... 000. = Service Interval Granularity: 5 ms (0)
> ...0 .... = Identifier Location: Not supported
> ..0. .... = U-APSD Coexistence: Not supported
> .0.. .... = WNM Notification: Not supported
> 0... .... = QAB Capability: 0x0
> Extended Capabilities: 0x00 (octet 7)
> .... ...0 = UTF-8 SSID: Not supported
> .... ..0. = QMF Activated: False
> .... .0.. = QMF Reconfiguration Activated: False
> .... 0... = Robust AV Streaming: False
> ...0 .... = Advanced GCR: False
> ..0. .... = Mesh GCR: False
> .0.. .... = SCS: False
> 0... .... = QLoad Report: False
> Extended Capabilities: 0x0040 (octets 8 & 9)
> .... .... .... ...0 = Alternate EDCA: False
> .... .... .... ..0. = Unprotected TXOP Negotiation: False
> .... .... .... .0.. = Protected TXOP Negotiation: False
> .... .... .... 0... = Reserved: 0x0
> .... .... ...0 .... = Protected QLoad Report: False
> .... .... ..0. .... = TDLS Wider Bandwidth: Not supported
> .... .... .1.. .... = Operating Mode Notification: Supported
> .... ...0 0... .... = Max Number Of MSDUs In A-MSDU:
> No limit (0)
> .... ..0. .... .... = Channel Schedule Management: False
> .... .0.. .... .... = Geodatabase Inband Enabling Signal: False
> .... 0... .... .... = Network Channel Control: False
> ...0 .... .... .... = White Space Map: False
> ..0. .... .... .... = Channel Availability Query: False
> .0.. .... .... .... = Fine Timing Measurement Responder: False
> 0... .... .... .... = Fine Timing Measurement Initiator: False
> Extended Capabilities: 0x40 (octet 10)
> .... ...0 = FILS Capable: False
> .... ..0. = Extended Spectrum Management Capable: False
> .... .0.. = Future Channel Capable: False
> .... 0... = Reserved: 0x0
> ...0 .... = Reserved: 0x0
> ..0. .... = TWT Requester Support: False
> .1.. .... = TWT Responder Support: True
> 0... .... = OBSS Narrow Bandwidth RU in UL OFDMA
> Tolerance Support: False
> Tag: Tx Power Envelope
> Tag Number: Tx Power Envelope (195)
> Tag length: 2
> Tx Pwr Info: 0x18
> .... .000 = Max Tx Pwr Count: 0
> ..01 1... = Max Tx Pwr Unit Interpretation: Unknown (3)
> 00.. .... = Reserved: 0
> Local Max Tx Pwr Constraint 20MHz: -1.0 dBm
> Tag: Tx Power Envelope
> Tag Number: Tx Power Envelope (195)
> Tag length: 2
> Tx Pwr Info: 0x58
> .... .000 = Max Tx Pwr Count: 0
> ..01 1... = Max Tx Pwr Unit Interpretation: Unknown (3)
> 01.. .... = Reserved: 1
> Local Max Tx Pwr Constraint 20MHz: 5.0 dBm
> Tag: RSN eXtension (1 octet)
> Tag Number: RSN eXtension (244)
> Tag length: 1
> RSNX: 0x20 (octet 1)
> .... 0000 = RSNX Length: 0
> ...0 .... = Protected TWT Operations Support: 0
> ..1. .... = SAE Hash to element: 1
> 00.. .... = Reserved: 0x0
> Ext Tag: HE Capabilities
> Tag Number: Element ID Extension (255)
> Ext Tag length: 38
> Ext Tag Number: HE Capabilities (35)
> HE MAC Capabilities Information: 0x10409a18000d
> .... .... .... .... .... .... .... .... .... .... ....
> ...1 = +HTC HE Support: Supported
> .... .... .... .... .... .... .... .... .... .... ....
> ..0. = TWT Requester Support: Not supported
> .... .... .... .... .... .... .... .... .... .... ....
> .1.. = TWT Responder Support: Supported
> .... .... .... .... .... .... .... .... .... .... ...0
> 1... = Dynamic Fragmentation Support: Level 1 dynamic fragmentation
> support (1)
> .... .... .... .... .... .... .... .... .... .... 000.
> .... = Maximum Number of Fragmented MSDUs: 1
> .... .... .... .... .... .... .... .... .... ..00 ....
> .... = Minimum Fragment Size: No restriction on minimum payload size
> (0)
> .... .... .... .... .... .... .... .... .... 00.. ....
> .... = Trigger Frame MAC Padding Duration: 0 (0)
> .... .... .... .... .... .... .... .... .000 .... ....
> .... = Multi-TID Aggregation Rx Support: 0
> .... .... .... .... .... .... .... ...0 0... .... ....
> .... = HE Link Adaptation Support: No feedback if the STA does not
> provide HE MFB (0)
> .... .... .... .... .... .... .... ..0. .... .... ....
> .... = All Ack Support: Not supported
> .... .... .... .... .... .... .... .0.. .... .... ....
> .... = TRS Support: Not supported
> .... .... .... .... .... .... .... 1... .... .... ....
> .... = BSR Support: Supported
> .... .... .... .... .... .... ...1 .... .... .... ....
> .... = Broadcast TWT Support: Supported
> .... .... .... .... .... .... ..0. .... .... .... ....
> .... = 32-bit BA Bitmap Support: Not supported
> .... .... .... .... .... .... .0.. .... .... .... ....
> .... = MU Cascading Support: Not supported
> .... .... .... .... .... .... 0... .... .... .... ....
> .... = Ack-Enabled Aggregation Support: Not supported
> .... .... .... .... .... ...0 .... .... .... .... ....
> .... = Reserved: 0x0
> .... .... .... .... .... ..1. .... .... .... .... ....
> .... = OM Control Support: Supported
> .... .... .... .... .... .0.. .... .... .... .... ....
> .... = OFDMA RA Support: Not supported
> .... .... .... .... ...1 1... .... .... .... .... ....
> .... = Maximum A-MPDU Length Exponent Extension: 3
> .... .... .... .... ..0. .... .... .... .... .... ....
> .... = A-MSDU Fragmentation Support: Not supported
> .... .... .... .... .0.. .... .... .... .... .... ....
> .... = Flexible TWT Schedule Support: Not supported
> .... .... .... .... 1... .... .... .... .... .... ....
> .... = Rx Control Frame to MultiBSS: Supported
> .... .... .... ...0 .... .... .... .... .... .... ....
> .... = BSRP BQRP A-MPDU Aggregation: Not supported
> .... .... .... ..0. .... .... .... .... .... .... ....
> .... = QTP Support: Not supported
> .... .... .... .0.. .... .... .... .... .... .... ....
> .... = BQR Support: Not supported
> .... .... .... 0... .... .... .... .... .... .... ....
> .... = PSR Responder: Not supported
> .... .... ...0 .... .... .... .... .... .... .... ....
> .... = NDP Feedback Report Support: Not supported
> .... .... ..0. .... .... .... .... .... .... .... ....
> .... = OPS Support: Not supported
> .... .... .1.. .... .... .... .... .... .... .... ....
> .... = A-MSDU Not Under BA in Ack-Enabled A-MPDU Support: Supported
> .... ..00 0... .... .... .... .... .... .... .... ....
> .... = Multi-TID Aggregation Tx Support: 0
> .... .0.. .... .... .... .... .... .... .... .... ....
> .... = HE Subchannel Selective Transmission Support: Not supported
> .... 0... .... .... .... .... .... .... .... .... ....
> .... = UL 2x996-tone RU Support: Not supported
> ...1 .... .... .... .... .... .... .... .... .... ....
> .... = OM Control UL MU Data Disable RX Support: Supported
> ..0. .... .... .... .... .... .... .... .... .... ....
> .... = HE Dynamic SM Power Save: Not supported
> .0.. .... .... .... .... .... .... .... .... .... ....
> .... = Punctured Sounding Support: Not supported
> 0... .... .... .... .... .... .... .... .... .... ....
> .... = HT And VHT Trigger Frame RX Support: Not supported
> HE PHY Capabilities Information
> .... ...0 = Reserved: 0x0
> .... ...0 = Reserved: 0x0
> 0000 110. = Channel Width Set: 0x06
> .... ..0. = Reserved: 0x0
> .... .1.. = 40 & 80 MHz in the 5 GHz and 6 GHz
> bands: Supported
> .... 1... = 160 MHz in the 5 GHz and 6 GHz bands: Supported
> ...0 .... = 160/80+80 MHz in the 5 GHz and 6 GHz
> bands: Not supported
> ..0. .... = Reserved: 0x0
> .0.. .... = 242 tone RUs in the 5 GHz and 6 GHz
> bands: Not supported
> 0... .... = Reserved: 0x0
> Bits 8 to 23: 0x4c60
> .... .... .... 0000 = Punctured Preamble Rx: 0x0
> .... .... ...0 .... = Device Class: Class B Device (0x0)
> .... .... ..1. .... = LDPC Coding In Payload: Supported
> .... .... .1.. .... = HE SU PPDU With 1x HE-LTF
> And 0.8us GI: Supported
> .... ...0 0... .... = Midamble Tx/Rx Max NSTS: 1
> Space-Time Stream (0x0)
> .... ..0. .... .... = NDP With 4x HE-LTF and 3.2us
> GI: Not supported
> .... .1.. .... .... = STBC Tx <= 80 MHz: Supported
> .... 1... .... .... = STBC Rx <= 80 MHz: Supported
> ...0 .... .... .... = Doppler Tx: Not supported
> ..0. .... .... .... = Doppler Rx: Not supported
> .1.. .... .... .... = Full Bandwidth UL MU-MIMO: Supported
> 0... .... .... .... = Partial Bandwidth UL
> MU-MIMO: Not supported
> Bits 24 to 39: 0xfc08
> .... .... .... ..00 = DCM Max Constellation Tx:
> DCM is not supported (0x0)
> .... .... .... .0.. = DCM Max NSS Tx: 1 Spatial Stream (0x0)
> .... .... ...0 1... = DCM Max Constellation Rx: BPSK (0x1)
> .... .... ..0. .... = DCM Max NSS Rx: 1 Spatial Stream (0x0)
> .... .... .0.. .... = Rx Partial BW SU In 20 MHz
> HE MU PPDU: Not supported
> .... .... 0... .... = SU Beamformer: Not supported
> .... ...0 .... .... = SU Beamformee: Not supported
> .... ..0. .... .... = MU Beamformer: Not supported
> ...1 11.. .... .... = Beamformee STS <= 80 MHz: 0x7
> 111. .... .... .... = Beamformee STS > 80 MHz: 0x7
> Bits 40 to 55: 0x83db
> .... .... .... .011 = Number Of Sounding
> Dimensions <= 80 MHz: 3
> .... .... ..01 1... = Number Of Sounding
> Dimensions > 80 MHz: 3
> .... .... .1.. .... = Ng = 16 SU Feedback: Supported
> .... .... 1... .... = Ng = 16 MU Feedback: Supported
> .... ...1 .... .... = Codebook Size SU Feedback: Supported
> .... ..1. .... .... = Codebook Size MU Feedback: Supported
> .... .0.. .... .... = Triggered SU Beamforming
> Feedback: Not supported
> .... 0... .... .... = Triggered MU Beamforming
> Feedback: Not supported
> ...0 .... .... .... = Triggered CQI Feedback: Not supported
> ..0. .... .... .... = Partial Bandwidth Extended
> Range: Not supported
> .0.. .... .... .... = Partial Bandwidth DL
> MU-MIMO: Not supported
> 1... .... .... .... = PPE Thresholds Present: True
> Bits 56 to 71: 0x119c
> .... .... .... ...0 = PSR-based SR Support: Not supported
> .... .... .... ..0. = Power Boost Factor ar
> Support: Not supported
> .... .... .... .1.. = HE SU PPDU And HE MU PPDU
> With 4x HE-LTF And 0.8us GI: Supported
> .... .... ..01 1... = Max Nc: Supported
> .... .... .0.. .... = STBC Tx > 80 MHz: Not supported
> .... .... 1... .... = STBC Rx > 80 MHz: Supported
> .... ...1 .... .... = HE ER SU PPDU With 4x HE-LTF
> And 0.8us GI: Supported
> .... ..0. .... .... = 20 MHz In 40 MHz HE PPDU In
> 2.4 GHz Band: Not supported
> .... .0.. .... .... = 20 MHz In 160/80+80 MHz HE
> PPDU: Not supported
> .... 0... .... .... = 80 MHz In 160/80+80 MHz HE
> PPDU: Not supported
> ...1 .... .... .... = HE ER SU PPDU With 1x HE-LTF
> And 0.8us GI: Supported
> ..0. .... .... .... = Midamble Tx/Rx 2x And 1x
> HE-LTF: Not supported
> 00.. .... .... .... = DCM Max RU: 242-tone RU (0x0)
> Bits 72 to 87: 0x000c
> .... .... .... ...0 = Longer Than 16 HE SIG-B OFDM
> Symbols Support: Not supported
> .... .... .... ..0. = Non-Triggered CQI Feedback:
> Not supported
> .... .... .... .1.. = Tx 1024-QAM Support <
> 242-tone RU Support: Supported
> .... .... .... 1... = Rx 1024-QAM Support <
> 242-tone RU Support: Supported
> .... .... ...0 .... = Rx Full BW SU Using HE MU
> PPDU With Compressed HE-SIG-B: Not supported
> .... .... ..0. .... = Rx Full BW SU Using HE MU
> PPDU With Non-Compressed HE-SIG-B: Not supported
> .... .... 00.. .... = Nominal Packet Padding: 0 µs
> for all constellations, Nss and RU allocations (0)
> .... ...0 .... .... = HE MU PPDU With More Than
> One RU Rx Max N_HE-LTF: 0
> 0000 000. .... .... = Reserved: 0x00
> Supported HE-MCS and NSS Set
> Rx and Tx MCS Maps <= 80 MHz
> Rx HE-MCS Map <= 80 MHz: 0xffaa
> .... .... .... ..10 = Max HE-MCS for 1 SS:
> Support for HE-MCS 0-11 (0x2)
> .... .... .... 10.. = Max HE-MCS for 2 SS:
> Support for HE-MCS 0-11 (0x2)
> .... .... ..10 .... = Max HE-MCS for 3 SS:
> Support for HE-MCS 0-11 (0x2)
> .... .... 10.. .... = Max HE-MCS for 4 SS:
> Support for HE-MCS 0-11 (0x2)
> .... ..11 .... .... = Max HE-MCS for 5 SS: Not
> supported for HE PPDUs (0x3)
> .... 11.. .... .... = Max HE-MCS for 6 SS: Not
> supported for HE PPDUs (0x3)
> ..11 .... .... .... = Max HE-MCS for 7 SS: Not
> supported for HE PPDUs (0x3)
> 11.. .... .... .... = Max HE-MCS for 8 SS: Not
> supported for HE PPDUs (0x3)
> Tx HE-MCS Map <= 80 MHz: 0xffaa
> .... .... .... ..10 = Max HE-MCS for 1 SS:
> Support for HE-MCS 0-11 (0x2)
> .... .... .... 10.. = Max HE-MCS for 2 SS:
> Support for HE-MCS 0-11 (0x2)
> .... .... ..10 .... = Max HE-MCS for 3 SS:
> Support for HE-MCS 0-11 (0x2)
> .... .... 10.. .... = Max HE-MCS for 4 SS:
> Support for HE-MCS 0-11 (0x2)
> .... ..11 .... .... = Max HE-MCS for 5 SS: Not
> supported for HE PPDUs (0x3)
> .... 11.. .... .... = Max HE-MCS for 6 SS: Not
> supported for HE PPDUs (0x3)
> ..11 .... .... .... = Max HE-MCS for 7 SS: Not
> supported for HE PPDUs (0x3)
> 11.. .... .... .... = Max HE-MCS for 8 SS: Not
> supported for HE PPDUs (0x3)
> Rx and Tx MCS Maps 160 MHz
> Rx HE-MCS Map 160 MHz: 0xffaa
> .... .... .... ..10 = Max HE-MCS for 1 SS:
> Support for HE-MCS 0-11 (0x2)
> .... .... .... 10.. = Max HE-MCS for 2 SS:
> Support for HE-MCS 0-11 (0x2)
> .... .... ..10 .... = Max HE-MCS for 3 SS:
> Support for HE-MCS 0-11 (0x2)
> .... .... 10.. .... = Max HE-MCS for 4 SS:
> Support for HE-MCS 0-11 (0x2)
> .... ..11 .... .... = Max HE-MCS for 5 SS: Not
> supported for HE PPDUs (0x3)
> .... 11.. .... .... = Max HE-MCS for 6 SS: Not
> supported for HE PPDUs (0x3)
> ..11 .... .... .... = Max HE-MCS for 7 SS: Not
> supported for HE PPDUs (0x3)
> 11.. .... .... .... = Max HE-MCS for 8 SS: Not
> supported for HE PPDUs (0x3)
> Tx HE-MCS Map 160 MHz: 0xffaa
> .... .... .... ..10 = Max HE-MCS for 1 SS:
> Support for HE-MCS 0-11 (0x2)
> .... .... .... 10.. = Max HE-MCS for 2 SS:
> Support for HE-MCS 0-11 (0x2)
> .... .... ..10 .... = Max HE-MCS for 3 SS:
> Support for HE-MCS 0-11 (0x2)
> .... .... 10.. .... = Max HE-MCS for 4 SS:
> Support for HE-MCS 0-11 (0x2)
> .... ..11 .... .... = Max HE-MCS for 5 SS: Not
> supported for HE PPDUs (0x3)
> .... 11.. .... .... = Max HE-MCS for 6 SS: Not
> supported for HE PPDUs (0x3)
> ..11 .... .... .... = Max HE-MCS for 7 SS: Not
> supported for HE PPDUs (0x3)
> 11.. .... .... .... = Max HE-MCS for 8 SS: Not
> supported for HE PPDUs (0x3)
> PPE Thresholds
> .... .011 = NSS: 3
> .111 1... = RU Index Bitmask: 0xf
> NSS 0
> RU allocation: 242
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> RU allocation: 484
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> RU allocation: 996
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> RU allocation: 2x996
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> NSS 1
> RU allocation: 242
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> RU allocation: 484
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> RU allocation: 996
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> RU allocation: 2x996
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> NSS 2
> RU allocation: 242
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> RU allocation: 484
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> RU allocation: 996
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> RU allocation: 2x996
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> NSS 3
> RU allocation: 242
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> RU allocation: 484
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> RU allocation: 996
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> RU allocation: 2x996
> PPET16: BPSK (0x00)
> PPET8: None (0x07)
> Ext Tag: HE Operation
> Tag Number: Element ID Extension (255)
> Ext Tag length: 11
> Ext Tag Number: HE Operation (36)
> HE Operation Parameters: 0x023ff0
> .... .... .... .... .... .000 = Default PE Duration: 0
> .... .... .... .... .... 0... = TWT Required: Not required
> .... .... ..11 1111 1111 .... = TXOP Duration RTS
> Threshold: 1023
> .... .... .0.. .... .... .... = VHT Operation
> Information Present: False
> .... .... 0... .... .... .... = Co-Hosted BSS: False
> .... ...0 .... .... .... .... = ER SU Disable: False
> .... ..1. .... .... .... .... = 6 GHz Operation
> Information Present: True
> 0000 00.. .... .... .... .... = Reserved: 0x00
> BSS Color Information: 0x92
> ..01 0010 = BSS Color: 0x12
> .0.. .... = Partial BSS Color: False
> 1... .... = BSS Color Disabled: True
> Basic HE-MCS and NSS Set: 0xfffc
> .... .... .... ..00 = Max HE-MCS for 1 SS: Support for
> HE-MCS 0-7 (0)
> .... .... .... 11.. = Max HE-MCS for 2 SS: Not
> supported for HE PPDUs (3)
> .... .... ..11 .... = Max HE-MCS for 3 SS: Not
> supported for HE PPDUs (3)
> .... .... 11.. .... = Max HE-MCS for 4 SS: Not
> supported for HE PPDUs (3)
> .... ..11 .... .... = Max HE-MCS for 5 SS: Not
> supported for HE PPDUs (3)
> .... 11.. .... .... = Max HE-MCS for 6 SS: Not
> supported for HE PPDUs (3)
> ..11 .... .... .... = Max HE-MCS for 7 SS: Not
> supported for HE PPDUs (3)
> 11.. .... .... .... = Max HE-MCS for 8 SS: Not
> supported for HE PPDUs (3)
> 6 GHz Operation Information
> Primary Channel: 33
> Control: 0x03
> .... ..11 = Channel Width: 160MHz or 80MHz+80MHz (3)
> .... .0.. = Duplicate Beacon: False
> ..00 0... = Regulatory Info: 0
> 00.. .... = Reserved: 0
> Channel Center Frequency Segment 0: 39
> Channel Center Frequency Segment 1: 47
> Minimum Rate: 6
> Ext Tag: HE 6 GHz Band Capabilities
> Tag Number: Element ID Extension (255)
> Ext Tag length: 2
> Ext Tag Number: HE 6 GHz Band Capabilities (59)
> Capabilities Information: 0x36b8
> .... .... .... .000 = Minimum MPDU Start Spacing: No
> restriction (0x0)
> .... .... ..11 1... = Maximum A-MPDU Length Exponent:
> 1 048 575 (0x7)
> .... .... 10.. .... = Maximum MPDU Length: 11 454 (0x2)
> .... ...0 .... .... = Reserved: 0x0
> .... .11. .... .... = SM Power Save: SM Power Save
> disabled (0x3)
> .... 0... .... .... = RD Responder: Not supported
> ...1 .... .... .... = Rx Antenna Pattern Consistency: Supported
> ..1. .... .... .... = Tx Antenna Pattern Consistency: Supported
> 00.. .... .... .... = Reserved: 0x0
> Tag: Vendor Specific: Microsoft Corp.: WMM/WME: Parameter Element
> Tag Number: Vendor Specific (221)
> Tag length: 24
> OUI: 00:50:f2 (Microsoft Corp.)
> Vendor Specific OUI Type: 2
> Type: WMM/WME (0x02)
> WME Subtype: Parameter Element (1)
> WME Version: 1
> WME QoS Info: 0x01
> 0... .... = U-APSD: Disabled
> .... 0001 = Parameter Set Count: 0x1
> .000 .... = Reserved: 0x0
> Reserved: 00
> Ac Parameters ACI 0 (Best Effort), ACM no, AIFSN 3,
> ECWmin/max 4/10 (CWmin/max 15/1023), TXOP 0
> ACI / AIFSN Field: 0x03
> .... 0011 = AIFSN: 3
> ...0 .... = Admission Control Mandatory: No
> .00. .... = ACI: Best Effort (0)
> 0... .... = Reserved: 0
> ECW: 0xa4
> 1010 .... = ECW Max: 10
> .... 0100 = ECW Min: 4
> CW Max: 1023
> CW Min: 15
> TXOP Limit: 0
> Ac Parameters ACI 1 (Background), ACM no, AIFSN 7,
> ECWmin/max 4/10 (CWmin/max 15/1023), TXOP 0
> ACI / AIFSN Field: 0x27
> .... 0111 = AIFSN: 7
> ...0 .... = Admission Control Mandatory: No
> .01. .... = ACI: Background (1)
> 0... .... = Reserved: 0
> ECW: 0xa4
> 1010 .... = ECW Max: 10
> .... 0100 = ECW Min: 4
> CW Max: 1023
> CW Min: 15
> TXOP Limit: 0
> Ac Parameters ACI 2 (Video), ACM no, AIFSN 2, ECWmin/max
> 3/4 (CWmin/max 7/15), TXOP 94
> ACI / AIFSN Field: 0x42
> .... 0010 = AIFSN: 2
> ...0 .... = Admission Control Mandatory: No
> .10. .... = ACI: Video (2)
> 0... .... = Reserved: 0
> ECW: 0x43
> 0100 .... = ECW Max: 4
> .... 0011 = ECW Min: 3
> CW Max: 15
> CW Min: 7
> TXOP Limit: 94
> Ac Parameters ACI 3 (Voice), ACM no, AIFSN 2, ECWmin/max
> 2/3 (CWmin/max 3/7), TXOP 47
> ACI / AIFSN Field: 0x62
> .... 0010 = AIFSN: 2
> ...0 .... = Admission Control Mandatory: No
> .11. .... = ACI: Voice (3)
> 0... .... = Reserved: 0
> ECW: 0x32
> 0011 .... = ECW Max: 3
> .... 0010 = ECW Min: 2
> CW Max: 7
> CW Min: 3
>
>
> If I can check anyhing in between pls. let me know.
> OpenWRT is known to have some tuning for these things but ath11k was
> not included by default hence also QCN9074. So I am now also working
> with 5.15 master, compiled custom OpenWRT with enabled ath11k and
> included *.bin firmware into OpenWRT. Resolved MSI issues to VT-D but
> so far this is still work in progress as the card does not error out
> but never responds to power on command. MHI keeps waiting for power
> on. This is however secondary topic I started looking into due lack of
> progress on a regular distro. Tried also latest 6.1 rc4 kernel on
> ubuntu with no change.
>
> Regards,
> Mariusz
>
>
> On Mon, 14 Nov 2022 at 14:19, Nagarajan Maran (QUIC)
> <quic_nmaran@quicinc.com> wrote:
> >
> > Hi Mariusz,
> >
> >
> >
> > We checked the upstream driver code and firmware bins similar to your setup environment and it seems to work well.
> >
> > Could you kindly check whether your Wi-Fi card has been OTP fused for 6Ghz?
> >
> >
> >
> > -Thanks
> >
> > Nagarajan M.
> >
> >
> >
> > From: Mariusz <enebeo@gmail.com>
> > Sent: Tuesday, November 8, 2022 8:25 PM
> > To: Nagarajan Maran (QUIC) <quic_nmaran@quicinc.com>
> > Cc: ath11k@lists.infradead.org
> > Subject: Re: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
> >
> >
> >
> > Perhaps also something interesting, I apply reg domain of Belgium/BE. It has lower 6GHz channels allowed.
> >
> >
> >
> > iw reg get
> > global
> > country BE: DFS-ETSI
> > (2400 - 2483 @ 40), (N/A, 20), (N/A)
> > (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
> > (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
> > (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
> > (5725 - 5875 @ 80), (N/A, 13), (N/A)
> > (5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
> > (57000 - 66000 @ 2160), (N/A, 40), (N/A)
> >
> > phy#3 (self-managed)
> > country US: DFS-FCC
> > (2402 - 2472 @ 40), (6, 30), (N/A)
> > (5170 - 5250 @ 80), (N/A, 30), (N/A), AUTO-BW
> > (5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
> > (5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS, AUTO-BW
> > (5735 - 5895 @ 160), (N/A, 30), (N/A), AUTO-BW
> > (5945 - 7125 @ 160), (N/A, 30), (N/A), NO-OUTDOOR, AUTO-BW
> >
> >
> >
> > When I start hostapd with acs_survey or channel=0 it starts but pretends to work, no other client can connect to this ssid.
> >
> >
> >
> > When I disable acs in hostapd.conf and set channel=1 (freq 5955 in 6GHz range) so allowed per reg domain it refuses to start:
> >
> >
> >
> > Mode: IEEE 802.11a Channel: 1 Frequency: 5955 MHz
> > nl80211: Set freq 5955 (ht_enabled=0, vht_enabled=0, he_enabled=1, eht_enabled=0, bandwidth=160 MHz, cf1=5955 MHz, cf2=0 MHz)
> > * freq=5955
> > * eht_enabled=0
> > * he_enabled=1
> > * vht_enabled=0
> > * ht_enabled=0
> > * radar_background=0
> > * bandwidth=160
> > * channel_width=5
> > * center_freq1=5955
> > * center_freq2=0
> > nl80211: kernel reports: invalid channel definition
> > nl80211: Failed to set channel (freq=5955): -22 (Invalid argument)
> >
> >
> >
> > reg domain BE is more restrictive than US so channel 1 should be enabled in both cases
> >
> > Previous country code BE, new country code BE
> > nl80211: Regulatory information - country=US (DFS-FCC)
> > nl80211: 2402-2472 @ 40 MHz 30 mBm
> > nl80211: 5170-5250 @ 80 MHz 30 mBm
> > nl80211: 5250-5330 @ 80 MHz 24 mBm (DFS)
> > nl80211: 5490-5730 @ 160 MHz 24 mBm (DFS)
> > nl80211: 5735-5895 @ 160 MHz 30 mBm
> > nl80211: 5945-7125 @ 160 MHz 30 mBm (no outdoor)
> > nl80211: Mode IEEE 802.11a: 5955 5975 5995 6015 6035 6055 6075 6095 6115 6135 6155 6175 6195 6215 6235 6255 6275 6295 6315 6335 6355 6375 6395 6415 6435 6455 6475 6495 6515 6535 6555 6575 6595 6615 6635 6655 6675 6695 6715 6735 6755 6775 6795 6815 6835 6855 6875 6895 6915 6935 6955 6975 6995 7015 7035 7055 7075 7095 7115 5935[DISABLED]
> >
> >
> >
> > for op_class=134 = 160MHz valid channels are 1-29, 33-61, 65-93, 97-125, 129-157, 161-189, 193-221
> >
> >
> >
> >
> >
> > phy: phy3
> > BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
> > wlp1s0: interface state UNINITIALIZED->COUNTRY_UPDATE
> > Previous country code BE, new country code BE
> > nl80211: Regulatory information - country=US (DFS-FCC)
> > nl80211: 2402-2472 @ 40 MHz 30 mBm
> > nl80211: 5170-5250 @ 80 MHz 30 mBm
> > nl80211: 5250-5330 @ 80 MHz 24 mBm (DFS)
> > nl80211: 5490-5730 @ 160 MHz 24 mBm (DFS)
> > nl80211: 5735-5895 @ 160 MHz 30 mBm
> > nl80211: 5945-7125 @ 160 MHz 30 mBm (no outdoor)
> > nl80211: Mode IEEE 802.11a: 5955 5975 5995 6015 6035 6055 6075 6095 6115 6135 6155 6175 6195 6215 6235 6255 6275 6295 6315 6335 6355 6375 6395 6415 6435 6455 6475 6495 6515 6535 6555 6575 6595 6615 6635 6655 6675 6695 6715 6735 6755 6775 6795 6815 6835 6855 6875 6895 6915 6935 6955 6975 6995 7015 7035 7055 7075 7095 7115 5935[DISABLED]
> > Completing interface initialization
> > Mode: IEEE 802.11a Channel: 33 Frequency: 6115 MHz
> > nl80211: Set freq 6115 (ht_enabled=0, vht_enabled=0, he_enabled=1, eht_enabled=0, bandwidth=160 MHz, cf1=6115 MHz, cf2=0 MHz)
> > * freq=6115
> > * eht_enabled=0
> > * he_enabled=1
> > * vht_enabled=0
> > * ht_enabled=0
> > * radar_background=0
> > * bandwidth=160
> > * channel_width=5
> > * center_freq1=6115
> > * center_freq2=0
> > nl80211: kernel reports: invalid channel definition
> > nl80211: Failed to set channel (freq=6115): -22 (Invalid argument)
> > Could not set channel for kernel driver
> > Interface initialization failed
> >
> >
> >
> >
> >
> >
> >
> > How is this invalid channel?
> >
> >
> >
> > root@s4:/home/angel/hostap/hostapd# iw phy3 channels
> > Band 4:
> > * 5955 MHz [1]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 5975 MHz [5]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 5995 MHz [9]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6015 MHz [13]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6035 MHz [17]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6055 MHz [21]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6075 MHz [25]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6095 MHz [29]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6115 MHz [33]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6135 MHz [37]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6155 MHz [41]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6175 MHz [45]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6195 MHz [49]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6215 MHz [53]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6235 MHz [57]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6255 MHz [61]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6275 MHz [65]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6295 MHz [69]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6315 MHz [73]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6335 MHz [77]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6355 MHz [81]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6375 MHz [85]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6395 MHz [89]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6415 MHz [93]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6435 MHz [97]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6455 MHz [101]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6475 MHz [105]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6495 MHz [109]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6515 MHz [113]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6535 MHz [117]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6555 MHz [121]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6575 MHz [125]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6595 MHz [129]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6615 MHz [133]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6635 MHz [137]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6655 MHz [141]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6675 MHz [145]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6695 MHz [149]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6715 MHz [153]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6735 MHz [157]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6755 MHz [161]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6775 MHz [165]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6795 MHz [169]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6815 MHz [173]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6835 MHz [177]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6855 MHz [181]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6875 MHz [185]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6895 MHz [189]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6915 MHz [193]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6935 MHz [197]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6955 MHz [201]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6975 MHz [205]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 6995 MHz [209]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 7015 MHz [213]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 7035 MHz [217]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 7055 MHz [221]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 7075 MHz [225]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 7095 MHz [229]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 7115 MHz [233]
> > Maximum TX power: 30.0 dBm
> > Channel widths: 20MHz
> > * 5935 MHz [2] (disabled)
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On Mon, 7 Nov 2022 at 17:07, Nagarajan Maran (QUIC) <quic_nmaran@quicinc.com> wrote:
> >
> > Hi Mariusz,
> >
> > We are looking into this issue. It seems that this error can occur when the given frequency is not present or when the given frequency is disabled.
> > To further analyze the issue, could you kindly let us know the output of the below commands during failure case.
> > 1) iw dev
> > 2) iw phyX channels
> >
> > Also, could you kindly send the WiFi driver boot up logs with "debug_mask=0x212" enabled during insmod of ath11k.ko module.
> >
> > Thanks,
> > Nagarajan M.
> >
> > -----Original Message-----
> >
> > From: Mariusz <enebeo@gmail.com>
> > To: ath11k@lists.infradead.org
> > Subject: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
> > Message-ID:
> > <CAJrE-q6NVEF4sNW1s4Zz7Pb2ryzCi69e+_vLQswBWm747DHYDw@mail.gmail.com>
> > Content-Type: text/plain; charset="UTF-8"
> >
> > Hi,
> >
> > As support for QCN9074 got better I went ahead and built a 6E linux based AP. Dell R720 server x86 running Linux s4 5.19.0-23-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64
> > x86_64 x86_64 GNU/Linux.
> >
> > My issue is that I cannot get it working on 6GHz bands but it works fine on 5GHz. I bought 6E version and since this is a single band module it cannot be both 5G & 6G and linux driver does not agree with it being 6E version:
> >
> > [71914.038562] ath11k_pci 0000:03:00.0: BAR 0: assigned [mem 0xdf800000-0xdf9fffff 64bit] [71914.038840] ath11k_pci 0000:03:00.0: MSI vectors: 16 [71914.038852] ath11k_pci 0000:03:00.0: qcn9074 hw1.0 [71914.194459] mhi mhi0: Requested to power ON [71914.194712] mhi mhi0: Power on setup success [71914.297749] mhi mhi0: Wait for device to enter SBL or Mission mode [71914.647118] ath11k_pci 0000:03:00.0: chip_id 0x0 chip_family 0x0 board_id 0xff soc_id 0xffffffff [71914.647134] ath11k_pci 0000:03:00.0: fw_version 0x250a04b8 fw_build_timestamp 2021-12-20 06:41 fw_build_id [71916.310787] ath11k_pci 0000:03:00.0 wlp3s0: renamed from wlan0
> >
> > HE PHY Capabilities: (0x1c604c88ffdb839c110c00):
> > HE40/HE80/5GHz
> > HE160/5GHz
> > HE160/HE80+80/5GHz
> >
> > iw dev wlp3s0 set freq 6195 160MHz
> > kernel reports: Channel is disabled
> > command failed: Invalid argument (-22)
> >
> > I am using the latest firmware files from ath11k tree. Is there any special firmware to force this to 6GHz? I read somewhere board_id determines which one it is and 255 disables 6GHz but I miss more data on that.
> >
> > phy#2 (self-managed)
> > country US: DFS-FCC
> > (2402 - 2472 @ 40), (6, 30), (N/A)
> > (5170 - 5250 @ 80), (N/A, 30), (N/A), AUTO-BW
> > (5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
> > (5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS, AUTO-BW
> > (5735 - 5895 @ 160), (N/A, 30), (N/A), AUTO-BW
> > (5945 - 7125 @ 160), (N/A, 30), (N/A), NO-OUTDOOR, AUTO-BW
> >
> > It works fine in 5GHz but this is not what I purchased it for, so I am puzzled if this is something in software or I was sold wrong hardware.Is there a specific board-2.bin for 6GHz? Since the 9074 chip is the same in all versions perhaps this is a software hiccup.
> >
> > Any clues are welcome.
> >
> > Regards,
> > Mario
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
2022-11-15 18:29 ` walde
2022-11-15 19:18 ` Mariusz
@ 2022-11-18 11:26 ` Sven Eckelmann
2022-11-18 12:48 ` Mariusz
1 sibling, 1 reply; 18+ messages in thread
From: Sven Eckelmann @ 2022-11-18 11:26 UTC (permalink / raw)
To: walde; +Cc: Mariusz, ath11k
[-- Attachment #1.1: Type: text/plain, Size: 924 bytes --]
On Tuesday, 15 November 2022 19:29:13 CET walde wrote:
> we probably have the same problem.
> We have two Pinapple 6 Wifi 6 cards from the manufacturer 8devices that
> we want to operate at 6 GHz. The modules have the QCN 9074 chipset and
> are also certified for the 6E standard. The modules work very well at 5
> GHZ. However the option to transmit on 6 GHz is not available. The board
> ID is also defined as 0xff. If there is any information you could share
> to enable the modules for 6 GHz, we would appreciate it.
You have to return it to them via their RMA procedure [1]. I already did that
in (mid) January 2022 and they replaced our cards with properly working
versions in (mid) February 2022.
Maybe you got a card from their first batch(es) (which had this problem) - or
the problem was reintroduced for some reason.
Kind regards,
Sven
[1] https://shop.8devices.com/index.php?route=account/return/add
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 102 bytes --]
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
2022-11-18 11:26 ` Sven Eckelmann
@ 2022-11-18 12:48 ` Mariusz
2022-11-18 14:05 ` Sven Eckelmann
0 siblings, 1 reply; 18+ messages in thread
From: Mariusz @ 2022-11-18 12:48 UTC (permalink / raw)
To: Sven Eckelmann; +Cc: walde, ath11k
Mine is from a different supplier - Wallys - and I bought it 2 weeks
ago but not sure how old their stock is. PCB looks slightly different
than Pinapple's. Is it likely to have the same issue?
What I noticed is that not only it does not have board_id preset but
also 6Ghz / 6E is only enabled (at least by the driver) when the
regulatory domain is set to US. Any other setting disables 6Ghz
channels. That is not in line with regulatory situation in EU as lower
6E bands are allowed. Intel AX210 has this right.
Also looking into their pre-compiled driver .ko, they seemed to for
whatever reason customize it. Path is far from standard kernel source
/home/wallystech/qca_ath11k/wt_ath11k/ath11k_5_17_0/
Of course I cannot load their pre-compiled driver due kernel issues. I
used the same kernel 5.17.0 but vermagic was different, I patched
vermagic plus copied symbol_table id from my 5.17.0 kernel ath11k.ko
module to the pre-compiled module which resulted in missing symbols of
course.
Not clear what they did to the driver code and no feedback of course.
Right now the only last clue I am left with is that QCN9074 has 6E on
only when iw reg is set to US. Client on the other hand forces this to
EU via LAR. Lower frequencies match between reg domains i.e. 5955
channel 1 is allowed by both reg domains. Maybe there is something
else at play that client with reg set to EU ignores beacons from AP
with reg set to US. This I cannot overcome for now, client does not
accept any change being intel iwlwifi driver and QCN9074 disables all
6E channels when reg is set to anything else than US.
Regards,
Mariusz
On Fri, 18 Nov 2022 at 12:27, Sven Eckelmann <sven@narfation.org> wrote:
>
> On Tuesday, 15 November 2022 19:29:13 CET walde wrote:
> > we probably have the same problem.
> > We have two Pinapple 6 Wifi 6 cards from the manufacturer 8devices that
> > we want to operate at 6 GHz. The modules have the QCN 9074 chipset and
> > are also certified for the 6E standard. The modules work very well at 5
> > GHZ. However the option to transmit on 6 GHz is not available. The board
> > ID is also defined as 0xff. If there is any information you could share
> > to enable the modules for 6 GHz, we would appreciate it.
>
> You have to return it to them via their RMA procedure [1]. I already did that
> in (mid) January 2022 and they replaced our cards with properly working
> versions in (mid) February 2022.
>
> Maybe you got a card from their first batch(es) (which had this problem) - or
> the problem was reintroduced for some reason.
>
> Kind regards,
> Sven
>
> [1] https://shop.8devices.com/index.php?route=account/return/add
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
2022-11-18 12:48 ` Mariusz
@ 2022-11-18 14:05 ` Sven Eckelmann
2022-11-19 13:39 ` Mariusz
2022-12-06 8:56 ` Sven Eckelmann
0 siblings, 2 replies; 18+ messages in thread
From: Sven Eckelmann @ 2022-11-18 14:05 UTC (permalink / raw)
To: Mariusz; +Cc: walde, ath11k
[-- Attachment #1.1: Type: text/plain, Size: 2053 bytes --]
On Friday, 18 November 2022 13:48:43 CET Mariusz wrote:
> Mine is from a different supplier - Wallys - and I bought it 2 weeks
> ago but not sure how old their stock is. PCB looks slightly different
> than Pinapple's. Is it likely to have the same issue?
It definitely has the same issue (because you reported that board_id is
255/0xff) but I have no idea whether Wallytech ever fixed it. At least I was
never in contact about this problem with them. But sending around precompiled
kernel module binaries (for an unknown kernel build), with some hacks to fix
their hardware production errors (missing module id fusing in the OTP for
their separately sold modules), doesn't make me confident that they are able
to solve this problem correctly.
In their defense, QCA doesn't make it really easy. It seems like their
reference designs with Pine on 6Ghz are (mostly?) for (embedded Linux) APs
which use the normal flash (NOR or NAND) to store the calibration data. And
for these devices, they use the devicetree (or various other hacks) to load
the correct board data.
Wallystech has to find the correct document on createpoint which describes the
process. It was something like "module" "board id" "fusing". But it is not the
"Board ID Fusing for 802.11ax WLAN AP Chipsets" which only describes the way
how you would to it for thei internal wifi of the IPQ807x/IPQ60xx/... SoC.
You/they are searching for the corresponding document for Pine IPQ9074. Most
likely hidden in some QDART documents.
Regarding the problem that some countries are not allowing 6GHz: You have to
either get a firmware from QCA which has it enabled or you modify the BDFs
("board-" files in the board-2.bin) to enable 6GHz in the (enabled) embedded
REGDB of the BDFs for the specific country. Unfortunately, the data structures
of the BDF are not officially documented and you would need an official QSDK/
ATH.11.X release from QCA to fetch the bdf2txt.py, txt2bdf.py and the
corresponding template for your BDF to extract and modify it.
Kind regards,
Sven
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 102 bytes --]
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
2022-11-18 14:05 ` Sven Eckelmann
@ 2022-11-19 13:39 ` Mariusz
2022-11-19 15:16 ` Robert Marko
2022-12-06 8:56 ` Sven Eckelmann
1 sibling, 1 reply; 18+ messages in thread
From: Mariusz @ 2022-11-19 13:39 UTC (permalink / raw)
To: Sven Eckelmann; +Cc: walde, ath11k
I have contacted Wallys again but I am skeptical about resolution.
They don't consider board_id an issue and provided the same response,
on integrated systems it is due the bootloader to set it properly so
it is not fused and obviously not included in x86 scenario. Since this
is a private project I doubt QCA will support my efforts and free
access to their portals gives nothing. Found online some SDK for
version ath10k/IPQ8074 and athtestcmd to deal with OTP/fusing but
that's far beyond home project effort.
Tried also to compile it in OpenWRT with moderate success. ath11ko /
qrtr.ko modules are built but the module never goes past power on
success.
mhi mhi0: Requested to power ON
mhi mhi0: Power on setup success
mhi mhi0: Wait for device to enter SBL or Mission mode
Even the newest kernel in OpenWRT master development branch 5.16 is
quite behind and backporting anything is another non-trivial task.
On Fri, 18 Nov 2022 at 15:06, Sven Eckelmann <sven@narfation.org> wrote:
>
> On Friday, 18 November 2022 13:48:43 CET Mariusz wrote:
> > Mine is from a different supplier - Wallys - and I bought it 2 weeks
> > ago but not sure how old their stock is. PCB looks slightly different
> > than Pinapple's. Is it likely to have the same issue?
>
> It definitely has the same issue (because you reported that board_id is
> 255/0xff) but I have no idea whether Wallytech ever fixed it. At least I was
> never in contact about this problem with them. But sending around precompiled
> kernel module binaries (for an unknown kernel build), with some hacks to fix
> their hardware production errors (missing module id fusing in the OTP for
> their separately sold modules), doesn't make me confident that they are able
> to solve this problem correctly.
>
> In their defense, QCA doesn't make it really easy. It seems like their
> reference designs with Pine on 6Ghz are (mostly?) for (embedded Linux) APs
> which use the normal flash (NOR or NAND) to store the calibration data. And
> for these devices, they use the devicetree (or various other hacks) to load
> the correct board data.
>
> Wallystech has to find the correct document on createpoint which describes the
> process. It was something like "module" "board id" "fusing". But it is not the
> "Board ID Fusing for 802.11ax WLAN AP Chipsets" which only describes the way
> how you would to it for thei internal wifi of the IPQ807x/IPQ60xx/... SoC.
> You/they are searching for the corresponding document for Pine IPQ9074. Most
> likely hidden in some QDART documents.
>
>
> Regarding the problem that some countries are not allowing 6GHz: You have to
> either get a firmware from QCA which has it enabled or you modify the BDFs
> ("board-" files in the board-2.bin) to enable 6GHz in the (enabled) embedded
> REGDB of the BDFs for the specific country. Unfortunately, the data structures
> of the BDF are not officially documented and you would need an official QSDK/
> ATH.11.X release from QCA to fetch the bdf2txt.py, txt2bdf.py and the
> corresponding template for your BDF to extract and modify it.
>
> Kind regards,
> Sven
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
2022-11-19 13:39 ` Mariusz
@ 2022-11-19 15:16 ` Robert Marko
2022-11-19 16:09 ` Mariusz
2022-11-20 8:13 ` Mariusz
0 siblings, 2 replies; 18+ messages in thread
From: Robert Marko @ 2022-11-19 15:16 UTC (permalink / raw)
To: Mariusz; +Cc: Sven Eckelmann, walde, ath11k
On Sat, Nov 19, 2022 at 2:40 PM Mariusz <enebeo@gmail.com> wrote:
>
> I have contacted Wallys again but I am skeptical about resolution.
> They don't consider board_id an issue and provided the same response,
> on integrated systems it is due the bootloader to set it properly so
> it is not fused and obviously not included in x86 scenario.
Hi, this is not really the case, how would the bootloader set the board_id
which is supposed to be fused on the device so FW would report the correct one?
You can only workaround that by hardcoding it in the driver or on non-x86
in DTS and force-loading the correct BDF that way.
> Since this
> is a private project I doubt QCA will support my efforts and free
> access to their portals gives nothing. Found online some SDK for
> version ath10k/IPQ8074 and athtestcmd to deal with OTP/fusing but
> that's far beyond home project effort.
>
> Tried also to compile it in OpenWRT with moderate success. ath11ko /
> qrtr.ko modules are built but the module never goes past power on
> success.
> mhi mhi0: Requested to power ON
> mhi mhi0: Power on setup success
> mhi mhi0: Wait for device to enter SBL or Mission mode
>
> Even the newest kernel in OpenWRT master development branch 5.16 is
> quite behind and backporting anything is another non-trivial task.
ath11k won't work in OpenWrt master currently, I have been supporting IPQ807x
and recently PCI version as well out-of-tree with hopes of getting it soon into
OpenWrt once 6.1 backports become available as that gets rid of like 300-ish
backported patches.
Regards,
Robert
>
> On Fri, 18 Nov 2022 at 15:06, Sven Eckelmann <sven@narfation.org> wrote:
> >
> > On Friday, 18 November 2022 13:48:43 CET Mariusz wrote:
> > > Mine is from a different supplier - Wallys - and I bought it 2 weeks
> > > ago but not sure how old their stock is. PCB looks slightly different
> > > than Pinapple's. Is it likely to have the same issue?
> >
> > It definitely has the same issue (because you reported that board_id is
> > 255/0xff) but I have no idea whether Wallytech ever fixed it. At least I was
> > never in contact about this problem with them. But sending around precompiled
> > kernel module binaries (for an unknown kernel build), with some hacks to fix
> > their hardware production errors (missing module id fusing in the OTP for
> > their separately sold modules), doesn't make me confident that they are able
> > to solve this problem correctly.
> >
> > In their defense, QCA doesn't make it really easy. It seems like their
> > reference designs with Pine on 6Ghz are (mostly?) for (embedded Linux) APs
> > which use the normal flash (NOR or NAND) to store the calibration data. And
> > for these devices, they use the devicetree (or various other hacks) to load
> > the correct board data.
> >
> > Wallystech has to find the correct document on createpoint which describes the
> > process. It was something like "module" "board id" "fusing". But it is not the
> > "Board ID Fusing for 802.11ax WLAN AP Chipsets" which only describes the way
> > how you would to it for thei internal wifi of the IPQ807x/IPQ60xx/... SoC.
> > You/they are searching for the corresponding document for Pine IPQ9074. Most
> > likely hidden in some QDART documents.
> >
> >
> > Regarding the problem that some countries are not allowing 6GHz: You have to
> > either get a firmware from QCA which has it enabled or you modify the BDFs
> > ("board-" files in the board-2.bin) to enable 6GHz in the (enabled) embedded
> > REGDB of the BDFs for the specific country. Unfortunately, the data structures
> > of the BDF are not officially documented and you would need an official QSDK/
> > ATH.11.X release from QCA to fetch the bdf2txt.py, txt2bdf.py and the
> > corresponding template for your BDF to extract and modify it.
> >
> > Kind regards,
> > Sven
>
> --
> ath11k mailing list
> ath11k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath11k
--
Robert Marko
Staff Embedded Linux Engineer
Sartura Ltd.
Lendavska ulica 16a
10000 Zagreb, Croatia
Email: robert.marko@sartura.hr
Web: www.sartura.hr
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
2022-11-19 15:16 ` Robert Marko
@ 2022-11-19 16:09 ` Mariusz
2022-11-20 8:13 ` Mariusz
1 sibling, 0 replies; 18+ messages in thread
From: Mariusz @ 2022-11-19 16:09 UTC (permalink / raw)
To: Robert Marko; +Cc: Sven Eckelmann, walde, ath11k
I am just relying on what I am told by their support, really wanted to
deploy a 6E SoftAP for my home lab and expected some hackery but this
is like an early dev sample kind of environment with most stuff in the
works.
For the time being this is exactly what I did with hardcoding board_id
into the driver: /drivers/net/wireless/ath/ath11k/qmi.c:2234:
ab->qmi.target.board_id = 0xA2;
After this no more board.bin hackery is needed and correct firmware is
loaded from board-2.bin. This of course means I cannot use any other
ath11k card in the system as it would be forced to this id but that's
not an issue. My objective is to have only 6E add on to my network.
Now correctly reported:
[ 1525.142906] ath11k_pci 0000:07:00.0: chip_id 0x0 chip_family 0x0
board_id 0xa2 soc_id 0xffffffff
[ 1525.142909] ath11k_pci 0000:07:00.0: fw_version 0x270206d0
fw_build_timestamp 2022-08-04 12:48 fw_build_id
WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1
and the correct FW is loaded with 6Ghz channels enabled.
Debug is no longer showing any errors, hostapd is not reporting
anything wrong everything pretends to work but it does not in
practice. What puzzles me is that raw dump of wireless frames off
AX210 client shows there is beacon transmission from the module but
for whatever reason the client ignores it as a valid AP option.
airodump-ng -C 6115 -i wlan0mon --bssid C4:4B:D1:D0:00:7E
Freq 6115 ][ Elapsed: 0 s ][ 2022-11-18 13:48
BSSID PWR Beacons #Data, #/s CH MB ENC CIPHER AUTH ESSID
C4:4B:D1:D0:00:7E -46 12 0 0 33 54e WPA3 CCMP SAE dupa
On Sat, 19 Nov 2022 at 16:16, Robert Marko <robert.marko@sartura.hr> wrote:
>
> On Sat, Nov 19, 2022 at 2:40 PM Mariusz <enebeo@gmail.com> wrote:
> >
> > I have contacted Wallys again but I am skeptical about resolution.
> > They don't consider board_id an issue and provided the same response,
> > on integrated systems it is due the bootloader to set it properly so
> > it is not fused and obviously not included in x86 scenario.
>
> Hi, this is not really the case, how would the bootloader set the board_id
> which is supposed to be fused on the device so FW would report the correct one?
> You can only workaround that by hardcoding it in the driver or on non-x86
> in DTS and force-loading the correct BDF that way.
>
> > Since this
> > is a private project I doubt QCA will support my efforts and free
> > access to their portals gives nothing. Found online some SDK for
> > version ath10k/IPQ8074 and athtestcmd to deal with OTP/fusing but
> > that's far beyond home project effort.
> >
> > Tried also to compile it in OpenWRT with moderate success. ath11ko /
> > qrtr.ko modules are built but the module never goes past power on
> > success.
> > mhi mhi0: Requested to power ON
> > mhi mhi0: Power on setup success
> > mhi mhi0: Wait for device to enter SBL or Mission mode
> >
> > Even the newest kernel in OpenWRT master development branch 5.16 is
> > quite behind and backporting anything is another non-trivial task.
>
> ath11k won't work in OpenWrt master currently, I have been supporting IPQ807x
> and recently PCI version as well out-of-tree with hopes of getting it soon into
> OpenWrt once 6.1 backports become available as that gets rid of like 300-ish
> backported patches.
>
> Regards,
> Robert
> >
> > On Fri, 18 Nov 2022 at 15:06, Sven Eckelmann <sven@narfation.org> wrote:
> > >
> > > On Friday, 18 November 2022 13:48:43 CET Mariusz wrote:
> > > > Mine is from a different supplier - Wallys - and I bought it 2 weeks
> > > > ago but not sure how old their stock is. PCB looks slightly different
> > > > than Pinapple's. Is it likely to have the same issue?
> > >
> > > It definitely has the same issue (because you reported that board_id is
> > > 255/0xff) but I have no idea whether Wallytech ever fixed it. At least I was
> > > never in contact about this problem with them. But sending around precompiled
> > > kernel module binaries (for an unknown kernel build), with some hacks to fix
> > > their hardware production errors (missing module id fusing in the OTP for
> > > their separately sold modules), doesn't make me confident that they are able
> > > to solve this problem correctly.
> > >
> > > In their defense, QCA doesn't make it really easy. It seems like their
> > > reference designs with Pine on 6Ghz are (mostly?) for (embedded Linux) APs
> > > which use the normal flash (NOR or NAND) to store the calibration data. And
> > > for these devices, they use the devicetree (or various other hacks) to load
> > > the correct board data.
> > >
> > > Wallystech has to find the correct document on createpoint which describes the
> > > process. It was something like "module" "board id" "fusing". But it is not the
> > > "Board ID Fusing for 802.11ax WLAN AP Chipsets" which only describes the way
> > > how you would to it for thei internal wifi of the IPQ807x/IPQ60xx/... SoC.
> > > You/they are searching for the corresponding document for Pine IPQ9074. Most
> > > likely hidden in some QDART documents.
> > >
> > >
> > > Regarding the problem that some countries are not allowing 6GHz: You have to
> > > either get a firmware from QCA which has it enabled or you modify the BDFs
> > > ("board-" files in the board-2.bin) to enable 6GHz in the (enabled) embedded
> > > REGDB of the BDFs for the specific country. Unfortunately, the data structures
> > > of the BDF are not officially documented and you would need an official QSDK/
> > > ATH.11.X release from QCA to fetch the bdf2txt.py, txt2bdf.py and the
> > > corresponding template for your BDF to extract and modify it.
> > >
> > > Kind regards,
> > > Sven
> >
> > --
> > ath11k mailing list
> > ath11k@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/ath11k
>
>
>
> --
> Robert Marko
> Staff Embedded Linux Engineer
> Sartura Ltd.
> Lendavska ulica 16a
> 10000 Zagreb, Croatia
> Email: robert.marko@sartura.hr
> Web: www.sartura.hr
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
2022-11-19 15:16 ` Robert Marko
2022-11-19 16:09 ` Mariusz
@ 2022-11-20 8:13 ` Mariusz
2022-11-22 15:14 ` Mariusz
1 sibling, 1 reply; 18+ messages in thread
From: Mariusz @ 2022-11-20 8:13 UTC (permalink / raw)
To: Robert Marko; +Cc: Sven Eckelmann, walde, ath11k
I also got my hands on AXE75 which is a 6E router and I am able to get
QCN9074 work in STA mode.
With 160Mhz it did not work but it may be anything. However with 80Mhz
I am able to get a successful connection fully authenticated with
WPA3. So radio wise it operates in 6Ghz band after driver patch with
board_id=0xa2. Now I'm trying to understand why it still does not work
in AP mode.
root@s4:/home/angel# wpa_cli status
Selected interface 'wlp6s0'
bssid=1c:61:b4:c8:93:f4
freq=6115
ssid=test
id=0
mode=station
wifi_generation=6
pairwise_cipher=CCMP
group_cipher=CCMP
key_mgmt=SAE
pmf=2
mgmt_group_cipher=BIP
wpa_state=COMPLETED
ip_address=192.168.6.123
address=c4:4b:d1:d0:00:7e
uuid=07aaca38-a259-53ef-b12b-bb4cf5dad8d8
On Sat, 19 Nov 2022 at 16:16, Robert Marko <robert.marko@sartura.hr> wrote:
>
> On Sat, Nov 19, 2022 at 2:40 PM Mariusz <enebeo@gmail.com> wrote:
> >
> > I have contacted Wallys again but I am skeptical about resolution.
> > They don't consider board_id an issue and provided the same response,
> > on integrated systems it is due the bootloader to set it properly so
> > it is not fused and obviously not included in x86 scenario.
>
> Hi, this is not really the case, how would the bootloader set the board_id
> which is supposed to be fused on the device so FW would report the correct one?
> You can only workaround that by hardcoding it in the driver or on non-x86
> in DTS and force-loading the correct BDF that way.
>
> > Since this
> > is a private project I doubt QCA will support my efforts and free
> > access to their portals gives nothing. Found online some SDK for
> > version ath10k/IPQ8074 and athtestcmd to deal with OTP/fusing but
> > that's far beyond home project effort.
> >
> > Tried also to compile it in OpenWRT with moderate success. ath11ko /
> > qrtr.ko modules are built but the module never goes past power on
> > success.
> > mhi mhi0: Requested to power ON
> > mhi mhi0: Power on setup success
> > mhi mhi0: Wait for device to enter SBL or Mission mode
> >
> > Even the newest kernel in OpenWRT master development branch 5.16 is
> > quite behind and backporting anything is another non-trivial task.
>
> ath11k won't work in OpenWrt master currently, I have been supporting IPQ807x
> and recently PCI version as well out-of-tree with hopes of getting it soon into
> OpenWrt once 6.1 backports become available as that gets rid of like 300-ish
> backported patches.
>
> Regards,
> Robert
> >
> > On Fri, 18 Nov 2022 at 15:06, Sven Eckelmann <sven@narfation.org> wrote:
> > >
> > > On Friday, 18 November 2022 13:48:43 CET Mariusz wrote:
> > > > Mine is from a different supplier - Wallys - and I bought it 2 weeks
> > > > ago but not sure how old their stock is. PCB looks slightly different
> > > > than Pinapple's. Is it likely to have the same issue?
> > >
> > > It definitely has the same issue (because you reported that board_id is
> > > 255/0xff) but I have no idea whether Wallytech ever fixed it. At least I was
> > > never in contact about this problem with them. But sending around precompiled
> > > kernel module binaries (for an unknown kernel build), with some hacks to fix
> > > their hardware production errors (missing module id fusing in the OTP for
> > > their separately sold modules), doesn't make me confident that they are able
> > > to solve this problem correctly.
> > >
> > > In their defense, QCA doesn't make it really easy. It seems like their
> > > reference designs with Pine on 6Ghz are (mostly?) for (embedded Linux) APs
> > > which use the normal flash (NOR or NAND) to store the calibration data. And
> > > for these devices, they use the devicetree (or various other hacks) to load
> > > the correct board data.
> > >
> > > Wallystech has to find the correct document on createpoint which describes the
> > > process. It was something like "module" "board id" "fusing". But it is not the
> > > "Board ID Fusing for 802.11ax WLAN AP Chipsets" which only describes the way
> > > how you would to it for thei internal wifi of the IPQ807x/IPQ60xx/... SoC.
> > > You/they are searching for the corresponding document for Pine IPQ9074. Most
> > > likely hidden in some QDART documents.
> > >
> > >
> > > Regarding the problem that some countries are not allowing 6GHz: You have to
> > > either get a firmware from QCA which has it enabled or you modify the BDFs
> > > ("board-" files in the board-2.bin) to enable 6GHz in the (enabled) embedded
> > > REGDB of the BDFs for the specific country. Unfortunately, the data structures
> > > of the BDF are not officially documented and you would need an official QSDK/
> > > ATH.11.X release from QCA to fetch the bdf2txt.py, txt2bdf.py and the
> > > corresponding template for your BDF to extract and modify it.
> > >
> > > Kind regards,
> > > Sven
> >
> > --
> > ath11k mailing list
> > ath11k@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/ath11k
>
>
>
> --
> Robert Marko
> Staff Embedded Linux Engineer
> Sartura Ltd.
> Lendavska ulica 16a
> 10000 Zagreb, Croatia
> Email: robert.marko@sartura.hr
> Web: www.sartura.hr
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
2022-11-20 8:13 ` Mariusz
@ 2022-11-22 15:14 ` Mariusz
0 siblings, 0 replies; 18+ messages in thread
From: Mariusz @ 2022-11-22 15:14 UTC (permalink / raw)
To: Robert Marko; +Cc: Sven Eckelmann, walde, ath11k
I finally got it to work! Performance wise it is not terrible and now
I am moving from driver perimeter to hostapd perimeter. Running stable
for the last 24hrs, no drops.
160Mhz width on channel 5, client reports 2402/2402 (Mbps) which is
max since intel AX210 is a 2 stream device versus 4 on QCN. In
practice with iperf3 between NAS & my PC connected to the SoftAP and 4
threads:
[SUM] 0.00-10.00 sec 1.13 GBytes 972 Mbits/sec sender
[SUM] 0.00-10.00 sec 1.13 GBytes 972 Mbits/sec receiver
1669065192.525964: Mode: IEEE 802.11a Channel: 5 Frequency: 5975 MHz
1669065192.525965: nl80211: Set freq 5975 (ht_enabled=0,
vht_enabled=0, he_enabled=1, eht_enabled=0, bandwidth=160 MHz,
cf1=6025 MHz, cf2=0 MHz)
Not that it is specific to ath11k driver but in case anyone is looking
for some information getting it up required solving regulatory domain
issues, board_id issues and finally hostapd issues - maybe not issues
but considerations.
- First I got a list of channels off the internet wrongly listing PSC
channels as 1, 17 , 33 etc. Hostapd channel=0 with ACS was setting
channel 33 as optimal. I assumed this is a PSC channel wrongly.
Comparing live packet dumps from AXE75 and QCN9074 I started spotting
those nuances and a problem was already creating itself. As explained
this is a single band module so it does not have any 2.4/5G channels
to assist with broadcasting and 6E has only 1 active method of in-band
discovery - PSC. This made discovery tricky.
- Needed to update driver of AX210 to even discover commercial AXE75,
so also client required work.
- Then I compiled hostapd with FILS support but it is off by default.
You need to specify max_interval to turn it on which assists PSC with
passive discovery. fils_discovery_min_interval=20,
fils_discovery_max_interval=100. Yes, I understand we discourage use
of the 6E band for probing but if this is the only band it should be
on by default.
- op_class= it looks like you can set anything between 131-136, it has
meaning only to enable 6E but it does not preset channel/center
frequency or anything based on the channel number/PSC or not. I set
op_class=134 channel=5, he_oper_centr_freq_seg0_idx=15 (for 160Mhz)
and he_oper_chwidth=2 (chwidth can be anything, it is ignored). With
other 3 parameters set kernel is not reporting errors and AP is
functioning. Don't use ASC if you have a single band module due
in-band discovery issues.
- good thing it is working well in bridge mode incl. dhcp broadcasts
- in case anyone wonders, AP operates in US reg domain since firmware
still does not have proper lower 6E band support for EU, it disables
6E with iw reg set BE/DE or any non US country. Client is using LAR
and setting itself to BE. If you don't need DFS (not needed in 6E)
etc. country_code, ieee80211d don't need to be set. If you set it to
anything else than US you fail at start -> firmware does not have reg
domain for 6E in any other region than US. That consumed some time to
discover, understand and compilation of various kernel options for
self-managed setting.
So to conclude on this topic here likely most of the manufacturers of
these modules in China don't have tools/licenses for QCA
tools/software hence modules come not fused. Ask before you buy to
confirm. Likely mostly these are only PCB/assembly shops. I gave up
trying since support discussions were going nowhere. Secondly there's
been changes to 6E so some information out in the internet is not
accurate and greatly confusing between multi-band & single-band
scenarios. Most assume you work in a multi-band environment. Thirdly,
very early software/firmware with quite dynamic regulatory footprint -
expect differences to reality.
In any case working hostapd.conf for single band 6E which is now
discover-able in a reasonable time (20-30 seconds from AP start).
grep "^[^#]" hostapd.conf
interface=wlp1s0
bridge=br0
logger_syslog=-1
logger_syslog_level=0
logger_stdout=0
logger_stdout_level=0
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
ssid=XXXXXXX
hw_mode=a
channel=5
op_class=134
preamble=0
macaddr_acl=0
auth_algs=3
ignore_broadcast_ssid=0
ap_isolate=1
broadcast_deauth=0
ieee80211ax=1
he_oper_centr_freq_seg0_idx=15
he_6ghz_reg_pwr_type=0
eapol_key_index_workaround=0
eap_server=0
own_ip_addr=127.0.0.1
wpa=2
wpa_passphrase=XXXXXXXXX
wpa_psk_radius=0
wpa_key_mgmt=SAE
rsn_pairwise=CCMP
group_cipher=CCMP
wpa_group_rekey=1800
rsn_preauth=1
ieee80211w=2
group_mgmt_cipher=AES-128-CMAC
assoc_sa_query_max_timeout=10000
sae_pwe=2
fils_hlp_wait_time=30
fils_discovery_min_interval=20
fils_discovery_max_interval=100
proxy_arp=1
stationary_ap=1
On Sun, 20 Nov 2022 at 09:13, Mariusz <enebeo@gmail.com> wrote:
>
> I also got my hands on AXE75 which is a 6E router and I am able to get
> QCN9074 work in STA mode.
>
> With 160Mhz it did not work but it may be anything. However with 80Mhz
> I am able to get a successful connection fully authenticated with
> WPA3. So radio wise it operates in 6Ghz band after driver patch with
> board_id=0xa2. Now I'm trying to understand why it still does not work
> in AP mode.
>
> root@s4:/home/angel# wpa_cli status
> Selected interface 'wlp6s0'
> bssid=1c:61:b4:c8:93:f4
> freq=6115
> ssid=test
> id=0
> mode=station
> wifi_generation=6
> pairwise_cipher=CCMP
> group_cipher=CCMP
> key_mgmt=SAE
> pmf=2
> mgmt_group_cipher=BIP
> wpa_state=COMPLETED
> ip_address=192.168.6.123
> address=c4:4b:d1:d0:00:7e
> uuid=07aaca38-a259-53ef-b12b-bb4cf5dad8d8
>
> On Sat, 19 Nov 2022 at 16:16, Robert Marko <robert.marko@sartura.hr> wrote:
> >
> > On Sat, Nov 19, 2022 at 2:40 PM Mariusz <enebeo@gmail.com> wrote:
> > >
> > > I have contacted Wallys again but I am skeptical about resolution.
> > > They don't consider board_id an issue and provided the same response,
> > > on integrated systems it is due the bootloader to set it properly so
> > > it is not fused and obviously not included in x86 scenario.
> >
> > Hi, this is not really the case, how would the bootloader set the board_id
> > which is supposed to be fused on the device so FW would report the correct one?
> > You can only workaround that by hardcoding it in the driver or on non-x86
> > in DTS and force-loading the correct BDF that way.
> >
> > > Since this
> > > is a private project I doubt QCA will support my efforts and free
> > > access to their portals gives nothing. Found online some SDK for
> > > version ath10k/IPQ8074 and athtestcmd to deal with OTP/fusing but
> > > that's far beyond home project effort.
> > >
> > > Tried also to compile it in OpenWRT with moderate success. ath11ko /
> > > qrtr.ko modules are built but the module never goes past power on
> > > success.
> > > mhi mhi0: Requested to power ON
> > > mhi mhi0: Power on setup success
> > > mhi mhi0: Wait for device to enter SBL or Mission mode
> > >
> > > Even the newest kernel in OpenWRT master development branch 5.16 is
> > > quite behind and backporting anything is another non-trivial task.
> >
> > ath11k won't work in OpenWrt master currently, I have been supporting IPQ807x
> > and recently PCI version as well out-of-tree with hopes of getting it soon into
> > OpenWrt once 6.1 backports become available as that gets rid of like 300-ish
> > backported patches.
> >
> > Regards,
> > Robert
> > >
> > > On Fri, 18 Nov 2022 at 15:06, Sven Eckelmann <sven@narfation.org> wrote:
> > > >
> > > > On Friday, 18 November 2022 13:48:43 CET Mariusz wrote:
> > > > > Mine is from a different supplier - Wallys - and I bought it 2 weeks
> > > > > ago but not sure how old their stock is. PCB looks slightly different
> > > > > than Pinapple's. Is it likely to have the same issue?
> > > >
> > > > It definitely has the same issue (because you reported that board_id is
> > > > 255/0xff) but I have no idea whether Wallytech ever fixed it. At least I was
> > > > never in contact about this problem with them. But sending around precompiled
> > > > kernel module binaries (for an unknown kernel build), with some hacks to fix
> > > > their hardware production errors (missing module id fusing in the OTP for
> > > > their separately sold modules), doesn't make me confident that they are able
> > > > to solve this problem correctly.
> > > >
> > > > In their defense, QCA doesn't make it really easy. It seems like their
> > > > reference designs with Pine on 6Ghz are (mostly?) for (embedded Linux) APs
> > > > which use the normal flash (NOR or NAND) to store the calibration data. And
> > > > for these devices, they use the devicetree (or various other hacks) to load
> > > > the correct board data.
> > > >
> > > > Wallystech has to find the correct document on createpoint which describes the
> > > > process. It was something like "module" "board id" "fusing". But it is not the
> > > > "Board ID Fusing for 802.11ax WLAN AP Chipsets" which only describes the way
> > > > how you would to it for thei internal wifi of the IPQ807x/IPQ60xx/... SoC.
> > > > You/they are searching for the corresponding document for Pine IPQ9074. Most
> > > > likely hidden in some QDART documents.
> > > >
> > > >
> > > > Regarding the problem that some countries are not allowing 6GHz: You have to
> > > > either get a firmware from QCA which has it enabled or you modify the BDFs
> > > > ("board-" files in the board-2.bin) to enable 6GHz in the (enabled) embedded
> > > > REGDB of the BDFs for the specific country. Unfortunately, the data structures
> > > > of the BDF are not officially documented and you would need an official QSDK/
> > > > ATH.11.X release from QCA to fetch the bdf2txt.py, txt2bdf.py and the
> > > > corresponding template for your BDF to extract and modify it.
> > > >
> > > > Kind regards,
> > > > Sven
> > >
> > > --
> > > ath11k mailing list
> > > ath11k@lists.infradead.org
> > > http://lists.infradead.org/mailman/listinfo/ath11k
> >
> >
> >
> > --
> > Robert Marko
> > Staff Embedded Linux Engineer
> > Sartura Ltd.
> > Lendavska ulica 16a
> > 10000 Zagreb, Croatia
> > Email: robert.marko@sartura.hr
> > Web: www.sartura.hr
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
2022-11-18 14:05 ` Sven Eckelmann
2022-11-19 13:39 ` Mariusz
@ 2022-12-06 8:56 ` Sven Eckelmann
1 sibling, 0 replies; 18+ messages in thread
From: Sven Eckelmann @ 2022-12-06 8:56 UTC (permalink / raw)
To: Mariusz; +Cc: walde, ath11k
[-- Attachment #1.1: Type: text/plain, Size: 1688 bytes --]
On Friday, 18 November 2022 15:05:49 CET Sven Eckelmann wrote:
> Wallystech has to find the correct document on createpoint which describes the
> process. It was something like "module" "board id" "fusing". But it is not the
> "Board ID Fusing for 802.11ax WLAN AP Chipsets" which only describes the way
> how you would to it for thei internal wifi of the IPQ807x/IPQ60xx/... SoC.
> You/they are searching for the corresponding document for Pine IPQ9074. Most
> likely hidden in some QDART documents.
It seems like this can be found easier via the search terms "Steps to fuse
board ID in OTP for QCN9074". For example in document "80-YC644-3 Rev. A" on
page 62. Qualcomm wrote there that this is needed for cards but can be skipped
for internal radio - must likely referring there to the possibility to
overwrite the board_id via devicetree (or using other hacks like providing
only the specific board.bin instead of the board-2.bin).
I cannot say much about the document but is basically telling them to use
QDART and enable the option to write a specific "bdf version" (yes, Qualcomm
has many names for the same things).
There is also another documents which describe similar methods for various
chips. For example "Fusing board ID to OTP in QCN61xx" in 80-19559-1 Rev. AA
on page 76. Here they have a lot less steps - only the ones which set the
"bdf version".
At the end, these are documents which are only released under NDA and which
need tools which you also can only get under NDA. So the manufacturer of these
devices has to take care to write the board_id (or "bdf version") to the OTP
before shipping them out to customers or resellers.
Kind regards,
Sven
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 102 bytes --]
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
2022-11-05 11:23 Mariusz
@ 2022-12-17 10:31 ` Sven Eckelmann
0 siblings, 0 replies; 18+ messages in thread
From: Sven Eckelmann @ 2022-12-17 10:31 UTC (permalink / raw)
To: ath11k
[-- Attachment #1.1: Type: text/plain, Size: 1899 bytes --]
On Saturday, 5 November 2022 12:23:02 CET Mariusz wrote:
> My issue is that I cannot get it working on 6GHz bands but it works
> fine on 5GHz. I bought 6E version and since this is a single band
> module it cannot be both 5G & 6G and linux driver does not agree with
> it being 6E version:
>
> [71914.038562] ath11k_pci 0000:03:00.0: BAR 0: assigned [mem
> 0xdf800000-0xdf9fffff 64bit]
> [71914.038840] ath11k_pci 0000:03:00.0: MSI vectors: 16
> [71914.038852] ath11k_pci 0000:03:00.0: qcn9074 hw1.0
> [71914.194459] mhi mhi0: Requested to power ON
> [71914.194712] mhi mhi0: Power on setup success
> [71914.297749] mhi mhi0: Wait for device to enter SBL or Mission mode
> [71914.647118] ath11k_pci 0000:03:00.0: chip_id 0x0 chip_family 0x0
> board_id 0xff soc_id 0xffffffff
> [71914.647134] ath11k_pci 0000:03:00.0: fw_version 0x250a04b8
> fw_build_timestamp 2021-12-20 06:41 fw_build_id
> [71916.310787] ath11k_pci 0000:03:00.0 wlp3s0: renamed from wlan0
Just to have this documented publicly: I was in contact with the Wallys
support and used this opportunity to point out this problem. I've provided
references to interesting QCA documents and they were able to fix the problem
on their end (via QDART).
The current status is:
* there will be most likely no tool by them to allow the customer to fix this
problem ("missing boards_id which is shown as 0xff") directly
* they will replace these cards. But they have to be send back to the
reseller. My understanding is, that the reseller must then also send back
his stock to get properly configured cards which can then be given to the
customers as replacements. But I am not involved in this process and can
therefore only guess the interactions between reseller and Wallys.
So it is basically the same process as with 8devices. And Mariusz is for
example already in contact with an EU based reseller.
Kind regards,
Sven
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 102 bytes --]
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
^ permalink raw reply [flat|nested] 18+ messages in thread
* Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band
@ 2022-11-05 11:23 Mariusz
2022-12-17 10:31 ` Sven Eckelmann
0 siblings, 1 reply; 18+ messages in thread
From: Mariusz @ 2022-11-05 11:23 UTC (permalink / raw)
To: ath11k
Hi,
As support for QCN9074 got better I went ahead and built a 6E linux
based AP. Dell R720 server x86 running Linux s4 5.19.0-23-generic
#24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64
x86_64 x86_64 GNU/Linux.
My issue is that I cannot get it working on 6GHz bands but it works
fine on 5GHz. I bought 6E version and since this is a single band
module it cannot be both 5G & 6G and linux driver does not agree with
it being 6E version:
[71914.038562] ath11k_pci 0000:03:00.0: BAR 0: assigned [mem
0xdf800000-0xdf9fffff 64bit]
[71914.038840] ath11k_pci 0000:03:00.0: MSI vectors: 16
[71914.038852] ath11k_pci 0000:03:00.0: qcn9074 hw1.0
[71914.194459] mhi mhi0: Requested to power ON
[71914.194712] mhi mhi0: Power on setup success
[71914.297749] mhi mhi0: Wait for device to enter SBL or Mission mode
[71914.647118] ath11k_pci 0000:03:00.0: chip_id 0x0 chip_family 0x0
board_id 0xff soc_id 0xffffffff
[71914.647134] ath11k_pci 0000:03:00.0: fw_version 0x250a04b8
fw_build_timestamp 2021-12-20 06:41 fw_build_id
[71916.310787] ath11k_pci 0000:03:00.0 wlp3s0: renamed from wlan0
HE PHY Capabilities: (0x1c604c88ffdb839c110c00):
HE40/HE80/5GHz
HE160/5GHz
HE160/HE80+80/5GHz
iw dev wlp3s0 set freq 6195 160MHz
kernel reports: Channel is disabled
command failed: Invalid argument (-22)
I am using the latest firmware files from ath11k tree. Is there any
special firmware to force this to 6GHz? I read somewhere board_id
determines which one it is and 255 disables 6GHz but I miss more data
on that.
phy#2 (self-managed)
country US: DFS-FCC
(2402 - 2472 @ 40), (6, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 30), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS, AUTO-BW
(5735 - 5895 @ 160), (N/A, 30), (N/A), AUTO-BW
(5945 - 7125 @ 160), (N/A, 30), (N/A), NO-OUTDOOR, AUTO-BW
It works fine in 5GHz but this is not what I purchased it for, so I am
puzzled if this is something in software or I was sold wrong
hardware.Is there a specific board-2.bin for 6GHz? Since the 9074 chip
is the same in all versions perhaps this is a software hiccup.
Any clues are welcome.
Regards,
Mario
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
^ permalink raw reply [flat|nested] 18+ messages in thread
end of thread, other threads:[~2022-12-17 10:31 UTC | newest]
Thread overview: 18+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <mailman.7.1667674802.1691884.ath11k@lists.infradead.org>
2022-11-07 16:07 ` Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band Nagarajan Maran (QUIC)
2022-11-07 18:57 ` Mariusz
2022-11-08 21:03 ` Mariusz
[not found] ` <CAJrE-q73Jt8MfGn4bbyPs_VEb5DcjLMb7BWBp5MjMDjhZ2g5Wg@mail.gmail.com>
[not found] ` <MW2PR02MB38992059ED67678172D6604DED059@MW2PR02MB3899.namprd02.prod.outlook.com>
2022-11-15 10:02 ` Mariusz
2022-11-15 18:29 ` walde
2022-11-15 19:18 ` Mariusz
2022-11-18 11:26 ` Sven Eckelmann
2022-11-18 12:48 ` Mariusz
2022-11-18 14:05 ` Sven Eckelmann
2022-11-19 13:39 ` Mariusz
2022-11-19 15:16 ` Robert Marko
2022-11-19 16:09 ` Mariusz
2022-11-20 8:13 ` Mariusz
2022-11-22 15:14 ` Mariusz
2022-12-06 8:56 ` Sven Eckelmann
2022-11-17 16:51 ` Mariusz
2022-11-05 11:23 Mariusz
2022-12-17 10:31 ` Sven Eckelmann
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.