From: Sven Luther <sven.luther@wanadoo.fr>
To: Sebastian Heutling <sheutlin@gmx.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: How to build the zImage.prep was Re: Bug#345424 acknowledged by developer (Bug#345424: fixed in linux-2.6 2.6.15-1)
Date: Thu, 5 Jan 2006 12:05:23 +0100 [thread overview]
Message-ID: <20060105110523.GA21982@localhost.localdomain> (raw)
In-Reply-To: <43BCFA15.5070304@gmx.de>
On Thu, Jan 05, 2006 at 11:51:01AM +0100, Sebastian Heutling wrote:
> Hi Sven,
>
> maybe I'm just stupid - but I am not able to get an image built that can
No, you just fail to read the manual :)
please : man mkvmlinuz :)
mkvmlinuz allows to build the zImage.prep from the vmlinux outside of the
kernel build process, which is what we are doing, otherwise the zImage.prep
may indeed be the way to handle this.
> be netbooted or put into the prep-bootloader partition. Looking at the
> sources I wonder how you do it for the debian linux-images-* as the only
> Makefile where it seems to generate a "zImage.prep" automagically is in
> arch/ppc/boot/simple/Makefile. But that doesn't work, I guess, because
> CONFIG_PPC_PREP doesn't exist anymore (at least I couldn't find it in
> "menuconfig" or in the ".config" file).
Should work, i booted 2.6.14 on my powerstack II, didn't try 2.6.15 yet, but
will this WE.
> Before trying to build a kernel myself I tried the debian linux binary
> image. An image for powerpc is not there yet so I used rc7. I netbooted
> "/boot/vmlinuz-2.6.15-rc7-powerpc" and the result was that I got a lot
> of output saying that there is something wrong. I assume the output was
> from the firmware because the kernel usually doesn't report an endless
> list of errors saying something about "stack exception" every now and
> then and mostly printing zeros followed by a new line character.
Mmm, upstream may have broken prep on 2.6.15, i have to say i didn't test it,
will have a look this WE, ok ?
> After that I copied the config from that kernel, downloaded the debian
> sources of 2.6.15, enabled ISA and some alsa ISA sound drivers and run
> into the trouble above.
Mmm, i am leaving for two days now, but i will have a look afterward.
Friendly,
Sven Luther
next prev parent reply other threads:[~2006-01-05 11:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1EtnU9-0008HI-I0@spohr.debian.org>
[not found] ` <20051230171705.32043.38767.reportbug@sengor.ath.cx>
[not found] ` <handler.345424.D345424.113629990832428.notifdone@bugs.debian.org>
2006-01-05 10:51 ` How to build the zImage.prep was Re: Bug#345424 acknowledged by developer (Bug#345424: fixed in linux-2.6 2.6.15-1) Sebastian Heutling
2006-01-05 11:05 ` Sven Luther [this message]
2006-01-05 12:59 ` Sebastian Heutling
2006-01-05 16:04 ` Grant Likely
[not found] ` <oqr77koggf.fsf@merlin.sez.to>
2006-01-07 4:25 ` Grant Likely
2006-01-07 19:55 ` Sebastian Heutling
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=20060105110523.GA21982@localhost.localdomain \
--to=sven.luther@wanadoo.fr \
--cc=linuxppc-dev@ozlabs.org \
--cc=sheutlin@gmx.de \
/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).