On Sat, Oct 30, 2010 at 04:41:12PM -0600, John Mitchell wrote: > > I don't think this is a 'grub' error -- perhaps a grub user error. I built > a kernel using my existing .config file so I expect it to be good. However, > my existing kernel uses a initrd.img file but I don't know how to create one > of those? I'm not even sure I need one? It wasn't mentioned in the > book-6.7? > Oh dear. [ /me shakes his head sadly ]
We don't use initrds - they are distro-specific, and I don't have a clue how to create one. But yes, if you boot a kernel with an initrd, you need to make a fresh initrd for each new kernel. Here, we assume you will build everything required to boot into the kernel, not as modules, Specifically, disk drivers, filesystems (at a minimum the filesystem for your LFS rootfs), and probably the console driver (if you are using kms, you might need to specify firmware) - I sort of guess that even distros might not build the console as a module, but you never know. The best place to start is on your *host* system. If possible, boot into single user mode, ideally without a graphical login (because less will have been loaded) and then 'lsmod'. After that, match the module names to .config options and try to work out which are *necessary* (a distro might load a lot of modules that don't check for particular hardware). Then reconfigure your LFS kernel by changing those options from M to Y. After a few repeats, you should get there. Until you can login on the new kernel, best to save each variant of the .config, just in case anything happens, because you won't be able to examine /proc/config.gz if the boot fails. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
