summary |
shortlog | log |
commit |
commitdiff |
tree
first ⋅ prev ⋅ next
Sathish Kuppuswamy [Tue, 11 Jun 2013 18:22:42 +0000 (11:22 -0700)]
Add variable 'grubdisk' to export boot disk
Boot disk name is required by 'gptpriority' grub command to read the
priority of partitions from the GPT disk and set the default
partition to boot accordingly in grub.cfg
BUG=None
TEST=Built the changes along with chromeOS. Verified the value being
exported to grubdisk in grub shell and also the usage of this
variable with "gptprioriry" grub command in grub.cfg.
Change-Id: Ib52de5e2ab32eb9538b5f537d11c549eeb25278d
Reviewed-on: https://gerrit.chromium.org/gerrit/58273
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Queue: Josh Triplett <josh@joshtriplett.org>
Tested-by: Josh Triplett <josh@joshtriplett.org>
Han Shen [Thu, 16 Aug 2012 00:44:32 +0000 (17:44 -0700)]
Fix grub2 for gcc 4.7.
"-melf_x86_64" is a linker option, prefix it with "-Wl".
Gcc prior to 4.7 seems to pass this option to ld, but 4.7 doesn't.
TEST=Built using gcc 4.7
BUG=None
Change-Id: I5908d34fd0f9dc939581a2eaed5cd20d282c6d3a
Reviewed-on: https://gerrit.chromium.org/gerrit/30486
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Han Shen <shenhan@chromium.org>
Tested-by: Han Shen <shenhan@chromium.org>
Shawn Nematbakhsh [Fri, 20 Jul 2012 19:14:39 +0000 (12:14 -0700)]
Fix EFI boot on certain non-Chromebook platforms.
Some non-chromebook platforms cannot EFI boot Chromium OS due to "cannot
allocate protected mode pages" error. This is a very old grub2 bug, and
is worked around in this change. A better fix is to upgrade to a newer
version of grub2, but this has caused big problems in the past. This
change is relatively risk-free because it only takes effect if EFI boot
were to fail.
BUG=32776.
TEST=build image with new grub-mkimage, EFI boot on platform.
Change-Id: Ic332f3af3a771d084189dca7fc2f88b281e653b3
Reviewed-on: https://gerrit.chromium.org/gerrit/28043
Reviewed-by: Micah Catlin <micahc@chromium.org>
Commit-Ready: Shawn Nematbakhsh <shawnn@chromium.org>
Reviewed-by: Shawn Nematbakhsh <shawnn@chromium.org>
Tested-by: Shawn Nematbakhsh <shawnn@chromium.org>
Shawn Nematbakhsh [Fri, 20 Jul 2012 01:20:51 +0000 (18:20 -0700)]
Fix grub2 compile errors.
grub2 does not compile due to strict warning checks. This is fixed by
removing variables that are declared + assigned but never used.
BUG=32776.
TEST=configure / make, copy grub-mkimage binary, then build_image.
Change-Id: I9fe488c06edcde01dfdf244773323a2088285879
Reviewed-on: https://gerrit.chromium.org/gerrit/27961
Tested-by: Shawn Nematbakhsh <shawnn@chromium.org>
Commit-Ready: Shawn Nematbakhsh <shawnn@chromium.org>
Reviewed-by: Micah Catlin <micahc@chromium.org>
Daniel Erat [Wed, 16 Jun 2010 15:51:39 +0000 (08:51 -0700)]
grub2: Add missing inherit-review-settings-ok file
BUG=none
TEST=none
TBR=anush
Review URL: http://codereview.chromium.org/2863006
Nick Sanders [Wed, 9 Jun 2010 23:52:42 +0000 (16:52 -0700)]
Support standard EFI ordering
Bill Richardson [Fri, 14 May 2010 23:58:57 +0000 (16:58 -0700)]
Add variables to grub2 for Chrome OS bringup workarounds.
This adds a temporary hack to grub2, which we're using while the full BIOS
changes aren't yet completed. We set four variables automatically that we
can use in the grub.cfg file to ensure that we get the kernel and rootfs
from the boot device, regardless of which device that is.
Grub refers to the boot device as hd0, hd1, etc. The kernel needs it to be
sda, sdb (and yes, I know that's dependent on the architecture and media,
but so is grub). In addtion, our current BIOS doesn't enumerate the hard
disk in recovery mode, so the first removable drive is hd0, not hd1. Linux
always sees it though.
Grub now sets two variables to specify the rootfs in grub's terms:
grubpartA == (hdX,3)
grubpartB == (hdX,5)
where X is the boot device, so we can pick the right kernel in grub.cfg:
linux $grubpartA/boot/vmlinuz ...
linux $grubpartB/boot/vmlinuz ...
But we also need to provide "rootfs=/dev/sdX" for the kernel.
We'll map this normally:
(hd0) -> sda
(hd1) -> sdb
etc.
But if the booted media is removable, we'll map like this:
(hd0) -> sdb
(hd1) -> sdc
etc.
and so grub can set two more variables:
linuxpartA == /dev/sdX3
linuxpartB == /dev/sdX5
and now our grub.cfg can say:
linux $grubpartA/boot/vmlinuz root=/dev/$linuxpartA ...
linux $grubpartB/boot/vmlinuz root=/dev/$linuxpartB ...
And this will let the same grub.cfg file work on any boot device, regardless
of how many others are plugged in or how they're numbered.
Note that once we've switched to our official BIOS we'll no longer be
needing grub at all, so this is just temporary.
Review URL: http://codereview.chromium.org/2113004
Bill Richardson [Thu, 1 Apr 2010 22:26:56 +0000 (15:26 -0700)]
Import grub-1.97.tar.gz release from gnu.org