[TriLUG] network cards
Steven Blanchard
sgblanch at email.unc.edu
Fri Jan 25 15:45:39 EST 2002
i know it is possible to specify in
/etc/sysconfig/network-scripts/ifcfg-eth[0,1] (on RedHat systems, at
least) which kernel module to use for a certain interface. I don't know
the exact way to do so, but i believe that this would allow you to
specify which name coresponds to which physical interface.
~steven
M. Mueller (bhu5nji) wrote:
> eth<x> is the symbolic name assigned by the kernel to the Ethernet interface.
> With PCI, an interface that is eth0 in a singly homed machine can become eth1
> when a second interface is to the machine. This effect is due to the order
> in which the cards are found during the boot up sequence. Probes can run
> high to low, or low to high. This is a software decision that may not be
> open for change - but it's worth a look-see in the BIOS. You may want to try
> swapping the card positions in your machine to gauge the effect, for example,
> will card A become eth0 in a machine where it is 1 of 1 Ethernet IF and 1 of
> 2 Ethernet IF? Another approach is to accept the eth<x> names assigned to
> the cards by the system and then "ifconfig" them to match the appropriate net
> address for you network.
>
> Mike M.
>
>
> On Friday 25 January 2002 08:00 am, you wrote:
>
>>I am having a bizzare problem - I have a netfinity-5100 with dual nic's
>>- It has an on board (eth0) pcnet32 --- the second is in pci slot 1
>>(eepro100) (eth1) ... When the system boots up, eth0 expects, eepro100
>>and eth1 exepect pcnet32 - so I bring it up in Single user mode, change
>>the drivers and do an init 5 (all is well) -- if i try to reboot, then I
>>start all over. Has anyone any idea why the devices/software switch
>>positions? Could it be the bios?
>>
>>tia,
>>mark
>>
>>
>>_______________________________________________
>>TriLUG mailing list
>>http://www.trilug.org/mailman/listinfo/trilug
>>
> _______________________________________________
> TriLUG mailing list
> http://www.trilug.org/mailman/listinfo/trilug
>
More information about the TriLUG
mailing list