readme

Intel 82546系列lan driver源码

an unusable LAN device.  This option is provided to override that protection
in order to update the NVM as-needed via ethtool or other means.  Once any 
necessary NVM change is complete, it is highly recommended to reload the 
driver with this option set back to the default (enabled) to reinstate the 
write-protection.


Additional Configurations
=========================

  Configuring the Driver on Different Distributions
  -------------------------------------------------
  Configuring a network driver to load properly when the system is started
  is distribution dependent.  Typically, the configuration process involves
  adding an alias line to /etc/modules.conf or /etc/modprobe.conf as well
  as editing other system startup scripts and/or configuration files.  Many
  popular Linux distributions ship with tools to make these changes for you.
  To learn the proper way to configure a network device for your system,
  refer to your distribution documentation.  If during this process you are
  asked for the driver or module name, the name for the Linux Base Driver
  for the Gigabit Family of Adapters is e1000e.

  As an example, if you install the e1000e driver for two Gigabit adapters 
  (eth0 and eth1) and want to set the interrupt mode to MSI-X and MSI 
  respectively, add the following to modules.conf or /etc/modprobe.conf:

       alias eth0 e1000e
       alias eth1 e1000e
       options e1000e IntMode=2,1

  Viewing Link Messages
  ---------------------
  Link messages will not be displayed to the console if the distribution is
  restricting system messages.  In order to see network driver link messages
  on your console, set dmesg to eight by entering the following:

       dmesg -n 8

  NOTE: This setting is not saved across reboots.

  Jumbo Frames
  ------------
  Jumbo Frames support is enabled by changing the MTU to a value larger than
  the default of 1500.  Use the ifconfig command to increase the MTU size.
  For example:

       ifconfig eth<x> mtu 9000 up

  This setting is not saved across reboots.  It can be made permanent if
  you add:

       MTU=9000

   to the file /etc/sysconfig/network-scripts/ifcfg-eth<x>.  This example
   applies to the Red Hat distributions; other distributions may store this
   setting in a different location.

  Notes:

  - To enable Jumbo Frames, increase the MTU size on the interface beyond
    1500.

  - The maximum MTU setting for Jumbo Frames is 9216.  This value coincides
    with the maximum Jumbo Frames size of 9234 bytes. 

  - Using Jumbo Frames at 10 or 100 Mbps may result in poor performance or
    loss of link.

  - Adapters based on the Intel(R) 82573V/E controller do not support 
    Jumbo Frames. These correspond to the following product names:
     Intel(R) PRO/1000 Gigabit Server Adapter
     Intel(R) PRO/1000 PM Network Connection

  - The following adapters do not support Jumbo Frames:
     Intel(R) 82562V 10/100 Network Connection
     Intel(R) 82566DM Gigabit Network Connection
     Intel(R) 82566DC Gigabit Network Connection
     Intel(R) 82566MM Gigabit Network Connection
     Intel(R) 82566MC Gigabit Network Connection
     Intel(R) 82562GT 10/100 Network Connection
     Intel(R) 82562G 10/100 Network Connection
     Intel(r) 82566DC-2 Gigabit Network Connection
     Intel(R) 82562V-2 10/100 Network Connection
     Intel(R) 82562G-2 10/100 Network Connection
     Intel(R) 82562GT-2 10/100 Network Connection

  Ethtool
  -------
  The driver utilizes the ethtool interface for driver configuration and
  diagnostics, as well as displaying statistical information.  Ethtool
  version 3 or later is required for this functionality, although we 
  strongly recommend downloading the latest version at:

  http://sourceforge.net/projects/gkernel.

  Speed and Duplex
  ----------------
  Speed and Duplex are configured through the Ethtool* utility.  Ethtool is 
  included with all versions of Red Hat after Red Hat 7.2.  For other Linux 
  distributions, download and install Ethtool from the following website:
  http://sourceforge.net/projects/gkernel.

  Enabling Wake on LAN* (WoL)
  ---------------------------
  WoL is configured through the Ethtool* utility.  Ethtool is included with
  all versions of Red Hat after Red Hat 7.2.  For other Linux distributions,
  download and install Ethtool from the following website:
  http://sourceforge.net/projects/gkernel.

  For instructions on enabling WoL with Ethtool, refer to the website listed
  above.

  WoL will be enabled on the system during the next shut down or reboot.
  For this driver version, in order to enable WoL, the e1000e driver must be
  loaded when shutting down or rebooting the system.

  Wake On LAN is only supported on port A for the following devices:
  Intel(R) PRO/1000 PT Dual Port Network Connection
  Intel(R) PRO/1000 PT Dual Port Server Connection
  Intel(R) PRO/1000 PT Dual Port Server Adapter
  Intel(R) PRO/1000 PF Dual Port Server Adapter
  Intel(R) PRO/1000 PT Quad Port Server Adapter
  Intel(R) Gigabit PT Quad Port Server ExpressModule 

  NAPI
  ----
  NAPI (Rx polling mode) is supported in the e1000e driver.  NAPI is enabled
  by default.

  To disable NAPI, compile the driver module, passing in a configuration option:

       # make CFLAGS_EXTRA=-DE1000E_NO_NAPI install

  See www.cyberus.ca/~hadi/usenix-paper.tgz for more information on NAPI.

  To Enable a Separate Vector for TX
  ---------------------------------- 
  # make CFLAGS_EXTRA=-DCONFIG_E1000E_SEPARATE_TX_HANDLER

  This will allocate a separate handler for tx cleanups. This might be useful 
  if you have a lot of CPU cores under heavy load and want to spread the 
  processing load around.  

  With this option, you would get three MSI-X vectors: one for TX, one for RX, 
  and one for link.


Known Issues/Troubleshooting
============================

  NOTE: After installing the driver, if your Intel Network Connection is not 
  working, verify in the "In This Release" section of the readme that you have 
  installed the correct driver.

  Intel(R) Active Management Technology 2.0, 2.1, 2.5 not supported in 
  conjunction with Linux driver
  ---------------------------------------------------------------------

  Detected Tx Unit Hang in Quad Port Adapters
  -------------------------------------------
  In some cases ports 3 and 4 don't pass traffic and report 'Detected Tx Unit
  Hang' followed by 'NETDEV WATCHDOG: ethX: transmit timed out' errors. Ports 
  1 and 2 don't show any errors and will pass traffic.

  This issue MAY be resolved by updating to the latest kernel and BIOS. The 
  user is encouraged to run an OS that fully supports MSI interrupts. You can 
  check your system's BIOS by downloading the Linux Firmware Developer Kit 
  that can be obtained at http://www.linuxfirmwarekit.org/

  Adapters with 4 ports behind a PCIe bridge 
  ------------------------------------------
  Adapters that have 4 ports behind a PCIe bridge may be incompatible with 
  some systems. The user should run the Linux firmware kit from 2686434
  http://www.linuxfirmwarekit.org to test their BIOS, if they have interrupt or 
  "missing interface" problems, especially with older kernels.

  82573(V/L/E) TX Unit Hang Messages
  ----------------------------------
  Several adapters with the 82573 chipset display "TX unit hang" messages 
  during normal operation with the e1000e driver. The issue appears both with 
  TSO enabled and disabled, and is caused by a power management function that 
  is enabled in the EEPROM. Early releases of the chipsets to vendors had the 
  EEPROM bit that enabled the feature. After the issue was discovered newer 
  adapters were released with the feature disabled in the EEPROM. 

  If you encounter the problem in an adapter, and the chipset is an 82573-based
  one, you can verify that your adapter needs the fix by using ethtool: 

  # ethtool -e eth0
  Offset          Values
  ------          ------
  0x0000          00 12 34 56 fe dc 30 0d 46 f7 f4 00 ff ff ff ff
  0x0010          ff ff ff ff 6b 02 8c 10 d9 15 8c 10 86 80 de 83
                                                           ^^
  The value at offset 0x001e (de) has bit 0 unset. This enables the problematic 
  power saving feature. In this case, the EEPROM needs to read "df" at offset 
  0x001e. 

  A one-time EEPROM fix is available as a shell script. This script will verify 
  that the adapter is applicable to the fix and if the fix is needed or not. If 
  the fix is required, it applies the change to the EEPROM and updates the 
  checksum. The user must reboot the system after applying the fix if changes 
  were made to the EEPROM. 

  Example output of the script: 

  # bash fixeep-82573-dspd.sh eth0
  eth0: is a "82573E Gigabit Ethernet Controller"
  This fixup is applicable to your hardware
  executing command: ethtool -E eth0 magic 0x109a8086 offset 0x1e value 0xdf
  Change made. You *MUST* reboot your machine before changes take effect!

  The script can be downloaded at 
  http://e1000.sourceforge.net/files/fixeep-82573-dspd.sh

  Dropped Receive Packets on Half-duplex 10/100 Networks
  ------------------------------------------------------
  If you have an Intel PCI Express adapter running at 10mbps or 100mbps, half-
  duplex, you may observe occasional dropped receive packets.  There are no
  workarounds for this problem in this network configuration.  The network must
  be updated to operate in full-duplex, and/or 1000mbps only.

  Driver Compilation
  ------------------
  When trying to compile the driver by running make install, the following
  error may occur:

    "Linux kernel source not configured - missing version.h"

  To solve this issue, create the version.h file by going to the Linux source
  tree and entering:

    # make include/linux/version.h.

  Jumbo Frames System Requirement
  -------------------------------
  Memory allocation failures have been observed on Linux systems with 64 MB
  of RAM or less that are running Jumbo Frames.  If you are using Jumbo
  Frames, your system may require more than the advertised minimum
  requirement of 64 MB of system memory.

  Performance Degradation with Jumbo Frames
  -----------------------------------------
  Degradation in throughput performance may be observed in some Jumbo frames
  environments.  If this is observed, increasing the application's socket
  buffer size and/or increasing the /proc/sys/net/ipv4/tcp_*mem entry values
  may help.  See the specific application manual and
  /usr/src/linux*/Documentation/networking/ip-sysctl.txt for more details.

  Jumbo Frames on Foundry BigIron 8000 switch
  -------------------------------------------
  There is a known issue using Jumbo frames when connected to a Foundry
  BigIron 8000 switch.  This is a 3rd party limitation.  If you experience
  loss of packets, lower the MTU size.

  Allocating Rx Buffers when Using Jumbo Frames 
  ---------------------------------------------
  Allocating Rx buffers when using Jumbo Frames on 2.6.x kernels may fail if 
  the available memory is heavily fragmented. This issue may be seen with PCI-X 
  adapters or with packet split disabled. This can be reduced or eliminated 
  by changing the amount of available memory for receive buffer allocation, by
  increasing /proc/sys/vm/min_free_kbytes. 

  Multiple Interfaces on Same Ethernet Broadcast Network
  ------------------------------------------------------
  Due to the default ARP behavior on Linux, it is not possible to have
  one system on two IP networks in the same Ethernet broadcast domain
  (non-partitioned switch) behave as expected.  All Ethernet interfaces
  will respond to IP traffic for any IP address assigned to the system.
  This results in unbalanced receive traffic.

  If you have multiple interfaces in a server, either turn on ARP
  filtering by entering:

    echo 1 > /proc/sys/net/ipv4/conf/all/arp_filter
  (this only works if your kernel's version is higher than 2.4.5),

  NOTE: This setting is not saved across reboots.  The configuration
  change can be made permanent by adding the line:
    net.ipv4.conf.all.arp_filter = 1
  to the file /etc/sysctl.conf

      or,

  install the interfaces in separate broadcast domains (either in
  different switches or in a switch partitioned to VLANs).

  Disable rx flow control with ethtool
  ------------------------------------
  In order to disable receive flow control using ethtool, you must turn
  off auto-negotiation on the same command line.

  For example:

   ethtool -A eth? autoneg off rx off

  Unplugging network cable while ethtool -p is running
  ----------------------------------------------------
  In kernel versions 2.5.50 and later (including 2.6 kernel), unplugging 
  the network cable while ethtool -p is running will cause the system to 
  become unresponsive to keyboard commands, except for control-alt-delete.  
  Restarting the system appears to be the only remedy.

  MSI-X Issues with Kernels between 2.6.19 - 2.6.21 (inclusive)
  -------------------------------------------------------------
  Kernel panics and instability may be observed on any MSI-X hardware if you 
  use irqbalance with kernels between 2.6.19 and 2.6.21. If such problems are 
  encountered, you may disable the irqbalance daemon or upgrade to a newer 
  kernel.

  Rx Page Allocation Errors
  -------------------------
  Page allocation failure. order:0 errors may occur under stress with kernels 
  2.6.25 and above. This is cause by the way the Linux kernel reports this 
  stressed condition.

Support
=======

For general information, go to the Intel support website at:

    http://support.intel.com

or the Intel Wired Networking project hosted by Sourceforge at:

    http://sourceforge.net/projects/e1000

If an issue is identified with the released source code on the supported
kernel with a supported adapter, email the specific information related
to the issue to [e-mail]



License
=======

Intel Gigabit Linux driver.
Copyright(c) 1999 - 2008 Intel Corporation.

This program is free software; you can redistribute it and/or modify it
under the terms and conditions of the GNU General Public License,
version 2, as published by the Free Software Foundation.

This program is distributed in the hope it will be useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for
more details.

You should have received a copy of the GNU General Public License along with
this program; if not, write to the Free Software Foundation, Inc.,
51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.

The full GNU General Public License is included in this distribution in
the file called "COPYING".



Trademarks
==========

Intel, Itanium, and Pentium are trademarks or registered trademarks of
Intel Corporation or its subsidiaries in the United States and other
countries.

* Other names and brands may be claimed as the property of others.