From: Anatolij Gustschin <agust@denx.de>
To: SETTE AGOSTINO - technolabs <Agostino.Sette@technolabs.it>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MPC8568MDS RAMDISK Problem
Date: Tue, 02 Sep 2008 12:10:52 +0200 [thread overview]
Message-ID: <48BD112C.6080902@denx.de> (raw)
In-Reply-To: <F1F6EC0C8B75034F9E3A79FC85122E8E01000FD1@aquib01a>
Hi Agostino,
SETTE AGOSTINO - technolabs wrote:
> First of all thanks for your help. I modified the mpc8568mds_defconfig
>
>>> cat kernel/linux/arch/powerpc/configs/mpc8568mds_defconfig
> #
<snip>
>
> But now I face this problem
>
> ## Checking Image at 02000100 ...
> Image Name: Linux-2.6.25.5
> Image Type: PowerPC Linux Kernel Image (gzip compressed)
> Data Size: 1354578 Bytes = 1.3 MB
> Load Address: 00000000
> Entry Point: 00000000
> Verifying Checksum ... OK
> ## Booting image at 02000100 ...
> Image Name: Linux-2.6.25.5
> Image Type: PowerPC Linux Kernel Image (gzip compressed)
> Data Size: 1354578 Bytes = 1.3 MB
> Load Address: 00000000
> Entry Point: 00000000
> Verifying Checksum ... OK
> Uncompressing Kernel Image ... OK
> ## Loading RAMDisk Image at 02200100 ...
> Image Name: initrd
> Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
> Data Size: 3658110 Bytes = 3.5 MB
> Load Address: 00000000
> Entry Point: 00000000
> Verifying Checksum ... OK
> Booting using the fdt at 0x21f0100
> Loading Ramdisk to 00482000, end 007ff17e ... OK
> Loading Device Tree to 007fa000, end 007fcfff ... OK
Ramdisk image is partially overwritten while loading the
Device Tree: Ramdisk ends at 0x007ff17e, Device Tree starts
at 0x007fa000. You probably need to update U-Boot to recent
version to solve this issue.
> Using MPC85xx MDS machine description
> Memory CAM mapping: CAM0=16Mb, CAM1=16Mb, CAM2=16Mb residual: 15Mb
> Linux version 2.6.25.5 (ity10223@aqlbl05x) (gcc version 4.2.2) #1 Mon Sep 1 10:44:44 CEST 2008
> Found initrd at 0xc0482000:0xc07ff17e
<snip>
> RAMDISK: Compressed image found at block 0
> invalid compressed format (err=1)
Ramdisk decompression failed, it's expected as ramdisk was
overwritten by DTB while booting.
Try to update U-Boot to v1.3.4.
Best regards,
Anatolij
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office@denx.de
next prev parent reply other threads:[~2008-09-02 10:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 14:11 GPIO interrupt on AMCC 460EX Felix Radensky
2008-08-28 15:20 ` Stefan Roese
2008-08-28 21:47 ` Felix Radensky
2008-08-29 15:31 ` MPC8568MDS RAMDISK Problem SETTE AGOSTINO - technolabs
2008-08-29 18:03 ` Bhupender Saharan
2008-08-29 21:45 ` Anatolij Gustschin
2008-09-01 9:02 ` SETTE AGOSTINO - technolabs
2008-09-02 10:10 ` Anatolij Gustschin [this message]
2008-09-02 13:18 ` SETTE AGOSTINO - technolabs
2008-09-02 21:27 ` Anatolij Gustschin
2008-09-03 9:30 ` SETTE AGOSTINO - technolabs
-- strict thread matches above, loose matches on Subject: below --
2008-09-01 9:18 yanlong wang
2008-09-02 10:01 ` Detlev Zundel
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=48BD112C.6080902@denx.de \
--to=agust@denx.de \
--cc=Agostino.Sette@technolabs.it \
--cc=linuxppc-embedded@ozlabs.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).