Re: Intel Comet Lake Wifi (8086:02f0) only working after cold start, failed with error -110

[Marc Haber]

No takers after half a week?

Greetings
Marc

On Sun, Dec 15, 2024 at 10:15:19PM +0100, Marc Haber wrote:
> I recently bought a used ThinkPad X13 1st Generation. That one is
> equipped with an:
> 00:14.3 Network controller [0280]: Intel Corporation Comet Lake PCH-LP CNVi WiFi[8086:02f0]
> 
> (lspci output avaible online as https://www.zugschlus.de/stuff/lspci-v
> and https://www.zugschlus.de/stuff/lspci-nn)
> 
> I can reproduce the following behavior with all Linux kernels beginning
> with the one that is in Debian Stable (didn't try anything older than
> that), Debian unstable, current Linux Mint, Fedora Workstation 41, up to
> a self-compiled Linux 6.12.5).
> 
> While there was a Windows installed on the box when I got it, I do not
> intend to dual boot the machine, and Windows has been erased by
> installing the first Linux over it. Hence, I dont consider the hints
> found on the Internet regarding Windows fast startup applicable in my
> case. In any case, I disabled Windows fast startup before overwriting
> Windows.
> 
> When the notebook is freshly cold booted (machine OFF, no led blinking,
> pulsing or anything, power supply disconnected), Wifi works. When I just
> reboot the machine without turning it actually off, or turn it off while
> leaving the power supply connected, Wifi does not work. The Wifi chip
> still shows up in lspci but not in ip addr / ip link. dmesg looks like
> it does not even try uploading firmware.
> 
> In the non-working case, I see a bunch of lines like
> [    3.998476] iwlwifi 0000:00:14.3: CSR_RESET = 0x10
> [    3.998494] iwlwifi 0000:00:14.3: Host monitor block 0x0 vector 0x0
> [    3.998524] iwlwifi 0000:00:14.3:     value [iter 0]: 0x00000000
> [    3.998545] iwlwifi 0000:00:14.3:     value [iter 1]: 0x00000000
> [    3.998566] iwlwifi 0000:00:14.3:     value [iter 2]: 0x00000000
> [    3.998587] iwlwifi 0000:00:14.3:     value [iter 3]: 0x00000000
> [    3.998608] iwlwifi 0000:00:14.3:     value [iter 4]: 0x00000000
> ending with
> [    4.007732] iwlwifi 0000:00:14.3: probe with driver iwlwifi failed with error -110
> 
> (full output on https://www.zugschlus.de/stuff/dmesg-notwork)
> 
> For reference, see dmesg output for a working case on
> https://www.zugschlus.de/stuff/dmesg-work.
> 
> As per the instructions given on
> https://wireless.docs.kernel.org/en/latest/en/users/drivers/iwlwifi/debugging.html,
> I have not yet upped the debug level. I am prepared to try with a kernel
> that has CONFIG_IWLWIFI_DEVICE_TRACING and/or CONFIG_IWLWIFI_DEBUG set.
> If you ask me to do this, please give me instructions about how to
> enable the desired debugging if module parameters, kernel command line
> parameters etc are necessary.
> 
> I would apprecaite any help. I can keep the machine in the current state
> for a few days, I only need it after chrismas.
> 
> Please keep me on Cc, I am not subscribed to the mailing lists.
> 
> Greetings
> Marc
> 
> 
> -- 
> -----------------------------------------------------------------------------
> Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
> Leimen, Germany    |  lose things."    Winona Ryder | Fon: *49 6224 1600402
> Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany    |  lose things."    Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421