linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Andy Fleming" <afleming@gmail.com>
To: Pieter <phenning@vastech.co.za>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: networking fails to activate
Date: Tue, 14 Oct 2008 17:38:05 -0500	[thread overview]
Message-ID: <2acbd3e40810141538w3781fa4r75cfbe2833a21f81@mail.gmail.com> (raw)
In-Reply-To: <48F450CD.8060309@vastech.co.za>

On Tue, Oct 14, 2008 at 2:57 AM, Pieter <phenning@vastech.co.za> wrote:
> Hi
>
> We have a powerpc (8548) based board. running eldk4.1. the board has
> three ethernet ports using Gainfair ethernet controller v1.2.
>
> If the board powers up with any network cable plugged in, that specific
> network is accessible.
> if the board powers up without network cables connected and a cable is
> plugged in, the network does not become active.
> The kernal makes a log entry stating that the phy is up when the cable
> is plugged in - but the interface is not pingable
> Running ifdown and ifup manually does not result in a pingable interface.
> Neither does running /etc/init.d/network restart
>
> can anyone help me pls.


Check the statistics counters to see if you are getting any bad
packets, or to see if you are getting interrupts.  Several people have
reported that their PHYs have powerdown issues, though I wouldn't
expect the PHY to report the link as up, then.  Make sure that your
dts specifies the correct PHY address for the connected PHY.

What happens if you start up with the PHY connected, bring up the
interface, and *then* disconnect and reconnect the cable (after a
delay)?

Andy

  reply	other threads:[~2008-10-14 22:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14  7:57 networking fails to activate Pieter
2008-10-14 22:38 ` Andy Fleming [this message]
2008-10-15 15:03   ` networking fails to activate - more info Pieter
2008-10-16 15:02     ` networking fails to activate - even " Pieter
2008-10-27  6:47       ` Solved: " Pieter

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=2acbd3e40810141538w3781fa4r75cfbe2833a21f81@mail.gmail.com \
    --to=afleming@gmail.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=phenning@vastech.co.za \
    /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).