DebianThis forum is for the discussion of Debian Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Distribution: Debian Wheezy/Jessie/Sid, Linux Mint DE
As a matter of fact, if you do not have initrd, you should remove the reference to it from you grub or lilo config. That is the line starting with initrd or initrd=
As a matter of fact, if you look in the description for initrd, it is almost never needed to use initrd as opposed to compile IDE and ext3 support into the kernel. I don't understand why Debian (other distro's as well?) insists on using it.
I am not using initrd for years whenever I recompile my kernel.
The issue is, you haven't compiled ramdisk support into your kernel. I don't know if it is faster or more efficient to use the ramdisk/initrd support or no ramdisk/initrd and just boot the entire compiled kernel. I know for most purposes, it is best to compile into the kernel for things you use EVERY boot. For example if your root filesystem is EXT3, then compile it into the kernel. If you only mount EXT3 occasionally, then compile it as a module to conserve memory when your not using it.
Kernelyogi, the point is that you must put into the kernel the access to the filesystems you are going to work with, for example ext3, reiserfs and a couple other filesystems. After that you should be able to boot your kernel without initrd.