| 1 |
On 2011/05/16 11:26 (GMT-0400) Indi composed: |
| 2 |
|
| 3 |
> On Mon, May 16, 2011 at 05:00:02AM +0200, Felix Miata wrote: |
| 4 |
|
| 5 |
>> On 2011/05/15 22:18 (GMT-0400) Felix Miata composed: |
| 6 |
|
| 7 |
>> > I have two Gentoo stanzas in my primary bootloader, one to load the kernel, |
| 8 |
>> > another to chainload Gentoo's Grub. Loading the kernel works, but chainload |
| 9 |
>> > gives error 13 invalid executable format. I named the bzImage copied to /boot |
| 10 |
>> > "kernel-2.6.37-r4f", and symlinked it a vmlinuz. vmlinuz is the name I use in |
| 11 |
>> > the Grub stanzas. Is Gentoo's Grub expecting the kernel to have a particular |
| 12 |
>> > name, and I picked a wrong one? Or maybe what it doesn't like is that I |
| 13 |
>> > uncommented splashimage=(hd0,6)/boot/grub/splash.xpm.gz in menu.lst? |
| 14 |
|
| 15 |
> I always just copy the bzImage to (for example) |
| 16 |
> /boot/vmlinux-2.6.38-gentoo-r5, but the name doesn't really matter as |
| 17 |
> long as it matches your bootloader entry. |
| 18 |
|
| 19 |
I spent more time thinking about what happened, and decided the Grub message |
| 20 |
had to be coming from the master Grub trying to chainload the non-existent |
| 21 |
Gentoo Grub, and finding old data from a partition previously using that |
| 22 |
space, rather than something recognizable as boot code. |
| 23 |
|
| 24 |
>> Why setup didn't get this right via emerge I have no idea, unless it didn't |
| 25 |
>> actually do anything toward actually setting Grub up. If so, it could be |
| 26 |
>> there was already some mismatched Grub code there already from a previous use |
| 27 |
>> of the sectors there that didn't like the file format. |
| 28 |
|
| 29 |
> The install docs are fairly clear that installing the grub pkg is only |
| 30 |
> the first step of setting up the bootloader. |
| 31 |
|
| 32 |
At that point I was seriously burned out on reading and rereading docs on |
| 33 |
install attempt #8 on my 5th day trying. I was so joyful seeing pretty colors |
| 34 |
and no error messages that I couldn't think logically. ;-) |
| 35 |
|
| 36 |
> It seems to me (though I could certainly be wrong) that your best bet |
| 37 |
> really is to perform a "vanilla install" first, as much as your hardware |
| 38 |
> allows. Just to get to know the system before attempting to customize it. |
| 39 |
> :) |
| 40 |
|
| 41 |
Actually after the first or 2nd or some subsequent attempt that was my plan. |
| 42 |
After so much time passed (days, not just hours) and I had good kernel, NFS, |
| 43 |
and MC that I didn't see much point delaying KDE. After the errors |
| 44 |
disappeared around 10 last night and I reported same here I started to wonder |
| 45 |
where to go next on a tired brain. I set qt3support emerging around that |
| 46 |
time, and more than 3 hours later and time for bed its hundred & some |
| 47 |
packages were still emerging. I woke up hours later to goto the bathroom and |
| 48 |
found that done, so set kdm to install. That hundred plus set of packages is |
| 49 |
still emerging now, nearly 6 hours later. Maybe 32 bit 1667MHz & 512M RAM is |
| 50 |
on the skimpy side for installing Gentoo? |
| 51 |
-- |
| 52 |
"The wise are known for their understanding, and pleasant |
| 53 |
words are persuasive." Proverbs 16:21 (New Living Translation) |
| 54 |
|
| 55 |
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! |
| 56 |
|
| 57 |
Felix Miata *** http://fm.no-ip.com/ |
Archives