Pages

Friday, May 11, 2012

SLES 10.2 Network Failure

SUSE Linux Enterprise Sever 10 SP2, referred to as SLES 10.2 hereafter, is a very old Linux operating system and I do not recommend using it. However, I know some businesses still run ancient distributions of Linux because certain payrole and billing software is no longer maintained and other options can cost thousands.

So here it is, my set of solutions to common SLES 10.2 problems, some of which that have yet to be answered on Google.

Failure of SLES 10.2 to detect an integrated NIC
 If your fresh installation of SLES fails to recognize your common ethernet controller, it's probably because your NIC utilizes the e1000e driver-set rather than the e1000. Fortunately, this is an easy fix!! Assuming that you have no connectivity on the target machine, you will have to transfer any downloads via CD, Flash-media, or some other means.

1.) Download the e1000e driver set.
e1000e [v1.11.3] is the version I used and the latest as of this posting. [Download]
Here is the e1000e [Stable] directory if you'd like to check for a newer version. [Stable]

2.) Extract [untar] the driver set to a good working directory. I'm a GUI lover, so I was able to simply right-click the tar.gz and "extract" it to my desktop.

3.) Issue the following command to unload the e1000 module. 'modprobe -r e1000'

4.) Navigate to the "src" directory of the e1000e driver set that you just extracted and issue a 'make install'.

5.) Finally, 'modprobe e1000' and you should have connectivity. :)


Compile errors [make install] fails
When you attempt to compile or 'make install' you might receive an error saying that "kernel-devel" is required. This isn't the case and this error can throw you for a loop. You'll need the "kernel-source" and "gcc" packages to compile sources on SLES 10.2.

No comments: