mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: jjs <jjs@tmsusa.com>
To: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: NICs trading places ?
Date: Fri, 28 Mar 2003 14:15:38 -0800	[thread overview]
Message-ID: <3E84C98A.50201@tmsusa.com> (raw)
In-Reply-To: <20030328221037.GB25846@suse.de>

That's bitten me several times, not
just 2.4 -> 2.5 but also within different
versions of 2.4-RHL :-(

I've head you can spell out pci IDs
in modules.conf to nail it down but
I haven't gotten around to trying it -

Joe

Dave Jones wrote:

>I just upgraded a box with 2 NICs in it to 2.5.66, and found
>that what was eth0 in 2.4 is now eth1, and vice versa.
>Is this phenomenon intentional ? documented ?
>What caused it to do this ?
>
>The box in question has a DEC Tulip and a 3com 3c905,
>but I imagine this would affect any system with >1 NIC
>of different vendors/drivers ?
>
>		Dave
>
>-
>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/
>
>  
>



  parent reply	other threads:[~2003-03-28 22:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-28 22:10 Dave Jones
2003-03-28 22:14 ` Jeff Garzik
2003-03-28 22:15 ` jjs [this message]
2003-03-28 22:25 ` Joel Becker
2003-03-28 22:27   ` Randy.Dunlap
2003-03-28 22:34   ` Dave Jones
2003-03-28 22:48 ` Andries Brouwer
2003-03-28 23:02   ` Andrew Morton
2003-03-28 23:20     ` Andries Brouwer
2003-03-28 23:41       ` Greg KH
2003-03-28 23:56         ` Jeff Garzik
2003-03-29  0:03           ` Greg KH
2003-03-29  9:20   ` Marc Zyngier
2003-03-28 23:30 ` Dax Kelson
2003-03-28 23:42   ` Sean Neakums
     [not found] <20030328221037.GB25846@suse.de.suse.lists.linux.kernel>
2003-03-29  4:47 ` Andi Kleen

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=3E84C98A.50201@tmsusa.com \
    --to=jjs@tmsusa.com \
    --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

all inboxes | Powered by JetHome®