Intel AX210 WiFi doesn't initialize in OS 12.2 about operating-system HOT 10 CLOSED

Any updates on this? When can I upgrade the OS again? I now have multiple updates needed. I really hate running in this mode. The one circled is the one which broke WiFi and BT when I installed it.

from operating-system.

I pulled another DMESG after dropping the OS back to 12.1 - attached here:

DMESG_Output-16APR2024-dropped to OS 12.1.txt

from operating-system.

dmesg | grep wl
[ 0.000000] DMI: Hewlett-Packard HP t620 Quad Core TC/21B4, BIOS L40 v02.19 02/19/2019
[ 2.898961] iwlwifi 0000:01:00.0: enabling device (0100 -> 0102)
[ 2.917889] iwlwifi 0000:01:00.0: Detected crf-id 0x400410, cnv-id 0x400410 wfpm id 0x80000000
[ 2.927619] iwlwifi 0000:01:00.0: PCI dev 2725/0024, rev=0x420, rfid=0x10d000
[ 2.955435] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-83.ucode failed with error -2
[ 2.958049] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-82.ucode failed with error -2
[ 2.960570] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-81.ucode failed with error -2
[ 2.963135] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-80.ucode failed with error -2
[ 2.965748] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-79.ucode failed with error -2
[ 2.968411] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-78.ucode failed with error -2
[ 2.971197] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-77.ucode failed with error -2
[ 2.974008] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-76.ucode failed with error -2
[ 2.976781] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-75.ucode failed with error -2
[ 2.979765] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-74.ucode failed with error -2
[ 2.982686] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-73.ucode failed with error -2
[ 3.005451] iwlwifi 0000:01:00.0: api flags index 2 larger than supported by driver
[ 3.009646] iwlwifi 0000:01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.36
[ 3.012689] iwlwifi 0000:01:00.0: loaded firmware version 72.a764baac.0 ty-a0-gf-a0-72.ucode op_mode iwlmvm
[ 3.222975] iwlwifi 0000:01:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
[ 3.455490] iwlwifi 0000:01:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x1f
[ 3.457157] iwlwifi 0000:01:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[ 3.457172] iwlwifi 0000:01:00.0: WFPM_AUTH_KEY_0: 0x80
[ 3.457185] iwlwifi 0000:01:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
[ 3.459796] iwlwifi 0000:01:00.0: loaded PNVM version e28bb9d7
[ 3.476901] iwlwifi 0000:01:00.0: Detected RF GF, rfid=0x10d000
[ 3.545477] iwlwifi 0000:01:00.0: base HW address: 60:e3:2b:fb:b1:b6
[ 3.587551] iwlwifi 0000:01:00.0 wlp1s0: renamed from wlan0
[ 7.621116] iwlwifi 0000:01:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x1f
[ 7.621157] iwlwifi 0000:01:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[ 7.621175] iwlwifi 0000:01:00.0: WFPM_AUTH_KEY_0: 0x80
[ 7.621194] iwlwifi 0000:01:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
[ 7.709127] iwlwifi 0000:01:00.0: Registered PHC clock: iwlwifi-PTP, with index: 0
[ 10.881043] wlp1s0: authenticate with 78:d2:94:36:3d:f0
[ 10.884240] wlp1s0: send auth to 78:d2:94:36:3d:f0 (try 1/3)
[ 10.915902] wlp1s0: authenticated
[ 10.916626] wlp1s0: associate with 78:d2:94:36:3d:f0 (try 1/3)
[ 10.967679] wlp1s0: RX AssocResp from 78:d2:94:36:3d:f0 (capab=0x1511 status=0 aid=7)
[ 10.970910] wlp1s0: associated
[ 20.021077] wlp1s0: deauthenticating from 78:d2:94:36:3d:f0 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 27.055381] wlp1s0: authenticate with 78:d2:94:36:3d:f0
[ 27.060653] wlp1s0: send auth to 78:d2:94:36:3d:f0 (try 1/3)
[ 27.093019] wlp1s0: authenticated
[ 27.094927] wlp1s0: associate with 78:d2:94:36:3d:f0 (try 1/3)
[ 27.142556] wlp1s0: RX AssocResp from 78:d2:94:36:3d:f0 (capab=0x1511 status=0 aid=7)
[ 27.146232] wlp1s0: associated

from operating-system.

This seems to be either a driver kernel regression or AX210 doesn't like the new firmware. I think I have this card somewhere, I will check if I can reproduce.

from operating-system.

boot-broken.log
boot-working.log

Having a related issue, in that bluetooth on my AX201 card also fails some of the bluetooth boot log output:

Apr 18 08:15:32 homeassistant kernel: Bluetooth: Core ver 2.22
Apr 18 08:15:32 homeassistant kernel: NET: Registered PF_BLUETOOTH protocol family
Apr 18 08:15:32 homeassistant kernel: Bluetooth: HCI device and connection manager initialized
Apr 18 08:15:32 homeassistant kernel: Bluetooth: HCI socket layer initialized
Apr 18 08:15:32 homeassistant kernel: Bluetooth: L2CAP socket layer initialized
Apr 18 08:15:32 homeassistant kernel: Bluetooth: SCO socket layer initialized
Apr 18 08:15:32 homeassistant kernel: usbcore: registered new interface driver btusb
Apr 18 08:15:32 homeassistant kernel: Bluetooth: hci0: Firmware timestamp 2023.42 buildtype 1 build 73111
Apr 18 08:15:32 homeassistant kernel: Bluetooth: hci0: Found device firmware: intel/ibt-0040-1050.sfi
Apr 18 08:15:32 homeassistant kernel: Bluetooth: hci0: Boot Address: 0x100800
Apr 18 08:15:32 homeassistant kernel: Bluetooth: hci0: Firmware Version: 60-48.23
Apr 18 08:15:32 homeassistant kernel: usb 2-1: USB disconnect, device number 2
Apr 18 08:15:32 homeassistant kernel: Bluetooth: hci0: FW download error recovery failed (-19)
Apr 18 08:15:32 homeassistant kernel: Bluetooth: hci0: sending frame failed (-19)
Apr 18 08:15:32 homeassistant kernel: Bluetooth: hci0: Reading supported features failed (-19)
Apr 18 08:15:32 homeassistant kernel: Bluetooth: hci0: Error reading debug features

Luckily I had old firmware backed up in /mnt/boot/firmware/intel that I've switched back to for the time being that option was discovered in a previous issue: home-assistant/core#98523

updated to add broken/working bluetooth boot output

from operating-system.

I hope they fix this in the 12.3 or 12.4 OS update - I hate seeing that Orange dot telling me I need to do an update.

from operating-system.

I'm using the same card and run into the same issues.

Intel(R) Wi-Fi 6 AX210

[ 1.691899] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-83.ucode failed with error -2
[ 1.691928] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-82.ucode failed with error -2
[ 1.691956] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-81.ucode failed with error -2
[ 1.691983] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-80.ucode failed with error -2
[ 1.692006] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-79.ucode failed with error -2
[ 1.692035] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-78.ucode failed with error -2
[ 1.698141] iwlwifi 0000:02:00.0: api flags index 2 larger than supported by driver

from operating-system.

I installed 12.3 today....my WiFi is GONE again.

from operating-system.

@dndlion

RE-installed OS 12.1 -- and it comes back

from operating-system.

There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

from operating-system.