When I installed RH 5.1 (with the 2.0.34-0.6 kernel) I couldn't mount my
Fat32 partition. it either said vfat was an unsopported fs type or there
was no valid vfat fs on the disk. So I went to rebuild the kernel but
alas there was no source. So now Red Hat released the 2.0.34-1 RPM and I
upgraded to that (foolishly using the -U flag instead of the -i flag). I
also installed the source so I could customize it. It completely removed
the 2.0.34-0.6 kernel and now it doesn't boot all the way...=< I don't
remember the exact message, something about not being able to umnount
the old root. I'll try it again tonight and give the exact message. But
I've historically been unable to add a newer kernel to my system. This
is how I've been (trying) to do it:

make [x/menu]config
make dep ; make clean
make boot
make modules
<move old libs to different directory if rebuilding same version of
kernel>
make modules_install
cp arch/i386/boot/zImage /boot/vmlinuz<version>
vi /etc/lilo.conf <add new kernel>
lilo
reboot

If I've missed something crucial please let me know. Where does the
initrd image come into play, I'm not sure what it does but I've also
tried making a new initrd when adding a newer version kernel and
specifying that in lilo.conf, no help there either. Usually waht happens
after I do all this is the computer boots but without ppp support or the
ability to recompile the kernel anymore. Anyhow If someone can spot
something I'm goofing up here I'ld be grateful. I'm going to try using
the rescue.img boot disk tongiht and see if that helps.
begin:          vcard
fn:             Justin Georgeson
n:              Georgeson;Justin
org:            Institute for Advanced Technology
adr:            4030-2 W. Braker Ln.;;;Austin;Tx;78759;USA
email;internet: [EMAIL PROTECTED]
title:          System Administrator
tel;work:       (512)232-4421
tel;fax:        (512)471-9096
x-mozilla-cpt:  ;0
x-mozilla-html: FALSE
version:        2.1
end:            vcard

Reply via email to