> When I run the rpm -qa | grep kernel command I get the following:
Okay, so the RPM database thinks these packages have been installed.
It's possible that they are corrupted, though - `rpm -V kernel' will
tell you if the right files are indeed in the right place.
Quote:> Lilo.conf seems to have the right entry as well;
2.2.14, I presume?
> and there is no other entry for the old kernel.
> Running /sbin/lilo gives me;
> Added linux *
So, when you boot, it should load the 2.2.14 kernel. What's the
output of uname -a now?
Quote:> You should know that I do run NT boot loader in order to invoke
> linux but this shouldn't matter right?
Correct, assuming that the NT bootloader points to the boot record
where lilo is installed (I don't know how it works, but I assume
Quote:> ...still can't load those modules and I'm also not able to mount
> any fat partitions as well; this seems to me a related problem where the
> old kernel is still active (namely, /lib/modules/2.2.14-5.0/fs contains
> the fs modules to access these partitions!)
If uname -a returns the 2.2.14 kernel, and you're having problems with
the modules, it might be because of the config file where the module
loader looks up which modules to load.
Quote:> Should I reinstall all of RH6.2 or just all kernel related rpms?
> Or should I simply download the lastest kernel (2.2.16?) and recompile
> and install a brand new one?
It sounds as though your kernel package installation is somehow
screwed up. No need to reinstall all of RH6.2, though. I wouldn't
recommend simply reinstalling the kernel packages either, unless
you're confident about what you're doing - some config. files were set
up to match your hardware when you installed, and it's possible that
these would be deleted or overwritten (*).
I would suggest that the best fix is to install the updated 2.2.16
kernel RPM's that you will find on the Red Hat support site - you just
need to download and install the RPM's, no need to recompile. You
should do this anyway, for security reasons. The announcement (in the
`security fixes' section) gives a link to how to perform this kernel
upgrade in a safe way.
If downloading these packages is too expensive or time consuming,
another option is to recompile the kernel from the sources you have
(though this does leave you open to the security holes that are fixed
in 2.2.16). To do this, you will have to know about your hardware,
though it's quite likely that the default kernel config file that
ships with Red Hat will work. The Red Hat documentation contains
instructions on how to recompile - follow them to the letter and you
should be safe. The golden rule is to make sure that you have a
bootable kernel in /boot/ that also has an entry in /etc/lilo.conf,
and preferably one on a boot floppy too.
(*) When springcleaning a recent installation, I accidentally removed
the kernel-pcmcia-cs package. No problem, I thought - the RPM file
was still on my hard disk, so all I had to do was reinstall it.
WRONG! The deinstallation process had removed the file containing the
hardware configuration (and the flag that says that PCMCIA is allowed
to be used), and reinstallation of the files did not re-probe for
these values. I had to enter the controller type, excluded IRQ's,
etc. by hand in order to get it working.
University of Cambridge, Zoology Department, Downing Street, CAMBRIDGE CB2 3EJ