From: "Tang Nguyen" <tang@netoriented.com>
To: "OTAVIO ISAMU SUGENO" <otavio.sugeno@siemens.com>, <wd@denx.de>
Cc: "LinuxPPC" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: eth0 configuration
Date: Wed, 31 Mar 2004 16:45:45 -0800 [thread overview]
Message-ID: <000f01c41782$ab3b6400$150a0a0a@netoriented.com> (raw)
In-Reply-To: 05866645C8E0B842836A1E91B2AD6B7F01465781@CUR1006V.br002.siemens.net.br
Hi,
I think because in the kernel, you have configured IP:kernel level auto
configuration. So, when the kernel boots up, it required correct IP address
and netmask to configure the eth0 interface.
If you turn off IP:kernel level auto configuration in Kernel Configure then
I think your old boot args should work. But you need to configure IP
address for eth0 by command: ifconfig eth0 xxx.
-tang
----- Original Message -----
From: "OTAVIO ISAMU SUGENO" <otavio.sugeno@siemens.com>
To: <wd@denx.de>
Cc: "LinuxPPC" <linuxppc-embedded@lists.linuxppc.org>
Sent: Wednesday, March 31, 2004 11:07 AM
Subject: RE: eth0 configuration
Hi, thanks for the tip.
Using parameters: "root=/dev/ram0 rw ip=:::::eth0:", it works.
Could you explain me what it happens to start ip auto configuration when
this boot args is used?
Otavio I. Sugeno
-----Original Message-----
From: wd@denx.de [mailto:wd@denx.de]
Sent: quarta-feira, 31 de março de 2004 16:01
To: OTAVIO ISAMU SUGENO
Cc: LinuxPPC
Subject: Re: eth0 configuration
In message
<05866645C8E0B842836A1E91B2AD6B7F01465777@CUR1006V.br002.siemens.net.br> you
wrote:
>
> I am sure that interrupts are correctly because it is working with HHL_20.
With exactly the same boot arguments?
> If it does not disturb you so much, I attached the complete boot log and
> config file to analysis.
...
> PPCBoot 1.0.5 (Mar 28 2002 - 14:25:53)
>
> CPU: XPC860xxZPnnD4 at 49.200 MHz: 4 kB I-Cache 4 kB D-Cache FEC present
...
> Loading PPCBOOT File.
> RARP broadcast 1
> TFTP from server 129.214.68.21; our IP address is 129.214.68.10
> Filename 'ppcboot.bin'.
I have no idea why you load a binary image of PPCBoot when you
already have PPCBoot running, but I hope you know hwat you are doing.
...
> Linux version 2.4.24-pre2 (root@cur1307x) (gcc version 3.2.2 20030217
(Yellow Dog Linux 3.0 3.2.2-2a_1)) #51 Seg Mar 29 16:43:07 BRT 2004
> On node 0 totalpages: 8192
> zone(0): 8192 pages.
> zone(1): 0 pages.
> zone(2): 0 pages.
> Kernel command line: root=/dev/ram0 rw
...
Try passing: "root=/dev/ram0 rw ip=:::::eth0:"
Or even "root=/dev/ram0 rw ip=:::::eth0:rarp"
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
"If that makes any sense to you, you have a big problem."
-- C. Durance, Computer Science 234
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2004-04-01 0:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <05866645C8E0B842836A1E91B2AD6B7F01465781@CUR1006V.br002.siemens.net.br>
2004-04-01 0:45 ` Tang Nguyen [this message]
2004-03-30 11:22 eth0 configuration OTAVIO ISAMU SUGENO
2004-03-31 19:00 ` Wolfgang Denk
[not found] <05866645C8E0B842836A1E91B2AD6B7F0147DDA9@CUR1006V.br002.siemens.net.br>
2004-03-30 8:05 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2004-03-29 12:25 OTAVIO ISAMU SUGENO
2004-03-29 14:17 ` 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='000f01c41782$ab3b6400$150a0a0a@netoriented.com' \
--to=tang@netoriented.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=otavio.sugeno@siemens.com \
--cc=wd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.