[QuestionIP_CONFIG : incomplete network configration info...

[QuestionIP_CONFIG : incomplete network configration info...

[kingseft]

 Hi all developers.
 I ported ppcboot, linux kernel and ramdisk.
 when I boot kernel and ramdisk I got this message..

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

 but I got linux shell. and all linux function worked fine......
 I use ppcboot and HardHat Linux kernel 2.2.14
 following list is myboard_config.h


#define	CONFIG_ETHADDR		08:00:30:31:32:33		/* Ethernet address 	*/
#define	CONFIG_IPADDR		  55.121.204.131			/* Target IP address 	*/
#define	CONFIG_SERVERIP		55.121.204.174				/* Servier IP address 	*/
#define CONFIG_BOOTDELAY	5	/* autoboot after 5 seconds		*

#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"


 I think CONFIG_BOOTCOMMAND is imcomplte.
 Could someone describe how to use this BOOTCOMMAND for booting with ramdisk
 any comments will help me.. thanks.


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

Re: [QuestionIP_CONFIG : incomplete network configration info...

[Wolfgang Denk]

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/