FILE NAME:			hp-e1000-8.0.25-1.src.rpm

TITLE:			HP NC-Series Intel e1000 Driver for Linux

VERSION:			8.0.25

RELEASE:			1

LANGUAGE:			English

CATEGORY:			Software Solutions

DIVISIONS:			Enterprise and Mainstream Servers

PRODUCTS AFFECTED:
				HP NC340T PCI-X Quad-port Gigabit Server Adapter
				HP NC310F PCI-X Gigabit Server Adapter
				HP NC61xx Gigabit Server Adapter
				HP NC71xx Gigabit Server Adapter

OPERATING SYSTEM:
				Red Hat Enterprise Linux 6 AS/ES for AMD64/EM64T
				Red Hat Enterprise Linux 6 AS/ES for x86
				Red Hat Enterprise Linux 5 AS/ES for AMD64/EM64T
				Red Hat Enterprise Linux 5 AS/ES for x86
				SUSE LINUX Enterprise Server 11 for AMD64/EM64T
				SUSE LINUX Enterprise Server 11 for x86
				SUSE LINUX Enterprise Server 10 for AMD64/EM64T
				SUSE LINUX Enterprise Server 10 for x86

PREREQUISITES:
				ProLiant server supporting above operating systems
				256 MB RAM minimum
				Latest HP System ROM
				Build Environment Setup

				NOTE: Visit the following URL and download latest System ROM
				http://welcome.hp.com/country/us/en/support.html
				Select "Download drivers and software"

EFFECTIVE DATE:		02/08/2011

SUPERSEDES:			8.0.23-2

DESCRIPTION:
				This RPM contains the HP Tested and Approved Linux e1000 
				driver for use with the Server Adapters mentioned in the 
				PRODUCTS AFFECTED section of this document.

ENHANCEMENTS/FIXES:
				1) KMP is now built for each SLES kernel flavor
				2) RHEL 5 update 6 support has been added

Table of Contents
=================
Introduction
Packaging
Build Environment Setup
Installing the RPM Package
Uninstalling the RPM
Limitations
Caveats 


Introduction
============
This file describes the Linux Ethernet driver for HP NC-Series Intel 
Adapters mentioned in the PRODUCTS AFFECTED section of this document.

User guides and additional HP Network Adapter information can be found at:
http://h18004.www1.hp.com/products/servers/networking/index-nic.html


Packaging
=========
The driver is released in Kernel Module Package (KMP) source RPM format. KMP 
packages use macros that determine kernel flavors for which binary packages need
to be built based on spec file rules.

It is important to have the right build environment set up in order to compile a 
binary RPM from the source package.  See "Build Environment Setup" section below.


Build Environment Setup
========================
The e1000 package requires the presence of some packages that provide the 
right build environment. These packages provide kernel headers, makefiles and 
symbol files, though the last one is suggested only on SLES distributions.

RHEL installation:
	1. redhat-rpm-config package
	2. kernel-devel-<kernel_version> package
	3. kernel-<flavor>-devel-<kernel_version> package
	Eg: kernel-2.6.18.92.el5 requires kernel-devel-2.6.18-92.el5
	    kernel-PAE-2.6.18.92.el5 requires kernel-PAE-devel-2.6.18-92.el5

	See the "Caveats" section below for more details.

SLES Installation:
	1. kernel-source-<kernel_version> package
	2. kernel-syms-<kernel_version> package
	3. SLES11 requires kernel-<flavor>-devel-<kernel_version> package as well


Installing the RPM Package
=============================
1. This package requires a build environment.  Please refer to the
"Build Environment Setup" Section before proceding to the next step.

2. Install the source RPM package.

	# rpm -ivh hp-e1000-<version>.src.rpm

3. Build the binary RPM for the e1000 driver.

	RHEL 5:
	# rpmbuild -bb /usr/src/redhat/SPECS/hp-e1000.spec

	RHEL 6:
	# rpmbuild -bb ~/rpmbuild/SPECS/hp-e1000.spec

	SLES:
	# rpmbuild -bb /usr/src/packages/SPECS/hp-e1000.spec

	If you get an error during the build process, refer to the 
	"Build Environment Setup" section.

	NOTE: One can build binary RPM for a specfic kernel flavor as follows:

	# rpmbuild -bb SPECS/hp-e1000.spec --define "KVER <kver>"

	NOTE:  RHEL 5 x86 installations require the "--target" switch when
	building on Intel compatible machines. Please see the "Caveats" 
	section below for more details.

	#rpmbuild --target=i686 -bb /usr/src/redhat/SPECS/hp-e1000.spec

4. Check for the existence of a current version of the e1000 package as follows:
	
	RHEL
	# rpm -q kmod-hp-e1000-<flavor> 

	SLES
	# rpm -q hp-e1000-kmp-<flavor>

	If an old version of the package exists, the RPM package should be
	removed. Remove the corresponding tools package before removing 
	driver package.

	RHEL
	# rpm -e kmod-hp-e1000-<flavor>

	SLES
	# rpm -e hp-e1000-kmp-<flavor>

	Verify if the old hp-e1000 package has been removed as follows:

	RHEL
	# rpm -q kmod-hp-e1000-<kernel flavor>

	SLES
	# rpm -q hp-e1000-kmp-<kernel flavor>  

5. Install the new binary RPM package.

	RHEL 5
	# rpm -ivh \
	/usr/src/redhat/RPMS/<arch>/kmod-hp-e1000-<flavor>-<version>.<arch>.rpm 

	RHEL 6
	# rpm -ivh \
	~/rpmbuild/RPMS/<arch>/kmod-hp-e1000-<flavor>-<version>.<arch>.rpm 

	The modules are installed in the following directory:
	/lib/modules/<kernel_version>/extra/hp-e1000

	Note:  The "--nodeps" switch is required when installing to RHEL 5.4 and 
	RHEL 5.5. See the "Caveats" section below for more details.

	# rpm -ivh \
	/usr/src/redhat/RPMS/<arch>/kmod-hp-e1000-<flavor>-<version>.<arch>.rpm --nodeps 

	SLES
	# rpm -ivh RPMS/<arch>/hp-e1000-kmp-<version>-<flavor>.<arch>.rpm 

	The modules are installed in the following directory:
	/lib/modules/<kernel_version>/updates/hp-e1000

6. Configure your network setting and address. You may need to refer to your 
Linux vendor documentation. Helpful network configuration tools such as 
"yast2" in SLES or linuxconf/redhat-config-network/netconfig in Red Hat 
exist for easy configuration.

For SLES, user may have to specify the module as e1000 while configuring 
the network. The module can be specified in Hardware Details of Advanced 
configuration

7. Ensure that the /etc/modules.conf file is configured similar to the example 
listed below. The example below is presented as if more than one adapter is 
present. If so, one eth# instance should exist for each ethernet port. Refer to 
the modules.conf man page for more information.

	alias eth0 e1000
	alias eth1 e1000

For SLES, the configuration file is /etc/modprobe.conf or /etc/modprobe.conf.local

8. You can now reboot your server or restart the network services. Upon reboot 
the network should start with the e1000 driver loaded

To verify that the e1000 driver is loaded use the following command.

	# lsmod

You should find e1000 listed. You can also verify if the correct e1000 driver 
is loaded through any of the following methods. Note that version of the driver 
loaded should be same as that of the package version.

A. Look for driver load messages in the system log.

	#dmesg | grep Intel

You should see messages similar to the one below:

	Intel(R) PRO/1000 Network Driver - version x.x.x

B. Check the /var/log/messages file for similar messages as indicated in method A.

Note: To load the driver from command line use 'modprobe' instead of 'insmod'. 
Refer to the man pages for lsmod, ifconfig, rmmod, insmod, modprobe, modules.conf 
and modprobe.conf for more detailed information.


Uninstalling the RPM
====================
The following command will uninstall the RPM.

	RHEL
	# rpm -e kmod-hp-e1000-<kernel flavor>

	SLES
	# rpm -e hp-e1000-kmp-<kernel flavor>


Limitations
===========
Some Linux distributions may not add the default route back to a specified 
network device when a network stop/start command is used. Use the route 
command to add the default router back to the network device.

Some Linux distributions may not add the default assigned IP address back to 
a specified network device when using the following:

		ifconfig eth(x) down
		rmmod <module name>
		insmod <module name> <optional parameter changes>
		ifconfig eth(x) up

Another step to reassign the IP address back to the device may be required:

		ifconfig eth(x) <ip address>

Some Linux distributions may add multiple IP addresses with the same system 
name in the /etc/hosts file when configuring multiple network devices. 

An error regarding the "PCI_BUS_SPEED" may also be encountered. 33MHz is 
displayed for 33MHz bus speeds, however 66MHz speed will be reported for 
50MHz and 100MHz PCI-X busses as well as 66MHz PCI busses

Caveats
===========
1. The rpmbuild will fail the dependency check when building the non-base
(xen,pae,etc) kernel if the kernel-devel package is not installed. 
Example:  If the OS installed only the PAE kernel, then the user would need to
install the kernel-pae-devel and kernel-devel packages.

2. The use of a "--target" switch is required so that rpmbuild does not try
to find an i386 kernel on the system.  If the "--target" switch is not used
then the build will fail with bizarre messages stating that specific kernel
packages are not installed on the machine yet those packages do not exist.

3. The rpmbuild will fail if the redhat-rpm-config package is not installed 
because it cannot resolve the %kernel_module_package_buildreqs macro.  The 
error will be similar to the following: 

error: line xx: Dependency tokens must begin with alpha-numeric,'_'or'/': 
BuildRequires: %kernel_module_package_buildreqs

4. RPM uses KMP packaging dependency data to ensure the dependencies are met
before installing the binary RPM.  Red Hat maintains a whitelist of kernel
symbols which RPM uses to validate against the KMP binaries.  Some symbols 
may be in the kernel but not on the whitelist which results in a failed 
binary RPM install.  The user will need to use the "--nodeps" switch when 
installing the binary.  The e1000 driver uses the following symbol on 
RedHat EL5 Update 4 and Update 5 that is not on the whitelist:

ksym(napi_gro_flush) 

(C) Copyright 2002, 2003 - 2011  Hewlett-Packard Development Company, L.P.
Product names mentioned herein may be trademarks and/or registered trademarks
of their respective companies.