On Thu, Oct 31, 2024 at 16:37:49AM +0100, Gang Yan wrote: Hi, Johannes: Thanks for your reply. > On Thu, Oct 31, 2024 at 09:06:49AM +0100, Johannes Berg wrote: > > > > To address this issue, I have considered two potential solutions: > > > > 1、Modify the Driver Code: Implement a mechanism, such as delayed_work, to > > give iwlwifi another chance to load the firmware after the filesystem has > > been mounted. This would involve adding additional logic to the driver to > > handle retries for firmware loading. > > > > 2、Modify the Kconfig: Change the configuration to allow iwlwifi to be > > compiled only as a module [CONFIG_IWLWIFI=m]. This way, the module can be > > loaded after the filesystem is fully mounted, ensuring that the firmware > > can be found and loaded successfully. > > Neither of those is going to happen - you should just build the firmware > into the kernel (or initramfs might be enough?) if you want it built-in. > Or set up firmware loading userspace, and set it up appropriately to > only respond after / is mounted. > > In any case, not a kernel problem. You need to fix it on your userspace. > > johannes 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. I still think some clarification will be helpful to make the configuration process here clearer. Thanks. Gang Yan
