Another compile problem

[windoze killa]

After compiling my kernel and amazingily being able to boot, I have a question about *.img files. Under the original install and also a subsequent upgrade there are 2 img files in my /boot directory.

linux-2.2.4.img and
linux-2.4.7-10.img

I don't exactly know what these are for other than grub seems to need them to boot. After compiling 2.4.19 I expected to see something like linux-2.4.19.img but there isn't one. Why not? And how do I create one?

[rapture]

Have you even bothered searching on google?? I found some help first try. Here's the link:

Click Me!!! (http://www.google.com/linux?hl=en&lr=&ie=ISO-8859-1&q=making+initrd+image&btnG=Google+Search)

[windoze killa]

Thank you for your reply and yes I did do a search but didn't find much. It probably would have helped if I knew I had to search for something called an initrd image.

[windoze killa]

Having had a quick browse thtough some of the links it appears that I do not need one. It is only needed if you have a scsi adapter or ext3 fs being loaded as a module. Does having an IDE CDRW class as having a scsi device? It doesn't load from lilo that I can remember so I am assumming I can delete that line from grub. Would that be correct?

[mdwatts]

Whenever I compile a new kernel, I create a new initrd as I always select my filesystem support to be modules.

Usually my initrd includes

ext3
jbd
scsi_mod
usbcore

If you have compiled your root/boot partition filesystem support into the kernel, I would suggest you try booting the new kernel without creating a new initrd.

If problems, you can always boot the previous kernel and then create a initrd for the new kernel.

[windoze killa]

I have booted the new kernel without the initrd.img using lilo and it worked fine. It was just grub was having problems so I will try it without the line calling for the image file. I like grub a little better than lilo, it is a little more asthetically pleasing.

**** that sounded flowery.