According to David Hajoglou: While burning my CPU.
>
> I am running RH50, kernel 2.0.35. We started with K2.0.31 and upgraded to
> the 2.0.35 source code. While the compile went just fine, every time I do
> something that is version specific (compile and load a module) I get a
> warning that I have a mod compiled for 2.0.35 and the kernal version is
> 2.0.31. Does anybody know how to fix such a problem?
It looks like you are "using" kernel 2.0.31, check your /etc/lilo.conf to
see where lilo looks for the image at boottime, i presume you use lilo of
course.
uname -a will show the kernel version number and compile date.
Normaly "after" the kernel image has been compiled you copy
/usr/src/linux/arch/i386/boot/zImage to /boot/vmlinuz-2.0.35 for example,
after doing that you would edit /etc/lilo.conf and make a new entry for the
"new" kernel as follows.
{You should already have something like}
boot=/dev/hda
prompt
timeout=300
New entry..
image=/boot/vmlinuz-2.0.35
label=2.0.35
root=/dev/hda2
read-only
Of course the line "root=/dev/hda2" would need to refelect to your system.
Note: The first "image" entry in /etc/lilo.conf is the default boot image.
Now RERUN 'lilo'
Reboot
At the LILO: prompt just type in 2.0.35 <enter>
Then you will have kernel 2.0.35 running.
It would possably be a good idea to do the following, just to make sure
2.0.35 gets compiled with all its modules.
cd /usr/src/linux
make oldconfig (if no changes are required, if changes are needed) then;
make config
make dep clean zImage
make modules modules_install
cp arch/i386/boot/zImage /boot/vmlinuz-2.0.35
edit /etc/lilo.conf as per above.
rerun lilo
reboot
LILO: 2.0.35 <enter>
>
> Thank You
> David Hajoglou
> [EMAIL PROTECTED]
>
--
Regards Richard.
[EMAIL PROTECTED]
