All of lore.kernel.org
 help / color / mirror / Atom feed
From: JobHunts02 at aol.com <JobHunts02@aol.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Passing IP address to kernel
Date: Thu, 5 May 2005 20:25:02 EDT	[thread overview]
Message-ID: <110.49487932.2fac135e@aol.com> (raw)

Should U-Boot be able to pass the board's IP address to the kernel?


Immediately after logging in, I cannot ping.  ifconfig shows the correct 
hardware address that was set in U-Boot, but not the IP address, which was 
similarly set in U-Boot.  Also, many of the statistical fields have garbage data in 
them (see below).  If I then set the IP address, ifconfig returns the IP 
address and the other fields are correct.  Then, I can ping.


Is this the expected behavior?


Thank you.







                                                                              
  

(none) login: root

login[44]: root login  on `ttyS0'

                                                                              
  

# ping 10.174.100.14

PING 10.174.100.14 (10.174.100.14): 56 data bytes

ping: sendto: Network is unreachable

# ifconfig eth0

eth0      Link encap:Ethernet  HWaddr 1A:34:01:9C:69:15

          BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:4039443 errors:1743791573 dropped:0 overruns:0 
frame:1156359170

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:4144766653 txqueuelen:1000

          RX bytes:1290872887 (1231.0 MiB)  TX bytes:0 (0.0 iB)

                                                                              
  

# ifconfig eth0 address 10.174.100.211

eth0: OPEN

BD rings initialised, RBASE=3D8160, TBASE=3D8360

# ifconfig eth0

eth0      Link encap:Ethernet  HWaddr 1A:34:01:9C:69:15

          inet addr:10.174.100.211  Bcast:10.255.255.255  Mask:255.0.0.0

          UP BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 iB)  TX bytes:0 (0.0 iB)

# ping 10.174.100.14

PING 10.174.100.14 (10.174.100.14): 56 data bytes

64 bytes from 10.174.100.14: icmp_seq=0 ttl=64 time=1.1 ms

64 bytes from 10.174.100.14: icmp_seq=1 ttl=64 time=0.5 ms

64 bytes from 10.174.100.14: icmp_seq=2 ttl=64 time=0.5 ms

64 bytes from 10.174.100.14: icmp_seq=3 ttl=64 time=0.5 ms

64 bytes from 10.174.100.14: icmp_seq=4 ttl=64 time=0.5 ms

64 bytes from 10.174.100.14: icmp_seq=5 ttl=64 time=0.5 ms

64 bytes from 10.174.100.14: icmp_seq=6 ttl=64 time=0.5 ms

64 bytes from 10.174.100.14: icmp_seq=7 ttl=64 time=0.6 ms

64 bytes from 10.174.100.14: icmp_seq=8 ttl=64 time=0.5 ms

                                                                              
  

--- 10.174.100.14 ping statistics ---

9 packets transmitted, 9 packets received, 0% packet loss

round-trip min/avg/max = 0.5/0.5/1.1 ms

                                                                              
  

#

             reply	other threads:[~2005-05-06  0:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-06  0:25 JobHunts02 at aol.com [this message]
2005-05-06  7:47 ` [U-Boot-Users] Passing IP address to kernel 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=110.49487932.2fac135e@aol.com \
    --to=jobhunts02@aol.com \
    --cc=u-boot@lists.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.