From: Daris Nevil <dnevil@snmc.com>
To: Manie Steyn <msteyn@wmux.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: FEC support
Date: Mon, 26 Jun 2000 12:48:19 -0500 [thread overview]
Message-ID: <39579763.365AE86E@snmc.com> (raw)
In-Reply-To: NEBBIKAICMIJKJMMELBFKELBCAAA.msteyn@wmux.com
Manie,
The message "neighbour table overflow" is the result of some
changes to the IP stack software in Linux version 2.2.x +. This
simply means that you are unable to connect to your NFS
server. It may be related to the driver, but it may also be
related to other issues, such as NFS server not running or
incorrectly installed, no physical connectivity to NFS server,
etc. Check the configuration of your NFS server and IP
network before diving into the driver.
Daris Nevil
SiSIC Inc/SNMC
www.snmc.com
Manie Steyn wrote:
> Hi,
>
> I am running the Embedded Planet Classic 860T with Monta Vista's 2.2.13
> kernel and have some trouble in getting the FEC interface up and running.
>
> The "link" LED comes on but after using ifconfig to assign an IP, I get
> "neighour table overflow" when pinging to or from the device.
>
> I saw the following mail from Dan regarding the 2.4 tree:
>
> > >>> "dan@netx4.com" 06/08/00 20:56 >>>
>
> > I merged a ton of changes into the FEC driver from Magnus, Graham,
> > and myself for generic PHY support. Don't even think about complaining
> > that this doesn't yet work. I know it doesn't.
>
> Does this also hold for the FEC driver in the 2.2.13 port, or am I doing
> something wrong?
>
> Regards
> Manie Steyn
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-26 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-26 17:36 FEC support Manie Steyn
2000-06-26 17:48 ` Daris Nevil [this message]
2000-06-26 19:07 ` FEC support - False Alarm Manie Steyn
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=39579763.365AE86E@snmc.com \
--to=dnevil@snmc.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=msteyn@wmux.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).