Bug#1031721: closed by Michael Biebl <biebl at debian.org> (Re: Bug#1031721: udev fails to autoload kernel modules (wifi, sound, video, bluetooth, thermals))

Sohum Banerjea sohum at nsb0.net
Sat Oct 21 22:33:30 BST 2023


Hi there. Apologies — I just missed your previous email.

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.

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.

What exactly is responsible for autoloading kernel modules based on
hardware? Maybe it would help if I gained familiarity with that code file?

Thanks,
—Sohum

On Sun, 22 Oct 2023 at 06:39, Debian Bug Tracking System <
owner at bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the udev package:
>
> #1031721: udev fails to autoload kernel modules (wifi, sound, video,
> bluetooth, thermals)
>
> It has been closed by Michael Biebl <biebl at debian.org>.
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Michael Biebl <
> biebl at debian.org> by
> replying to this email.
>
>
> --
> 1031721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031721
> Debian Bug Tracking System
> Contact owner at bugs.debian.org with problems
>
>
>
> ---------- Forwarded message ----------
> From: Michael Biebl <biebl at debian.org>
> To: Sohum Banerjea <sohum at nsb0.net>, 1031721-done at bugs.debian.org
> Cc:
> Bcc:
> Date: Sat, 21 Oct 2023 21:34:13 +0200
> Subject: Re: Bug#1031721: udev fails to autoload kernel modules (wifi,
> sound, video, bluetooth, thermals)
> Am 26.08.23 um 15:25 schrieb Michael Biebl:
> > Am 07.05.23 um 02:53 schrieb Sohum Banerjea:
> >> Yes, the problem reproduces on my system on udev 253-1. The debug log
> >> you requested is attached, I believe.
> >>
> >> It seems the main takeaway from it is that my hwdb is missing? But I
> >> do have a `/usr/lib/udev/hwdb.bin` and a `/usr/lib/udev/hwdb.d`, and
> >> udev 250 picks up that hwdb just fine.
> >>
> >
> > How do you conclude that there is problem your your hwdb?
> > If you refer to
> >
> > May 07 10:42:44 dynast systemd-udevd[1656]: Trying to open
> > "/etc/systemd/hwdb/hwdb.bin"...
> > May 07 10:42:44 dynast systemd-udevd[1656]: Trying to open
> > "/etc/udev/hwdb.bin"...
> >
> >
> > This just means, it tries those locations (which apparently don't
> > exist), before it tries /usr/lib/udev/hwdb.bin
> >
> > The log doesn't reveal anything unusual afaics.
>
> I'm closing this bug report as the existing information is not actionable.
>
>
>
>
>
> ---------- Forwarded message ----------
> From: Sohum Banerjea <sohum at nsb0.net>
> To: Debian Bug Tracking System <submit at bugs.debian.org>
> Cc:
> Bcc:
> Date: Wed, 22 Feb 2023 00:55:21 +1100
> Subject: udev fails to autoload kernel modules (wifi, sound, video,
> bluetooth, thermals)
> Package: udev
> Version: 252.5-2
> Severity: important
>
> Dear Maintainer,
>
> Since upgrading my system to udev 252 from 250, kernel module autoloading
> has been broken
> on my machine. I've confirmed that it's exactly a problem with the udev
> package via zfs
> rollbacks.
>
> The modules themself work fine; I can run:
>
>     sudo modprobe coretemp intel_pch_thermal thinkpad_acpi iwlwifi
> nvidia-current-drm modeset=1 bluetooth snd-hda-intel btusb
>
> and return to a functioning system.
>
> I do not understand how kernel module autoloading is supposed to work, and
> could not find
> documentation that helped, so I apologise for not having further
> information. I'm happy to
> do any further investigation that may help.
>
> -- Package-specific info:
>
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers unstable
>   APT policy: (700, 'unstable'), (600, 'testing'), (550, 'stable'), (500,
> 'stable-security'), (500, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 6.1.0-5-amd64 (SMP w/12 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
> TAINT_UNSIGNED_MODULE
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE
> not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages udev depends on:
> ii  adduser      3.131
> ii  libacl1      2.3.1-3
> ii  libblkid1    2.38.1-5
> ii  libc6        2.36-8
> ii  libcap2      1:2.66-3
> ii  libkmod2     30+20221128-1
> ii  libselinux1  3.4-1+b5
> ii  libudev1     252.5-2
>
> udev recommends no packages.
>
> udev suggests no packages.
>
> Versions of packages udev is related to:
> ii  systemd  252.5-2
>
> -- no debconf information
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20231022/adc4f70b/attachment-0001.htm>


More information about the Pkg-systemd-maintainers mailing list