From: Bob Beck <beck@assurtech.com>
To: linuxppc-embedded@lists.linuxppc.org
Cc: m.venkatraj@exgate.tek.com
Subject: Re: ADS860 - unable to load kernel- Bad magic number
Date: 27 Feb 2004 07:24:51 +1400 [thread overview]
Message-ID: <1077816291.4242.6.camel@budweiser> (raw)
In-Reply-To: <Iq959772845498.03218@webmail1.inner-21cn.com>
On Fri, 2004-02-27 at 21:45, li wrote:
>
> which kernel image did you download into the target via tftp?
> vmlinux.gz is just gzip version of vmlinux Here i downloaded
> zImage.embedded, which has the following features: ELF 32-bit MSB
> executable, PowerPC or cisco 4500, version 1 (SYSV), staticlly linked,
> not stripped. then, with the offset 0x10000 from loadaddr, the kernel
> is up.
What is the difference between vmlinux and zImage.embedded ?
Bob
> > I am a linux-newbie working on a parallel track on the MPC 860, on
> > a ADS board. I am facing difficulty in getting the kernel to load.
> > This is what I have done so far:
> >
> > - built a cross-toolchain using Dan Kegel's crosstool.
> > - built u-boot-1.0.1 and flashed it to the board using BDI2000
> > - built linus-2.4.22, (with the below mentioned patch on last attempt).
> >
> > The compilation goes through fine, I get "vmlinux" on the top-dir,
> > and also a vmlinux.gz in the arch/ppc/boot/images if I do a "make
> > zImage".
> >
> > When I configure bootp, and bootup the board, u-boot comes up fine,
> > the tftp download of the kernel image goes through fine too. Then I
> > am stuck with a "Bad Magic Number". Some initial digup led me to a
> > mismatched image header magic number.
> >
> > Could anyone please help me with how to go ahead? Am I missing
> > something?
> >
> > Also thanks to everyone whose postings on this and other lists
> > helped me get started!
> >
> > -----Original Message-----
> > From: Xavier Miville [mailto:xmiville@oerlikon.ca]
> > Sent: Thursday, February 26, 2004 9:58 PM
> > Subject: RE: PCI daughter card with USB on a 405GP
> >
> > You will need to apply the corresponding linuxppc patch
> > (/pub/linux/kernel/ports/ppc/2.4) to 2.4.22. The zvmlinux doesn't seem
> > to be built with only 2.4.22.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2004-02-26 17:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Iq959772845498.03218@webmail1.inner-21cn.com>
2004-02-26 17:24 ` Bob Beck [this message]
2004-02-27 16:32 ` ADS860 - unable to load kernel- Bad magic number Marius Groeger
2004-02-26 22:22 ` Bob Beck
2004-02-27 17:29 ` Marius Groeger
2004-02-26 22:38 ` Bob Beck
2004-02-27 19:32 ` Dan Malek
2004-02-27 1:32 ` Bob Beck
2004-02-27 21:05 ` Dan Malek
2004-03-01 22:58 ` Booting Linux on a Custom PPC Board Bob Beck
2004-03-02 23:51 ` Wolfgang Denk
2004-03-02 17:45 ` Bob Beck
2004-02-27 4:34 ADS860 - unable to load kernel- Bad magic number m.venkatraj
2004-02-27 4:45 ` John Zhou
2004-02-27 8:07 ` song sam
-- strict thread matches above, loose matches on Subject: below --
2004-02-27 8:27 Demke, Torsten
2004-02-27 9:14 m.venkatraj
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=1077816291.4242.6.camel@budweiser \
--to=beck@assurtech.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=m.venkatraj@exgate.tek.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).