From: Matt Sealey <matt@genesi-usa•com>
To: Gabriel Paubert <paubert@iram•es>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs•org>
Subject: Re: 2.6.26 does not boot on Pegasos
Date: Fri, 18 Jul 2008 13:14:12 +0100 [thread overview]
Message-ID: <48808914.20702@genesi-usa.com> (raw)
In-Reply-To: <20080715155944.GA11881@iram.es>
Gabriel Paubert wrote:
> 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.
Note to the linux-ppc guys; is there any changelog entry which reports
this requirement somewhere? I didn't find one...
> Thanks, this is likely the problem. The distribution is Debian stable
> with all security udates but the binutils are still 2.17.
That's generally the problem we had with SuSE 10.3. Debian stable
should be updated by Christmas.. :D
> Trying to add Lenny source does not help, bummer. Aptitude fails
> with an error message like "Dynamic MMap ran out of room".
Ouch. Well, all I can recommend is grabbing the source files from;
http://packages.debian.org/source/testing/binutils
And compiling and installing it manually. There is a bit of a
disparity between glibc support between testing and stable that
the prebuild packages will complain about (you have to install
half of Lenny to do it, which is a bad idea just to update one
package).
Once you have the files you can just use "dpkg -x binutils-blah.dsc"
to get going.
--
Matt Sealey <matt@genesi-usa•com>
Genesi, Manager, Developer Relations
next prev parent reply other threads:[~2008-07-18 12:14 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
2008-07-18 12:14 ` Matt Sealey [this message]
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=48808914.20702@genesi-usa.com \
--to=matt@genesi-usa$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=paubert@iram$(echo .)es \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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