Module Conflict (I think)

[ChaosCrypt]

Hi there.

I have a Dell 2450 with an onboard Intel e100 NIC and a Netgear 10/100/1000 NIC based on the r8169 chipset.

When it boots it detects the cards as below

e100: eth0: e100_probe: addr 0xeb100000, irq 185, MAC addr 00:B00:49:6D:EA
eth1: Identified chip type is 'RTL8169s/8110s'.
eth1: RTL8169 at 0xe0838000, 00:0f:b5:fd:bc:c8, IRQ 193

It then proceeds to boot.

eth1 is sucessfully brought up, but eth0 is missing.

If I try to ifconfig or ifup eth0 I get a message that the device does not exist.

I have found a way around this - here is the script I have written

#! /bin/sh
ifdown eth1
rmmod e100
rmmod r8169
modprobe -i r8169
modprobe -i e100
ifup eth0
ifup eth1

So basically if you shutdown the working interface, unload the modules and reload them with the r8169 1st it all works - if you reload the e100 1st, eth0 is unusable - its as if the onboard NIC doesnt want to be eth0.

My suspicion is a conflict in the drivers where the r8169 causes a problem with the e100 when it initialised and the e100 is loaded.

Can anyone help with this?

I have tried creating an entry in /etx/modutils/interfaces to alias the eth ports to their modules, but with no success, I think I actually need to tweak detection of the cards during the boot sequence to resolve this.

At the moment I am going to get the system to run my fixit script after booting is complete to get round this.

I am more than willing to poke and prod at this to get a proper-fix/bug report out of it tho

Thanks

David

[burnit]

Well... you should post the /etc/network/interfaces file, so we know how network interfaces are handled...

I have a PC (Desktop) with the same configuration, and I never had this problem.