I may repeat myself:
You do not need an initrd if all necessary components (filesystem, device driver) are compiled into the kernel. In this case, there is nothing more to do than to add the kernel to your bootloder config. No need to worry about initrd.
But when they are compiled as modules (obviously your previous kernel is like that, since it uses initrd), you need to create an initrd (use mkinitrd) and refer to it in your bootloader configuration. Otherwise the kernel is unable to mount te root filesystem and will not boot. In this case you will know where initrd is located (since you created it yourself).
Last edited by abisko00; 12-03-2004 at 02:12 PM.