From: Gabriel Paubert <paubert@iram.es>
To: Matt Sealey <matt@genesi-usa.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: 2.6.26 does not boot on Pegasos
Date: Tue, 15 Jul 2008 17:59:44 +0200 [thread overview]
Message-ID: <20080715155944.GA11881@iram.es> (raw)
In-Reply-To: <487CC1F5.5090706@genesi-usa.com>
On Tue, Jul 15, 2008 at 04:27:49PM +0100, Matt Sealey wrote:
> If you built this kernel yourself, you need to do it from a system with
> an up-to-date binutils (2.18) otherwise, it does this.
>
Thanks, this is likely the problem. The distribution is Debian stable
with all security udates but the binutils are still 2.17. I was also
wondering why the zImage was exploding from 2 to 5MB and why it spent
so much time in gzip at the end of a build.
Trying to add Lenny source does not help, bummer. Aptitude fails
with an error message like "Dynamic MMap ran out of room".
Regards,
Gabriel
next prev parent reply other threads:[~2008-07-15 16:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 10:00 2.6.26 does not boot on Pegasos Gabriel Paubert
2008-07-15 10:05 ` Benjamin Herrenschmidt
2008-07-15 10:45 ` Gabriel Paubert
2008-07-15 14:17 ` David Woodhouse
2008-07-15 15:27 ` Matt Sealey
2008-07-15 15:59 ` Gabriel Paubert [this message]
2008-07-18 12:14 ` Matt Sealey
2008-07-22 17:54 ` Segher Boessenkool
2008-07-15 16:15 ` Jon Smirl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080715155944.GA11881@iram.es \
--to=paubert@iram.es \
--cc=linuxppc-dev@ozlabs.org \
--cc=matt@genesi-usa.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).