I had this same problem with my system when I compiled a new kernel. The
fix consists of:
a) Booting the new kernel
b) cat /proc/version > /lib/modules/2.2.x/.rhkmvtag {2.2.x is the NEW
kernel version}
c) making a modification to rc.sysinit as shown in the file snippit
below
d) reboot your machine
You may also need to edit the rc.sysinit file to look in 2.2.x module
directories as well as 2.0.x. I believe on a 5.2 system the script is setup
to only look in 2.0.x directories.
--------excerpt from rc.sysinit------------------
# Set up kernel version-dependent symlinks.
rm -f /lib/modules/preferred
if [ -n $USEMODULES ]; then
ktag="`cat /proc/version`"
mtag=`grep -l "$ktag" /lib/modules/2.*/.rhkmvtag`
^^^^^
If I remember correctly, on a 5.2 system the above line is:
mtag=`grep -l "$ktag" /lib/modules/2.0.*/.rhkmvtag`
Hope that helps.
------------------------------------------------------
Another message from Jer Wiebe
Find me at...
email: [EMAIL PROTECTED]
ICQ: 4945359
>
> Redhat removes the symbolic link in /boot called preferred at boottime,
take
> a look at /etc/rc.d/rc.sysinit.
> As far as i can tell the next few lines looks for the kernel version
number
> with 'cat /proc/version' the next part is magic, i rather think it looks
for
> an extention like 2.2.7-1 it uses a script called "rhkmvtag"
> RedHatKernelMakeVersionTag so i think maybe the thing to do is rename the
> image in /boot as follows.
>
P.S. My experience was that you don't need an extension on the kernel
version. But I download kernels from ftp.kernel.org and don't bother with
the rpm'ed kernels.
