1 |
That's an excellent utility, I'll definitely add it to my toolbox, thanks. |
2 |
|
3 |
I actually was able to solve my problem myself: shortly after posting I |
4 |
found a post by renergy on the forums: |
5 |
|
6 |
http://forums.gentoo.org/viewtopic-p-6988228.html |
7 |
|
8 |
It looks like the magic parameters to grub2-install are --root-directory |
9 |
and --boot-directory. Annoyingly, --root-directory is not listed in the |
10 |
help output or man page, so I had no easy way of knowing it existed. But at |
11 |
least everything works now. |
12 |
|
13 |
On Thu, Mar 22, 2012 at 3:32 PM, Maxim Wexler <maxim.wexler@×××××.com>wrote: |
14 |
|
15 |
> Here's a marvelous program crying out for an ebuild; |
16 |
> |
17 |
> https://launchpad.net/boot-repair |
18 |
> |
19 |
> It's part of my Ubuntu setup. With one click it goes out and finds all |
20 |
> the boot partitions on your hd(s) and automatically writes the proper |
21 |
> grub2 configuration for them. It even pastebins a copy of grub.cfg |
22 |
> for troubleshooting purposes, though I have never needed it, sof far. |
23 |
> When you boot all your OSes are there in the menu ready to be |
24 |
> selected. In my case Ubuntu, Gentoo and Sabayon. . |
25 |
> |
26 |
> On 3/21/12, Julian Simioni <julian.simioni@×××××.com> wrote: |
27 |
> > Hi all, |
28 |
> > I'm working on the exciting and challenging task of installing Gentoo |
29 |
> > on a new Macbook Pro with grub2 and EFI. I've got things booting, but |
30 |
> > every time grub complains of many missing commands including search, |
31 |
> > echo, and most surprisingly '['. It also can't find any modules, and |
32 |
> > in order to get everything to work I had to specify about 10 modules |
33 |
> > to be built in using grub2-mkimage. This feels a little suboptimal to |
34 |
> > me, but I can't figure out where various things need to be for grub to |
35 |
> > find them happily. |
36 |
> > |
37 |
> > My partition layout at least is simple since I don't plan on dual |
38 |
> booting: |
39 |
> > /dev/sda1: big root partition using ext4 |
40 |
> > /dev/sda2: 200MB vfat EFI partition, set to bootable (yes this should |
41 |
> > be sda1: I didn't know you needed an EFI partition until after I had |
42 |
> > already made the root partition and started installing things. I was |
43 |
> > able to add this partition later with gparted) |
44 |
> > |
45 |
> > Of course I'm using GPT, not MBR. |
46 |
> > |
47 |
> > On /dev/sda2 I've got the grub2 image at /EFI/BOOT/BOOTX64.EFI as is |
48 |
> > standard, and I have been mounting /dev/sda2 at /boot/efi. I can put |
49 |
> > either a grub2 image or a 3.3 kernel with EFI stub support at |
50 |
> > /EFI/BOOT/BOOTX64.EFI and it gets detected just fine, so I'm on the |
51 |
> > right track. |
52 |
> > |
53 |
> > I've tried messing with various permutations of the -p parameter to |
54 |
> > grub2-mkimage, but haven't gotten anywhere. Right now the *.mod and |
55 |
> > *.lst files from /usr/lib/grub/x86_64-efi/ can be found at both |
56 |
> > /boot/grub2/x86_64-efi and /boot/efi/EFI/BOOT/. Where is it that they |
57 |
> > actually should be? |
58 |
> > |
59 |
> > Thanks, |
60 |
> > Julian |
61 |
> > |
62 |
> > |
63 |
> |
64 |
> |