f-16 Grub2 config. Problem -

[Bob Goodwin]

On 14/01/12 14:38, Mike Chambers wrote:
> On Sat, 2012-01-14 at 14:26 -0500, Bob Goodwin wrote:
>> .
>>
>>          And everything works pretty much the way I would like it to
>>          except that now I have to select the kernel version to boot else
>>          it boots to the older one.
>>
>>          The grub screen shows them listed in the following order and
>>          defaults to  the third line 3.1.0-7.fc16.x86_64 which I believe
>>          is not what it should do?
>>
>>              3.1.7-1.fc16.x86_64
>>              3.1.7-1.fc16.x86_64 Recovery Mode
>>              3.1.0-7.fc16.x86_64
>>              3.1.0-7.fc16.x86_64 Recovery Mode
>>
>>          Assuming that 3.1.7-1.fc16.x86_64 is the later version how do I
>>          fix that?
> On your grub2.cfg file, check the top (below) and see what it has for
> default=...
>
> # DO NOT EDIT THIS FILE
> #
> # It is automatically generated by grub2-mkconfig using templates
> # from /etc/grub.d and settings from /etc/default/grub
> #
>
> ### BEGIN /etc/grub.d/00_header ###
> if [ -s $prefix/grubenv ]; then
>    load_env
> fi
> set default="0"
>
>
> Might be 1 or something else.  If so, change it to 0 and you do NOT have
> to run the command it says to run.  Just editing is enough.  Reboot and
> test.
>


        I'm stymied, file is different! Perhaps because my installation
        was from a "live USB" version?

            ### BEGIN /etc/grub.d/00_header ###
            if [ -s $prefix/grubenv ]; then
               load_env
            fi
            set default="${saved_entry}"
            if [ "${prev_saved_entry}" ]; then
               set saved_entry="${prev_saved_entry}"
               save_env saved_entry
               set prev_saved_entry=
               save_env prev_saved_entry
               set boot_once=true
            fi

            function savedefault {
               if [ -z "${boot_once}" ]; then
                 saved_entry="${chosen}"
                 save_env saved_entry
               fi
            }

        Maybe I need to create a new grub2? That would be a science project!

        I've done the last several installs that way but this is a new
        problem.

        Bob