All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Krishnakumar. R" <krishnakumar@naturesoft.net>
To: andreas.hartmann@fiducia.de, linux-kernel@vger.kernel.org
Subject: Re: distinguish two identical network cards
Date: Mon, 23 Feb 2004 14:37:17 +0530	[thread overview]
Message-ID: <200402231437.17847.krishnakumar@naturesoft.net> (raw)
In-Reply-To: <OF3A73498C.45F49506-ONC1256E43.002FC840@fiducia.de>

Hi,

If its physically identifying the cards that you want,  
then you can  use 'ethtool' for it.  ' -p ' option of 
ethtool will help you physically identify the cards.

Hope it helps,
Regards,
KK.



> Hello!
>
> I've got a little problem with XSeries machines, containing two identical
> builtin Broadcom NIC's. Is there any chance to get some information, which
> one of the two cards is the upper, and which one is the lower card?
> I need this information, because I want to install a lot of these machines
> automatically.
>
>
> Thank you for every hint,
> kind regards,
> Andreas Hartmann
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
HomePage: http://puggy.symonds.net/~krishnakumar



  reply	other threads:[~2004-02-23  9:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-23  8:49 distinguish two identical network cards andreas.hartmann
2004-02-23  9:07 ` Krishnakumar. R [this message]
2004-02-23 10:35   ` Toon van der Pas
2004-02-23  9:32 ` Micha Feigin
2004-02-23 22:51 ` Karl Tatgenhorst
  -- strict thread matches above, loose matches on Subject: below --
2004-02-23  9:53 andreas.hartmann
2004-02-23 16:33 ` Bill Davidsen

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=200402231437.17847.krishnakumar@naturesoft.net \
    --to=krishnakumar@naturesoft.net \
    --cc=andreas.hartmann@fiducia.de \
    --cc=linux-kernel@vger.kernel.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 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.