From: Amit D Chaudhary <amitc@brocade.com>
To: karanthk@lycos.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: initrd failing.
Date: Thu, 06 Sep 2001 11:56:18 -0700 [thread overview]
Message-ID: <3B97C6D2.3040904@brocade.com> (raw)
In-Reply-To: BJMJJOGDMKJHLAAA@mailcity.com
Things to check.
Ensure that you have the correct size set in the .config. Next time,
please email the relevant .config entries for the kernel and also what
is the size of initrd.
Next, check that your boot loader is copying the initrd and kernel at
correct offset and uncompressing it. Since you mention it is a custom
board, you will have to try it on your own, these are just pointers.
Amit
karanth wrote:
> Hai,
>
> Iam Using a custom made board, using kernel 2.2.14. Iam able to
> boot from the NFS and from the flash, I want ramdisk to work,
> but it is failing in start_kernel.
> while booting it gives the message,
>
> Uncompressing Linux...done.
> hold_residual=00600100
> Now booting the kernel
>
> bi_memory_size = 0x04000000 ?
> Linux version 2.2.14
> Boot arguments: console=ttyS0,19200n8 root=/dev/ram0
> time_init: decrementer frequency = 247500000/60
> con_init()
> calling kmem_cache_init (memory_start=0xc019efa8, memory_end=0xc1000000)
> Initilize I2C bus: done
> Calibrating delay loop... 65.74 BogoMIPS
> initrd overwritten (0xc00721fc < 0xc019efa8) - disabling it. ----------> why it is failing ??????????
> Memory: 14852k available (752k kernel code, 740k data, 40k init) [c0000000,c100]
> POSIX conformance testing by UNIFIX
> ......................
> .....................
>
> my question in what circumstances initrd is overwritten, how can it be avoided, and how can it be repaired.
>
> Thank for any suggestion in advance.
> Regards
> Ambarish.
>
>
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-09-06 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-06 5:56 initrd failing karanth
2001-09-06 18:56 ` Amit D Chaudhary [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=3B97C6D2.3040904@brocade.com \
--to=amitc@brocade.com \
--cc=karanthk@lycos.com \
--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).