| 1 |
On Mon, May 16, 2011 at 05:00:02AM +0200, Felix Miata wrote: |
| 2 |
> On 2011/05/15 22:18 (GMT-0400) Felix Miata composed: |
| 3 |
> |
| 4 |
> > I have two Gentoo stanzas in my primary bootloader, one to load the kernel, |
| 5 |
> > another to chainload Gentoo's Grub. Loading the kernel works, but chainload |
| 6 |
> > gives error 13 invalid executable format. I named the bzImage copied to /boot |
| 7 |
> > "kernel-2.6.37-r4f", and symlinked it a vmlinuz. vmlinuz is the name I use in |
| 8 |
> > the Grub stanzas. Is Gentoo's Grub expecting the kernel to have a particular |
| 9 |
> > name, and I picked a wrong one? Or maybe what it doesn't like is that I |
| 10 |
> > uncommented splashimage=(hd0,6)/boot/grub/splash.xpm.gz in menu.lst? |
| 11 |
> |
| 12 |
|
| 13 |
|
| 14 |
I always just copy the bzImage to (for example) |
| 15 |
/boot/vmlinux-2.6.38-gentoo-r5, but the name doesn't really matter as |
| 16 |
long as it matches your bootloader entry. |
| 17 |
|
| 18 |
> |
| 19 |
> Why setup didn't get this right via emerge I have no idea, unless it didn't |
| 20 |
> actually do anything toward actually setting Grub up. If so, it could be |
| 21 |
> there was already some mismatched Grub code there already from a previous use |
| 22 |
> of the sectors there that didn't like the file format. |
| 23 |
> |
| 24 |
|
| 25 |
The install docs are fairly clear that installing the grub pkg is only |
| 26 |
the first step of setting up the bootloader. |
| 27 |
|
| 28 |
It seems to me (though I could certainly be wrong) that your best bet |
| 29 |
really is to perform a "vanilla install" first, as much as your hardware |
| 30 |
allows. Just to get to know the system before attempting to customize it. |
| 31 |
:) |
| 32 |
|
| 33 |
-- |
| 34 |
caveat utilitor |
| 35 |
♫ ❤ ♫ ❤ ♫ ❤ ♫ |
Archives