On Sat, 2010-10-30 at 18:11 -0600, John Mitchell wrote: > Thanks Andy and Ken. > > I suspect that some combination of modules and perhaps a missing > initrd.img file is my issue. >
You don't need an initrd, unless you've created some fairly exotic setup - distros use them because they give a lot more flexibility around mounting the root filesystem, allowing for stuff like RAID / LVM setups, encrypted filesystems, or dealing with the case where a single kernel image needs to work on every possible piece of hardware and filesystem type. What *you* need is probably just a straightforward config that supports your hardware. In particular, it needs the drivers for the disk controller and for the root filesystem - and it needs those drivers as built-ins, not as modules. Running lsmod on Fedora can probably tell you what driver it's using for the controller - if it's a fairly modern SATA-based setup, it's likely to be the standard 'ahci', but on an older machine it might be something chipset-specific (which in my case is 'sata_nv'). Getting those two bits right should give you a booting system, at least. With that working, you can then go looking at the other config options to support the rest of your hardware - sound, network, etc - and anything else you might need or want. Simon
signature.asc
Description: This is a digitally signed message part
-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
