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] [thread-next>] [day] [month] [year] [list]
Message-ID: <5fc092da11b3d81c99fc4bc4b78e87783280414f.camel@sipsolutions.net>
Date: Thu, 31 Oct 2024 09:57:33 +0100
From: Johannes Berg <johannes@...solutions.net>
To: Gang Yan <gang_yan@...mail.com>, "miriam.rachel.korenblit"
	 <miriam.rachel.korenblit@...el.com>, kvalo <kvalo@...nel.org>
Cc: 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, 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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ