Dave Howorth wrote:
Go to /etc/modules.conf and check, if eth0 is assigned to e1000.
Andreas, many thanks for your continuing patience and help.
eth0 appears in two lines and one's a comment:
alias eth0 off
#alias eth0 nvnet
e1000 does not occur in the file. I don't know anything about kernel modules or this file, so after a quick look at the man page I did 'modprobe -c', expecting to see a line for e1000 (because I have now installed that module) but there was nothing, just the same line for eth0.
Please change the line: alias eth0 off to: alias eth0 e1000 Then reboot...
I'd guess that taking out the 'alias eth0 off' line might permit the module to load properly, but I'm nervous about making changes when (a) I don't understand how/why it got to be like that, and (b) I suspect there may be a SuSE-way (yast?) to make the change rather than just edit the file. I made the change but it didn't change the behaviour so I've put it back how it was
I don't know yast[2] very good, maybe there are ways, but i know none.
And maybe check your bootup "dmesg | less".
The only lines referring to the e1000 driver are at the end:
Intel(R) PRO/1000 Network Driver - version 5.2.13 Copyright (c) 1999-2003 Intel Corporation. PCI: Setting latency timer of device 02:01.0 to 64 eth0: Intel(R) PRO/1000 Network Connection e1000: eth0 NIC Link is Up 100 Mbps Full Duplex eth0: no IPv6 routers present
which look good to me, but they were added by my manual modprobe command :( These are also the only reference to eth0.
-- Andreas