Re: How does "alias ethX drivername" in modules.conf work?

Thomas Duffy (Thomas.Duffy.99@alumni.brown.edu)
06 Aug 2001 12:59:22 -0700


On 04 Aug 2001 20:35:37 +0100, Riley Williams wrote:

> One of my systems has SIX ethernet cards, these being three ISA and
> two PCI NE2000 clones and a DEC Tulip. Here's the relevant section of
> modules.conf on the system in question:
>
> Q> alias eth0 ne
> Q> options eth0 io=0x340
> Q> alias eth1 ne
> Q> options eth1 io=0x320
> Q> alias eth2 ne
> Q> options eth2 io=0x2c0
> Q> alias eth3 ne2k-pci
> Q> alias eth4 ne2k-pci
> Q> alias eth5 tulip
>
> Best wishes from Riley.

ok, well this makes sense for the ISA cards. I have card A in my hand,
I set the jumpers on it to an io port 0x340, stick it in slot X on my
computer, plug the wire into it from network 1, then I mentally can map
all the stuff together, so I know how to setup the network in Linux

eth0 == io 0x340 == card A == slot X in my computer == network 1

but, how can you tell the difference between eth3 and eth4 -- and
specify which *physical* card gets assigned to which virtual eth?
name...ie, how do I know which pci slot is which eth? besides reading
the motherboard documentation and maybe learning which direction and how
the pci bus is ordered...which can differ between motherboard
manufacturers and BIOS's, etc, etc.

and how do I change it if I don't like the default order (based off of
pci scan order). what if I want card B, a pci card stuck in PCI slot Y
to be eth4?

hope this is clearer...

thanks,

-tduffy

-
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/