From: Kevin Brosius <cobra@compuserve.com>
To: kernel <linux-kernel@vger.kernel.org>
Subject: Re: QM_MODULES, bk current initrd problems?
Date: Sun, 17 Nov 2002 16:39:39 -0500 [thread overview]
Message-ID: <3DD80C9B.42A8AD73@compuserve.com> (raw)
In-Reply-To: 3DD7C050.759F7973@compuserve.com
Kevin Brosius wrote:
>
> So I worked through bk current again this morning, needing most of
> Arnaldo Carvalho de Melo fixes to compile (see example at
> http://marc.theaimsgroup.com/?l=linux-kernel&m=103753350710937&w=2),
> then grabbed Rusty's new modutils(
> http://marc.theaimsgroup.com/?l=linux-kernel&m=103741153016225&w=2),
> because initrd couldn't load modules with "insmod: QM_MODULES: "
> notices. However, I still cannot load modules even with Rusty's
> modutils installed. Is there anything else required? I'm only trying
> to load DAC960, reiserfs, and aix7xxx from initrd, none of which loads.
> (DAC960 is the updated version from DMO, at
> http://www.osdl.org/archive/dmo/)
>
This is partly my fault (although I'll share the blame with Rusty and
SuSE equally.)
On SuSE 8.1, insmod is installed twice, once as /sbin/insmod and also as
/sbin/insmod.static. The static version is used for building rd images
for initrd. Rusty's package doesn't build a static version, so until I
looked into this, it was still the old insmod.static without the
module-init changes.
I made an attempt to work around this, both by forcing the SuSE mkinitrd
script to include libc and by building a static version of Rusty's
insmod. However, the kernel still will not boot, although the problem
changes to 'no such file or dir' during the module load attempt. I'm no
expert on initrd, so am not sure why this is a problem at this point.
--
Kevin
prev parent reply other threads:[~2002-11-17 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-17 16:14 QM_MODULES, bk current initrd problems? Kevin Brosius
2002-11-17 21:39 ` Kevin Brosius [this message]
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=3DD80C9B.42A8AD73@compuserve.com \
--to=cobra@compuserve.com \
--cc=linux-kernel@vger.kernel.org \
/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