From: Micha Feigin <michf@post.tau.ac.il>
To: linux-kernel@vger.kernel.org
Subject: Re: distinguish two identical network cards
Date: Mon, 23 Feb 2004 11:32:06 +0200 [thread overview]
Message-ID: <20040223093206.GB26628@pc-math-vis1> (raw)
In-Reply-To: <OF3A73498C.45F49506-ONC1256E43.002FC840@fiducia.de>
On Mon, Feb 23, 2004 at 09:49:35AM +0100, andreas.hartmann@fiducia.de wrote:
> 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.
>
Two things I can think about.
First thing is that you can look at the link lights on the card and try
doing a ping and see which one blinks.
Second, if the machines are the same they should scan the bus in the
same direction and IIRC linux numbers the cards in the order of
detection, especially if they are the same (use the same driver) and
thus it should be consistent with the numbering order of the cards
(they will always get the same number on consecutive boots).
>
> 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/
next prev parent reply other threads:[~2004-02-23 9:32 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
2004-02-23 10:35 ` Toon van der Pas
2004-02-23 9:32 ` Micha Feigin [this message]
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=20040223093206.GB26628@pc-math-vis1 \
--to=michf@post.tau.ac.il \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox