I installed UbuntuME inside windows and proceeded to compile 2.6.25.7 kernel (UbuntuME had 2.6.24, I think). After a few glitches I managed to compile the kernel and its modules, installed the modules and then the kernel. However, I wasnt able to make the initrd image for the new kernel. I did some research on mkinitrd (which was cited by the article I was referring to all the time) and found that it is only shipped with Fedora. I decided to skip creating the initrd image and my worst fears came true.

I rebooted and the boot failed citing some files missing in the /lib directory. Now I am pretty sure that this is as much of a problem with not having an initrd image for the new kernel as having those files missing. I wish I could post some more information but Im at work right now and do not have my personal laptop along. I do intend to reply to this message sometime in the evening with the details of the actual error.

In the meantime, has anyone encountered this issue ? and if so, what are your suggestions. Any help would be appreciated.

Thanks,
Anjum.

You can boot without an initrd if you make some loadable modules resident in the kernel. Compile your kernel again and this time make all of the modules that would be loaded by initrd resident in the kernel.

---------------------
Steve Stites

Thanks Steve! My apologies but im a n00b
So kindly help me with some details
Thanks again

When you compile a kernel you can select for each module whether that module will be compiled as a loadable module (select M) or as a permanent part of the kernel (select Y). You need to select Y for such things as the device drivers for your root partition, your root file system, and anything else that your kernel needs to access the root partition.

The distributions have the problem that if they include everything in the kernel that any hardware configuration might need to be permanent their kernel would be too large to be practical. So the distributions say M for everything. Then they create an initrd tailored to each user's individual needs. The initrd includes the loadable modules that that particular user needs to access his root partition.

People who compile their own kernels can do it either way. Since you can compile your kernel and can't create an initrd I suggest that you do your kernel compile again and set the modules necessary for the kernel to access the root partition to Y. What those modules are depends on your hardware configuration, choice of file system, etc.

---------------------
Steve Stites