ax210 [8086:2725] subsystem [8086:0020] wifi adapter disappears with upgrade to linux-firmware 1.187.16 due to the presence of '/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm'

[Logan Symons]

$ lsb_release -rd
Description: Ubuntu 20.04.3 LTS

$ uname -r
5.11.0-27-generic

$ apt-cache policy linux-firmware
linux-firmware:
  Installed: 1.187.16

$ ip a
1: lo
2: enp0s31f6

Device:
Lenovo T14 Gen 2 w/ Intel AX210 WiFi [8086:2725]

WiFi adapter disappears from network manager and
> ip a
following update to
> linux-firmware 1.187.16
and a restart

Able to confirm this package is the problem as the issue can be reversed by downgrading to
> linux-firmware 1.187.15

Our organisation has had at least one other identical device experience the same issue before
> apt-mark hold linux-firmware
was pushed out.

Happy to supply any other information or logs on request.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-firmware 1.187.16
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: logansymons 7485 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 25 18:10:49 2021
Dependencies:

IwConfig:
 lo no wireless extensions.

 enp0s31f6 no wireless extensions.
Lsusb:
 Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 003 Device 002: ID 04f2:b6d0 Chicony Electronics Co., Ltd Integrated Camera
 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20W0005AAU
PackageArchitecture: all
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-27-generic root=/dev/mapper/my_vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-27-generic N/A
 linux-backports-modules-5.11.0-27-generic N/A
 linux-firmware 1.187.16
RfKill:
 0: tpacpi_bluetooth_sw: Bluetooth
  Soft blocked: yes
  Hard blocked: no
SourcePackage: linux-firmware
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/08/2021
dmi.bios.release: 1.41
dmi.bios.vendor: LENOVO
dmi.bios.version: N34ET41W (1.41 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20W0005AAU
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.8
dmi.modalias: dmi:bvnLENOVO:bvrN34ET41W(1.41):bd07/08/2021:br1.41:efr1.8:svnLENOVO:pn20W0005AAU:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0005AAU:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T14 Gen 2i
dmi.product.name: 20W0005AAU
dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
dmi.product.version: ThinkPad T14 Gen 2i
dmi.sys.vendor: LENOVO

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[You-Sheng Yang (vicamo)]

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 140
model name : 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
stepping : 1

09:00.0 Network controller [0280]: Intel Corporation Device [8086:2725] (rev 1a)
 Subsystem: Intel Corporation Device [8086:0020]

[ 14.331678] iwlwifi 0000:09:00.0: enabling device (0000 -> 0002)
[ 14.376763] iwlwifi 0000:09:00.0: api flags index 2 larger than supported by driver
[ 14.376783] iwlwifi 0000:09:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 93.8.63.28
[ 14.377057] iwlwifi 0000:09:00.0: loaded firmware version 59.601f3a66.0 ty-a0-gf-a0-59.ucode op_mode iwlmvm
[ 14.435158] iwlwifi 0000:09:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
[ 14.607931] iwlwifi 0000:09:00.0: loaded PNVM version 0x324cd670
[ 14.711389] iwlwifi 0000:09:00.0: Timeout waiting for PNVM load!
[ 14.711400] iwlwifi 0000:09:00.0: Failed to start RT ucode: -110
[ 14.711409] iwlwifi 0000:09:00.0: iwl_trans_send_cmd bad state = 1
[ 14.915356] iwlwifi 0000:09:00.0: firmware didn't ACK the reset - continue anyway
[ 14.927676] iwlwifi 0000:09:00.0: Failed to run INIT ucode: -110

[You-Sheng Yang (vicamo)]

* ddaffc5e iwlwifi: add new FWs from core60-51 release (for bug 1933415)
| WHENCE | 26 ++++++++++++++++++++++++++
| iwlwifi-Qu-b0-hr-b0-63.ucode | Bin 0 -> 1334856 bytes
| iwlwifi-Qu-b0-jf-b0-63.ucode | Bin 0 -> 1252748 bytes
| iwlwifi-Qu-c0-hr-b0-63.ucode | Bin 0 -> 1334872 bytes
| iwlwifi-Qu-c0-jf-b0-63.ucode | Bin 0 -> 1252764 bytes
| iwlwifi-QuZ-a0-hr-b0-63.ucode | Bin 0 -> 1334804 bytes
| iwlwifi-QuZ-a0-jf-b0-63.ucode | Bin 0 -> 1252744 bytes
| iwlwifi-cc-a0-63.ucode | Bin 0 -> 1298688 bytes
| iwlwifi-ty-a0-gf-a0-63.ucode | Bin 0 -> 1460012 bytes
| iwlwifi-ty-a0-gf-a0.pnvm | Bin 0 -> 27456 bytes
| 10 files changed, 26 insertions(+)

[Logan Symons (logansymons)]

Temporary workaround:

```
# This is an official source, despite the less common url
wget http://launchpadlibrarian.net/543359934/linux-firmware_1.187.15_all.deb

# Remove linux-firmware 1.187.16
sudo apt purge linux-firmware

# Install linux-firmware .deb
sudo dpkg -i linux-firmware_1.187.15_all.deb

# Hold linux-firmware package to stop updates replacing 1.187.15
sudo apt-mark hold linux-firmware

# Verify installed version
apt policy linux-firmware
```

Once a fixed version of linux-firmware is out the following will need to be run:

```
sudo apt-mark unhold linux-firmware
```

[Logan Symons (logansymons)]

I am also experiencing this, which may be related:

https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1940411

[You-Sheng Yang (vicamo)]

bug 1940411 is harmless. Marked WONTFIX there.

[You-Sheng Yang (vicamo)]

I can reproduce this with TGL platform, AX210 [8086:2725] subsystem [8086:0020], kernel linux-hwe-5.11 and linux-oem-5.10.

linux-oem-5.13 works for me, but somehow it claimed otherwise in bug 1943918.

[You-Sheng Yang (vicamo)]

This should have been addressed in v5.13-rc1 that bumped FW API to 63.

[You-Sheng Yang (vicamo)]

I think there is a defect in iwlwifi-ty-a0-gf-a0.pnvm that its existence would force older kernels to use FW API 63 or so. The current pnvm file cannot be loaded along with -59 firmware even with v5.15-rc2 kernel, and we'd need -63 fw for ADL platforms anyway.

[You-Sheng Yang (vicamo)]

Affected fw from bug 1933415:

* AX201
iwlwifi-Qu-b0-hr-b0-59.ucode
iwlwifi-Qu-b0-hr-b0-63.ucode

* 9560
iwlwifi-Qu-b0-jf-b0-59.ucode
iwlwifi-Qu-b0-jf-b0-63.ucode

* AX201
iwlwifi-Qu-c0-hr-b0-59.ucode
iwlwifi-Qu-c0-hr-b0-63.ucode

* 9560
iwlwifi-Qu-c0-jf-b0-59.ucode
iwlwifi-Qu-c0-jf-b0-63.ucode

* AX201
iwlwifi-QuZ-a0-hr-b0-59.ucode
iwlwifi-QuZ-a0-hr-b0-63.ucode

* 9560
iwlwifi-QuZ-a0-jf-b0-59.ucode
iwlwifi-QuZ-a0-jf-b0-63.ucode

* AX200
iwlwifi-cc-a0-59.ucode
iwlwifi-cc-a0-63.ucode

* AX210:
iwlwifi-ty-a0-gf-a0-59.ucode
iwlwifi-ty-a0-gf-a0-63.ucode

[You-Sheng Yang (vicamo)]

IWL_22000_UCODE_API_MAX:
* oem-5.14: 64
* oem-5.13: will be 64 in 1933938
* hwe-5.11: 59
* oem-5.10: 59

[Sanchu Varkey (mailsanchu)]

[ 4.135644] Intel(R) Wireless WiFi driver for Linux
[ 4.135902] iwlwifi 0000:92:00.0: enabling device (0000 -> 0002)
[ 4.175646] iwlwifi 0000:92:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-63.ucode failed with error -2
[ 4.175891] iwlwifi 0000:92:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-62.ucode failed with error -2
[ 4.176355] iwlwifi 0000:92:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-61.ucode failed with error -2
[ 4.176613] iwlwifi 0000:92:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-60.ucode failed with error -2
[ 4.178816] iwlwifi 0000:92:00.0: api flags index 2 larger than supported by driver
[ 4.178838] iwlwifi 0000:92:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 93.8.63.28
[ 4.179219] iwlwifi 0000:92:00.0: loaded firmware version 59.601f3a66.0 ty-a0-gf-a0-59.ucode op_mode iwlmvm
[ 4.311312] iwlwifi 0000:92:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
[ 4.552309] iwlwifi 0000:92:00.0: base HW address: 28:df:eb:91:91:23
[ 4.636878] iwlwifi 0000:92:00.0 wlp146s0: renamed from wlan0

[Sanchu Varkey (mailsanchu)]

I see the above in the logs after applying the temp fix

[Juerg Haefliger (juergh)]

Is this still an issue?

[Logan Symons (logansymons)]

A subsequent update has resolved this issue, roughly corresponding with the release of the 5.13 kernel if I remember correctly.