Anton Graham wrote:
>
> Submitted 31-May-00 by Brian Fleischman:
> | I have updated the kernel 3 times in the last week. Initially started
> | with -9mdksmp, now I am at -12mdksmp. The problem I have is the login
> | page and uname -r always display the -9 kernel version. Why? Where is
> | this information kept so I can update it? I have reconfigured
> | /boot...System.map linked to -12 System.map, etc. I have a separate
> | problem with updating MBR with lilo (previous post). How does
> | /etc/issue get created to display on the login screen and where does
> | uname -r get its info? /proc reflects the -9 kernel also. Am I
> | actually still loading the -9 kernel?
>
> I would say yes. In your /boot directory, you will likely find that
> the vmlinuz symlink still points at vmlinuz-2.2.15-9mdksmp. The
> install-kernel script does not seem to automatically update this
> consistently.
>
> --
> _
> _|_|_
> ( ) * Anton Graham
> /v\ / <[EMAIL PROTECTED]>
> /( )X
> (m_m) GPG ID: 18F78541
> Penguin Powered!
I suppose your kernel is installed
correctly ??
Like this:(in /usr/src/linux)
make dep
make clean
make bzImage
make modules
make modules install (after rename your
/lib/modules to /lib/modules.old)
then:
cp
/usr/src/linux/arch/i386/boot/bzImage
/boot/vmlinuz-2.2.15-xxmdk
(where xx is the EXTRAVERSION-nbr)
cp /usr/src/linux/System.map
/boot/System.map-2.2.15-xxmdk
rm /boot/System.map
ln -s /boot/System.map-2.2.15-xxmdk
/boot/System.map
Then change in /etc/lilo.conf :
image=/boot/vmlinuz-2.2.15-xxmdk
At last: (if lilo is used)
type in console or xterm : lilo
And of course rebout your system.(be
carfull, have a rescue-disk)
If you did it and the pb persist, take a
look at your Makefile in
the linux dir and see if the
EXTRAVERSION= -xxmdk
Eric
--
FRANCE (Be careful, my English can hurt
you)
