From: Wolfgang Denk <wd@denx.de>
To: "Kamalesh B" <kamal@tataelxsi.co.in>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: RAMDISK Problem
Date: Mon, 03 Mar 2003 13:30:51 +0100 [thread overview]
Message-ID: <20030303123056.178AFC6E0C@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 03 Mar 2003 17:49:23 +0530." <3E63484A.6340720C@tataelxsi.co.in>
In message <3E63484A.6340720C@tataelxsi.co.in> you wrote:
>
> Iam working on MPC8260ADS and trying to boot linux-2.4.1 in a standalone
> mode without NFS support.
2.4 1. is very old. Did you make sure that the "clocks_in_mhz"
variable is set in your PPCBoot environment?
> I loaded both kernel image which was booting earlier with NFS system and
I understand the NFS based kernel was working on your system?
> newly downloaded ramdisk at address 100000 and 200000 respectively. And
> i also updated the bootargs environment variable as
> ---
> setenv bootargs root=/dev/ram
> ip=10.1.40.176:10.1.40.175:10.1.1.1:255.255.0.0:10.1.40.175::off
> ---
>
> where,
> target ip = 10.1.40.176
> server ip = 10.1.40.175
> gateway ip = 10.1.1.1
You should not configure a gateway address when you need none.
> netmask = 255.255.0.0
> host name = 10.1.40.175
This is an IP address, but not a host name.
[Not that teither of these would cause the boot to fail.]
> Verifying Checksum ... OK
> Loading Ramdisk to 00ed4000, end 00f5eab4 ... OK
>
> [After this, no messages]
If your NFS based kernel was working correctly, you should at least
see the same boot messages until it tires to mount the root
filesystem.
> I am stuck at this point and don't know what could be the reason. Can
> somebody help me?
Attach a debugger (BDI2000) and check where it's hanging.
As a poor man's solution, try to find out if a post-mortem dump of
the log_buf area contains some information: grep the System.map file
in your kernel directory for the virtual address of "log_buf" and
subtract 0xC0000000 to get the physical address; when you board hangs
press the reset button and use PPCBoot's "md" command to print a
memory dump of this area.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Put your Nose to the Grindstone!
-- Amalgamated Plastic Surgeons and Toolmakers, Ltd.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-03-03 12:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 12:19 RAMDISK Problem Kamalesh B
2003-03-03 12:30 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-05 13:53 ramdisk problem 刘彩苹
2003-11-20 20:10 RAMDISK problem VanBaren, Gerald (AGRE)
2003-11-20 15:34 Joao Vicente
2003-11-20 16:27 ` Wolfgang Denk
2003-11-19 19:49 VanBaren, Gerald (AGRE)
2003-11-19 19:13 Joao Vicente
2003-11-12 21:01 Jean-Denis Boyer
2003-11-12 21:29 ` Wolfgang Denk
[not found] <DEF39A0710293E489D45B10E06645CBD026719AB@dub-msx1.spectelcorp.com>
2003-11-12 19:45 ` Wolfgang Denk
2003-11-11 19:58 Steven Blakeslee
2003-11-11 15:44 Joao Vicente
2003-11-11 19:58 ` Wolfgang Denk
2003-03-13 9:38 RAMDISK Problem Kamalesh B
2002-06-13 15:20 Re: ramdisk problem somshekar chandrashekar kadam
2002-06-13 15:35 ` Wolfgang Denk
2002-06-13 13:43 somshekar chandrashekar kadam
2002-06-13 13:54 ` Wolfgang Denk
2002-06-13 11:14 somshekar chandrashekar kadam
2002-06-13 11:49 ` 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=20030303123056.178AFC6E0C@atlas.denx.de \
--to=wd@denx.de \
--cc=kamal@tataelxsi.co.in \
--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).