<div dir="ltr"><div>Hi there. Apologies — I just missed your previous email. <br></div><div><br></div><div>I can confirm the problem still reproduces on 254.5-1. To be clear: my symptoms are that I have at this point collected the list of modules my system needs to run, and listed them in /etc/modules. If I remove, say, iwlwifi from them, I boot into a system that does not have iwlwifi loaded, and thus no wifi functionality, until I manually modprobe iwlwifi.</div><div><br></div><div>It was merely a guess that it couldn't find hwdb, based on those log lines — if they are not unusual, then that guess falls apart. I'm willing to do any further log collection or investigation required, but I would need instructions on how to do so.</div><div><br></div><div>What exactly is responsible for autoloading kernel modules based on hardware? Maybe it would help if I gained familiarity with that code file?</div><div><br></div><div>Thanks,</div><div>—Sohum<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, 22 Oct 2023 at 06:39, Debian Bug Tracking System <<a href="mailto:owner@bugs.debian.org">owner@bugs.debian.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">This is an automatic notification regarding your Bug report<br>
which was filed against the udev package:<br>
<br>
#1031721: udev fails to autoload kernel modules (wifi, sound, video, bluetooth, thermals)<br>
<br>
It has been closed by Michael Biebl <<a href="mailto:biebl@debian.org" target="_blank">biebl@debian.org</a>>.<br>
<br>
Their explanation is attached below along with your original report.<br>
If this explanation is unsatisfactory and you have not received a<br>
better one in a separate message then please contact Michael Biebl <<a href="mailto:biebl@debian.org" target="_blank">biebl@debian.org</a>> by<br>
replying to this email.<br>
<br>
<br>
-- <br>
1031721: <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031721" rel="noreferrer" target="_blank">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031721</a><br>
Debian Bug Tracking System<br>
Contact <a href="mailto:owner@bugs.debian.org" target="_blank">owner@bugs.debian.org</a> with problems<br>
<br><br><br>---------- Forwarded message ----------<br>From: Michael Biebl <<a href="mailto:biebl@debian.org" target="_blank">biebl@debian.org</a>><br>To: Sohum Banerjea <<a href="mailto:sohum@nsb0.net" target="_blank">sohum@nsb0.net</a>>, <a href="mailto:1031721-done@bugs.debian.org" target="_blank">1031721-done@bugs.debian.org</a><br>Cc: <br>Bcc: <br>Date: Sat, 21 Oct 2023 21:34:13 +0200<br>Subject: Re: Bug#1031721: udev fails to autoload kernel modules (wifi, sound, video, bluetooth, thermals)<br>Am 26.08.23 um 15:25 schrieb Michael Biebl:<br>
> Am 07.05.23 um 02:53 schrieb Sohum Banerjea:<br>
>> Yes, the problem reproduces on my system on udev 253-1. The debug log <br>
>> you requested is attached, I believe.<br>
>><br>
>> It seems the main takeaway from it is that my hwdb is missing? But I <br>
>> do have a `/usr/lib/udev/hwdb.bin` and a `/usr/lib/udev/hwdb.d`, and <br>
>> udev 250 picks up that hwdb just fine.<br>
>><br>
> <br>
> How do you conclude that there is problem your your hwdb?<br>
> If you refer to<br>
> <br>
> May 07 10:42:44 dynast systemd-udevd[1656]: Trying to open <br>
> "/etc/systemd/hwdb/hwdb.bin"...<br>
> May 07 10:42:44 dynast systemd-udevd[1656]: Trying to open <br>
> "/etc/udev/hwdb.bin"...<br>
> <br>
> <br>
> This just means, it tries those locations (which apparently don't <br>
> exist), before it tries /usr/lib/udev/hwdb.bin<br>
> <br>
> The log doesn't reveal anything unusual afaics.<br>
<br>
I'm closing this bug report as the existing information is not actionable.<br>
<br>
<br>
<br><br><br>---------- Forwarded message ----------<br>From: Sohum Banerjea <<a href="mailto:sohum@nsb0.net" target="_blank">sohum@nsb0.net</a>><br>To: Debian Bug Tracking System <<a href="mailto:submit@bugs.debian.org" target="_blank">submit@bugs.debian.org</a>><br>Cc: <br>Bcc: <br>Date: Wed, 22 Feb 2023 00:55:21 +1100<br>Subject: udev fails to autoload kernel modules (wifi, sound, video, bluetooth, thermals)<br>Package: udev<br>
Version: 252.5-2<br>
Severity: important<br>
<br>
Dear Maintainer,<br>
<br>
Since upgrading my system to udev 252 from 250, kernel module autoloading has been broken<br>
on my machine. I've confirmed that it's exactly a problem with the udev package via zfs<br>
rollbacks.<br>
<br>
The modules themself work fine; I can run:<br>
<br>
sudo modprobe coretemp intel_pch_thermal thinkpad_acpi iwlwifi nvidia-current-drm modeset=1 bluetooth snd-hda-intel btusb<br>
<br>
and return to a functioning system.<br>
<br>
I do not understand how kernel module autoloading is supposed to work, and could not find<br>
documentation that helped, so I apologise for not having further information. I'm happy to<br>
do any further investigation that may help.<br>
<br>
-- Package-specific info:<br>
<br>
-- System Information:<br>
Debian Release: bookworm/sid<br>
APT prefers unstable<br>
APT policy: (700, 'unstable'), (600, 'testing'), (550, 'stable'), (500, 'stable-security'), (500, 'experimental')<br>
Architecture: amd64 (x86_64)<br>
Foreign Architectures: i386<br>
<br>
Kernel: Linux 6.1.0-5-amd64 (SMP w/12 CPU threads; PREEMPT)<br>
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE<br>
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set<br>
Shell: /bin/sh linked to /usr/bin/dash<br>
Init: systemd (via /run/systemd/system)<br>
LSM: AppArmor: enabled<br>
<br>
Versions of packages udev depends on:<br>
ii adduser 3.131<br>
ii libacl1 2.3.1-3<br>
ii libblkid1 2.38.1-5<br>
ii libc6 2.36-8<br>
ii libcap2 1:2.66-3<br>
ii libkmod2 30+20221128-1<br>
ii libselinux1 3.4-1+b5<br>
ii libudev1 252.5-2<br>
<br>
udev recommends no packages.<br>
<br>
udev suggests no packages.<br>
<br>
Versions of packages udev is related to:<br>
ii systemd 252.5-2<br>
<br>
-- no debconf information<br>
</blockquote></div>