Linux wireless drivers development
 help / color / mirror / Atom feed
From: Bohdan <boulderobscura@gmail.com>
To: Mark <markmunene827@gmail.com>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [BUG] iwlwifi: Comet Lake PCH CNVi AX201 (8086:06f0) fails with error -110 on warm reboot
Date: Thu, 27 Aug 2026 20:47:33 +0300	[thread overview]
Message-ID: <1EF6CC70-90BC-4B9F-9F96-9DB1F3A69F1E@gmail.com> (raw)
In-Reply-To: <CAMSTZO=2dm21hYcKKeDGCTb4KJ6R0ukDAFBQtsp4QVzPmCfcSg@mail.gmail.com>

> Hi Bohdan and Boulder,

Both are me, for some reason Thunderbird on Android decided to use "Boulder" which is Google account name. Hope this won't happen this time. Please bear with me while I debug identity settings.

>I tried testing the mainline 7.1 build directly, but on this Precision 7550
>the generic mainline image hits an early boot panic. It looks to be related
>to the out-of-tree proprietary GPU module and its initramfs hooks, so I
>wasn't able to get a clean 7.1 boot on this installation.

We still can debug this, but you'll have to blacklist the drivers that make your system not boot (and lose the graphical interface in the meantime, or rely purely on integrated graphics during debugging if they are present) and try iwlwifi through the command line. In the worst-case scenario, you will need a USB with Linux distro ISO on it, and a guide on how to use chroot. Keep track of the changes you will have done, that way it will be easier to restore the system.

If you use NetworkManager for wireless (you likely do, most Linux distros do), you can use nmtui to connect to Wi-Fi from there, which may be useful for further testing.

Hope it's not NVIDIA (it will surely be NVIDIA),
Bohdan

  parent reply	other threads:[~2026-08-27 17:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27 16:26 [BUG] iwlwifi: Comet Lake PCH CNVi AX201 (8086:06f0) fails with error -110 on warm reboot Mark
2026-08-27 17:10 ` Bohdan
     [not found]   ` <CAMSTZO=2dm21hYcKKeDGCTb4KJ6R0ukDAFBQtsp4QVzPmCfcSg@mail.gmail.com>
2026-08-27 17:47     ` Bohdan [this message]
2026-08-27 18:06       ` Mark
2026-08-27 19:20         ` Bohdan
2026-08-28 11:46           ` Mark

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1EF6CC70-90BC-4B9F-9F96-9DB1F3A69F1E@gmail.com \
    --to=boulderobscura@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=markmunene827@gmail.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox