Topic: SME5.6 / e1000 NIC

[Steve Bush]

Has anyone compiled the Intel e1000 NIC driver for 5.6b7.
I'm putting SME on a new Dell PE2600 server and I would
like to use the onboard NIC and an addon card.

fyi - SME found the onboard raid with no problem and installed perfectly!!!

[Charlie Brady]

Steve Bush wrote:
>
> Has anyone compiled the Intel e1000 NIC driver for 5.6b7.
> I'm putting SME on a new Dell PE2600 server and I would
> like to use the onboard NIC and an addon card.

The e1000 driver is a standard module.

/lib/modules/2.4.18-5/kernel/drivers/addon/e1000/e1000.o

> fyi - SME found the onboard raid with no problem and
> installed perfectly!!!

From what you say I guess that the NIC was not autodetected. Please send the output of "cat /proc/pci" and "lspci -vxx" to bugs@e-smith.com. Your NIC must not be one of the 12 Intel Gigabit NICs which are autodetected.

Regards

Charlie

[Steve Bush]

Thanks for the response.  The NIC's weren't autodetected.
I'll go into the office tonight to pull more information.

[Steve Bush]

I emailed the requested files along with an additional one that showed the nics being detected, but not transfered to SME.

/etc/sysconfig/hwinfo

The e1000 driver isn't an option when setting up the NICs

[Steve Bush]

I used the following message with a solution from Charlie to solve the problem.
http://www.mail-archive.com/devinfo@lists.e-smith.org/msg02327.html

I substituted e1000 for e100 and applied this to both EthernetDriver1 and 2.

/sbin/e-smith/db configuration set EthernetDriver1 e1000
/sbin/e-smith/db configuration set EthernetDriver2 e1000
/sbin/e-smith/signal-event console-save

I rebooted the server and the NICs both work....

[Boris]

Just run in exactly the same issue with DELL PE 1650 (two onboard Intel 1GB NICs).
The same solution as above helped.
Thanks Steve, Charly
Boris.
P.S. Is bug report needed since its the same problem just different family of the DELL servers?

[Steve Bush]

I'm glad the posting helped.

I can't answer to the bug report question.  The one I submitted has been closed with a message that it has been resolved, but I don't see it on the bugs list.

Maybe it is being treated as a feature instead of a bug since it wasn't in prior releases...

Steve

[Steve Bush]

fyi - I just installed the 5.6dev final release and it has the same issue.

[Charlie Brady]

Steve Bush wrote:

> fyi - I just installed the 5.6dev final release and it has
> the same issue.

Unfortunately RedHat moved the e1000 driver module from  net/e1000.o to drivers/addon/e1000/e1000.o without telling us and the console doesn't think to go looking there for an ethernet module, hence the e1000 doesn't show up in the pick lists. The bug has been entered into our engineering task tracking system, and will be allocated to be fixed according to the needs of our paying customers.

If someone were to submit a fix before we get to it, all the better for everyone.

Regards

Charlie

[Damien Curtain]

--- /usr/lib/perl5/site_perl/esmith/ethernet.pm.orig    Wed Jan 22 09:11:43 2003
+++ /usr/lib/perl5/site_perl/esmith/ethernet.pm Wed Jan 22 09:32:48 2003
@@ -64,32 +64,37 @@
     my $kernel = (split(' ', ))[2];
     close VERSION;
 
-    my $modules = "/lib/modules/" . $kernel . "/kernel/drivers/net";
-    unless (-d $modules)
-    {
-       # Also handle 2.2.x kernels
-       $modules = "/lib/modules/" . $kernel . "/net";
-    }
-
-    unless (opendir MODULES, $modules)
-    {
-       warn "Could not open network modules directory $modules: $!\n";
-       return;
-    }
+    my @modules_path = (
+            "/lib/modules/" . $kernel . "/net",
+            "/lib/modules/" . $kernel . "/kernel/drivers/net",
+            "/lib/modules/" . $kernel . "/kernel/drivers/addon/e100",
+            "/lib/modules/" . $kernel . "/kernel/drivers/addon/e1000"
+    );
 
     my %network_drivers;
-
-    foreach (readdir MODULES)
+    foreach my $modules (@modules_path)
     {
-       next if /^\.\.?$/;              # Ignore "." and ".."
-       next if -d;                     # Ignore directories
+        if (-d $modules)
+        {
+            unless (opendir MODULES, $modules)
+            {
+               warn "Could not open network modules directory $modules: $!\n";
+               return;
+            }
+
+            foreach (readdir MODULES)
+            {
+               next if /^\.\.?$/;              # Ignore "." and ".."
+               next if -d;                     # Ignore directories
+
+               s/\.o$//;
+               ++$network_drivers{$_};
+            }
 
-       s/\.o$//;
-       ++$network_drivers{$_};
+            closedir MODULES;
+        }
     }
 
-    closedir MODULES;
-
     my $pcitable = "/usr/share/hwdata/pcitable";
 
     unless (open(PCITABLE, $pcitable) ||


--
 Damien

[Shad Lords]

For those of you just waiting for the intel drivers for sme v5.6, I have
downloaded and compiled the latest version of the drivers for all e100 and
e1000 based cards.  I have also compiled the following utilities that go
with the drivers: iANS, inic-snmp, procfg, and procfgd.

You can find them here:

http://lordsfam.net/downloads/production/intel_drivers/

These have been tested on single and dual processor boards and appear to
work great.  As always please try theses yourself on a test box before
loading them on a production box.

After installing these rpm's the server manager will pick up on the new drivers.

-Shad

[.nate]

I just ran this as root:
 
# /etc/rc.d/init.d/network stop
# /sbin/insmod/e1000
# /etc/rc.d/init.d/network start
 
Brings up the internal GB NIC on a Dell box.