linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: kingseft@samsung.co.kr
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: [QuestionIP_CONFIG : incomplete network configration info...
Date: Mon, 12 Mar 2001 09:26:31 +0100	[thread overview]
Message-ID: <20010312082636.63B2B281DB@denx.denx.de> (raw)
In-Reply-To: Your message of "Mon, 12 Mar 2001 10:42:00 +0900." <H00002af04ab19e3@MHS>


In message <H00002af04ab19e3@MHS> kingseft@samsung.co.kr wrote:
>
>  Hi all developers.

I don't think _all_ developers are interested in this.

Please send PPCBoot related messages to the PPCBoot mailing list instead.

>  IP_CONFIG: Incomplete network configuration info
>  dev_cluse: bug eth0 still running....

That means you are passing incomplete network  configuration  to  the
kernel.

> #define CONFIG_BOOTCOMMAND							\
> "bootp ;" 									\
> "setenv bootargs console=tty0 console=ttyS0 " 					\
> "root=/dev/nfs nfsroot=$(serverip):$(rootpath) " 				\
> "ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname):eth0:off ;" 	\
> "bootm"

When the kernel starts, it prints a  line  with  the  boot  arguments
which  were  passed  to  it.  There  must be some parameters missing;
probably the "rootpath" environment variable is not set.

>  I think CONFIG_BOOTCOMMAND is imcomplte.

No, it it OK. But your BOOTP server configuration in probably incomplete.

>  Could someone describe how to use this BOOTCOMMAND for booting with ramdisk
>  any comments will help me.. thanks.

Now when you want to boot with a ramdisk, you definitely DO NOT  want
to  pass  "root=/dev/nfs  nfsroot=$(serverip):$(rootpath)" as part of
the boot arguments!

Try "root=/dev/ram" instead!

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Quote from the Boss... "I didn't say it was your fault.  I said I was
going to blame it on you."

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2001-03-12  8:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-12  1:42 [QuestionIP_CONFIG : incomplete network configration info kingseft
2001-03-12  8:26 ` Wolfgang Denk [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=20010312082636.63B2B281DB@denx.denx.de \
    --to=wd@denx.de \
    --cc=kingseft@samsung.co.kr \
    --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).