Peter Van Lone wrote:
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 [snip] 02:02.0 Class 0200: 1282:9102 (rev 31)
OK, the '1282' identifies the manufacturer to be Davicom Semiconductor, Inc., and the '9102' means "21x4x DEC-Tulip compatible 10/100 Ethernet", which is of course what lspci/YaST tells us. (You can look up PCI ids in /usr/share/pci.ids). I checked the source for the dmfe module, and it is definitely the right driver for that chip.
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.
You need to look a bit further back in the dmesg output. I don't know what the tulip_stop_rxtx() failed means, but at the very least we should see the module being loaded and recognising the chip. If you don't know where to look, just send the entire dmesg output to me (off-line) and I'll have a look. Also, once you've loaded the "dmfe" module, check if you've got a new ethernet device - cat /proc/net/dev/. /Per Jessen, Zürich