Unclaimed Network Controller

seth · 2024-10-06 14:12:42

https://bugs.launchpad.net/ubuntu/+sour … ug/2031226 is the only match for the OPs

Subsystem: Intel Corporation Comet Lake PCH CNVi WiFi [8086:0000]

https://askubuntu.com/questions/1524546 … ss-network at least has "CNVi WiFi [8086:0000]"

Have you treid to reset the CMOS?

halaquin2 · 2024-10-07 01:28:10

Hello rnp and seth, thanks for your continued support.

@rnp, thanks for the highlighting those bug reports. I've read through id=208711 and am not sure it's the same issue, given the probe fails with a different error code (110 vs 22) and this business about `RIP: 0010:iwl_pci_probe+0x4da/0x540 [iwlwifi]`, which does not appear in my dmesg.

@seth, the bug report and askubuntu questions you identified were actually filed by myself about 1 year ago. Sorry, I should have provided links to those in my original question. I've provided further information on the bug report to hopefully clarify my situation.

I have not tried to reset the CMOS, but will give that a go.

rnp · 2024-11-20 10:44:59

The problem, once solved in my case, appeared again, even with the fast boot disabled. I tried to reset the CMOS and other distros as well and the problem still persists.
would the

by the way, my wifi adapter, a bit different than yours, a previous generation:

➜  ~ lshw -c network
  *-network UNCLAIMED       
       description: Network controller
       product: Raptor Lake PCH CNVi WiFi
       vendor: Intel Corporation
       physical id: 14.3
       bus info: pci@0000:00:14.3
       version: 01
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix cap_list
       configuration: latency=0
       resources: iomemory:600-5ff memory:601d174000-601d177fff

@seth: could it be related to the linux-firmware package? since the solution disabling fastboot there were new versions of this Package and Linux Kernel. and for linux-firmware, there were some iwlwifi*.ucode files changed around one month ago.

Last edited by rnp (2024-11-20 10:50:19)

seth · 2024-11-20 14:30:20

seth wrote:

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 disenabling fast-start and just have the system hang out on the bootloader while you're getting yourself a cup of coffee

Have we seen a journal from your system?
Does the firmware even get loaded? (I guess not?)

You could™ have trashed the NIC w/ a bogus firmware and that condition surviving a (warm) reboot. Surviving a cmos reset? Probably not.
W/ your previous UEFI fast-boot driven success, what if you add "rootdelay=30" to the kernel parameters to stall the boot for 30s?

rnp · 2024-11-20 18:08:19

If it was a coincidence, it survived many turn on/off cycles in the last weeks. I tried hot/cold boot with different kernel versions. I have to narrow down the right firmware file and check that.
That is what I get during the boot process:

❯ journalctl -b | ag -i iwlwifi
Nov 20 09:57:18 computer kernel: iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
Nov 20 09:57:18 computer kernel: iwlwifi 0000:00:14.3: Detected crf-id 0x1300504, cnv-id 0x80400 wfpm id 0x30
Nov 20 09:57:18 computer kernel: iwlwifi 0000:00:14.3: Adding cdb to rf id
Nov 20 09:57:18 computer kernel: iwlwifi 0000:00:14.3: Adding jacket to rf id
Nov 20 09:57:18 computer kernel: iwlwifi 0000:00:14.3: Detected rf-type 0x504 step-id 0x1 slave-id 0x0 from crf id 0x3010a100
Nov 20 09:57:18 computer kernel: iwlwifi 0000:00:14.3: Detected cdb-id 0x1 jacket-id 0x1 from wfpm id 0x30
Nov 20 09:57:18 computer kernel: iwlwifi 0000:00:14.3: Detected jacket-id 0x1 from cnvi id 0x80400
Nov 20 09:57:18 computer kernel: iwlwifi 0000:00:14.3: PCI dev 51f1/0000, rev=0x370, rfid=0x3010a100
Nov 20 09:57:18 computer kernel: iwlwifi: No config found for PCI dev 51f1/0000, rev=0x370, rfid=0x3010a100
Nov 20 09:57:18 computer kernel: iwlwifi 0000:00:14.3: probe with driver iwlwifi failed with error -22

The kernel parameter you suggested is the low hanging fruit, I shall test it first.

Arch Linux

#26 2024-10-06 14:12:42

Re: Unclaimed Network Controller

#27 2024-10-07 01:28:10

Re: Unclaimed Network Controller

#28 2024-11-20 10:44:59

Re: Unclaimed Network Controller

#29 2024-11-20 14:30:20

Re: Unclaimed Network Controller

#30 2024-11-20 18:08:19

Re: Unclaimed Network Controller

Board footer