From: Johannes Berg <johannes@sipsolutions.net>
To: Gang Yan <gang_yan@foxmail.com>,
"miriam.rachel.korenblit" <miriam.rachel.korenblit@intel.com>,
kvalo <kvalo@kernel.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Issue with iwlwifi Firmware Loading When Compiled into the Kernel
Date: Thu, 31 Oct 2024 09:57:33 +0100 [thread overview]
Message-ID: <5fc092da11b3d81c99fc4bc4b78e87783280414f.camel@sipsolutions.net> (raw)
In-Reply-To: <tencent_7DC9187727BD32FEEC99045E754751A0CA08@qq.com>
On Thu, 2024-10-31 at 16:52 +0800, Gang Yan wrote:
>
> In fact, I'm using Ubuntu's userspace, but I've simply replaced Ubuntu's
> kernel with the mainline 6.12.rc2 version (x86_64_defconfig). By merely
> changing CONFIG_IWLWIFI from 'm' to 'y', the network functionality normalized,
> which is inevitably confusing. By the way, both of my computers encountered
> this issue, with network devices being Intel Wireless 8265 and Intel AX210, respectively.
Yeah well, so Ubuntu integrated everything in a certain way, and because
they build everything as modules they didn't integrated anything to make
it possible to build modules in the kernel.
When you change it, you own the integration. I gave you a few ways to
solve this, simplest is just specifying the firmware to build into the
kernel in the .config file.
> I still think some clarification will be helpful to make the configuration process
> here clearer.
I don't think we need to change anything. Whoever makes some changes to
a distro needs to actually do the integration too. This is in no way
specific to iwlwifi, every other devices with firmware has the problem,
and generic ways of fixing it already exist.
johannes
next prev parent reply other threads:[~2024-10-31 8:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 1:46 Gang Yan
2024-10-31 8:06 ` Johannes Berg
2024-10-31 8:52 ` Gang Yan
2024-10-31 8:57 ` Johannes Berg [this message]
2024-10-31 9:08 ` Gang Yan
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=5fc092da11b3d81c99fc4bc4b78e87783280414f.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=gang_yan@foxmail.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
/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
all inboxes | Powered by JetHome®