From: "Randy.Dunlap" <rddunlap@osdl.org>
To: George R Goffe <grgoffe@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: A problem I'm having with mkinitrd for linux-2.6-test7
Date: Wed, 15 Oct 2003 17:19:10 -0700 [thread overview]
Message-ID: <20031015171910.604cfad6.rddunlap@osdl.org> (raw)
In-Reply-To: <20031015202709.38652.qmail@web21307.mail.yahoo.com>
On Wed, 15 Oct 2003 13:27:09 -0700 (PDT) George R Goffe <grgoffe@yahoo.com> wrote:
| I have built a linux 2.6-test7 kernel on my redhat 8.0 system and am trying to
| use mkinitrd. I am getting this message relating to a module not being found
| (see command and error message below).
|
| I'm not sure what to do at this point. The make modules produced no problems
| but make modules_install had a bunch of depmod problems. I have been using the
| module-init-tools-0.9.15-pre2 tools from Rusty's site.
|
| Any/all help/tips/hints/suggestions would be greatly appreciated.
|
|
| 2.4.20-20.8smp root->server3# mkinitrd /boot/initrd-2.6.0-test7.img
| 2.6.0-test7
| No module mptbase found for kernel 2.6.0-test7
The 'mkinitrd' script is probably different on our systems. I expect
that distros customize it a bit and I don't have a RH 8.0 version
of it.
The latest version that I found (3.5.14) searches for module files
ending in o.gz, o, or ko. I expect that you are using a version of
mkinitrd that does not search for module files ending in ko.
You (or I) could modify your mkinitrd file to search for ko module
names, or you could try an updated version of mkinitrd that does
search for modules names that end with ko.
Do you actually want/need the mptbase module in your initrd?
If not, edit /etc/modules.conf and remove that module name.
But mkinitrd needs to be updated to look in /etc/modprobe.conf
instead of /etc/modules.conf for module names. I expect that
the distros will take care of that.
--
~Randy
prev parent reply other threads:[~2003-10-16 0:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 20:27 George R Goffe
2003-10-15 23:08 ` Randy.Dunlap
2003-10-16 0:19 ` Randy.Dunlap [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=20031015171910.604cfad6.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=grgoffe@yahoo.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
all inboxes | Powered by JetHome®