Andreas Winkelmann 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. 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
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. ------------------------------------------------------ BandiPat wrote:
There were problems with Mantel's 2.4.21-58, which is mostly corrected with the -59 build he presently has on his site. I still don't have 3D with the -59 build, but we have traced that down now as well and I am looking forward to the next one to get that back also. So far, the 2.4.21-59 build is working quite well.
Hmm, OK, a kernel that's less than a week old. I'm trying to build a system for a biologist to use reliably for their daily work, so you're making me nervous about stability. Anyway, I've installed the -59 kernel, but it seems to behave exactly like the -58 as far as I can tell in 5 minutes. I'd like to ask another question about this kernel. Once I get the network reliable, I'd like to set the BIOS to make the SATA drives visible in native mode. At the moment it's in legacy mode so I can't see the SATA drives, the PATA drive and the CD at the same time. At least the disks work reliably in this mode, and getting the network to boot is higher priority. But do you think native SATA will work? Thanks again, Dave