[eepro100] destination host unreachable

Lookman Fazal fazall@research.avayalabs.com
Mon Jan 21 17:02:00 2002

Hello All

I am running redhat 7.1 kernel 2.4.14(uname -r)

I have the Intel eepro100 card installed in addition to my 3Com card.
The 3Com works great

Doing the same for the Intel, I am unable to ping my default gateway, it
says destination host unreachable

Netstat -rn
P routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface   U        40 0          0
eth0   U        40 0          0
eth1       U        40 0          0
lo         UG       40 0          0
[root@warp /]# 

[root@warp /tmp]# more /etc/modules.conf
alias eth0 3c59x
alias parport_lowlevel parport_pc
alias eth1 eepro100
pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S
>/dev/null 2>&1 || :
alias sound-slot-0 sb
post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L
>/dev/null 2>&1 || :

[root@warp /downloads]# ./eepro100-diag -a -f
eepro100-diag.c:v2.06 12/10/2001 Donald Becker (becker@scyld.com)
Index #1: Found a Intel i82557/8/9 EtherExpressPro100 adapter at 0xfce0.
i82557 chip registers at 0xfce0:
  0c000050 05f95000 00000000 00080002 18250021 00000600
  No interrupt sources are pending.
   The transmit unit state is 'Suspended'.
   The receive unit state is 'Ready'.
  This status is normal for an activated but idle interface.
 The Command register has an unprocessed command 0c00(?!).

[root@warp src]# insmod e100
Using /lib/modules/2.4.14/net/e100.o
/lib/modules/2.4.14/net/e100.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters