linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Bordug <vbordug@ru.mvista.com>
To: Manjunath AM <Manjunath.AM@Lntemsys.com>
Cc: kernelnewbies@nl.linux.org, linuxppc-embedded@ozlabs.org
Subject: Re: enabling two eths
Date: Tue, 20 Feb 2007 16:44:16 +0300	[thread overview]
Message-ID: <20070220164416.5a3906bc@vitb.dev.rtsoft.ru> (raw)
In-Reply-To: <OFAEAB5385.D1B18D5F-ON65257288.0048394A-65257288.00493E72@lntemsys.com>

On Tue, 20 Feb 2007 18:51:41 +0530
Manjunath AM <Manjunath.AM@Lntemsys.com> wrote:

> Hi,
> 
> We are using MPC8272 based target board, we use montavista Linux version 
> 2.6.10 kernel image (with NFS enabled) to our target board,
> 
> Our board has  2 FCCs (eth0 and eth1). bot the eth's works perfectly when 
> we use them independently, but when we are trying to enable second one 
> after the kernel is up using linux command  "ifconfig eth1 192.168.33.64 
> up"(IP address)nothing is working.
> Please suggest how to enable second eth (either 0 or 1) once the kernel is 
> up with NFS file system
> 

I could recall no problems with mpc8272 except stuck PHY which were cured by board power cycle.
I brought up second Ethernet interface a number of times without any problem; even had them replace each 
other serving as NFS root gate.

So I would suggest supplying more information on "nothing is working", prolly kernel output and details about MVL product you are using.

-- 
Sincerely, 
Vitaly

  reply	other threads:[~2007-02-20 13:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-20 13:21 enabling two eths Manjunath AM
2007-02-20 13:44 ` Vitaly Bordug [this message]
2007-02-20 15:31 ` Alex Zeffertt
2007-02-20 16:00   ` Vitaly Bordug
2007-02-21  4:50     ` Manjunath AM
2007-02-21 16:28       ` Leisner, Martin
2007-02-22  4:24         ` Manjunath AM
2007-02-22 20:38           ` Leisner, Martin

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=20070220164416.5a3906bc@vitb.dev.rtsoft.ru \
    --to=vbordug@ru.mvista.com \
    --cc=Manjunath.AM@Lntemsys.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linuxppc-embedded@ozlabs.org \
    /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).