hi, couldn't find similar problem, so i;m posting..

(debian box, kernel 2.6.18)
I have three network cards:

eth0 (8139too) module loading and card is working fine
eth1 (e100) module loading and card is working fine
eth2 (e100) module is loading fine but i can't fetch the interface via ifconfig command?

here are some logs from console:

bando:~# modprobe -r e100
ACPI: PCI interrupt for device 0000:02:0b.0 disabled
ACPI: PCI interrupt for device 0000:02:09.0 disabled

bando:~# modprobe e100
e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
PCI: Enabling device 0000:02:09.0 (0110 -> 0113)
ACPI: PCI Interrupt 0000:02:09.0[A] -> GSI 21 (level, low) -> IRQ 217
e100: eth1: e100_probe: addr 0xf8000000, irq 217, MAC addr 00:50:8B:05:12:AD
PCI: Enabling device 0000:02:0b.0 (0110 -> 0113)
ACPI: PCI Interrupt 0000:02:0b.0[A] -> GSI 23 (level, low) -> IRQ 193
e100: eth2: e100_probe: addr 0xf8001000, irq 193, MAC addr 00:50:8B:05:13:C8

bando:~# ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:50:8B:05:12:AD
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

bando:~# ifconfig eth2
eth2: error fetching interface information: Device not found
bando:~#


I added alias lines to the modules.conf file:

alias eth1 e100
alias eth2 e100

but it didn't work either...

output form dmesg:

bando:/home/tom# dmesg |grep e100
PCI: Firmware left 0000:02:09.0 e100 interrupts enabled, disabling
PCI: Firmware left 0000:02:0a.0 e100 interrupts enabled, disabling
e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
e100: eth1: e100_probe: addr 0xe8300000, irq 217, MAC addr 00:90:27:BC:E7:58
e100: eth2: e100_probe: addr 0xe8301000, irq 225, MAC addr 00:02:B3:C7:5C1
e100: eth1: e100_watchdog: link up, 100Mbps, full-duplex


does anyone have an idea what i'm doing wrong ?
tom

thanks

I'm a bit rusty with that many cards, but... dmesg shows that eth2 has a MAC address, so it is being seen.

Have you remembered to ifconfig eth2 up ?

If so, and still having problems, does debian have a built-in configuration tool? While not a panacea, these can often point you in the direction of a problem. If the distro's config tool sees the status as up, then the problem is between the status being up and it actually being used. If the config tool sees the status as down, or not there, the problem is lower-level.

Try "netconfig -d eth2" ( configure ip) & issue "service network restart"

having exact same issue, no idea why, but for me it is any 3 nics, I have tried 6 different nic chips, the first 2 always work, the third fails regardles of order or anything else. tried 2.6.17, 18, an d19, both minimal and everything I need, modules and builtin... every once in a while it will boot and all 3 work, but usually the third always fails

I do not have the ability to copy and paste or in any way transfer the contents of ifconfig -a to this system for posting, but I ran it and had interesting results!

eth0 and eth2 are both listed, eth2 is not there, but it suddenly jumps and there is an eth4!

'dmesg | grep eth' shows only messages for eth0-2.


I tried giving an IP to eth4 and it did have conectivity......

I was once confused by something I saw when using a number of network cards.

The reason was that udev had renamed the devices and added it as a persistant rule. While this has the advantage of making sure they get renamed the same way on each reboot, they have to be right!

Check the file /etc/udev/rules.d/z25_persistant-net.rules

I don't know if this will help sort out anything but may eliminate confusion.

wow, opened the udrev rule, indeed if's 2 and 3 are listed w/ firewire and one of my temp cards a while back.. thanx!