Latest Kernel causes reboot hell

[Louis Lagendijk]

On Mon, 2009-12-07 at 20:07 +0000, Chris wrote:
> >-----Original Message-----
> >From: Marc Wilson [mailto:msw at cox.net]
> >Sent: Monday, December 7, 2009 01:37 PM
> >To: 'Community assistance, encouragement,	and advice for using Fedora.'
> >Subject: Re: Latest Kernel causes reboot hell
> >
> >On Mon, Dec 7, 2009 at 10:44 AM, Chris <racerx at makeworld.com> wrote:
> >
> >> Currently, I tossed on Ubuntu just so I can get some work done however, would really prefer to be back running F12.
> >
> >Other than that it let you make a snarky Ubuntu remark, why would you
> >need to replace F12 "just so that you can get some work done"?  It
> >would seem obvious that all you have to do is not perform the latest
> >upgrade until whatever happened to it gets fixed.
> >
> >Oh, wait... that would't let you version-chase.  After all, apparently
> >software with lower version numbers magically ceases to work.
> >
> >There, that's MY snarky remark.
> >
> >Gods, people, if you want to use Ubuntu, go use Ubuntu already... no
> >need to tell everyone about it.
> 
> *IF* I really wanted to make a "snarky" remark I would have inserted something more appropriate like windows however, I thought my question was certainly genuine enough. 
> 
> As I did mention in the post - I did exactly that, I updated all but the kernel stuff (second time around) and mentioned that all worked well. Then,  simply stated that the newest kernel seems to have caused a break (in my system at least) and felt I might say something to see if anyone else had the same experience, and if they did - how did they rectify it.
> 
> I apologize to you, Marc, if me question infuriated you to the point to get upset. I have to believe that others didn't see it the same fashion as you.

Chris, I think your question was correct. 
The best way to avoid the problem might be to get grub to display the
list of installed (assuming that the original F12 kernel worked for you)
and select that kernel to boot from. Change the default line
in /etc/grub.conf to automate that.....