On Wednesday 21 January 2004 12:58 am, John T Nelson wrote:
Don't think this is the problem. THere is only one kernel on
this
machine... the FC1 kernel. Problem is that the FC1 upgrade didn't install
all the module support needed. I can boot into FC1 but get lots of errors
complaining about missing modules.
No, this is not what happened. The kernel version you quoted (2.4.20) is NOT
the FC1 kernel, it IS the RHL8 kernel. The right kernel and all modules (a
2.4.22 kernel) are all installed, but the bootloader is not booting the FC1
kernel. You have to tell the bootloader to do so. If you previously had
LILO as your bootloader, this can happen; I had it happen to me. I fixed it
by rerunning /sbin/lilo after tracking down a good LILO package for FC1 and
getting all the files straightened out. It was a mess.
Any chance I can correct this by hand since the installer disk does
not
correct this condition (the installer created the problem in the fist
place)?
I've already described how to do it:
> > This box use LILO? I ran into this with a box; the cure
was getting
> > LILO properly configured for the 2.4.22 kernel used by FC1. This was
> > not trivial, since several LILO support files had been changed in
> > /boot. The modules were removed by the RPM upgrade process, but LILO
> > is still pointing to the old kernel binary. I do not remember the full
> > sequence of steps that were required; if this box CAN use GRUB you will
> > want to use GRUB on it; installing GRUB from scratch isn't too fun,
> > though. To boot the the right kernel you can run mkbootdisk (that is,
> > if the kernel isn't too large to fit on a floppy) and boot from that,
> > or you can boot the install CD in rescue mode to get things mounted to
> > where you can work on them.
--
Lamar Owen
Director of Information Technology
Pisgah Astronomical Research Institute
1 PARI Drive
Rosman, NC 28772
(828)862-5554
www.pari.edu