Fixed: eth1 won't start "device eth1 does not seem to be present, delaying ..."
 

I have a Redhat 9 (?) box with an e1000 and a dlink Ethernet card. The e1000 starts fine. No matter what I do I can't get the dlink to start. I have similar ifcfg files for both cards.

listings of the ifcfg files and results of unamne, lsmod, dmesg, lspci and a restart below.

# uname -a
Linux <machine name deleted> 2.6.18-53.1.4.el5 #1 SMP Wed Nov 14 10:37:33 EST 2007 i686 i686 i386 GNU/Linux

#/sbin/ifup eth1
8139too device eth1 does not seem to be present, delaying initialization.

#/sbin/lsmod |grep mii
mii 9409 2 e100,8139too

# dmesg |grep 8139
8139too Fast Ethernet driver 0.9.27
eth0: RealTek RTL8139 at 0xf0836000, 00:40:05:00:ab:aa, IRQ 185
eth0: Identified 8139 chip type 'RTL-8100B/8139D'

whereas

# dmesg |grep e100
PCI: Firmware left 0000:02:08.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 0xf2000000, irq 201, MAC addr 00:09:6B:38:68:B8
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex

# /sbin/lspci | grep Eth
02:08.0 Ethernet controller: Intel Corporation 82801BA/BAM/CA/CAM Ethernet Controller (rev 03)
02:0d.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10)


One somewhat suspicious thing is that

find /lib/modules -name 8139too

gets nothing while

# find /lib/modules -name 8139too*
/lib/modules/2.6.18-53.el5/kernel/drivers/net/8139too.ko
/lib/modules/2.6.18-53.1.4.el5/kernel/drivers/net/8139too.ko

but

[root@tictac ]# find /lib/modules -name e1000
/lib/modules/2.6.18-53.el5/kernel/drivers/net/e1000
/lib/modules/2.6.18-53.1.4.el5/kernel/drivers/net/e1000

but I suppose that

# find /lib/modules -name e100*
/lib/modules/2.6.18-53.el5/kernel/drivers/net/e1000e
/lib/modules/2.6.18-53.el5/kernel/drivers/net/e1000e/e1000e.ko
/lib/modules/2.6.18-53.el5/kernel/drivers/net/e100.ko
/lib/modules/2.6.18-53.el5/kernel/drivers/net/e1000
/lib/modules/2.6.18-53.el5/kernel/drivers/net/e1000/e1000.ko
/lib/modules/2.6.18-53.1.4.el5/kernel/drivers/net/e1000e
/lib/modules/2.6.18-53.1.4.el5/kernel/drivers/net/e1000e/e1000e.ko
/lib/modules/2.6.18-53.1.4.el5/kernel/drivers/net/e100.ko
/lib/modules/2.6.18-53.1.4.el5/kernel/drivers/net/e1000
/lib/modules/2.6.18-53.1.4.el5/kernel/drivers/net/e1000/e1000.ko


and

# /etc/init.d/network restart
Shutting down interface eth0: [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface eth1: 8139too device eth1 does not seem to be present, delaying initialization.
[FAILED]


cat /etc/sysconfig/network-scripts/ifcfg-eth1
# network-scripts ifcfg-eth1
# D-Link System Inc RTL8139 Ethernet
DEVICE=eth1
ONBOOT=yes
#BOOTPROTO=dhcp
DHCPCDARGS="-S <names deleted here>"
NETMASK=255.255.255.0
IPADDR=<valid IP address deleted>
GATEWAY=<valid IP address deleted>
TYPE=Ethernet

but

cat /etc/sysconfig/network-scripts/ifcfg-eth0
# Intel Corporation 82801BA/BAM/CA/CAM Ethernet Controller
DEVICE=eth0
ONBOOT=yes
DHCPCDARGS="-S <names deleted here>"
NETMASK=255.255.255.0
IPADDR=<valid IP address deleted>
GATEWAY=<valid IP address deleted>
TYPE=Ethernet

Help! (whimper...)

So, of curse it comes up fine after a hard reboot. sheesh.