In brief, it's cactus. Aand to be fair to Don, I've not tried this kernel on
any other NIC, so don't know for certain this problem is specific to this
driver.
I have a working network with 2.4.2, and my kernel's configured to configure
the interface with BOOTP.
I came up in single-user mode with 2.4.3 and get this:
[ OK ]
Mounting local filesystems [ OK ]
Turning on user and group quotas for local filesystems [ OK ]
Enabling swap space [ OK ]
sh-2.03# ifconfig
eth0 Link encap:Ethernet HWaddr 00:E0:29:07:3B:1B
inet addr:192.168.1.6 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:10 Base address:0x9400
sh-2.03# ping -c4 192.168.1.6
connect: Invalid argument
sh-2.03# uname -a
Linux possum 2.4.3 #2 Tue Apr 3 09:45:49 WST 2001 i686 unknown
sh-2.03# cat >epic.bug
sh-2.03# service gpm start
Starting gpm mouse services: [ OK ]
Note the "invalid argment" when I try to ping myself.
Relevant fragments from dmesg:
ttyS01 at 0x02f8 (irq = 3) is a 16550A
epic100.c:v1.11 1/7/2001 Written by Donald Becker <becker@scyld.com>
http://www.scyld.com/network/epic100.html
(unofficial 2.4.x kernel port, version 1.1.6, January 11, 2001)
PCI: Found IRQ 10 for device 00:0c.0
epic100(00:0c.0): MII transceiver #3 control 3000 status 7809.
epic100(00:0c.0): Autonegotiation advertising 01e1 link partner 0001.
eth0: SMSC EPIC/100 83c170 at 0x9400, IRQ 10, 00:e0:29:07:3b:1b.
SCSI subsystem driver Revision: 1.00
<snip>
TCP: Hash tables configured (established 16384 bind 16384)
Sending BOOTP requests....<7>uhci.c: root-hub INT complete: port1: 1a3 port2: 80 data: 2
uhci.c: root-hub INT complete: port1: 1a3 port2: 80 data: 2
<duplicates deleted>
uhci.c: root-hub INT complete: port1: 1a3 port2: 80 data: 2
. OK
IP-Config: Got BOOTP answer from 192.168.1.1, my address is 192.168.1.6
ip_conntrack (1535 buckets, 12280 max)
ip_tables: (c)2000 Netfilter core team
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
