Bug#1014319: depmod: WARNING: could not open modules.builtin.modinfo at /var/tmp/mkinitramfs_vBlw4a/lib/modules/5.18.0-2-amd64: No such file or directory
Control: tags -1 + patch
On 2022-07-04 10:00 +0200, Vincent Lefevre wrote:
> On 2022-07-04 15:01:13 +1000, Konomi Kitten wrote:
>> When update-initramfs runs I receive the following message:
>>
>> depmod: WARNING: could not open modules.builtin.modinfo at
>> /var/tmp/mkinitramfs_vBlw4a/lib/modules/5.18.0-2-amd64: No such file or
>> directory
>
> I also got such a warning on two of my machines. It seems to
> be triggered when upgrading kmod (which provides depmod) to
> 30+20220630-1.
Same here. The following patch takes care of the problem.
Cheers,
Sven
From e41183925d51bd97cd0b85660b6abdaad0fd5b69 Mon Sep 17 00:00:00 2001
From: Sven Joachim <svenjoac@gmx.de>
Date: Mon, 4 Jul 2022 08:35:46 +0200
Subject: [PATCH] Copy modules.builtin.modinfo into initramfs
As of kmod version 30, depmod issues a warning if this file is
missing.
Closes: #1014319
---
mkinitramfs | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/mkinitramfs b/mkinitramfs
index a4d16f6..df1b940 100755
--- a/mkinitramfs
+++ b/mkinitramfs
@@ -316,10 +316,10 @@ for d in conf/conf.d etc run scripts ${MODULESDIR}; do
mkdir -p "${DESTDIR}/${d}"
done
-# Copy in modules.builtin and modules.order (not generated by depmod)
+# Copy in modules.builtin, modules.builtin.modinfo and modules.order (not generated by depmod)
# and modules.builtin.bin (generated by depmod, but too late to avoid
# error messages as in #948257)
-for x in modules.builtin modules.builtin.bin modules.order; do
+for x in modules.builtin modules.builtin.bin modules.builtin.modinfo modules.order; do
if [ -f "${MODULESDIR}/${x}" ]; then
cp -p "${MODULESDIR}/${x}" "${DESTDIR}${MODULESDIR}/${x}"
fi
--
2.36.1
Reply to: