I have a brand new Linksys v4.1 LNE100TX. It's an AMDtek AL985 Centar-P as
reported by tulip-diag v2.04. This card is eth0
I've tried the tulip driver v0.92n 11/3/2000 from
I've tried the tulip driver v0.92i 7/31/2000 from the netdriver-2.0.src.rpm
I've tried the tulip driver v0.92 4/17/2000 from the Linux drivers that
Linksys tells you to use with this NIC (these don't even detect the chip
properly, it just shows up AMDtek Comet rev17, so we really won't consider
this, but I had to let you know I tested the "Linksys approved" one)
I'm using the newest pci-scan.c, pci-scan.h, and kern_compat.h from
ftp.scyld.com:/pub/network/ to compile my tulip.c modules
There are no driver error messages from dmesg when the module load (from any
of them). If I use a static IP, the card intializes (ifup eth0) without any
problems. However, if I use DHCP, the initializtion fails (initialization
NOTE-1: My cable provider does not lock to a single NIC MAC address either
(I've got 3 PCs now all pulling unique IPs off the DHCP server, no NAT).
NOTE-2: I also have a RealTek RTL8139 card in here, using the net-driver2.0
rtl8139 driver. This card will load up with as static IP AND a DHCP ip in
the same linux box, so pump (redhat 6.2) is working correctly for DHCP.
I've e-mailed Donald Becker but I havn't heard back since my last e-mail
from him that provided some tulip-diag info. Becker said that since the
driver is letting the card work fine with a static IP, then the NIC and the
driver are working fine.
Sooo.. My problem is obviously, why won't DHCP work?
After a failed init via DHCP on the Linksys card, ifconfig -a shows packets
in TX and RX columns with no errors or collisions. So the card is obviously
communicating, it just won't init via DHCP.
Does anyone have ANY ideas what I might be able to do to remedy this? If I
can't get this to work, I guess I'll be returning the Linksys and having a
try with a Netgear card.