Unclaimed Network Controller

halaquin2 · 2024-08-18 10:43:05

Sadly, my system is never able to connect to the wifi. Running `nmcli device wifi list` returns no such networks.

Upon inspection of `sudo lshw -C network` I obtain:

```*-network UNCLAIMED
description: Network controller
product: Comet Lake PCH CNVi WiFi
vendor: Intel Corporation
physical id: 14.3
bus info: pci@0000:00:14.3
version: 00
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix cap_list
configuration: latency=0
resources: iomemory:600-5ff memory:606311c000-606311ffff

```
And running `sudo dmesg | grep iwl` yields:
```
[ 3.203163] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[ 3.205257] iwlwifi 0000:00:14.3: Detected crf-id 0x3617, cnv-id 0x20000302 wfpm id 0x0
[ 3.205279] iwlwifi 0000:00:14.3: Can't find a correct rfid for crf id 0x617
[ 3.205296] iwlwifi 0000:00:14.3: probe with driver iwlwifi failed with error -22
```

Which is unfortunate. I believe the device is an AX201. I have installed `linux-firmware`. Kernel version is `6.10.5-arch1-1`

seth · 2024-08-18 15:52:56

Please don't grep, post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

In case there's a parallel windows installation, see the 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

halaquin2 · 2024-08-18 15:56:27

Ok thanks. I have run that command.

seth · 2024-08-18 15:59:30

And do you intend to share the URL you got in return?

halaquin2 · 2024-08-18 16:01:56

Opps, sorry my mistake.

Here it is.

https://0x0.st/AFgH.txt

Last edited by halaquin2 (2024-10-02 00:40:59)

seth · 2024-08-18 17:37:54

lspci -nn -s 00:14.3 -v

Same HW seems to show up in https://discussion.fedoraproject.org/t/ … -39/101508 and isn't a AX201 chip
(unresolved, you're not loading the broadcom module)
It didn't seem to be an issue in this case: https://bbs.archlinux.org/viewtopic.php?id=278702 but unfortunately there's no journal in that thread to be compared.

Wild guess: what if you add iwlwifi to the initramfs (MODULES array in mkinitcpio)?

Aug 18 16:50:50 machine kernel: ACPI BIOS Error (bug): Could not resolve symbol [^^PCI0.RP01.PEGP.GPFG], AE_NOT_FOUND (20240322/psargs-330)
Aug 18 16:50:50 machine kernel: ACPI Error: Aborting method \_SB.WMID.STPS due to previous error (AE_NOT_FOUND) (20240322/psparse-529)
Aug 18 16:50:50 machine kernel: ACPI Error: Aborting method \HWMC due to previous error (AE_NOT_FOUND) (20240322/psparse-529)
Aug 18 16:50:50 machine kernel: ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_NOT_FOUND) (20240322/psparse-529)

looks like it could be related to the ACPI bugs.

You could also try to lie:

acpi_osi=! acpi_osi="Windows 2022"

https://learn.microsoft.com/en-us/windo … inacpi-osi

Sidebar: disable the dhcpcd service, NM runs it internal dhcp client.

halaquin2 · 2024-09-26 23:10:31

Thanks for the advice. I tested both options and unfortunately these things did not help

Last edited by halaquin2 (2024-09-26 23:11:00)

seth · 2024-09-27 07:39:10

The idea behind

lspci -nn -s 00:14.3 -v

was to share that output (it doesn't do anything but inspect the pci device)

Aug 18 16:50:50 machine kernel: DMI: HP HP Spectre x360 Convertible 15-eb0xxx/86E7, BIOS F.17 04/12/2023

Is there maybe meanwhile a newer BIOS version availbale?

There's https://forum.manjaro.org/t/manjaro-det … n-a/135654 but while a similar problem, it addresses a different generation
The patch there won't work for sure, from what I can tell you've some "Qu" chip.
You could try whether https://aur.archlinux.org/packages/iwlwifi-next builds and fixes this.

Also, sanity check: you're not dual-booting windows, also in a way where you're swapping disks or something like that?

halaquin2 · 2024-09-27 07:58:37

My mistake, and thanks for the continued support.

```
sudo lspci -nn -s 00:14.3 -v
00:14.3 Network controller [0280]: Intel Corporation Comet Lake PCH CNVi WiFi [8086:06f0]
Subsystem: Intel Corporation Comet Lake PCH CNVi WiFi [8086:0000]
Flags: fast devsel, IRQ 16, IOMMU group 7
Memory at 606311c000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [80] MSI-X: Enable- Count=16 Masked-
Capabilities: [100] Latency Tolerance Reporting
Capabilities: [164] Vendor Specific Information: ID=0010 Rev=0 Len=014 <?>
Kernel modules: iwlwifi
```

> Is there maybe meanwhile a newer BIOS version availbale?
I have not checked, and am unsure how I'd go about updating it. I'll have a google and figure it out.

>Also, sanity check: you're not dual-booting windows, also in a way where you're swapping disks or something like that?
I initially dual booted with windows 10 and arch such that I could disable fast boot on the windows end (had no effect on wifi functionality on arch end). I then deleted all partitions and installed arch such that its the only installed OS. Still no joy.

Last edited by halaquin2 (2024-09-27 07:59:46)

rnp · 2024-09-27 19:12:22

I have the same problem on the same Wifi hardware on my Laptop, using the latest linux (6.10.10-arch1-1) and linux-firmware (20240909.552ed9b8-1). I have only Arch Linux installed on a TUXEDO InfinityBook Pro Gen8 (MK1) Laptop.

rnp · 2024-09-30 19:24:03

I managed to make the wifi device work again, by disabling the "Fast Boot" in the UEFI.
What I could not explain, is why it worked since I bought the Laptop, and only recently it started to cause problems.

seth · 2024-09-30 19:41:12

I managed to make the wifi device work again, by disabling the "Fast Boot" in the UEFI.

Windows fast-start would make sense, UEFI fast boot (self tests) are either
1. co·in·ci·dence
2. because the NIC takes too long to power up

You could test (2) by disabling fat-start and just have the system hang out on the bootloader while you're getting yourself a cup of coffee

rnp · 2024-09-30 19:54:52

I tried (2) previously as well, with a halt time of 2 Minutes for a cold-/warm boot, and in both cases it did not work. The (1) is for sure not excluded.

halaquin2 · 2024-10-02 03:28:57

Ok, not a solution but if I cold boot into Linux, then go `sudo reboot` into linux again, and then run:

```
sudo modprobe -r btusb
sudo modprobe -n -v btusb
sudo rmmod btusb
sudo modprobe btusb
```

I can get bluetooth to work normally (it wasn't previously). However, wifi is still broke.

seth · 2024-10-02 07:58:45

rnp wrote:

I managed to make the wifi device work again, by disabling the "Fast Boot" in the UEFI.

Did you try?

halaquin2 · 2024-10-02 08:12:24

I restarted, entered the HP Bios setup screen (via Escape, then F10 on my system) but there is no option for "Fast Boot" anywhere in the configuration. There is one for secure boot and an option to adjust the post delay (currently it's 0 seconds), but I don't think that's it.

seth · 2024-10-02 08:31:16

I don't really understand how the BIOS self-test induced delay helps in rnp's case (while a delay in the bootloader doesn't - general boot delay makes sense) but if it does anything, I'd test to increase the post delay.

halaquin2 · 2024-10-02 09:38:06

Thanks, setting the post delay from 0s to 5s in the HP BIOS Configuration now means bluetooth works normally from a cold boot (no need for restart trick then modprobe described above).

However, wifi is still not working sadly, complaining it ` Can't find a correct rfid for crf id 0x617`
```
[ 2.433155] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[ 2.435305] iwlwifi 0000:00:14.3: Detected crf-id 0x3617, cnv-id 0x20000302 wfpm id 0x0
[ 2.435349] iwlwifi 0000:00:14.3: Can't find a correct rfid for crf id 0x617
[ 2.435361] iwlwifi: probe of 0000:00:14.3 failed with error -22
```

Last edited by halaquin2 (2024-10-02 09:38:38)

seth · 2024-10-02 13:34:18

What if you raise it more?
rnp will have to comment on his situation, but those self tests can easily run for 20 seconds…

Try the maximum post delay you can pick and see whether that helps.
If yes, you can fiddle bisect the value down (max/2, then the center of the good bracket etcetc)

halaquin2 · 2024-10-02 20:12:18

I tried 20 seconds post, sadly wifi is still unclaimed and not working. Bluetooth is intermittent, sometimes, if I cold-boot it works fine. Othertimes, I need to do one restart and then it works fine.

seth · 2024-10-02 20:51:49

Does yur UEFI offer any power saving related settings?
Does it make a difference whether you're booting the system on battery or external power?

halaquin2 · 2024-10-03 00:24:30

These are the results of my testing:

| bluetooth works | wifi works
cold boot (battery) | no | no
cold boot (power) | yes | no
hot restart (battery) | yes | no
hot restart (power) | yes | no

All tests performed with 20s post delay, non-dual booted system. Cold boot means powered of laptop and unplugged from charger.

UEFI has power-related settings for controlling fan speeds, backlights etc. But nothing I'd think would relate to the ax201.

Last edited by halaquin2 (2024-10-03 00:25:48)

rnp · 2024-10-05 16:54:39

Have you tried to boot using a USB Stick, either using Arch Linux or another distro?

halaquin2 · 2024-10-06 01:02:02

No success yet, but I did try:

0. Tried 18.04, 20.04, 22.04, 24.04 Ubuntu versions, no luck. Wifi works perfectly if running Windows 10.

1. Adding a PCI ID, as described in [https://bugzilla.redhat.com/show_bug.cgi?id=1977295], to https://github.com/torvalds/linux/blob/ … rv.c#L1218:

First, I checked my vendor and device id:
```
lspci -nnk | grep 0280 -A2
00:14.3 Network controller [0280]: Intel Corporation Comet Lake PCH CNVi WiFi [8086:06f0]
Subsystem: Intel Corporation Comet Lake PCH CNVi WiFi [8086:0000]
Kernel modules: iwlwifi
```
So my vendor ID is `8086` and device id is `06f0`. I then added a new IWL_DEV_INFO corresponding to my specific device which was not already in `drv.c` to line 418:

`IWL_DEV_INFO(0x06F0, 0x8086, iwl_ax201_cfg_quz_hr, NULL),`

and then tried reinstalling the modified driver, but no success.

2. Digging deeper into [drivers/net/wireless/intel/iwlwifi/pcie/drv.c](https://github.com/torvalds/linux/blob/ … rv.c#L1218) shows a bunch of switch cases for the field `iwl_trans->hw_rf_id`. None of these cases (listed below) correspond to my reported crf id, which is `0x617`:

The crf id cases in drv.c [from here](https://github.com/torvalds/linux/blob/ … rph.h#L452)
```
#define REG_CRF_ID_TYPE_JF_1 0x201
#define REG_CRF_ID_TYPE_JF_2 0x202
#define REG_CRF_ID_TYPE_HR_CDB 0x503
#define REG_CRF_ID_TYPE_HR_NONE_CDB 0x504
#define REG_CRF_ID_TYPE_HR_NONE_CDB_1X1 0x501
#define REG_CRF_ID_TYPE_HR_NONE_CDB_CCP 0x532
#define REG_CRF_ID_TYPE_GF 0x410
#define REG_CRF_ID_TYPE_FM 0x910
#define REG_CRF_ID_TYPE_WHP 0xA10
```

I wonder why my crf id is wrong. Perhaps I'm missing some critical piece of firmware?

Last edited by halaquin2 (2024-10-06 01:13:07)

rnp · 2024-10-06 08:52:58

Have you tried:
- to see if there is a bug in the Linux Kernel Bugzilla? (https://bugzilla.kernel.org/)
- apperently yes....
- https://bugzilla.kernel.org/buglist.cgi … t=specific
- https://bugzilla.kernel.org/show_bug.cgi?id=208711
- to talk to the driver maintainer?

Arch Linux

#1 2024-08-18 10:43:05

Unclaimed Network Controller

#2 2024-08-18 15:52:56

Re: Unclaimed Network Controller

#3 2024-08-18 15:56:27

Re: Unclaimed Network Controller

#4 2024-08-18 15:59:30

Re: Unclaimed Network Controller

#5 2024-08-18 16:01:56

Re: Unclaimed Network Controller

#6 2024-08-18 17:37:54

Re: Unclaimed Network Controller

#7 2024-09-26 23:10:31

Re: Unclaimed Network Controller

#8 2024-09-27 07:39:10

Re: Unclaimed Network Controller

#9 2024-09-27 07:58:37

Re: Unclaimed Network Controller

#10 2024-09-27 19:12:22

Re: Unclaimed Network Controller

#11 2024-09-30 19:24:03

Re: Unclaimed Network Controller

#12 2024-09-30 19:41:12

Re: Unclaimed Network Controller

#13 2024-09-30 19:54:52

Re: Unclaimed Network Controller

#14 2024-10-02 03:28:57

Re: Unclaimed Network Controller

#15 2024-10-02 07:58:45

Re: Unclaimed Network Controller

#16 2024-10-02 08:12:24

Re: Unclaimed Network Controller

#17 2024-10-02 08:31:16

Re: Unclaimed Network Controller

#18 2024-10-02 09:38:06

Re: Unclaimed Network Controller

#19 2024-10-02 13:34:18

Re: Unclaimed Network Controller

#20 2024-10-02 20:12:18

Re: Unclaimed Network Controller

#21 2024-10-02 20:51:49

Re: Unclaimed Network Controller

#22 2024-10-03 00:24:30

Re: Unclaimed Network Controller

#23 2024-10-05 16:54:39

Re: Unclaimed Network Controller

#24 2024-10-06 01:02:02

Re: Unclaimed Network Controller

#25 2024-10-06 08:52:58

Re: Unclaimed Network Controller

Board footer