From: Brendan J Simon <Brendan.Simon@ctam.com.au>
To: dony <dony.he@huawei.com.cn>
Cc: linuxppc-embed <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: decompress_kernel() questions......
Date: Tue, 04 Jan 2000 11:43:33 +1100 [thread overview]
Message-ID: <38714235.9CB27C5B@ctam.com.au> (raw)
In-Reply-To: 387553E8.86C9F334@huawei.com.cn
dony wrote:
> Now the bootloader can work. But when it enters into
> decompress_kernel( )£¬It shows a message " bad gzipped data " and
> exit. I trace the misc.c and find this message is appeared in
> gunzip(). I think it cannot locate the offset of the zipped kernel
> image file. Do you have any experience?
> Thanks.
Yep. I had the same experience.
It means that the kernel image isn't loaded into flash or it is loaded
in the wrong location.
Can you post the output of your terminal output and of "powerpc-linux
--headers zImage".
Brendan Simon.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2000-01-04 0:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <387553E8.86C9F334@huawei.com.cn>
2000-01-04 0:43 ` Brendan J Simon [this message]
2000-01-07 4:34 decompress_kernel() questions dony
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=38714235.9CB27C5B@ctam.com.au \
--to=brendan.simon@ctam.com.au \
--cc=dony.he@huawei.com.cn \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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).