Re: A problem I'm having with mkinitrd for linux-2.6-test7

[Randy.Dunlap]

On Wed, 15 Oct 2003 13:27:09 -0700 (PDT) George R Goffe <grgoffe@xxxxxxxxx> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/