Two identical network cards

RedShift · 2004-07-27 10:51:59

Lo all,

I have two network cards in my server, Intel Pro 10/100. Motherboard is a supermicro 370DER.
(www.supermicro.com/products/motherboard/P3/HE-SL/370DER.cfm)

The problem is, this board has two network cards. Only the first one is functioning.

This in /etc/modprobe.conf:

alias eth0 eepro100
alias eth1 eepro100

This in /etc/rc.conf:
eth0 = "eth0 192.168.123.2 netmask 255.255.255.0 broadcast 192.168.123.255"
eth1 = "eth1 192.168.123.3 netmask 255.255.255.0 broadcast 192.168.123.255"
INTERFACES=(lo0 eth0 eth1)

Now the first network port listens to both 2 and 3. The second network port is dead silent.

lanrat · 2004-07-27 12:45:09

Can you see both network cards with lspci ?

RedShift · 2004-07-27 12:54:17

Yep, lspci returned this:

root->/root> lspci
00:00.0 Host bridge: ServerWorks CNB20HE Host Bridge (rev 23)
00:00.1 PCI bridge: ServerWorks CNB20LE Host Bridge (rev 01)
00:00.2 Host bridge: ServerWorks: Unknown device 0006 (rev 01)
00:00.3 Host bridge: ServerWorks: Unknown device 0006 (rev 01)
00:04.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08)
00:05.0 SCSI storage controller: Adaptec AIC-7899P U160/m (rev 01)
00:05.1 SCSI storage controller: Adaptec AIC-7899P U160/m (rev 01)
00:06.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08)
00:0f.0 ISA bridge: ServerWorks OSB4 South Bridge (rev 51)
00:0f.1 IDE interface: ServerWorks OSB4 IDE Controller
00:0f.2 USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller (rev 04)
01:00.0 VGA compatible controller: ATI Technologies Inc Rage XL AGP 2X (rev 27)
root->/root>

lanrat · 2004-07-27 12:55:05

Oh, just realized that your modprobe doesn't know which io addresses and irq to use. Please read this (section two identical cards) http://www.tldp.org/HOWTO/Home-Network- … WTO-3.html and add options line. You can read your cards io and irq from lspci (or at least they should be there :-)).

lanrat · 2004-07-27 12:56:46

...and use lspci -vv to read all info you need.

RedShift · 2004-07-27 19:58:45

Bah, it still isn't working.

Ok, current configuration:

in /etc/modprobe.conf:

alias eth0 eepro100
alias eth1 eepro100
options eepro100 io=c800,d400 irq=153,161

in /etc/rc.conf:

eth0="dhcp"
eth1="dhcp"
INTERFACES=(lo eth0 eth1)

I'm having the weirdest stuff.

When I ping 192.168.123.151, both network ports reply (ie, activity let flickering). Same for 192.168.123.184. But when I pull out the cable of the first network jacket, the second port keeps replying, to both IP addresses. When I pull out the cable out the first port, nothing works.

Help!

RedShift · 2004-07-27 20:13:00

Found something interesting in /bin/dmesg:

eepro100: Unknown paramter `io'

lanrat · 2004-07-27 21:48:09

Hmmm. Indeed modinfo eepro100 does not return io and irq parameters while modinfo ne does. eepro100 module just doesn't have these parameters...

Ok. Let's search a little with google..... Forget about options line. Try to use e100 driver maybe. It's provided by Intel.

When you are doing modprobe eepro100 (or e100) "manually" what outputs ifconfig command? Even with eepro100 both cards should be visible... strange.

lanrat · 2004-07-27 22:14:31

BTW with your first setup do you have any other errors in dmesg? Something about resources?

cs25x · 2004-07-28 10:35:45

Years ago, somebody solved this problem by running a copy of the nic module with a different name.
cp mod.o mod0.o
modprobe mod
modprobe mod0

Do you sitll have to tell the kernel you have 2 nics at boot time?
It used to be that the kernel would only discover one, and you had no control over which was eth0 & which eth1.

RedShift · 2004-07-28 12:08:34

Usefull stuff out of dmesg

pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: acpi_shpchprm:get_device PCI ROOT HID fail=0x1001
eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
eth0: OEM i82557/i82558 10/100 Ethernet, 00:30:48:11:7A:85, IRQ 153.
  Board assembly 000000-000, Physical connectors present: RJ45
  Primary interface chip i82555 PHY #1.
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (0x04f4518b).
eth1: OEM i82557/i82558 10/100 Ethernet, 00:30:48:11:91:D9, IRQ 161.
  Board assembly 000000-000, Physical connectors present: RJ45
  Primary interface chip i82555 PHY #1.
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (0x04f4518b).
ohci_hcd: 2004 Feb 02 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ohci_hcd: block sizes: ed 64 td 64
PCI: Enabling device 0000:00:0f.2 (0000 -> 0002)
PCI: No IRQ known for interrupt pin @ of device 0000:00:0f.2. Probably buggy MP table.
ohci_hcd 0000:00:0f.2: Found HC with no IRQ.  Check BIOS/PCI 0000:00:0f.2 setup!
Disabled Privacy Extensions on device c06c18c0(lo)
eth0: no IPv6 routers present

This is when:

in modprobe.conf:

alias eth0 eepro100

in rc.conf:

eth0="dhcp"
INTERFACES=(lo eth0)

lanrat · 2004-07-28 19:29:39

cs25x wrote:

Years ago, somebody solved this problem by running a copy of the nic module with a different name.
cp mod.o mod0.o
modprobe mod
modprobe mod0
Do you sitll have to tell the kernel you have 2 nics at boot time?
It used to be that the kernel would only discover one, and you had no control over which was eth0 & which eth1.

Not really. I mean if you read the dmesg output above you will see that both cards are visible (different mac addresses). Having two aliases for one module is also harmless - kernel will not load the same module twice. But it's true that you can't decide which card will became eth0 and which eth1 - normally you could switch slots (and prey :-)) but they are builtin so you have to just try to configure it somehow.

This can be some bios issue. Check your pci/irq bios settings first (what's your mobo full name/product number? maybe it will be easier to search for advises in google with this information).

Another thing you can try is adding noapic option to your kernel grub/lilo line. This will force kernel to handle irqs - this mobo with two integrated nics is not "normal" :-) Do you have acpi/apm in both bios and kernel enabled/disabled?

You can also find a diagnostic program for your network cards type here http://www.scyld.com/ethercard_diag.html (eepro100-diag.c - instructions how to compile it are included in the comments at the end of this file). Maybe it will provide some more useful info.

If it's not hardware related then this can be something wrong with your other configs. I wonder if it would be possible to setup both cards manually with ifconfig command and without dhcp? (something like your first setup - unload eepro100 module first and then load it with modprobe, check ifconfig -a output to see if it recognizes both cards and then try to configure each card with ifconfig at the end try ifconfig -a again)

cs25x · 2004-07-28 20:36:05

If it's not hardware related then this can be something wrong with your other configs. I wonder if it would be possible to setup both cards manually with ifconfig command and without dhcp?

Looks like config problems, hw is seen. Manual config is what I would try too. This is behaving a bit like one IP is being aliased on top of the other.

cs25x · 2004-08-02 23:38:58

Mail list might give a clue
http://www.archlinux.org/pipermail/arch … 00727.html
and, later
http://www.archlinux.org/pipermail/arch … 00749.html

They say to try e100 module + a couple of other ideas which might help.

Arch Linux

#1 2004-07-27 10:51:59

Two identical network cards

#2 2004-07-27 12:45:09

Re: Two identical network cards

#3 2004-07-27 12:54:17

Re: Two identical network cards

#4 2004-07-27 12:55:05

Re: Two identical network cards

#5 2004-07-27 12:56:46

Re: Two identical network cards

#6 2004-07-27 19:58:45

Re: Two identical network cards

#7 2004-07-27 20:13:00

Re: Two identical network cards

#8 2004-07-27 21:48:09

Re: Two identical network cards

#9 2004-07-27 22:14:31

Re: Two identical network cards

#10 2004-07-28 10:35:45

Re: Two identical network cards

#11 2004-07-28 12:08:34

Re: Two identical network cards

#12 2004-07-28 19:29:39

Re: Two identical network cards

#13 2004-07-28 20:36:05

Re: Two identical network cards

#14 2004-08-02 23:38:58

Re: Two identical network cards

Board footer