i have two problems after i compile my kernel.

1.after successful make mrproper,make menucomfig(custom),make dep,make bzImge,make modules,make modules_install and later when i do make install at last it says
"all your loopback device are in use
Error1:.......leaving directory...........
Error2:.......leaving directory..........."
what could be the reason for this?and the solution?

2.after i compile custom kernel by removing all unwanted modules during the boot up process it says
"VFS:cannot open root device "LABEL=/" or 00:00
please append a correct "root=" boot option
kernel panic:unable to mount root fs on 00:00"
what could be the reason for this?
however if i do make oldconfig instead of make menuconfig it says "the kernel is to big for a standalone boot from floppy".but this one runs perfectly but with unnecessary modules.

2.after i compile custom kernel by removing all unwanted modules during the boot up process it says
"VFS:cannot open root device "LABEL=/" or 00:00
please append a correct "root=" boot option
kernel panic:unable to mount root fs on 00:00"
what could be the reason for this?

Did you reconfigure your bootloader (either lilo or grub) and then run either lilo or grub-install?

I'm having the exact same problem. I've messed around with the .conf file, but I get the "kernel panic" error you do every time. I've been doing some research and some suggest not using "make install". Instead they suggest copying bzImage and other files to /boot/. But I don't know how to copy the appropriate files from /usr/src/linux-2.4 to /boot/. If you figure it out, I would love to hear how. Thanks, eastj

-----------------------------------------------------------------------------------
But I don't know how to copy the appropriate files from /usr/src/linux-2.4 to /boot/


Try something similar to this:
cp /boot/vmlinuz /boot/vmlinuz.old
cp arch/i386/boot/bzImage /boot/vmlinuz

make modules_install

change /etc/lilo.conf to dual boot vmlinuz and vmlinuz.old
lilo
----------------------------------------------------------------------------------

Your first error means the Loop file system is not installed. Try 'insmod loop' and see if the compile work again. The initial ram disk is actually a loop file system containing a subset of your root directory. Enough to boot with. Things like modules and the init executable, etc. are in the initrd. (by the way, for those who are curious, a loop filesystem is a complete filesystem contained within a file residing on another filesystem, complete with directories and files, etc.)

Usually when the initrd is created (make install), the loopfs driver is loaded automatically. If it doesnt work, then perhaps you didn't have that module selected in the kernel config.

The second error is probably caused by the first. On booting, the root filesystem starts off as your initial ramdisk, then later in the boot process, the root filesystem switches from the initrd to the actual root directory on your harddrive. If the initrd was not created correctly from the above step, your kernel panic will always appear.

Jeff

Check out http://www.redhat.com/archives/anaco.../msg00011.html