Forcing Linux to recognize NICS in BIOS order

[Chris Linstid]

Hmm... on second thought, if the driver module for the on-board  
network and the PCI NIC are the same, I'm not sure how you would  
control the order for that.

	- Chris

On Aug 15, 2006, at 9:11 AM, Chris Linstid wrote:

> Isn't the order they come up in determined by the order in which  
> the driver modules are loaded?  So, say you have an on-board intel  
> NIC and a PCI 3com in one system and an on-board intel NIC and a  
> PCI tulip-based card in another, if the module load order is 3com,  
> intel, tulip they are of course going to come up in a different order.
>
> I think the way to fix this is to alias module names to network  
> interface names in the module configuration files.  Something like  
> this:
>
> http://www.newt.com/debian/thinkpad-t40p/#ethernet
>
> 	- Chris
>
> On Aug 15, 2006, at 9:01 AM, Paul Lussier wrote:
>
>>
>> Hi all,
>>
>> All our systems have multiple NICs on them.  On some systems however,
>> Linux brings up the NICs in a different order than the BIOS orders
>> them.  For example, the BIOS orders an on-board NIC as "the first"  
>> and
>> a PCI add-on card NIC as "the second".  But when Linux comes up, for
>> some reason it swaps that order and the add-on card is seen by the OS
>> as eth0 and the on-board NIC as eth1.
>>
>> I thought there was a way to force the OS to use the same ordering,
>> but can't remember the details. Anyone have pointers to an
>> explanation?
>>
>> fwiw, Debian, 2.4.3mumble, and mostly Intel ee1000 cards
>> (a few tulips, a few 3Coms, etc.)
>>
>> Thanks.
>> -- 
>> Seeya,
>> Paul
>> _______________________________________________
>> gnhlug-discuss mailing list
>> gnhlug-discuss at mail.gnhlug.org
>> http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
>