[3144] in RedHat Linux List
RE: Kernel Upgrading!
daemon@ATHENA.MIT.EDU (Al Longyear)
Thu Nov 7 09:41:33 1996
From: Al Longyear <longyear@sii.com>
To: "'redhat'" <redhat-list@redhat.com>,
"'q80@dimensional.com'"
<q80@dimensional.com>
Date: Thu, 7 Nov 1996 06:17:37 -0800
Resent-From: redhat-list@redhat.com
Reply-To: redhat-list@redhat.com
Did you forget to change the /usr/src/linux/Makefile so that the kernel
was written to the proper directory? (This one always seems to catch me
when I download a full kernel rather than just patch the existing one.
It never fails. I always flub the first build and wonder "what
happened?" --- duh!)
There is a line in the Makefile which says "INSTALL_PATH=/boot", but it
is commented so as to not have any effect. This makes the default
location for the newly built kernel the /vmlinuz file.
Do you have the proper lilo configuration file (/etc/lilo.conf) which
says that the kernel and the boot area is the diskette and not the fixed
disk? If this is not the case then LILO will built the wrong map file
and you will end up using the old one which will load the old kernel.
It is my experience that it is easier to use "make zdisk" rather than
"make zlilo" for the first time. The result is not a LILO diskette, but
a boot diskette which has nothing on it but the kernel. After you have
verified that the kernel will work then you can play with LILO.
p.s.: If you are using modules with the 2.1.7 kernel then make certain
that you have at least the 5.4.9 version of libc.so. (The last time that
I checked, 5.4.10 was the current one.) This library is in the 'private'
directories on tsx-11.mit.edu and sunsite.unc.edu as they are not
"officially" released.
If you attempt to use libc.so.5.4.7 with the 2.1.7 kernel then you will
find that insmod will fail with some very strange error numbers.
This is not a problem with the 2.0 series kernels.
>----------
>From: Proud Kuwaiti[SMTP:q80@dimensional.com]
>Sent: Thursday, November 07, 1996 3:30 AM
>To: redhat
>Subject: Kernel Upgrading!
>
> Hi all, I just upgraded the kernel that was shipped with RedHat
>4.0 "2.0.18" to kernel "2.1.7", and after I did the compiling steps, in
>the Linux kernel release 2.1.xx, and after I rebooted my system with a new
>zlilo boot disk, I found out that my kernel is still the same old one,
>what went wrong? and have anyone experianced this wierd thing? and is
>there a fix to it?
>
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
________________________________________________________________________
http://www.redhat.com/RedHat-FAQ http://www.redhat.com/RedHat-Errata
http://www.redhat.com/RedHat-Tips http://www.redhat.com/mailing-lists
------------------------------------------------------------------------
To unsubscribe: mail -s unsubscribe redhat-list-request@redhat.com < /dev/null
