[Bug 822644] Re: "Previous Kernels" Entry should be there even from clean install to avoid breaking boot entries

jessesmith 822644 at bugs.launchpad.net
Mon Sep 17 21:43:20 UTC 2012

I have also run into this problem. On my system Windows started out as
option "4" on GRUB2, so I changed /etc/defaults/grub to reflect this and
ran "sudo update-grub". All went well until the first kernel update,
which added the "Previous kernels" entry and bumped Windows down a
notch. My computer would then default to the memory check instead of
Windows. Updating the grub configuration file to default to entry "5"
fixes this issue.

This bug occurs using GRUB 2 on Ubuntu 12.04 LTS.

I see two possible solutions to this problem:

1. As the original poster suggested, create an empty "Previous kernels"
entry in the GRUB menu at install time to avoid it bumping entries

2. Force the "Previous kernels" entry to be the last menu item displayed
in the GRUB boot menu, which will leave the existing menu items in their
proper places.

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.

  "Previous Kernels" Entry should be there even from clean install to
  avoid breaking boot entries

Status in “grub2” package in Ubuntu:

Bug description:
  Example of problem:
  1) Do a clean install of Natty
  2) Edit grub.cfg and change DEFAULT to 3 to make Windows the default OS
  3) Update grub

  All is well until an updated kernel creates a new grub entry called "previous kernels". Now my friends machine doesn't boot because DEFAULT=3 gives a memory check (or somthing like that). So I have to manually edit grub.cfg again to make DEFAULT=4.

  Example solution:
  1)A clean install of Grub already has a "previous kernel" entry, which at this time is an empty list.
  2)Edit grub.cfg as you wish
  3)Update grub

  The DEFAULT boot entry will retain it's integrity.

To manage notifications about this bug go to:

More information about the foundations-bugs mailing list