From: maximilian attems <max@stro.at>
To: Frans Pop <elendil@planet.nl>, 518412@bugs.debian.org
Cc: md@linux.it, Jon Masters <jcm@jonmasters.org>,
linux-kernel@vger.kernel.org
Subject: linux-2.6 install errors due to incompatible depmod files [was Re: Bug#518412: initramfs-tools: must support relative paths in modules.dep ]
Date: Thu, 19 Mar 2009 21:13:10 +0100 [thread overview]
Message-ID: <20090319201310.GI3901@baikonur.stro.at> (raw)
In-Reply-To: <200903191940.47726.elendil@planet.nl>
[ adding jcm and lkml to Cc: ]
On Thu, Mar 19, 2009 at 07:40:46PM +0100, Frans Pop wrote:
>
> Hmmm. I wonder if it is the old m-i-t's modprobe that is the problem when
> you do:
> modprobe --set-version=2.6.26.3 --ignore-install --show-depends <module>
>
> Looks like that's it:
> # modprobe -V
> module-init-tools version 3.4
> # modprobe --set-version=2.6.26.3 --ignore-install --show-depends nfs
> WARNING: Could not open 'kernel/net/sunrpc/sunrpc.ko': No such file or
> directory
> WARNING: Could not open 'kernel/fs/nfs_common/nfs_acl.ko': No such file or
> directory
> WARNING: Could not open 'kernel/fs/lockd/lockd.ko': No such file or
> directory
> FATAL: Could not open 'kernel/fs/nfs/nfs.ko': No such file or directory
>
> # modprobe -V
> module-init-tools version 3.7-pre9
> # modprobe --set-version=2.6.26.3 --ignore-install --show-depends nfs
> WARNING: All config files need .conf: /etc/modprobe.d/pnp-hotplug, it will
> be ignored in a future release.
> WARNING: All config files need .conf: /etc/modprobe.d/display_class, it
> will be ignored in a future release.
> WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will
> be ignored in a future release.
> insmod /lib/modules/2.6.26.3/kernel/net/sunrpc/sunrpc.ko
> insmod /lib/modules/2.6.26.3/kernel/fs/nfs_common/nfs_acl.ko
> insmod /lib/modules/2.6.26.3/kernel/fs/lockd/lockd.ko
> insmod /lib/modules/2.6.26.3/kernel/fs/nfs/nfs.ko
>
> That would mean that m-i-t has created a backwards incompatibility problem
> _with itself_ and that the problem actually is "installing a kernel, that
> was built on a system with new m-i-t, on a system with old m-i-t".
> Or, installing a kernel, built on a system running unstable or testing, on
> a system running oldstable or stable. That sucks.
argh indeed.
arguably it is also a bug by initramfs-tools to suppress the error of above
modprobe calls see manual_add_modules() in hook-functions:
for mam_x in $(modprobe --set-version="${version}" --ignore-install \
--show-depends "${1}" 2>/dev/null | awk '/^insmod/ { print $2 }'); do
git history tells that jbailey added it from the start on,
so it must have been because modprobe was/is too chatty.
suse mkinitrd seems also only to have lost that suppression lately.
thanks for finding out fjp.
kind regards
--
maks
next parent reply other threads:[~2009-03-19 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090319153604.GB7954@stro.at>
[not found] ` <200903191843.28437.elendil@planet.nl>
[not found] ` <20090319181031.GH3901@baikonur.stro.at>
[not found] ` <200903191940.47726.elendil@planet.nl>
2009-03-19 20:13 ` maximilian attems [this message]
2009-03-19 20:30 ` Jon Masters
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090319201310.GI3901@baikonur.stro.at \
--to=max@stro.at \
--cc=518412@bugs.debian.org \
--cc=elendil@planet.nl \
--cc=jcm@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=md@linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®