e100.txt 6.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183
  1. Linux* Base Driver for the Intel(R) PRO/100 Family of Adapters
  2. ==============================================================
  3. March 15, 2011
  4. Contents
  5. ========
  6. - In This Release
  7. - Identifying Your Adapter
  8. - Building and Installation
  9. - Driver Configuration Parameters
  10. - Additional Configurations
  11. - Known Issues
  12. - Support
  13. In This Release
  14. ===============
  15. This file describes the Linux* Base Driver for the Intel(R) PRO/100 Family of
  16. Adapters. This driver includes support for Itanium(R)2-based systems.
  17. For questions related to hardware requirements, refer to the documentation
  18. supplied with your Intel PRO/100 adapter.
  19. The following features are now available in supported kernels:
  20. - Native VLANs
  21. - Channel Bonding (teaming)
  22. - SNMP
  23. Channel Bonding documentation can be found in the Linux kernel source:
  24. /Documentation/networking/bonding.txt
  25. Identifying Your Adapter
  26. ========================
  27. For more information on how to identify your adapter, go to the Adapter &
  28. Driver ID Guide at:
  29. http://support.intel.com/support/network/adapter/pro100/21397.htm
  30. For the latest Intel network drivers for Linux, refer to the following
  31. website. In the search field, enter your adapter name or type, or use the
  32. networking link on the left to search for your adapter:
  33. http://downloadfinder.intel.com/scripts-df/support_intel.asp
  34. Driver Configuration Parameters
  35. ===============================
  36. The default value for each parameter is generally the recommended setting,
  37. unless otherwise noted.
  38. Rx Descriptors: Number of receive descriptors. A receive descriptor is a data
  39. structure that describes a receive buffer and its attributes to the network
  40. controller. The data in the descriptor is used by the controller to write
  41. data from the controller to host memory. In the 3.x.x driver the valid range
  42. for this parameter is 64-256. The default value is 64. This parameter can be
  43. changed using the command:
  44. ethtool -G eth? rx n, where n is the number of desired rx descriptors.
  45. Tx Descriptors: Number of transmit descriptors. A transmit descriptor is a data
  46. structure that describes a transmit buffer and its attributes to the network
  47. controller. The data in the descriptor is used by the controller to read
  48. data from the host memory to the controller. In the 3.x.x driver the valid
  49. range for this parameter is 64-256. The default value is 64. This parameter
  50. can be changed using the command:
  51. ethtool -G eth? tx n, where n is the number of desired tx descriptors.
  52. Speed/Duplex: The driver auto-negotiates the link speed and duplex settings by
  53. default. The ethtool utility can be used as follows to force speed/duplex.
  54. ethtool -s eth? autoneg off speed {10|100} duplex {full|half}
  55. NOTE: setting the speed/duplex to incorrect values will cause the link to
  56. fail.
  57. Event Log Message Level: The driver uses the message level flag to log events
  58. to syslog. The message level can be set at driver load time. It can also be
  59. set using the command:
  60. ethtool -s eth? msglvl n
  61. Additional Configurations
  62. =========================
  63. Configuring the Driver on Different Distributions
  64. -------------------------------------------------
  65. Configuring a network driver to load properly when the system is started is
  66. distribution dependent. Typically, the configuration process involves adding
  67. an alias line to /etc/modprobe.d/*.conf as well as editing other system
  68. startup scripts and/or configuration files. Many popular Linux
  69. distributions ship with tools to make these changes for you. To learn the
  70. proper way to configure a network device for your system, refer to your
  71. distribution documentation. If during this process you are asked for the
  72. driver or module name, the name for the Linux Base Driver for the Intel
  73. PRO/100 Family of Adapters is e100.
  74. As an example, if you install the e100 driver for two PRO/100 adapters
  75. (eth0 and eth1), add the following to a configuration file in /etc/modprobe.d/
  76. alias eth0 e100
  77. alias eth1 e100
  78. Viewing Link Messages
  79. ---------------------
  80. In order to see link messages and other Intel driver information on your
  81. console, you must set the dmesg level up to six. This can be done by
  82. entering the following on the command line before loading the e100 driver:
  83. dmesg -n 8
  84. If you wish to see all messages issued by the driver, including debug
  85. messages, set the dmesg level to eight.
  86. NOTE: This setting is not saved across reboots.
  87. ethtool
  88. -------
  89. The driver utilizes the ethtool interface for driver configuration and
  90. diagnostics, as well as displaying statistical information. The ethtool
  91. version 1.6 or later is required for this functionality.
  92. The latest release of ethtool can be found from
  93. http://ftp.kernel.org/pub/software/network/ethtool/
  94. Enabling Wake on LAN* (WoL)
  95. ---------------------------
  96. WoL is provided through the ethtool* utility. For instructions on enabling
  97. WoL with ethtool, refer to the ethtool man page.
  98. WoL will be enabled on the system during the next shut down or reboot. For
  99. this driver version, in order to enable WoL, the e100 driver must be
  100. loaded when shutting down or rebooting the system.
  101. NAPI
  102. ----
  103. NAPI (Rx polling mode) is supported in the e100 driver.
  104. See www.cyberus.ca/~hadi/usenix-paper.tgz for more information on NAPI.
  105. Multiple Interfaces on Same Ethernet Broadcast Network
  106. ------------------------------------------------------
  107. Due to the default ARP behavior on Linux, it is not possible to have
  108. one system on two IP networks in the same Ethernet broadcast domain
  109. (non-partitioned switch) behave as expected. All Ethernet interfaces
  110. will respond to IP traffic for any IP address assigned to the system.
  111. This results in unbalanced receive traffic.
  112. If you have multiple interfaces in a server, either turn on ARP
  113. filtering by
  114. (1) entering: echo 1 > /proc/sys/net/ipv4/conf/all/arp_filter
  115. (this only works if your kernel's version is higher than 2.4.5), or
  116. (2) installing the interfaces in separate broadcast domains (either
  117. in different switches or in a switch partitioned to VLANs).
  118. Support
  119. =======
  120. For general information, go to the Intel support website at:
  121. http://support.intel.com
  122. or the Intel Wired Networking project hosted by Sourceforge at:
  123. http://sourceforge.net/projects/e1000
  124. If an issue is identified with the released source code on the supported
  125. kernel with a supported adapter, email the specific information related to the
  126. issue to e1000-devel@lists.sourceforge.net.