On 2011/05/16 11:26 (GMT-0400) Indi composed:

On Mon, May 16, 2011 at 05:00:02AM +0200, Felix Miata wrote:

 On 2011/05/15 22:18 (GMT-0400) Felix Miata composed:

 >  I have two Gentoo stanzas in my primary bootloader, one to load the kernel,
 >  another to chainload Gentoo's Grub. Loading the kernel works, but chainload
 >  gives error 13 invalid executable format. I named the bzImage copied to 
/boot
 >  "kernel-2.6.37-r4f", and symlinked it a vmlinuz. vmlinuz is the name I use 
in
 >  the Grub stanzas. Is Gentoo's Grub expecting the kernel to have a particular
 >  name, and I picked a wrong one? Or maybe what it doesn't like is that I
 >  uncommented splashimage=(hd0,6)/boot/grub/splash.xpm.gz in menu.lst?

I always just copy the bzImage to (for example)
/boot/vmlinux-2.6.38-gentoo-r5, but the name doesn't really matter as
long as it matches your bootloader entry.

I spent more time thinking about what happened, and decided the Grub message had to be coming from the master Grub trying to chainload the non-existent Gentoo Grub, and finding old data from a partition previously using that space, rather than something recognizable as boot code.

 Why setup didn't get this right via emerge I have no idea, unless it didn't
 actually do anything toward actually setting Grub up. If so, it could be
 there was already some mismatched Grub code there already from a previous use
 of the sectors there that didn't like the file format.

The install docs are fairly clear that installing the grub pkg is only
the first step of setting up the bootloader.

At that point I was seriously burned out on reading and rereading docs on install attempt #8 on my 5th day trying. I was so joyful seeing pretty colors and no error messages that I couldn't think logically. ;-)

It seems to me (though I could certainly be wrong) that your best bet
really is to perform a "vanilla install" first, as much as your hardware
allows. Just to get to know the system before attempting to customize it.
:)

Actually after the first or 2nd or some subsequent attempt that was my plan. After so much time passed (days, not just hours) and I had good kernel, NFS, and MC that I didn't see much point delaying KDE. After the errors disappeared around 10 last night and I reported same here I started to wonder where to go next on a tired brain. I set qt3support emerging around that time, and more than 3 hours later and time for bed its hundred & some packages were still emerging. I woke up hours later to goto the bathroom and found that done, so set kdm to install. That hundred plus set of packages is still emerging now, nearly 6 hours later. Maybe 32 bit 1667MHz & 512M RAM is on the skimpy side for installing Gentoo?
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Reply via email to