why I can not use the 3.2 kernel

[Tom H]

Resending in plain text.

On Mon, Nov 19, 2012 at 6:38 AM, Tom H <tomh0665 at gmail.com> wrote:
> On Mon, Nov 19, 2012 at 5:37 AM, Chen Liang <slimhigh at gmail.com> wrote:
>>
>> The output of the script at [1] is in the RESULT.txt. And the boot menu
>> when I startup shows below:
>>
>> entering in the Previous Linux versions option shows :
>> So there is not a 3.2 kernel options.
>>
>> 2012/11/19 Tom H <tomh0665 at gmail.com>
>>>
>>> On Sun, Nov 18, 2012 at 8:29 PM, Chen Liang <slimhigh at gmail.com> wrote:
>>> >
>>> > slim at lab:~$ sudo update-grub
>>> > [sudo] password for slim:
>>> > Searching for GRUB installation directory ... found: /boot/grub
>>> > Searching for default file ... found: /boot/grub/default
>>> > Testing for an existing GRUB menu.lst file ... found:
>>> > /boot/grub/menu.lst
>>> > Searching for splash image ... none found, skipping ...
>>> > Found kernel: /boot/vmlinuz-3.2.0-34-generic
>>> > Found kernel: /boot/vmlinuz-3.2.0-33-generic
>>> > Found kernel: /boot/vmlinuz-3.2.0-31-generic
>>> > Found kernel: /boot/vmlinuz-3.0.0-20-generic
>>> > Found kernel: /boot/memtest86+.bin
>>> > Updating /boot/grub/menu.lst ... done
>>> >
>>> > The 3.2 kernel titles do show in the menu.lst, but when I restart my
>>> > computer, I can't see the options. I really don't know why!
>>>
>>> What's the output of the script at [1]?
>>>
>>> You're updating your grub1 menu but it may be that you're, somehow,
>>> booting from grub2.
>>>
>>> 1. http://sourceforge.net/projects/bootinfoscript/files/bootinfoscript/
>
> The picture clearly shows that it'd grub2 (grub 1.99-12ubuntu5) that's
> controlling your boot through "boot/grub/grub.cfg" and not grub1. So the
> "menu.lst" that you're generating with "update-grub" has no influence on
> your boot menu.