8.4. Making the LFS System Bootable
w.mess at freenet.de
Fri Oct 31 10:39:46 PDT 2008
Wolfgang Messingschlager wrote:
> Ken Moffat wrote:
>> On Tue, Oct 28, 2008 at 10:53:12PM +0100, Wolfgang Messingschlager wrote:
>>> Wolfgang Messingschlager wrote:
>>> Hi all,
>>> I have meanwhile tried to build a kernel with EXT2 and EXT3 within the
>>> # egrep '(EXT2|EXT3)' .config
>>> # CONFIG_EXT2_FS_XIP is not set
>>> but without an initrd line in /boot/grub/menu.lst I get the well-known
>>> kernel panic. What is important during kernel configuration, so that no
>>> initrd file is needed?
>> Sorry for not replying earlier, I got confused by your partition
>> numbers (I had thought they could not exceed 15 - my thought was
>> wrong), and missed your reference to modules.
>> As you say, for everyone not using an initrd, the filesystem for
>> '/' has to be compiled in. You have now compiled in ext2, but a
>> recent distro will usually use ext3.
> thanks for your quick reply. I will try to build another KERNEL with
> Wolfgang Messingschlager
meanwhile I did
- make mrproper
- make menuconfig (CONFIG_EXT3_FS=y)
- make modules_install
- cp -v arch/i386/boot/bzImage /boot/vmlinuz-220.127.116.11
- cp -v .config /boot/config-18.104.22.168
- cp -v System.map /boot/System.map-22.214.171.124
I added the lines
title LFS kernel 126.96.36.199
kernel /vmlinuz-188.8.131.52 root=/dev/hdb20 ro
This caused the following errors during boot
VFS: cannot open root device "hdb20" or unknown block (0,0)
Please append a correct "root=" boot option; here are the available
Kernal panic - not syncing: VFS: Unable to mount rootfs on unknown -
If I add the initrd file to /boot/grub/menu.lst the kernel is bootable.
I use only EXT2, EXT3 and swap partitions. And my .config file is
egrep '(EXT2|EXT3)' .config
# CONFIG_EXT2_FS_XIP is not set
What is necessary to do in order not to need a initrd generated with
mkinitrd? Unfortunately mkinitrd is not available in the chroot environment.
Shall I attach my .config file?
More information about the lfs-support