I just upgraded to 17 and had the same problem as
always. Since I have been doing it manually (using
make install in /usr/src/linux) I have had some
bizarre behavior after I first upgrade. Only vmlinuz
and system.map are properly linked to 17. Config was
still linked to 16 and initrd was linked to 12 (having
overridden 16). 12 was the version I first had this
problem with.
After I do make install and then lilo... everything in
boot directory is linked properly.
--- SI Reasoning <[EMAIL PROTECTED]> wrote:
> Actually, he said he upgraded the kernel in that
> message. That is why I thought he might be having
> similar problems.
>
> --- Chmouel Boudjnah <[EMAIL PROTECTED]>
> wrote:
> > SI Reasoning <[EMAIL PROTECTED]> writes:
> >
> > > This might be related to the lack of initrd
> being
> > > created. I have had this problem on both of my
> > last 2
> > > kernel upgrades. As root goto /usr/src/linux and
> > type
> > > "make install" (without quotes). When this is
> > complete
> > > type "lilo". This will allow you to reboot and
> > have
> > > linux come up properly.
> >
> > humm make install call installkernel like
> > kernel-upgrade rpm and he
> > use a new kernel..
> >
> > --
> > MandrakeSoft Inc
> > http://www.chmouel.org
> > --Chmouel
> >
>
> =====
> SI Reasoning
> [EMAIL PROTECTED]
> gnupg/pgp key id 035213BC
>
> __________________________________________________
> Do You Yahoo!?
> Get email at your own domain with Yahoo! Mail.
> http://personal.mail.yahoo.com/
>
=====
SI Reasoning
[EMAIL PROTECTED]
gnupg/pgp key id 035213BC
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
