As an example, if you install the e driver for two Gigabit adapters eth0 and eth1 and set the speed and duplex to 10full and half, add the following to modules. Ports 1 and 2 don’t show any errors and will pass traffic. The identification LEDs of the adapters supported by the em driver can be controlled via the led 4 API for localization purposes. If mediaopt is not specified, the driver defaults to half-duplex. This is caused by the way the Linux kernel reports this stressed condition. NAPI Rx polling mode is supported in the e driver. IntMode controls allow load time control over the type of interrupt registered for by the driver.

Uploader: JoJogis
Date Added: 5 August 2011
File Size: 11.4 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 56223
Price: Free* [*Free Regsitration Required]

I always thought linux worked best with Intel hardware which is why I use it. This default mode is suitable for most applications.

Only full-duplex mode is supported at this speed. We recommend the newer 2. LLI allows for immediate generation of an interrupt upon processing receive packets that match certain criteria as set by the parameters described below. This setting is not saved across reboots. Many popular Linux distributions ship with tools to make these changes for you.

If the traffic is mostly transmit or mostly receive, the interrupt rate could be as high as For more information on configuring this device, see ifconfig 8. Proper tuning, along with TxIntDelay, may improve traffic throughput in specific network conditions.


Downloads for Intel® 82541GI Gigabit Ethernet Controller

It only needs to be set for Jumbo Frames. An interrupt is sent to the PF driver notifying it of the spoof attempt.

Connecting the system to a switch or router will filter out most traffic not addressed to the local port. If this occurs, the driver will report a “TX Timeout” and reset the adapter, after which the transmit flow will restart, though data may have stalled for as much as 10 seconds before it resumes.

If CPU utilization is not a concern, use default driver settings. Useful only if TxIntDelay is non-zero, this value ensures that an interrupt is generated after the initial packet is sent on the wire within linuxx set 82541ti of time.

Each descriptor is 16 bytes.

Linux Driver for Intel® Gigabit Network Connections

This value coincides with the maximum Jumbo Frames size of bytes. If you currently have the e driver installed and need to install ee, perform the following:.

First identify your adapter. After installing the driver, if your Intel Ethernet Network Connection is not working, verify that you have installed the correct driver. If mediaopt is not specified, the driver defaults to half-duplex.

Ubuntu Manpage: em — Intel(R) PRO/ Gigabit Ethernet adapter driver

If you believe your system needs to disable this style of interrupt, the driver can be built and installed with the command: LRO combines multiple Ethernet frames into a single receive in the stack, thereby potentially decreasing CPU utilization for receives. Defines the direction 825541gi which data is allowed to flow.


All interrupts are throttled via interrupt moderation. Adapters that have 4 ports behind a PCIe bridge may be incompatible with some systems.

Linux* Base Drivers for Intel® Ethernet Network Connection

Only use mediaopt to set the driver to full-duplex. The algorithm classifies the incoming traffic every interval into classes. If you have a machine with a BMC enabled but cannot receive IPMI traffic after loading or enabling the driver, try disabling this feature. MSI-X is required for multiple queue support, and some kernels and combinations of kernel.

LLI parameters are not enabled when Legacy interrupts are used. Setting InterruptThrottleRate to 0 turns off any interrupt moderation and may improve small packet latency, but is generally not suitable for bulk throughput traffic.

This parameter is different than other parameters, in that it is a single not 1,1,1 etc. The moderation value should be at least as large as the expected time for the driver to process an interrupt. That was causing the issue with pings not working when eth1 was up. This issue may be seen with PCI-X adapters or with packet split disabled.