Peter Van Lone wrote:
I've attached a file in a seperate message offline to you, that contains the entire dmesg output after a reboot. I can't tell exactly why it is failing from this, perhaps you will be able to. It appears as though it identified the ip address of the dhcp server ...
OK, here are some snippets from the dmesg output you've sent me: --------- Linux Tulip driver version 1.1.13-NAPI (May 11, 2002) tulip0: EEPROM default media type Autosense. tulip0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block. tulip0: Index #1 - Media 10baseT (#0) described by a 21140 non-MII (0) block. tulip0: Index #2 - Media 100baseTx (#3) described by a 21140 non-MII (0) block. tulip0: Index #3 - Media 10baseT-FDX (#4) described by a 21140 non-MII (0) block. tulip0: Index #4 - Media 100baseTx-FDX (#5) described by a 21140 non-MII (0) block. tulip0: MII transceiver #1 config 3100 status 7809 advertising 01e1. eth0: Davicom DM9102/DM9102A rev 49 at 0001d800, 00:08:A1:23:26:6E, IRQ 9. 0000:02:02.0: tulip_stop_rxtx() failed eth0: Setting full-duplex based on MII#1 link partner capability of 45e1. ---------- So your card is found, it's using IRQ9 and has MAC-address 00:08:A1:23:26:6E.
linux:~ # cat /proc/net/dev [snip] 0 0 0 0 0 0 0 0 eth0: 2977 24 241 0 0 0 0 0
Yep, there it is - eth0.
linux:~ # modprobe dmfe
Which as you've observed doesn't seem to do much. Reason being that the Davicom chip is also handled by the tulip driver:
linux:~ # lsmod Module Size Used by [snip] tulip 51360 0
It looks like the Linux tulip driver also covers the Davicom chip - I'm not sure if the dmfe module is any better. To summarise - your card is being recognised by YaST and the right driver is loaded etc. So what sort of problem are you seeing now? /Per Jessen, Zürich