From: "Mark Chambers" <markc@mail.com>
To: "apoorv sangal" <apoorvsangal@gmail.com>, <Linuxppc-embedded@ozlabs.org>
Subject: Re: Problem Regarding Ping in Linux kernel version 2.4.24
Date: Tue, 11 Oct 2005 08:23:45 -0400 [thread overview]
Message-ID: <005801c5ce5e$a5fd8470$0301a8c0@chuck2> (raw)
In-Reply-To: a79669360510102327o694dffb4pcf8ead02d95c9414@mail.gmail.com
Hi,
I am sending the output from the console of the boot sequence and ifconfig
command as following.
Please check the same and let me know where i am going wrong.
****************************************************************************
***************************
[snip]
eth0: FCC2 ENET Version 0.4, 00:10:EC:40:30:8C
[snip]
init started: BusyBox v0.60.5 (2004.11.09-16:07+0000) multi-call
binarymount: Mounting /dev/ram0 on /tmp failed: Invalid argument
# ifconfig eth0 down
# ifconfig eth0 172.19.56.218
# ifconfig eth0 up
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:10:EC:40:30:8C
inet addr:172.19.56.218 Bcast:172.19.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING 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)
Base address:0x8500
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 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:0
RX bytes:0 (0.0 iB) TX bytes:0 (0.0 iB)
# ping 127.0.0.1
PING 127.0.0.1 (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.6 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.2 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.2 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.2 ms
64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.2 ms
--- 127.0.0.1 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.2/0.2/0.6 ms
#
# ping 172.19.59.101
PING 172.19.59.101 (172.19.59.101): 56 data bytes
--- 172.19.59.101 ping statistics ---
6 packets transmitted, 0 packets received, 100% packet loss
****************************************************************************
***************************
Regards,
Apoorv Sangal.
It appears you have correctly assigned MAC and IP addresses. The problem
does appear to be at
the hardware level, because the ethernet interface is not doing anything at
all. My guess would be
that the driver is not configured for the correct pins. You mentioned that
you are using custom hardware,
so look, probably in arch/ppc/8260_io/fcc_enet.c and make sure you have it
configured for Tx and
Rx clock coming in on the right pins, and also check that you are configured
for the correct PHY
interrupt.
Good luck,
Mark Chambers
prev parent reply other threads:[~2005-10-11 12:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 5:05 Problem Regarding Ping in Linux kernel version 2.4.24 apoorv sangal
2005-10-07 12:31 ` Aristeu Sergio Rozanski Filho
2005-10-10 10:40 ` apoorv sangal
2005-10-10 12:36 ` Mark Chambers
2005-10-10 17:00 ` MPC8555 USB host support Stefan Roese
2005-10-11 20:29 ` Kylo Ginsberg
2005-10-12 6:59 ` Stefan Roese
2005-10-12 7:01 ` Pantelis Antoniou
2005-10-12 7:11 ` Mike Rapoport
2005-10-12 7:27 ` Stefan Roese
2005-10-12 12:34 ` Alex Zeffertt
2005-10-31 6:45 ` Mike Rapoport
[not found] ` <1131960060.7748.9.camel@hawk.pwav.net>
2005-11-15 6:59 ` Mike Rapoport
2005-11-15 12:03 ` Alexandre BASTOS
2005-11-15 15:22 ` Kumar Gala
2005-11-15 15:38 ` Mike Rapoport
2005-11-15 15:40 ` Vitaly Bordug
2005-11-16 15:50 ` Kumar Gala
2005-11-16 15:57 ` Vitaly Bordug
2005-11-17 12:34 ` Yuli Barcohen
2005-12-01 12:26 ` MPC8555 8280/8270 " Hans Schillstrom
2005-12-01 13:55 ` Mike Rapoport
2005-12-01 15:29 ` Wolfgang Denk
2005-10-11 6:27 ` Problem Regarding Ping in Linux kernel version 2.4.24 apoorv sangal
2005-10-11 12:23 ` Mark Chambers [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='005801c5ce5e$a5fd8470$0301a8c0@chuck2' \
--to=markc@mail.com \
--cc=Linuxppc-embedded@ozlabs.org \
--cc=apoorvsangal@gmail.com \
/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).