lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <tencent_9E86EA49928C177B25C1691D4454AAB21106@qq.com>
Date: Thu, 31 Oct 2024 17:08:07 +0800
From: Gang Yan <gang_yan@...mail.com>
To: Johannes Berg <johannes@...solutions.net>
Cc: "miriam.rachel.korenblit" <miriam.rachel.korenblit@...el.com>,
	kvalo <kvalo@...nel.org>,
	linux-wireless <linux-wireless@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Issue with iwlwifi Firmware Loading When Compiled into the Kernel

> On Thu, Oct 31, 2024 at 09:57:33AM +0100, Johannes Berg wrote:
> 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
Thanks a lot, I understand what you mean now.

Gang Yan


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ