topic Re: Chicken n egg problem with mkinitrd in Operating System - Linux

Chicken n egg problem with mkinitrd

K.C. Chan — Sun, 24 Feb 2002 02:11:44 GMT

All, I am running into a bit of a snag here? Here's what happen after compiling kernel 2.4.17 and running mkinitrd: "
mkinitrd -v initrd-2.4.17 2.4.17
Using modules:
All of your loopback devices are in use! ". How do I resolve this chicken-n-problem? The current kernel version is: "kernel-2.4.2-2". Thanks.

Re: Chicken n egg problem with mkinitrd

Ron Kinner — Sun, 24 Feb 2002 12:55:12 GMT

See:http://www.van-dijk.net/mailarchive/cpqlin0007/0081.html

Also shouldn't you have some sort of extension on the end of your first parameter like .img?

Ron

Re: Chicken n egg problem with mkinitrd

K.C. Chan — Mon, 25 Feb 2002 15:47:56 GMT

Ron Kinner,
I am stock at "cd /lib/modules//block" and insmod loop returns: "/lib/modules/2.4.17/block
insmod: loop: no module by that name found" Any suggestion on getting this to work. Thanks.

Re: Chicken n egg problem with mkinitrd

Eric Ladner — Mon, 25 Feb 2002 20:20:17 GMT

Go through the make config again and enable the loop device under block devices as 'Y', not a module or 'N'.

Re: Chicken n egg problem with mkinitrd

K.C. Chan — Fri, 01 Mar 2002 23:05:42 GMT

Eric Ladner,
I've compiled kernel 2.4.17 with loop back option = Y, but still getting same error: "all loop back are in use" when running mkinitrd initrd-2.4.17.img 2.4.17. Do you have any idea? Thanks.

Re: Chicken n egg problem with mkinitrd

Paul S_1 — Mon, 04 Mar 2002 18:30:42 GMT

You have no loopback devices available.

Either 'modprobe loop' or boot back to your stock linux kernel and run mkinitrd.

mkinitrd /boot/initrd-[kernel version].img [kernel version, not vmlinuz-*]

To see if you have the driver loaded, run lsmod (as root) or cat /proc/modules (as a normal user). You should see loop listed as unused.

To see if you even have the driver go:
cd /lib/modules/[kernel version]/kernel/drivers/block

and ls

you should see loop.o

--Paul

Re: Chicken n egg problem with mkinitrd

K.C. Chan — Thu, 16 May 2002 01:00:31 GMT

All, I've gotten this to work by rebuilding the current working kernel with loopback support. Then on the new kernel I've also make sure the loopback support is selected, so this way I can use mkinitrd on the future kernel. Thanks.