From: Rogan Dawes <rogan@dawes.za.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] Debugging why my kernel won't start
Date: Wed, 18 Aug 2010 11:48:10 +0200 [thread overview]
Message-ID: <4C6BAC5A.6060206@dawes.za.net> (raw)
In-Reply-To: <20100818055133.53E99157D71@gemini.denx.de>
On 2010/08/18 7:51 AM, Wolfgang Denk wrote:
> Dear Rogan Dawes,
>
> In message <4C6B08F1.9000804@dawes.za.net> you wrote:
>>
>> The ramdisk is located at ff9a0000 (in flash). Its image header
>> relocates it to 00800000:
>
> Try to copy the ramdisk to RAM, and pass the Linux kernl an address in
> RAM.
>
> Try it.
>
> Best regards,
>
> Wolfgang Denk
>
Hi Wolfgang,
Thanks for the suggestion. It did make a slight difference in the boot
logs. bootcmd uses the default (in flash) location for the ramdisk,
while the second one has a copy of the ramdisk image at 1600000
(including the header). Both logs are using mainline u-boot, not the
vendor one.
< DNS323B1> run bootcmd
> DNS323B1> bootm ff820000 1600000
< ## Loading init Ramdisk from Legacy Image@ff9a0000 ...
> ## Loading init Ramdisk from Legacy Image at 01600000 ...
< initrd (0xff9a0040 - 0xffe9f758) extends beyond physical memory -
disabling initrd
> checking if image is initramfs...it isn't (no cpio magic); looks like
an initrd
> Freeing initrd memory: 5117K
> RAMDISK: Compressed image found at block 0
> invalid compressed format (err=1)
So it seems that the ramdisk is getting corrupted somehow. And yet, it
is fine using the vendor u-boot. It must be something that I am doing wrong.
Rogan
next prev parent reply other threads:[~2010-08-18 9:48 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 7:24 [U-Boot] Debugging why my kernel won't start Rogan Dawes
2010-08-16 8:34 ` Gérald Kerma
2010-08-16 8:38 ` Rogan Dawes
2010-08-16 20:15 ` Rogan Dawes
2010-08-16 20:29 ` Wolfgang Denk
2010-08-16 21:08 ` Rogan Dawes
2010-08-16 21:11 ` [U-Boot] [PATCH] non-working dns323 config Rogan Dawes
2010-08-18 22:23 ` Wolfgang Denk
2010-08-19 5:25 ` Rogan Dawes
2010-08-19 5:35 ` Wolfgang Denk
2010-08-19 6:37 ` Rogan Dawes
2010-08-19 6:49 ` Wolfgang Denk
2010-08-16 22:03 ` [U-Boot] Debugging why my kernel won't start Wolfgang Denk
2010-08-17 4:30 ` Rogan Dawes
2010-08-17 10:10 ` Albert ARIBAUD
2010-08-17 10:21 ` Rogan Dawes
2010-08-17 10:41 ` Albert ARIBAUD
2010-08-17 11:19 ` Rogan Dawes
2010-08-17 11:42 ` Rogan Dawes
2010-08-17 15:38 ` Albert ARIBAUD
2010-08-17 19:56 ` Rogan Dawes
2010-08-17 20:09 ` Rogan Dawes
2010-08-17 21:20 ` Wolfgang Denk
2010-08-17 21:54 ` Rogan Dawes
2010-08-17 22:04 ` Wolfgang Denk
2010-08-17 22:10 ` Rogan Dawes
2010-08-18 5:51 ` Wolfgang Denk
2010-08-18 9:48 ` Rogan Dawes [this message]
2010-08-18 10:54 ` Wolfgang Denk
2010-08-18 14:42 ` Rogan Dawes
2010-08-18 15:33 ` Wolfgang Denk
2010-08-18 16:32 ` Rogan Dawes
2010-08-18 17:00 ` Wolfgang Denk
2010-08-17 21:18 ` Wolfgang Denk
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=4C6BAC5A.6060206@dawes.za.net \
--to=rogan@dawes.za.net \
--cc=u-boot@lists.denx.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