On 8 Apr 2003 at 13:54, Marc Wiesenhütter wrote:
Hi List,
well, this didn't work for me. I'm using SuSE 8.0 dual athlon 1GB ram. I installed the downloaded k_smp-2.4.18-243.i386.rpm kernel and proceeded like told in the announcement. rebootet, kernel panic. /etc/sysconfig/kernel: INITRD_MODULES="jbd ext3" new one: INITRD_MODULES="swap ext3 jbd" didn't change anything, so rechanged to
You were not told to write "swap ext3 jbd' into initrd but (from your old entry INITRD_MODULES="jbd ext3") just write INITRD_MODULES=" ext3 jbd". And don't forget to start lilo after that!
the old one. what helped was changing my lilo.conf to append = "noinitrd" what i'm wondering about is, mount shows me, all my partitions are mounted ext3 as it want them, but i thought noinitrd would change them to be mounted ext2. so, is there any problem changing my lilo.conf that way and what should i know? or did i miss any discussion? thanks and sorry if it's just stupid.
My explanation: If you do not use initrd that means: during bootup your root- filesystem can only be mounted with a filesystem type for which the support is in the kernel. That's ext2. You can boot, because it is possible to mount ext3 as ext2. Later (when the mount of the filesystems is done) the /etc/fstab ist there and also /lib/modules is available. So the ext3 module can be found and ... here we are. A problem might be that after a crash there will be _no_ journal recovery from your "journaled" root-filesystem (ext2 does not suppport journaling). You only have the "normal" fsck. So if you really need the benefits of a journaling filesystem for your root-filesystem you need to have the module loaded during startup! Andreas