Im having the same issue described on
http://ubuntuforums.org/showthread.php?t=1312798highlight=grub does
anybody know of a workaround?
--
Default grub2 configuration won't boot through to default OS
https://bugs.launchpad.net/bugs/428570
You received this bug notification because you are a
Hi:
I had an issue with karmic so now am on LTS 8.04. The issue was with
grub2
and I'm wondering if you had read this:
http://ubuntuforums.org/showthread.php?t=1312798highlight=grub
--
Default grub2 configuration won't boot through to default OS
Jason Heblack wrote:
Hi:
I had an issue with karmic so now am on LTS 8.04. The issue was with
grub2
and I'm wondering if you had read this:
http://ubuntuforums.org/showthread.php?t=1312798highlight=grub
This does sound like it could be the same (or similar)
It looks like I'm still having this issue with beta 4 in the karmic
final, although it may or may not have degraded further: the
abovementioned workaround involving a non-zero value for
GRUB_HIDDEN_TIMEOUT does not appear to work, and GRUB boots to a menu on
every occasion; the only case where it
On Thu, Oct 08, 2009 at 02:32:00AM -, Patrick Goetz wrote:
Yes, I understand, that's the point. If grub2 depends on grub-pc,
shouldn't this have updated as well when I updated grub2?
It's an unversioned dependency, so the old version satisfies the
dependency just as well and therefore apt
It's an unversioned dependency, so the old version satisfies the
dependency just as well and therefore apt doesn't bother to upgrade it.
(This may be an error in how the dependency is declared, but it's how it
is right now.)
Can we call this a bug? It seems pointless to have a dummy package
apt-get install grub2 updated the grub2 package to 1.97~beta3-1ubuntu8.
This appears to have fixed the problem, i.e. I ran
grub-install /dev/sda
and then changed the value of GRUB_HIDDEN_TIMEOUT back to 0 (the package
default)
GRUB_HIDDEN_TIMEOUT=0
ran grub-update, and the machine still
Steve Beattie wrote:
Patrick: can you update to the current version of grub2 in karmic and do
grub-install on your boot device (likely /dev/sda, but possibly not). I
am unable to reproduce the behavior you see with the current version of
grub2,
The current version is 1.97~beta3-1ubuntu8. I
The grub2 package itself contains nothing of any note. grub-common and
grub-pc are the packages it depends on that actually do something, and
you'd need to upgrade those. If you saw any effect from upgrading grub2
on its own, it was coincidental.
Package: grub2
Depends: grub-pc
Description: GRand
Yes, I understand, that's the point. If grub2 depends on grub-pc,
shouldn't this have updated as well when I updated grub2?
I noticed the grub problem on the initial install of alpha4 (or the
current daily build, I can't remember which) and worked around it as
outlined in the bug report. When
Patrick: can you update to the current version of grub2 in karmic and do
grub-install on your boot device (likely /dev/sda, but possibly not). I
am unable to reproduce the behavior you see with the current version of
grub2, but I did see it with an earlier install, and updating and
installing the
** Changed in: grub2 (Ubuntu)
Status: New = Triaged
** Changed in: grub2 (Ubuntu)
Importance: Undecided = Medium
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) = Colin Watson (cjwatson)
** Also affects: grub2 (Ubuntu Karmic)
Importance: Medium
Assignee: Colin Watson
12 matches
Mail list logo
