Topic: Intel 82573L nic?

[fmilano]

Trying to get SME7 to work with an onboard Intel 82573L nic that runs off of the ICH7-M chipset through PCI-E

The nic card cant be initialized, and in dmesg I can see "e1000 probe error -5"

Thanks

[CharlieBrady]

Trying to get SME7 to work with an onboard Intel 82573L nic
...

You're not the first to report a problem with such a NIC:

http://bugs.contribs.org/show_bug.cgi?id=1123

From your description, your card is recognised by SME7, but the driver doesn't work correctly with the hardware.

I'd suggest you enable the updates testing repository, and update your system. That will install a new kernel which might work.

If not, I suggest that you just get another NIC which does work.

[fmilano]

I have fixed the  Intel 82573L nic problem.

You must rebuild the driver, in order for the system to recognize the nic.

Go to Intel.com and download the .tar.gz for 82573L (e1000-7.1.9.tar.gz)

You also need to download the required RPMS for your build environment. They can be found in the Centos repository.

requirements:

Files -

e1000-7.1.9.tar.gz

Build Environment -

autoconf-2.59-5.noarch.rpm
glibc-kernheaders-2.4-9.1.98.EL.i386.rpm
automake-1.9.2-3.noarch.rpm
libstdc++-3.4.5-2.i386.rpm
cpp-3.4.5-2.i386.rpm
libstdc++-devel-3.4.5-2.i386.rpm
gcc-3.4.5-2.i386.rpm
m4-1.4.1-16.i386.rpm
gcc-c++-3.4.5-2.i386.rpm
make-3.80-5.i386.rpm
glibc-devel-2.3.4-2.19.i386.rpm
glibc-headers-2.3.4-2.19.i386.rpm

Untar/Unzip archive:

tar -zxf e1000-x.x.x.tar.gz

Change to the driver src directory:

cd e1000-x.x.x.tar.gz/src/

Compile the driver module:

make install

The binary will be installed as:

/lib/modules/<kernel version>/kernel/drivers/net/e1000/e1000.ko

reboot

Fabio

[p1ur]

Hi
I hope for some help here
I have a mainboard from MSI, im-945gse. It has 2 gigabit LAN, perfect for a low watt sme-server.
BUT the LAN is by Intel with an 82574L Controller and it is not configured to work during installation.
Two extra nic is not an option, so I have tried to follow the above, and this:
http://bugs.contribs.org/show_bug.cgi?id=1123
At Intel I have found 2 files that might get the LAN to work:
http://downloadcenter.intel.com/filter_results.aspx?strTypes=all&ProductID=3023&OSFullName=Linux*&lang=eng&strOSs=39&submit=Go!
e1000-8.0.9.tar.gz or e1000e-0.5.18.3.tar.gz
At Centos I have found the rest of the files mentioned in bug=1123.
I have transferred the files to the server with a usb-key (no network)
But when I come to "make install" I get an error:
makefile:70: *** Linux kernel source not found in any of those locations:
makefile:71: ***
makefile:72: *** Install the appropriate kernel development package, e.g.
makefile:73: *** kernel-devel, for building kernel modules and try again. Stop

I am already way beyond known territory, but I still hope to make this work. Only other option is another serversoftware.
What is the right thing to do, to make this work?

P1ur

[p1ur]

Hi
I have come a bit further
1. Downloaded
autoconf-2.59-5.noarch.rpm
automake-1.9.2-3.noarch.rpm
cpp-3.4.6-10.i386.rpm
gcc-3.4.6-10.i386.rpm
gcc-c++-3.4.6-10.i386.rpm
glibc-devel-2.3.4-2.41.i386.rpm
glibc-headers-2.3.4-2.41.i386.rpm
glibc-kernheaders-2.4-9.1.103.EL.i386.rpm
libstdc++-3.4.6-10.i386.rpm
libstdc++-devel-3.4.6-10.i386.rpm
m4-1.4.1-16.i386.rpm
make-3.80-7.EL4.i386.rpm
from: http://mirror.centos.org/centos-4/4.7/os/i386/CentOS/RPMS/

2. Downloaded
kernel-devel-2.6.9-78.0.8.EL.i686.rpm
from http://rpm.pbone.net/index.php3/stat/4/idpl/10424960/com/kernel-devel-2.6.9-78.0.8.EL.i686.rpm.html

3. Downloaded
e1000e-0.5.18.3.tar.gz
from: http://support.intel.com/support/network/sb/cs-006120.htm -> http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=15817

4. Copied all files to an usb-pen
5. mounted the usbdisk: (in /media/) mount usbdisk
6. copied the files to admin/home (using mc)
7. installed: yum localinstall * in the directory, where the files is located
8. Signal event post-upgrade ; signal event reboot
9. unpacked: tar -zxf e1000e-0.5.18.3.tar.gz
10 in directory e1000e-0.5.18.3/src make install
11. Reboot

etho is up and running
but eth1 is not - It has a MAC-adress, but the ir-nr. is 1.1.1.1.

Any ideas what to do now?

p1ur

[p1ur]

Hi
I've got it up and running
Started all over with a workning nic. Installed as server only behind existing sme-server.
Updated via server-manger.
Found new kernel version with uname -r - 2.6.9-78.0.13EL
Found at matching kernel-devel, so the files are now:
autoconf-2.59-5.noarch.rpm
automake-1.9.2-3.noarch.rpm
cpp-3.4.6-10.i386.rpm
gcc-3.4.6-10.i386.rpm
gcc-c++-3.4.6-10.i386.rpm
glibc-devel-2.3.4-2.41.i386.rpm
glibc-headers-2.3.4-2.41.i386.rpm
glibc-kernheaders-2.4-9.1.103.EL.i386.rpm
libstdc++-3.4.6-10.i386.rpm
libstdc++-devel-3.4.6-10.i386.rpm
m4-1.4.1-16.i386.rpm
make-3.80-7.EL4.i386.rpm
---
kernel-devel-2.6.9-78.0.13.EL.i686.rpm
e1000-7.1.9.tar.gz

Made yum localinstall *

signal-event post-upgrade; signal-event reboot

tar -zxf e1000e-0.5.18.3.tar.gz
make install in src
reboot and enable NICs in bios
Changing to a Intel Gigabit NIC, and everything works fine (both NICs)

Changing serversettings to server and gateway. So my settings looks something like this:
Internet -> server1 -> switch -> server2 -> workstation
server1 (existing server) internel IP: 192.168.1.100, DHCP: 192.169.1.36-96. Static IP to server2: 192.168.1.2
server2 (new server, with Intel Gigabit NIC): Internel IP: 192.168.1.200, DHCP: 192.168.1.236-246

Server2 settings: gateway: 192.168.1.100
Server2 gets external IP 192.168.1.2, gives ip to workstation.
BUT, there is no connection to Internet from server2 or workstation? - What have I done wrong?? (I guess it's obvious, but I can't see what)'

Secondly. I guess that the way I have made it work, will get me in trouble later, ie when the kernel is updated?

[johnp]

What subnet mask are you using? 255.255.255.128?

[p1ur]

Subnet: 255.255.255.0 on both servers
Update:
And changing the subnet mask to 255.255.255.128 on server2 worked

Thanx
P1ur

[johnp]

If I understand correctly, server1 is in server-gateway mode. If that is the case, either you will have to change the subnet mask on the internal interface of server1, both interfaces on server2 to 255.255.255.128. Or use a different subnet on the internal of server2.

If you change the subnet mask, valid ip adresses for the internal will be 192.168.1.1-126 on server1 and 192.168.1.129-254 on server2. What you have now with 255.255.255.0 is 192.168.1.1-254 valid on both sides of server2.

Otherwise use something like 192.168.2.X for the internal of server2 if you need to service more hosts.
 

[p1ur]

Hi
I have forseen this problem:

Hi
...
Secondly. I guess that the way I have made it work, will get me in trouble later, ie when the kernel is updated?

And Yes, I cant update to 7.5, because of my unsupported NIC Intel 82573L, without doing something extra. 
So I'm going to give it a try.

The question is what to do and how.
I know that I have to download a number of files including kernel-devel and "make install"(?build new kernel?) but what files do I need? Is there a way to show the needed files?

And In what order should I do the update and the "make install"?
I know I cant make the update first (The server wont update because of missing files), but what will be the proper way to do - whatever I have to do?

Thanx in advance, I know this is not mainstream, but any help is appreciated

P1ur

[CharlieBrady]

The question is what to do and how.

Use a different NIC

Or:

Use SME8 beta.

[p1ur]

Hi Charlie

Thanks for the replay. And thanks for all your work with SME/contribs.
I can use a different NIC, but only temporally, because there isn't room for a "normal" NIC in the cabinet. (and I don't want a SME-server with open cabinet)
Does SME 8beta support Intel 82573L NIC?
If yes, can I upgrade from 7.4 to 8.0? - I'm okay with upgrading to beta.

P1ur

[CharlieBrady]

Does SME 8beta support Intel 82573L NIC?

I don't know. If you try it, you can tell us

[p1ur]

Okay lets travel this road.
I'll try a fresh install on a spare HD. I'll be back, then there is an update.
P1ur

[RBT]

I have just installed an Intel 82574L PCIe NIC in an SME 7.4 box.
It didn't wouldn't work first up, but after a yum update it's all working fine.
I think the original post was for an 82573L.