Kernel Panic with 2.44.22-1.2166

stucklenp stucklenp at charter.net
Fri Feb 13 03:59:19 UTC 2004


Have you tried removing the broken kernel and using "yum update?"


----- Original Message ----- 
From: "Bobby Ryan Newberry" <brnewber at unity.ncsu.edu>
To: <fedora-list at redhat.com>
Sent: Thursday, February 12, 2004 9:45 PM
Subject: Re: Kernel Panic with 2.44.22-1.2166


> >First you have to get into a running shell.  If your machine has both the
> >SMP and the UP kernel installed, you might try booting the "other one"
> >(i.e. if the SMP one is leading to the kernel panic, try the UP one.)  If
> >you don't have a kernel installed that you can boot into, then you'll
want
> >to boot into rescue mode.  Boot from your original boot media, entering
> >"linux rescue" at the boot prompt.  Finish booting up, and you will be
> >prompted that the system is going to mount your partitions under
> >/mnt/sysimage.  After continuing, you will be dropped at a shell prompt.
> >There you will be able to recreate your initrd.  You'll want to use the
> >mkinitrd utility in order to do this.  The simpliest thing is to just run
> >it without any arguments, as it will then give you an example you can
> >follow.  Basically, you'll want to run something like this:
> >
> >mkinitrd -f /boot/initrd-2.4.21-9.EL.img 2.4.21-9.EL
> >
> >Course you'll have to substitute the appropriate versions into the
command
> >(in place of 2.4.21-9.EL.)
> >
> >- jkt
>
>
> I tried this, and the kernel continues to panic with the same errors. One
thing is, I can still boot into 2.44.22-1.2149 normally, it's just the when
I try to boot into the new one that is giving my the problem.
>
>
>
> -- 
> fedora-list mailing list
> fedora-list at redhat.com
> To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
>





More information about the users mailing list