Hrm, for me I still have an F16 kernel that seems to be eclipsing the
F17 kernel:
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
--
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
I also had problems doing an upgrade from F16 to F17 with old kernels
laying around. I though it was because I was using grub2+UEFI so the
installer couldn't find the grub.conf file. I hand-edited, and haven't
had any problems, since, except, I expect the first Kernel upgrade that
comes along will also not find my grub.conf.
I've probably completely setup my boot loader wrongly, but I suppose
that a matter for a separate thread.
I have the same thing, F16 kernel with F17. Panics during shutdown.
Can you provide specifics on how you "hand-edited?"
--
Tim Evans, TKEvans.com, Inc. | 5 Chestnut Court
### End of Message from Tim Evans ###
Well, in my case, I believe Anaconda failed to update my grub
configuration, which resulted in booting a lingering F16 kernel and also
panics on shutdown.
To remedy the situation, I used vim to edit
/boot/efi/EFI/redhat/grub.conf
In my case, the F17 kernel was listed first, and the F16 kernel was
second, but 'default=1' was set, which IIRC, is a zero-based pointer to
which kernel to boot automatically. I changed it to 'default=0' to refer
to the first kernel (the F17 kernel) and everything was okay after a
reboot. After the reboot I verified that I was running the F17 kernel
using 'uname'
--
×-×-×-×-×-×-×-×-×-×-×
Jeffrey A. Gipson
×-×-×-×-×-×-×-×-×-×-×
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
