Intel AX201 detected as AX101

gmccone

New Member
Sep 27, 2024
1
0
1
System: Trigkey G5
Kernel: Linux 6.8.12-2-pve
Manager Version: pve-manager/8.2.7

Have a mini PC that contains an Intel AX201 Wifi/Bluetooth adapter.

Looking at the dmesg, can see that it has incorrectly detected the AX201 as a AX101 and the wifi fails to function.

Bash:
[    4.307829] Intel(R) Wireless WiFi driver for Linux
[    4.307864] AVX2 version of gcm_enc/dec engaged.
[    4.307930] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[    4.308420] AES CTR mode by8 optimization enabled
[    4.311453] iwlwifi 0000:00:14.3: Detected crf-id 0x501, cnv-id 0x80400 wfpm id 0x80000030
[    4.311496] iwlwifi 0000:00:14.3: PCI dev 54f0/0244, rev=0x370, rfid=0x10c000
[    4.325179] snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
[    4.357408] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.41
[    4.357830] iwlwifi 0000:00:14.3: loaded firmware version 86.fb5c9aeb.0 so-a0-hr-b0-86.ucode op_mode iwlmvm
[    4.853287] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX101, REV=0x370
[    4.853407] thermal thermal_zone1: failed to read out thermal zone (-61)
[    4.866360] iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
[    4.876665] intel_rapl_msr: PL4 support detected.
[    4.876776] intel_rapl_common: Found RAPL domain package
[    4.876780] intel_rapl_common: Found RAPL domain core
[    4.876783] intel_rapl_common: Found RAPL domain uncore
[    5.025360] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
[    5.025407] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[    5.025421] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[    5.025483] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
[    5.025554] iwlwifi 0000:00:14.3: Detected RF HR1 B3, rfid=0x10c000
[    5.025709] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4

Intel Wireless Support page says this adapter should have in-kernel support as of 5.2+.

A Linux Mint Forum shows a similar device having the same problem and was fixed by using the mainline kernel, but unfortunately didn't list what the version of that kernel was that fixed this.

Associated with this, the bluetooth side of the adapter also was failing as the firmware was being reported as missing. I was able to resolve at least that issue by copying the files ipt-0040-1050.ddc and ibt-0040-1050.sfi from the firmware git.tree to /lib/firmware/intel and then rebuild using
Bash:
update-initramfs -k all -u

After a reboot the bluetooth seems to be loaded correctly, but I haven't been able to test anything with it yet.

Code:
[    4.422742] usbcore: registered new interface driver btusb
[    4.424512] Bluetooth: hci0: Device revision is 2
[    4.424518] Bluetooth: hci0: Secure boot is enabled
[    4.424520] Bluetooth: hci0: OTP lock is enabled
[    4.424522] Bluetooth: hci0: API lock is enabled
[    4.424523] Bluetooth: hci0: Debug lock is disabled
[    4.424525] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    4.424527] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
[    4.424533] Bluetooth: hci0: No support for _PRR ACPI method
[    4.427034] Bluetooth: hci0: Found device firmware: intel/ibt-0040-1050.sfi
[    4.427050] Bluetooth: hci0: Boot Address: 0x100800
[    4.427053] Bluetooth: hci0: Firmware Version: 46-14.24
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!