On 2/28/06, Per Jessen
What you need to do is make sure the system loads the right driver. The kernel has a whole section called "Tulip family network drivers", of which one option is "Davicom DM910x/DM980x support". The module is called "dmfe". I think that's what you're after - if you want to be sure, send us the PCI-ids (hex-numbers printed out by lspci -n) of the Davicom device.
Below is the last bit of lspci -v (only the Davicom portion) and then the lspci -n where the last entry is, I think, the one that matches the Davicom portion of lspci -v 02:02.0 Ethernet controller: Davicom Semiconductor, Inc. 21x4x DEC-Tulip compati ble 10/100 Ethernet (rev 31) Subsystem: Unknown device 4554:434e Flags: bus master, medium devsel, latency 64, IRQ 9 I/O ports at d800 [size=256] Memory at feaefc00 (32-bit, non-prefetchable) [size=256] Expansion ROM at f4700000 [disabled] [size=256K] Capabilities: [50] Power Management version 2 linux:~ # lspci -n 00:00.0 Class 0600: 8086:1a30 (rev 11) 00:01.0 Class 0604: 8086:1a31 (rev 11) 00:1d.0 Class 0c03: 8086:24c2 (rev 01) 00:1d.1 Class 0c03: 8086:24c4 (rev 01) 00:1d.2 Class 0c03: 8086:24c7 (rev 01) 00:1d.7 Class 0c03: 8086:24cd (rev 01) 00:1e.0 Class 0604: 8086:244e (rev 81) 00:1f.0 Class 0601: 8086:24c0 (rev 01) 00:1f.1 Class 0101: 8086:24cb (rev 01) 00:1f.3 Class 0c05: 8086:24c3 (rev 01) 00:1f.5 Class 0401: 8086:24c5 (rev 01) 01:00.0 Class 0300: 10de:0172 (rev a3) 02:01.0 Class 0780: 14f1:2016 (rev 01) 02:02.0 Class 0200: 1282:9102 (rev 31)
You didn't say anything about which kernel version you've got, so you may or may not have this module. Try "modprobe dmfe" and let us know what it says - optionally post the last few lines of "dmesg".
modprobe dmfe returns nothing ... I hit enter, and I just get a new bash line here is some output of dmesg: 0000:02:02.0: tulip_stop_rxtx() failed martian source 255.255.255.255 from 192.168.2.1, on dev eth0 ll header: ff:ff:ff:ff:ff:ff:00:04:e2:75:cb:2a:08:00 0000:02:02.0: tulip_stop_rxtx() failed 0000:02:02.0: tulip_stop_rxtx() failed 0000:02:02.0: tulip_stop_rxtx() failed martian source 255.255.255.255 from 169.254.155.50, on dev eth0 ll header: ff:ff:ff:ff:ff:ff:00:0e:35:6e:f7:2e:08:00 martian source 255.255.255.255 from 169.254.155.50, on dev eth0 ll header: ff:ff:ff:ff:ff:ff:00:0e:35:6e:f7:2e:08:00 martian source 255.255.255.255 from 169.254.155.50, on dev eth0 ll header: ff:ff:ff:ff:ff:ff:00:0e:35:6e:f7:2e:08:00 0000:02:02.0: tulip_stop_rxtx() failed martian source 255.255.255.255 from 192.168.2.1, on dev eth0 ll header: ff:ff:ff:ff:ff:ff:00:04:e2:75:cb:2a:08:00 0000:02:02.0: tulip_stop_rxtx() failed 0000:02:02.0: tulip_stop_rxtx() failed [tons and tons of these] 0000:02:02.0: tulip_stop_rxtx() failed dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17) 0000:02:02.0: tulip_stop_rxtx() failed 0000:02:02.0: tulip_stop_rxtx() failed 0000:02:02.0: tulip_stop_rxtx() failed 0000:02:02.0: tulip_stop_rxtx() failed 0000:02:02.0: tulip_stop_rxtx() failed 0000:02:02.0: tulip_stop_rxtx() failed 0000:02:02.0: tulip_stop_rxtx() failed So -- what next? This nic works in windows, so the issue is not failed hardware. Peter (thanx again, Per!)