From: "Jon Smirl" <jonsmirl@gmail.com>
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 12:15:41 -0400 [thread overview]
Message-ID: <9e4733910807150915n6993932dr780f00342fadb4e@mail.gmail.com> (raw)
In-Reply-To: <487CC1F5.5090706@genesi-usa.com>
On 7/15/08, Matt Sealey <matt@genesi-usa.com> 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.
>
> If you got it from somewhere (like a distribution) then please tell us
> where, as there are some other troubles with load-base location for
> Fedora and so on...
Is it hard to put a check into the kernel make system to look for
binutils 2.17 and refuse to build with a nice error message? I poked
around in the makefile but I'm not 100% sure of how it works.
>
> --
> Matt Sealey <matt@genesi-usa.com>
> Genesi, Manager, Developer Relations
>
>
> Gabriel Paubert wrote:
>
> > Hi,
> >
> > I just tried to boot 2.6.26 on a Pegasos and the kernel does not boot.
> > The last message I have is:
> > gunzip (0xffffffff <----- some more hex digits)
> >
> > The configuration has been created from a working 2.6.25 one with
> > make oldconfig and answering N to new config options.
> >
> > Anybody has seen this or do I have to start digging deeper?
> >
> > Regards,
> > Gabriel
> > _______________________________________________
> > Linuxppc-dev mailing list
> > Linuxppc-dev@ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-dev
> >
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
--
Jon Smirl
jonsmirl@gmail.com
prev parent reply other threads:[~2008-07-15 16:15 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
2008-07-22 17:54 ` Segher Boessenkool
2008-07-15 16:15 ` Jon Smirl [this message]
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=9e4733910807150915n6993932dr780f00342fadb4e@mail.gmail.com \
--to=jonsmirl@gmail.com \
--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).