Note: I do NOT speak on behalf of the kernel team. On Tuesday, 18 April 2023 09:47:14 CEST Marco d'Itri wrote: > On Apr 18, Jamie Bainbridge <jamie.bainbridge@gmail.com> wrote: > > I have a laptop with iwlwifi wireless card: > > $ sudo lspci -nn | grep Net > > Network controller [0280]: Intel Corporation Wireless 7265 [8086:095a] > > (rev 59)> > > > Ubuntu ships a file in its kmod package with the following contents: > > # /etc/modprobe.d/iwlwifi.conf > > # iwlwifi will dyamically load either iwldvm or iwlmvm depending on the > > # microcode file installed on the system. When removing iwlwifi, first > > # remove the iwl?vm module and then iwlwifi. > > remove iwlwifi \ > > (/sbin/lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs > > /sbin/rmmod) \ > > && /sbin/modprobe -r mac80211 > > > Adding this file to Debian resolves the problem. > > > This is a request to include the above iwlwifi.conf file in Debian's > > kmod package too. > > > > I can only assume from the massive Ubuntu install base that this file > > doesn't cause any problems for devices which don't need the modules > > loaded in this order, while also resolving whatever problem requires > > that modules are loaded in the order which the above file forces. > > > > in the first place. It's been there for a very long time, at least since > > kmod 9 from over 10 years ago. > > Given also that Debian never shipped this, I would like to better > understand why we should do it now. So in order for the wifi device to work properly, the modules need to be loaded in a specific order? And this *workaround* does that? If the kernel does not load modules in the right order, then that sounds like an upstream kernel bug which should be reported (upstream), so that it can be fixed properly. Pampering over that for 10 YEARS sounds like the wrong 'solution'? My 0.02
Attachment:
signature.asc
Description: This is a digitally signed message part.