From: wolfgang.grandegger@bluewin.ch
To: samble@xopnetworks.com,
"Linuxppc-Embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: Kernel boot
Date: Tue, 11 Feb 2003 09:45:51 +0100 [thread overview]
Message-ID: <3E34EB7F00023064@mss3n.bluewin.ch> (raw)
In-Reply-To: <200302101644.53246.samble@xopnetworks.com>
>-- Original Message --
>From: Srini Amble <samble@xopnetworks.com>
>Reply-To: samble@xopnetworks.com
>To: Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
>Subject: Kernel boot
>Date: Mon, 10 Feb 2003 16:44:53 -0600
>
>
>
>I am using ELDK-2.0 to create a bootable kernel image for PPC8xx. I have
>PPCBoot on my target and I want to download the kernel from the host to
the
>target using TFTP boot. I have verified that I can transfer the image via
>TFTP boot. I am creating the initrd image using the following sequence of
>commands.
>
>1. make config
>2. make dep
>3. make clean
>4. make zImage.initrd
>5. Compress the "zvmlinux.initrd" executable using "gzip"
>6. Execute mkimage command to prepare it for "ppcboot"
>
>After the image is downloaded the kernel image is uncompressed without any
>errors. But then I get the messsage "No initrd" and the system no longer
>responds. Can one of you please point to where I may be going wrong?
For PPCBoot you normally build a pImage with:
make pImage
and building a RAMDisk image is done differently as well. Have a
look to chapter 5 and 6 of the DENX PPCBoot and Linux Guide at http://www.denx.de/doc/TQM8xxL/.
The ELDK 2.0 comes already with
a working pRamdisk image provided by the RPM package SELF.It can
be found in "ppc_8xx/images". You need the SRPM if you want to
modify it. Also check ftp://ftp.denx.de/pub/LinuxPPC/usr/src/SELF/.
Hope it helps,
Wolfgang.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-02-11 8:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 22:44 Kernel boot Srini Amble
2003-02-10 23:36 ` Wolfgang Denk
2003-02-11 8:45 ` wolfgang.grandegger [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=3E34EB7F00023064@mss3n.bluewin.ch \
--to=wolfgang.grandegger@bluewin.ch \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=samble@xopnetworks.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).