Comment 3 for bug 475086

Steve Langasek wrote:
> Hi Daniel,
>
> There are several ways that you can wind up booting an old kernel after
> an upgrade. Bug #470490 describes one of the most common, and includes
> instructions on how to correct your menu.lst if this is the problem
> you're having.
>
> Have you previously modified the grub menu.lst configuration on this
> system? Were you prompted on upgrade whether you wanted to keep your
> local modifications to menu.lst, or install the package maintainer's
> version?
>
> ** This bug is no longer a duplicate of bug 470265
> jaunty to karmic upgrade failed to update menu.lst (update-grub missing from kernel-img.conf)
>
> ** Package changed: alsa-driver (Ubuntu) => grub (Ubuntu)
>
> ** Changed in: grub (Ubuntu)
> Status: New => Incomplete
>
>
>
Hi Steve,
Thanks for your attention to my problem. To answer your questions, yes
I did modify my grub menu.lst configuration with the grub editor I had
installed with Ubuntu 9.04. I edited out some of the older kernels that
were listed. When I upgraded to 9.10 I was asked if I wanted to keep my
menu.lst configuration and I answered yes as I have a dual-boot system
with Windows XP on another hard drive and I didn't want to loose access
to that OS. When I found out that the reason I had no sound was because
the kernel did not update I tried installing the 2.6.31.5 kernel that
according to linux.org was the latest stable version. That did not
install properly but in the process my grub/menu.lst file got updated
with the correct kernel that I needed (2.6.31.14-generic). How that
happened I don't know but I'm using that kernel now and everything seems
to be working fine. I have sound, video, internet. I still want to
edit the menu.lst file to remove the 2.6.31.5 kernel that I don't
need. I've gotten conflicting advice on how to do that. The grub
editor app that came with 9.04 worked great. Why was that eliminated?
Daniel
Than