Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 Apr 2025 21:03:31 +0000 (UTC)
From:      "Bjoern A. Zeeb" <bz@FreeBSD.org>
To:        Lars Tunkrans <drsnx60@gmail.com>
Cc:        freebsd-wireless@FreeBSD.org
Subject:   Re: iwlwifi speed test report
Message-ID:  <o0nr54n1-7494-4o73-4449-7q6o4q1n0p4r@SerrOFQ.bet>
In-Reply-To: <4ecc854e-3a50-4671-8081-4049ceea1559@gmail.com>
References:  <1741513893-14555-mlmmj-0fff379e@FreeBSD.org> <a9ef877f-6eac-420c-ad51-d3f6734d68f2@gmail.com> <53n10708-654p-50r8-8435-518298286104@SerrOFQ.bet> <717d5fc7-24a4-44f9-ac4b-9d5deaa27f4a@gmail.com> <17pn5075-r047-oorn-48q3-03qq11prpr89@SerrOFQ.bet> <c8deb609-3f17-4d88-9e12-55f8131bcf2c@gmail.com> <29810r9n-59r9-rq66-r0q8-q69o8r3r79oo@SerrOFQ.bet> <4ecc854e-3a50-4671-8081-4049ceea1559@gmail.com>

index | next in thread | previous in thread | raw e-mail

On Mon, 14 Apr 2025, Lars Tunkrans wrote:

>> What does:
>> sysctl compat.linuxkpi.80211.hw_crypto compat.linuxkpi.iwlwifi_11n_disable 
>> compat.linuxkpi.iwlwifi_disable_11ac
>> show for all three?
>
>> compat.linuxkpi.80211.hw_crypto: 0
>> compat.linuxkpi.iwlwifi_11n_disable: 0
>> compat.linuxkpi.iwlwifi_disable_11ac: 1

Okay, that explains and hw_crypto is indeed disabled (avoids the TKIP
problem) and my fallback caught this disabling AMPDU-RX.  Good.

Though I am still wondering why the AX201 does not freak out given it cannot
decrypt frames when doing HT.  Some hoemwork for me tonight to test on
AX200 or AX210 w/ and /wo VHT enabled.  I hope some others are reading
along as they may be curious to try this too.

Did you do change the hw_crypto and iwlwifi_disable_11ac value yourself
(in loader.conf.local) or did the firmware update not do the right thing?

For me it looks like:

cat /boot/loader.conf.d/iwlwifi-ax210.conf
compat.linuxkpi.80211.hw_crypto=1
compat.linuxkpi.iwlwifi_11n_disable=0
compat.linuxkpi.iwlwifi_disable_11ac=0

I am just asking in order to catch any possible general problems early.
If you've done it manually then that's all fine.

/bz


>> And once you are associated and have some traffic, what does
>> sysctl compat.linuxkpi.80211.wlan0
>> say?
>
>> # sysctl sysctl compat.linuxkpi.80211.wlan0
>> compat.linuxkpi.80211.wlan0.dump_stas:
>> lsta 0xfffff8005bb37000 sta 0xfffff8005bb371c0 added_to_drv 1
>> nl80211_sta_info (valid fields) 
>> 0x00004503<BEACON_RX,BEACON_SIGNAL_AVG,SIGNAL_AVG,RX_BITRATE,TX_BITRATE>
>> connected_time 0 inactive_time 0
>> rx_bytes 0 rx_packets 0 rx_dropped_misc 0
>> rx_duration 0 rx_beacon 76120 rx_beacon_signal_avg -34
>> tx_bytes 0 tx_packets 0 tx_failed 0
>> tx_duration 0 tx_retries 0
>> signal 0 signal_avg -24 ack_signal 0 avg_ack_signal 0
>> generation 0 assoc_req_ies_len 0 chains 0
>> rxrate: flags 5<MCS,SGI> bw 3(40) legacy 0 kbit/s mcs 15 nss 0
>>         he_dcm 0 he_gi 0 he_ru_alloc 0 eht_gi 0
>> txrate: flags 5<MCS,SGI> bw 3(40) legacy 0 kbit/s mcs 7 nss 1
>>         he_dcm 0 he_gi 0 he_ru_alloc 0 eht_gi 0

Great!


Lots of joy,
Bjoern

-- 
Bjoern A. Zeeb                                                     r15:7
home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?o0nr54n1-7494-4o73-4449-7q6o4q1n0p4r>