Kevin, If you haven't compiled the IDE driver into your kernel (which you should do if possible), you will need to build an initrd image with the IDE driver in it like Chad suggested previously. The same thing goes for root partitions that use LVM. You need to build an initrd image that has the lvm module so it can load your root partition and load the kernel with the module in order to continue booting. If it's not compiled in the kernel, and you need it to boot your machine, it needs to be in the initrd image (disclaimer: there may be something cool that I don't know about that defies the laws of booting so don't blame me for my ignorance if such a cool thing should exist :) ). Eric On 12/22/06, John T. Hoffoss <john.t.hoffoss at gmail.com> wrote: > > Thanks for the answers guys. > > > > One quick question though: if I have and IDE hdd, do I *have* to > > compile the IDE driver in to the kernel, or can it be modular? And > > does the same apply for any type of hdd, such as SATA? > > I can't think of a situation where I would remove an IDE driver from a > running system, so [for me] there is no reason not to compile it in. > To answer your question, (IIRC!) the driver to access your root > partition must be compiled in the kernel, or you must use an > initrd-type solution. > > -John > > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > tclug-list at mn-linux.org > http://mailman.mn-linux.org/mailman/listinfo/tclug-list >