On Tuesday 12 August 2003 00:18, Paul Ketelaar wrote:

SuSE Technologists,

I am puzzled! I am putting together an F/P server , SuSE of course. The mobo is a ASUS A7V8X, I have a TNT based AGP card in the AGP slot, a UDMA cont in PCI 3 and dual NIC's (3c905-cx-tx-m) in PCI slots 5 & 6 respectively. One NIC is on irq 11 and the other on irq 9 (ifconfig) no other devices share these interrupts, all un-used peripherals usb, onboard NIC and sound have been disabled in bios to free up the IRQs.

Everything installed ok, all h/w detected and it runs like a dream . The NICs were detected and the correct driver loaded. A single IP is allocated to each NIC. 'lspci' shows the two NIC's and 'lsmod' shows the driver '3c59x' being used by the two NICs.

This is where things get interesting. You can ping (from a wkstn) both IPs at eth0, with the network cable plugged into physical device eth0, but neither at physical device eth1. You can ping (from the linuxbox) the gw address with the cable in physical device eth0, but not in physical device eth1. For all intents and purposes the NIC appears dead even though it is configured. The ifcfg files in /etc/sysconfig/network appear ok. 'ifconfig' shows everthing to be working. 'modules.conf' aliases are correct.

Another 3com (different type - same driver) nic was used, the effect persists. The second NIC was replaced with a card based of the RTL8139D chipset, the effect persists.

Under this config I have also seen an error message appear at boot, this relates to line 154 of the 'ifup-route' script, I have passed this on to the author, Christian Zoz at SuSE (If he is still there!).

Now am I forgetting something simple or is something sinister and/or forgtten hiding somewhere. Can someone please help me.

I had similar problems with NICs using that driver. So far as I could discover it doesn't handle multiple NICs. The only solution I found was to use 2 different NICs which would use different driver modules. HTH Dylan -- Sweet moderation Heart of this nation Desert us not We are between the wars - Billy Bragg

On Mon August 11 2003 6:18 pm, Paul Ketelaar wrote:

SuSE Technologists,

>snip<

This is where things get interesting. You can ping (from a wkstn) both IPs at eth0, with the network cable plugged into physical device eth0, but neither at physical device eth1. You can ping (from the linuxbox) the gw address with the cable in physical device eth0, but not in physical device eth1. For all intents and purposes the NIC appears dead even though it is configured. The ifcfg files in /etc/sysconfig/network appear ok. 'ifconfig' shows everthing to be working. 'modules.conf' aliases are correct.

Another 3com (different type - same driver) nic was used, the effect persists. The second NIC was replaced with a card based of the RTL8139D chipset, the effect persists.

Under this config I have also seen an error message appear at boot, this relates to line 154 of the 'ifup-route' script, I have passed this on to the author, Christian Zoz at SuSE (If he is still there!).

Now am I forgetting something simple or is something sinister and/or forgtten hiding somewhere. Can someone please help me.

Regards Paul K

Is this a case where you are trying two NICs on the same network without bonding them? What happens if you assign them different IP addresses on different networks? 192.168.0.10/16 and 192.168.1.10/16 for example... Stan