Hey,
I setup a test6 kernel without module support. I did a make install
and got:
Kernel: arch/i386/boot/bzImage is ready
sh /usr/src/linux-2.6.0-test6/arch/i386/boot/install.sh 2.6.0-test6
arch/i386/boot/bzImage System.map ""
/lib/modules/2.6.0-test6 is not a directory.
mkinitrd failed
How can I fix this?
Thanks
Kevin Breit
On Tue, 30 Sep 2003 09:16:19 -0400 Kevin Breit <[email protected]> wrote:
| Hey,
| I setup a test6 kernel without module support. I did a make install
| and got:
|
| Kernel: arch/i386/boot/bzImage is ready
| sh /usr/src/linux-2.6.0-test6/arch/i386/boot/install.sh 2.6.0-test6
| arch/i386/boot/bzImage System.map ""
| /lib/modules/2.6.0-test6 is not a directory.
| mkinitrd failed
|
| How can I fix this?
We've seen this before, and I thought that we had determined that
it was a tools problem. Is "depmod" in $PATH the depmod from
modutils or the one from module-init-tools?
I.e., what does 'depmod -V' say?
and what execs mkinitrd? I don't find it with a quick grep.
--
~Randy
On Tue, 2003-09-30 at 11:14, Randy.Dunlap wrote:
> On Tue, 30 Sep 2003 09:16:19 -0400 Kevin Breit <[email protected]> wrote:
>
> | Hey,
> | I setup a test6 kernel without module support. I did a make install
> | and got:
> |
> | Kernel: arch/i386/boot/bzImage is ready
> | sh /usr/src/linux-2.6.0-test6/arch/i386/boot/install.sh 2.6.0-test6
> | arch/i386/boot/bzImage System.map ""
> | /lib/modules/2.6.0-test6 is not a directory.
> | mkinitrd failed
> |
> | How can I fix this?
>
> We've seen this before, and I thought that we had determined that
> it was a tools problem. Is "depmod" in $PATH the depmod from
> modutils or the one from module-init-tools?
> I.e., what does 'depmod -V' say?
modutils-2.4.22-8
[root@kbreit linux-2.6.0-test6]# depmod -V
depmod version 2.4.22
> and what execs mkinitrd? I don't find it with a quick grep.
No clue
Thanks
Kevin
On Tue, 30 Sep 2003 11:29:42 -0400 Kevin Breit <[email protected]> wrote:
| On Tue, 2003-09-30 at 11:14, Randy.Dunlap wrote:
| > On Tue, 30 Sep 2003 09:16:19 -0400 Kevin Breit <[email protected]> wrote:
| >
| > | Hey,
| > | I setup a test6 kernel without module support. I did a make install
| > | and got:
| > |
| > | Kernel: arch/i386/boot/bzImage is ready
| > | sh /usr/src/linux-2.6.0-test6/arch/i386/boot/install.sh 2.6.0-test6
| > | arch/i386/boot/bzImage System.map ""
| > | /lib/modules/2.6.0-test6 is not a directory.
| > | mkinitrd failed
| > |
| > | How can I fix this?
| >
| > We've seen this before, and I thought that we had determined that
| > it was a tools problem. Is "depmod" in $PATH the depmod from
| > modutils or the one from module-init-tools?
| > I.e., what does 'depmod -V' say?
|
| modutils-2.4.22-8
|
| [root@kbreit linux-2.6.0-test6]# depmod -V
| depmod version 2.4.22
|
|
| > and what execs mkinitrd? I don't find it with a quick grep.
|
| No clue
You need to use module-init-tools with 2.6.x, not modutils.
You can find them at
http://www.kernel.org/pub/linux/kernel/people/rusty/modules/
Just get the latest version.
--
~Randy
On Tue, 2003-09-30 at 11:34, Randy.Dunlap wrote:
> On Tue, 30 Sep 2003 11:29:42 -0400 Kevin Breit <[email protected]> wrote:
>
> | On Tue, 2003-09-30 at 11:14, Randy.Dunlap wrote:
> | > On Tue, 30 Sep 2003 09:16:19 -0400 Kevin Breit <[email protected]> wrote:
> | >
> | > | Hey,
> | > | I setup a test6 kernel without module support. I did a make install
> | > | and got:
> | > |
> | > | Kernel: arch/i386/boot/bzImage is ready
> | > | sh /usr/src/linux-2.6.0-test6/arch/i386/boot/install.sh 2.6.0-test6
> | > | arch/i386/boot/bzImage System.map ""
> | > | /lib/modules/2.6.0-test6 is not a directory.
> | > | mkinitrd failed
> | > |
> | > | How can I fix this?
> | >
> | > We've seen this before, and I thought that we had determined that
> | > it was a tools problem. Is "depmod" in $PATH the depmod from
> | > modutils or the one from module-init-tools?
> | > I.e., what does 'depmod -V' say?
> |
> | modutils-2.4.22-8
> |
> | [root@kbreit linux-2.6.0-test6]# depmod -V
> | depmod version 2.4.22
> |
> |
> | > and what execs mkinitrd? I don't find it with a quick grep.
> |
> | No clue
>
> You need to use module-init-tools with 2.6.x, not modutils.
> You can find them at
> http://www.kernel.org/pub/linux/kernel/people/rusty/modules/
> Just get the latest version.
Why do I need this for a moduleless kernel?
Kevin
On Tue, 30 Sep 2003 12:18:10 -0400 Kevin Breit <[email protected]> wrote:
| On Tue, 2003-09-30 at 11:34, Randy.Dunlap wrote:
| > On Tue, 30 Sep 2003 11:29:42 -0400 Kevin Breit <[email protected]> wrote:
| >
| > | On Tue, 2003-09-30 at 11:14, Randy.Dunlap wrote:
| > | > On Tue, 30 Sep 2003 09:16:19 -0400 Kevin Breit <[email protected]> wrote:
| > | >
| > | > | Hey,
| > | > | I setup a test6 kernel without module support. I did a make install
| > | > | and got:
| > | > |
| > | > | Kernel: arch/i386/boot/bzImage is ready
| > | > | sh /usr/src/linux-2.6.0-test6/arch/i386/boot/install.sh 2.6.0-test6
| > | > | arch/i386/boot/bzImage System.map ""
| > | > | /lib/modules/2.6.0-test6 is not a directory.
| > | > | mkinitrd failed
| > | > |
| > | > | How can I fix this?
| > | >
| > | > We've seen this before, and I thought that we had determined that
| > | > it was a tools problem. Is "depmod" in $PATH the depmod from
| > | > modutils or the one from module-init-tools?
| > | > I.e., what does 'depmod -V' say?
| > |
| > | modutils-2.4.22-8
| > |
| > | [root@kbreit linux-2.6.0-test6]# depmod -V
| > | depmod version 2.4.22
| > |
| > |
| > | > and what execs mkinitrd? I don't find it with a quick grep.
| > |
| > | No clue
| >
| > You need to use module-init-tools with 2.6.x, not modutils.
| > You can find them at
| > http://www.kernel.org/pub/linux/kernel/people/rusty/modules/
| > Just get the latest version.
|
| Why do I need this for a moduleless kernel?
arch/i386/boot/Makefile for 'make install' runs arch/i386/boot/install.sh.
This latter script runs /sbin/installkernel or ~/bin/installkernel.
You (user) control the latter one (if present).
Your distro controls the former one, so I can't say what's in your
system's /sbin/installkernel file.
In my /sbin/installkernel, I can see that using it with a "-i"
option tells it not to generated initrd files.
YMMV.
--
~Randy