Re: iwlwifi AX201 can no longer connect

On Sat, 13 Jul 2024, Joel Bodenmann wrote:

Hi,

> I have an Intel AX201 card in a Lenovo Carbon X1 Gen 9 which used to
> work reasonably well. After a few months I just updated to the latest
> stable/14 branch and I am no longer able to connect to my home WiFi
> network (WPA2).
>
> I keep seeing these messages:
>
> iwlwifi0: Not associated and the session protection is over already...
> iwlwifi0: linuxkpi_ieee80211_connection_loss: vif 0xfffffe0163888e80
> vap 0xfffffe0163888010 state AUTH
>
>
> Relevant dmesg:
>
> iwlwifi0: <iwlwifi> mem 0x603d1cc000-0x603d1cffff at device 20.3 on pci0
> iwlwifi0: Detected crf-id 0x3617, cnv-id 0x20000302 wfpm id 0x80000000
> iwlwifi0: PCI dev a0f0/0070, rev=0x351, rfid=0x10a100
> iwlwifi0: successfully loaded firmware image
> 'iwlwifi-QuZ-a0-hr-b0-77.ucode' iwlwifi0: api flags index 2 larger than
> supported by driver iwlwifi0: TLV_FW_FSEQ_VERSION: FSEQ Version:
> 89.3.35.37 iwlwifi0: loaded firmware version 77.2df8986f.0
> QuZ-a0-hr-b0-77.ucode op_mode iwlmvm iwlwifi0: Detected Intel(R) Wi-Fi
> 6 AX201 160MHz, REV=0x351 iwlwifi0: Detected RF HR B3, rfid=0x10a100
> iwlwifi0: base HW address: <REDACTED>
> wlan0: Ethernet address: <REDACTED>
> iwlwifi0: Not associated and the session protection is over already...
> iwlwifi0: linuxkpi_ieee80211_connection_loss: vif 0xfffffe0163888e80
> vap 0xfffffe0163888010 state AUTH Security policy loaded: MAC/ntpd
> (mac_ntpd) iwlwifi0: Not associated and the session protection is over
> already... iwlwifi0: linuxkpi_ieee80211_connection_loss: vif
> 0xfffffe0163888e80 vap 0xfffffe0163888010 state AUTH iwlwifi0: Not
> associated and the session protection is over already... iwlwifi0:
> linuxkpi_ieee80211_connection_loss: vif 0xfffffe0163888e80 vap
> 0xfffffe0163888010 state AUTH wlan0: link state changed to UP wlan0:
> link state changed to DOWN iwlwifi0: Not associated and the session
> protection is over already... iwlwifi0:
> linuxkpi_ieee80211_connection_loss: vif 0xfffffe0163888e80 vap
> 0xfffffe0163888010 state AUTH
>
>
> Any ideas?

It could not reliably associate.
It did manage to get the interface UP but lost the connection again.


> Any other info I can provide that would be deemed useful?

Has that state stayed or did it go away by itself?

If it is still reproducible how are scan results?
Is your environment/channel/neighbourhood noisy?
What if you move closer/further away from the AP?

/bz

-- 
Bjoern A. Zeeb                                                     r15:7