On Fri, Jun 01, 2012 at 03:30:28PM +0200, Ralf Corsepius wrote:
On 06/01/2012 02:53 PM, Darryl L. Pierce wrote:
>On Fri, Jun 01, 2012 at 04:28:01AM +0200, Ralf Corsepius wrote:
>>>No, but it sounds like a kernel panic.
>>In my case, it was an obvious kernel panic.
>>
>>AFAIS, the cause was running a Fedora 16 kernel underneath of Fedora
>>17. Preupgrade (rsp. yum and/or grub underneath) obviously did not
>>upgrade grub2.cfg to boot into the Fedora 17 kernel.
>>
>>For me, rebooting into the F17 installation with the F16 kernel
>>underneath and then explicitly removing and reinstalling the
>>fc17-kernel fixed this issue:
>>
>># rpm -qa 'kernel-PAE*'
>>kernel-PAE-3.3.7.fc17.i386
>>kernel-PAE-3.3.7.fc16.i386
>
>Hrm, for me I still have an F16 kernel that seems to be eclipsing the
>F17 kernel:
Presence of an fc16 kernel should not matter and not disturb.
Did you try what I wrote?
What I did was to remove the fc17 kernel and to re-install it.This
fixed the broken grub2.cfg for me.
That is what I did. I knocked out the 3.3.7-1 kernel from both 16 and
17, then installed the 3.3.7-1 F17 kernel and booted. I haven't tried
shutting down yet but will by end of day.
>mcpierce@mcpierce-laptop:~ $ rpm -qa kernel
>kernel-3.3.7-1.fc16.x86_64
>kernel-3.3.7-1.fc17.x86_64
>kernel-3.3.6-3.fc16.x86_64
>
>mcpierce@mcpierce-laptop:~ $ uname -r
>3.3.7-1.fc16.x86_64
Once you're running an fc17 kernel, you can remove all these.
--
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/