Difference between revisions of "Ethernet Controllers"

From ThinkWiki
Jump to: navigation, search
(another possible solution for latency issue -- RxIntDelay=5)
m (formatting stuff)
Line 53: Line 53:
 
Note: Some users report issues: [[Problem_with_e1000:_EEPROM_Checksum_Is_Not_Valid]]<br>
 
Note: Some users report issues: [[Problem_with_e1000:_EEPROM_Checksum_Is_Not_Valid]]<br>
 
Note: Some users have reported [http://forum.thinkpads.com/viewtopic.php?p=201279&sid=787564d7cf9de5d7d76b0cb312a98c61 latency problems] with e1000 driver. It seems, that [http://agenda.clustermonkey.net/index.php/Tuning_Intel_e1000_NICs switching off Interupt Throttle Rate (ITR)] helps. <br>
 
Note: Some users have reported [http://forum.thinkpads.com/viewtopic.php?p=201279&sid=787564d7cf9de5d7d76b0cb312a98c61 latency problems] with e1000 driver. It seems, that [http://agenda.clustermonkey.net/index.php/Tuning_Intel_e1000_NICs switching off Interupt Throttle Rate (ITR)] helps. <br>
Note: [http://support.intel.com/support/network/sb/CS-009209.htm Additional configuration options from Intel]
+
Note: [http://support.intel.com/support/network/sb/CS-009209.htm Additional configuration options from Intel]<br/>
Another possibility is using "RxIntDelay=5".
+
Note: Another possibility is to use "RxIntDelay=5".
  
 
For Gentoo users - compile e1000 as a kernel module and add 'options e1000 InterruptThrottleRate=0,0' to /etc/modules.d/e1000
 
For Gentoo users - compile e1000 as a kernel module and add 'options e1000 InterruptThrottleRate=0,0' to /etc/modules.d/e1000

Revision as of 17:20, 25 November 2006

Internal Ethernet controller

A variety of Ethernet controllers is integrated into almost all models starting with the introduction of the A, T and X series.

The Ethernet controller is located on either a MiniPCI card, Communications Daughter Card (CDC), or integrated on the systemboard.

3COM Fast Ethernet (10/100)

MiniPCI cards featuring this chip:

Intel Fast Ethernet (10/100)

CDC and MiniPCI cards featuring this chip:

In addition, this chip is integrated into select systemboards of the following machines:
Intel 82550GY

Intel 82558

Intel 82562ET

Intel 82562EZ

Driver: e100 (The 'e100' driver is the suggested driver, but 'eepro100' should also work.)

Intel Gigabit (10/100/1000)

Chipset: Intel PRO/1000 MT Mobile Ethernet
Driver: e1000

This chip is integrated into select systemboards of the following machines:
Intel 82540EP

Intel 82541GI

Intel 82573L (PCI-Express)

Note: This chip supports Auto-MDIX, meaning you will never need a crossover ethernet cable.
Note: The first signs of explicit support for this chip in 2.6 kernels is with 2.6.12-rc2.
Note: Red Hat Enterprise Linux 3.0 (2.4 kernel based) begins 82573L support with Update 7.
Note: Some users report issues: Problem_with_e1000:_EEPROM_Checksum_Is_Not_Valid
Note: Some users have reported latency problems with e1000 driver. It seems, that switching off Interupt Throttle Rate (ITR) helps.
Note: Additional configuration options from Intel
Note: Another possibility is to use "RxIntDelay=5".

For Gentoo users - compile e1000 as a kernel module and add 'options e1000 InterruptThrottleRate=0,0' to /etc/modules.d/e1000

Broadcom Fast Ethernet (10/100)

Driver: tg3 or bcm5700

This chip is integrated into select systemboards of the following machines:
Broadcom BCM5901

Broadcom BCM5751F

Broadcom Gigabit (10/100/1000)

Chipset: Broadcom BCM5751M
Driver: tg3 or bcm5700

This chip is integrated into select systemboards of the following machines:

Note: There are some problems with the driver since kernel 2.6.17 (at least on a Z61p, Z61m). After an ifdown && ifup it doesn't work anymore. A possible workaround is to build the tg3-driver as a module and reload it when this problem occours. (Adding pre-up modprobe tg3 and post-down rmmod tg3 to the corresponding section in /etc/network/interfaces works fine.) Rebooting the machine would also be possible. This is fixed in kenel 2.6.19-rc5.

The T43 with a stock Linus 2.6.18.1 kernel does not have any problems.