Ethernet drivers in linux

Linux Base Driver for Intel(R) Ethernet Network Connection¶

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

Contents¶

Identifying Your Adapter

Command Line Parameters

Identifying Your Adapter¶

For information on how to identify your adapter, and for the latest Intel network drivers, refer to the Intel Support website: https://www.intel.com/support

Command Line Parameters¶

If the driver is built as a module, the following optional parameters are used by entering them on the command line with the modprobe command using this syntax:

There needs to be a for each network port in the system supported by this driver. The values will be applied to each instance, in function order. For example:

In this case, there are two network ports supported by igb in the system.

NOTE: A descriptor describes a data buffer and attributes related to the data buffer. This information is accessed by the hardware.

max_vfs¶

This parameter adds support for SR-IOV. It causes the driver to spawn up to max_vfs worth of virtual functions. If the value is greater than 0 it will also force the VMDq parameter to be 1 or more.

The parameters for the driver are referenced by position. Thus, if you have a dual port adapter, or more than one adapter in your system, and want N virtual functions per port, you must specify a number for each port with each parameter separated by a comma. For example:

This will spawn 4 VFs on the first port.

This will spawn 2 VFs on the first port and 4 VFs on the second port.

NOTE: Caution must be used in loading the driver with these parameters. Depending on your system configuration, number of slots, etc., it is impossible to predict in all cases where the positions would be on the command line.

NOTE: Neither the device nor the driver control how VFs are mapped into config space. Bus layout will vary by operating system. On operating systems that support it, you can check sysfs to find the mapping.

NOTE: When either SR-IOV mode or VMDq mode is enabled, hardware VLAN filtering and VLAN tag stripping/insertion will remain enabled. Please remove the old VLAN filter before the new VLAN filter is added. For example:

Debug¶

This parameter adjusts the level debug messages displayed in the system logs.

Additional Features and Configurations¶

Jumbo Frames¶

Jumbo Frames support is enabled by changing the Maximum Transmission Unit (MTU) to a value larger than the default value of 1500.

Use the ifconfig command to increase the MTU size. For example, enter the following where is the interface number:

Alternatively, you can use the ip command as follows:

This setting is not saved across reboots. The setting change can be made permanent by adding ‘MTU=9000’ to the file:

For RHEL: /etc/sysconfig/network-scripts/ifcfg-eth

For SLES: /etc/sysconfig/network/

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

NOTE: Using Jumbo frames at 10 or 100 Mbps is not supported and may result in poor performance or loss of link.

ethtool¶

The driver utilizes the ethtool interface for driver configuration and diagnostics, as well as displaying statistical information. The latest ethtool version is required for this functionality. Download it at:

Enabling Wake on LAN (WoL)В¶

WoL is configured through the ethtool utility.

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

NOTE: Wake on LAN is only supported on port A of multi-port devices. Also Wake On LAN is not supported for the following device: — Intel(R) Gigabit VT Quad Port Server Adapter

Multiqueue¶

In this mode, a separate MSI-X vector is allocated for each queue and one for “other” interrupts such as link status change and errors. All interrupts are throttled via interrupt moderation. Interrupt moderation must be used to avoid interrupt storms while the driver is processing one interrupt. The moderation value should be at least as large as the expected time for the driver to process an interrupt. Multiqueue is off by default.

REQUIREMENTS: MSI-X support is required for Multiqueue. If MSI-X is not found, the system will fallback to MSI or to Legacy interrupts. This driver supports receive multiqueue on all kernels that support MSI-X.

NOTE: On some kernels a reboot is required to switch between single queue mode and multiqueue mode or vice-versa.

MAC and VLAN anti-spoofing feature¶

When a malicious driver attempts to send a spoofed packet, it is dropped by the hardware and not transmitted.

An interrupt is sent to the PF driver notifying it of the spoof attempt. When a spoofed packet is detected, the PF driver will send the following message to the system log (displayed by the “dmesg” command): Spoof event(s) detected on VF(n), where n = the VF that attempted to do the spoofing

Setting MAC Address, VLAN and Rate Limit Using IProute2 Tool¶

You can set a MAC address of a Virtual Function (VF), a default VLAN and the rate limit using the IProute2 tool. Download the latest version of the IProute2 tool from Sourceforge if your version does not have all the features you require.

Credit Based Shaper (Qav Mode)В¶

When enabling the CBS qdisc in the hardware offload mode, traffic shaping using the CBS (described in the IEEE 802.1Q-2018 Section 8.6.8.2 and discussed in the Annex L) algorithm will run in the i210 controller, so it’s more accurate and uses less CPU.

When using offloaded CBS, and the traffic rate obeys the configured rate (doesn’t go above it), CBS should have little to no effect in the latency.

The offloaded version of the algorithm has some limits, caused by how the idle slope is expressed in the adapter’s registers. It can only represent idle slopes in 16.38431 kbps units, which means that if a idle slope of 2576kbps is requested, the controller will be configured to use a idle slope of

2589 kbps, because the driver rounds the value up. For more details, see the comments on igb_config_tx_modes() .

NOTE: This feature is exclusive to i210 models.

Support¶

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

or the Intel Wired Networking project hosted by Sourceforge at:

If an issue is identified with the released source code on a supported kernel with a supported adapter, email the specific information related to the issue to e1000-devel @ lists . sf . net.

© Copyright The kernel development community.

Источник

Linux: Find out Ethernet card driver name

Under Linux, you use term called modules for device drivers. The driver can be loaded or unloaded as per your requirement using commands. Each driver or module gives the Linux information on how to control that particular Ethernet card. The name of each module (driver) is listed in the /etc/modules.conf file.

Command to find out Ethernet card driver name

You can try any one of the following command to find out your Ethernet card driver:

Or search a file called /var/log/dmesg:

You can also get driver name from config file:

• No ads and tracking
• In-depth guides for developers and sysadmins at Opensourceflare✨
• Join my Patreon to support independent content creators and start reading latest guides:
  • How to set up Redis sentinel cluster on Ubuntu or Debian Linux
  • How To Set Up SSH Keys With YubiKey as two-factor authentication (U2F/FIDO2)
  • How to set up Mariadb Galera cluster on Ubuntu or Debian Linux
  • A podman tutorial for beginners – part I (run Linux containers without Docker and in daemonless mode)
  • How to protect Linux against rogue USB devices using USBGuard

Join Patreon ➔

Search for eth0 string.

In above example 8139too is driver loaded for eth0. You can find out more information about this driver using modinfo command:

modinfo program to show information about a Linux Kernel module. You can also find out all loaded modules or drivers using lsmod command:

lsmod is a program to show the status of modules in the Linux Kernel.

🐧 Get the latest tutorials on Linux, Open Source & DevOps via

Category	List of Unix and Linux commands
Documentation	help • mandb • man • pinfo
Disk space analyzers	df • duf • ncdu • pydf
File Management	cat • cp • less • mkdir • more • tree
Firewall	Alpine Awall • CentOS 8 • OpenSUSE • RHEL 8 • Ubuntu 16.04 • Ubuntu 18.04 • Ubuntu 20.04
Linux Desktop Apps	Skype • Spotify • VLC 3
Modern utilities	bat • exa
Network Utilities	NetHogs • dig • host • ip • nmap
OpenVPN	CentOS 7 • CentOS 8 • Debian 10 • Debian 8/9 • Ubuntu 18.04 • Ubuntu 20.04
Package Manager	apk • apt
Processes Management	bg • chroot • cron • disown • fg • glances • gtop • jobs • killall • kill • pidof • pstree • pwdx • time • vtop
Searching	ag • grep • whereis • which
Shell builtins	compgen • echo • printf
Text processing	cut • rev
User Information	groups • id • lastcomm • last • lid/libuser-lid • logname • members • users • whoami • who • w
WireGuard VPN	Alpine • CentOS 8 • Debian 10 • Firewall • Ubuntu 20.04

Comments on this entry are closed.

The “ethtool” program has an option which will show the driver your Ethernet device is using:

# ethtool -i eth0
driver: tg3
version: 3.77
firmware-version: 5752-v3.13
bus-info: 0000:02:00.0

ethtool is the way to go, in my opinion. It also shows you bus information, which coupled with lspci can clarify which actual network card is using which driver.

To find out the exact name of the Ethernet card that you are using :

# lspci | grep -i Ethernet
02:00.0 Ethernet controller: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) (rev 01)
02:01.0 Ethernet controller: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) (rev 01)

It doesn’t provide driver or module information.

Источник

How do I install a network driver on Linux?

I want to use eth0 driver, but my network card is UNCLAIMED.

I use Killer e2200 Gigabit Ethernet controller.

Please tell me how to install the Networkdriver and how to use eth0 .

3 Answers 3

If you have installed OS and you want to run Network Card as new hardware, you must ask the vendor for network drivers. Usually network drivers come with source pakage of kernel modules. You must compile driver module for you kernel.

install «build essential» utilites

unpack your source pakage to some folder

After installation you can load just compiled module by enter command:

The latest network devices usually take a while to work their way into the Linux kernel. All drivers are usually built into big distributions like Debian (or Ubuntu) and Centos.

The other answer answers here give great detail on how to compile the driver module and insert it — if you look at the Linux source code, you can «grep» your device name in the /drivers/net directory eg.

It might yield something like:

I’ve trimmed some lines for brevity. But the module names are the same as the directory before Kconfig, so you can check if it is active with lsmod:

Sometimes my intel drivers for my onboard Wi-Fi dies, then I have to remove and re-add it:

Then magically it works again. I still need to contribute this fix to the NetworkManager project.

If this returns «alx», then the driver is already loaded:

If not, you’re out of luck. You can manage the interface with the «ifconfig» or «ip link» commands:

Newer Linuxes don’t use «eth» as interface names any more.

So I grepped my kernel tree for «killer» and «e2200» and couldn’t find anything. Then I did a web search, and found out that is is an Atheros device, and similar to the «alx» driver. Someone updated the driver to work with your card, lucky you. If there are enough cards like that out in the world, or he upstreamed it, all you have to do is to update Linux and it will just work.

Welcome to Linux! No go out and buy some older hardware that someone has already made free drivers for. 🙂

Источник

Linux* Base Driver for Intel® Gigabit Ethernet Network Connections

Content Type Install & Setup

Article ID 000005480

Last Reviewed 04/02/2021

There are three Linux* base drivers for Intel® Gigabit Network Connections:

• igb-x.x.x.tar.gzdriver: Supports all 82575/6, 82580, I350, I354, and I210/I211 based gigabit network connections.
• e1000e-x.x.x.x.tar.gzdriver: Supports the Intel® PRO/1000 PCI-E (82563/6/7, 82571/2/3/4/7/8/9, or 82583) I217/I218/I219 based gigabit network adapters.
• e1000-x.x.x.tar.gzdriver: Supports Intel® PRO/1000 PCI and PCI-X family of gigabit network connections.

Select the proper version below for download and installation instructions.

Click or the topic for details:

Linux* igb* base driver for Intel® Gigabit Ethernet Network Connection installation instructions

The Linux* igb driver supports all 82575, 82576, 82580, I350, I354, and I210/I211 based Intel® Gigabit Ethernet Network Connections.
For driver configuration details, see the Read Me file in Download Center.

The Linux base drivers support the 2.4.x, 2.6.x and 3.x kernels. These drivers include support for Intel® Itanium® 2 Processor-based systems.

These drivers are only supported as a loadable module. We don’t supply patches against the kernel source to allow for static linking of the drivers. For questions related to hardware requirements, see the documentation supplied with your Intel Gigabit adapter. All hardware requirements listed apply to use with Linux.

The following features are available in supported kernels:

• Native VLANs
• Channel Bonding (teaming)
• SNMP

Find channel bonding documentation in the Linux kernel source: /documentation/networking/bonding.txt.

The igb driver supports IEEE 1588 time stamping for kernels 2.6.30 and above. For a basic tutorial for the technology, see NIST.

The driver information previously displayed in the /proc file system isn’t supported in this release. You can use ethtool (version 1.6 or later), lspci, and ifconfig to obtain the same information.

Building and installation

The steps below require elevated privileges.

Red Hat based platforms: CentOS, RHEL, or Fedora

• yum install gcc make
• yum install kernel kernel-devel

Ubuntu and Debian based platforms

• apt-get install linux-headers-$(uname -r)
• apt-get install gcc make

You may need to perform a general update and restart before the next steps.

Prerequisites

Download current igb package from Download Center. Move the base driver tar file to the directory of your choice.
For example, use /home/username/igb or /usr/local/src/igb.

Untar/unzip the archive, where is the version number for the driver tar file:

tar zxf igb- .tar.gz

Change to the driver src directory, where is the version number for the driver tar:

Compile the driver module:

The binary will be installed as:

The install location listed above is the default location. This may differ for various Linux distributions.

Load the module using either the insmod or modprobe command:

modprobe igb insmod igb

Note that for 2.6 kernels the insmod command can be used if the full path to the driver module is specified. For example:

insmod /lib/modules/ /kernel/drivers/net/igb/igb.ko

With 2.6 based kernels also make sure that older igb drivers are removed from the kernel, before loading the new module:

rmmod igb; modprobe igb

Assign an IP address to the interface by entering the following, where is the interface number:

Verify that the interface works. Enter the following, where is the IP address for another machine on the same subnet as the interface that is being tested:

ping

Some systems have trouble supporting MSI and/or MSI-X interrupts. If your system needs to disable this style of interrupt, the driver can be built and installed with the command:

make CFLAGS_EXTRA=-DDISABLE_PCI_MSI install

Normally the driver will generate an interrupt every two seconds. If you’re no longer getting interrupts in cat /proc/interrupts for the ethX igb device, then this workaround may be necessary.

To build igb driver with DCA:

If your kernel supports DCA, the driver will build by default with DCA enabled.

Linux* e1000e base driver for Intel® Gigabit Ethernet Network Connection installation instructions

The Linux* e1000e driver supports the Intel® PRO/1000 PCI-E (82563/6/7, 82571/2/3/4/7/8/9, or 82583) I217/I218/I219 based gigabit network adapters.

For information concerning driver configuration details, refer to the Read Me file in the Download Center.

The Linux* base drivers support the 2.4.x and 2.6.x kernels. They include support for Intel® Itanium® 2 Processor-based systems.

The drivers are only supported as a loadable module. We don’t supply patches against the kernel source to allow for static linking of the drivers. For questions related to hardware requirements, see the documentation supplied with your Intel® Gigabit Network Adapter. All hardware requirements listed apply for use with Linux.

Features now available in supported kernels:

• Native VLANs
• Channel Bonding (teaming)
• SNMP

Find Channel Bonding documentation in the Linux kernel source: /documentation/networking/bonding.txt.

This release doesn’t support the driver information previously displayed in the /proc file system. You can also use ethtool (version 1.6 or later), lspci, and ifconfig to get the same information.

Note

Note	The Intel® 82562v 10/100 Network Connection only provides 10/100 support.

Building and installation

Steps below require elevated privileges.

Red Hat based platforms: CentOS, RHEL, or Fedora

• yum install gcc make
• yum install kernel kernel-devel

Ubuntu and Debian based platforms

• apt-get install linux-headers-$(uname -r)
• apt-get install gcc make

You may need to perform a general update and restart before the next steps.

Prerequisites

Download current e1000e package from Download Center. Move the base driver tar file to the directory of your choice.
For example, use /home/ /e1000e or /usr/local/src/e1000e.

Untar/unzip the archive, where is the version number for the driver tar file:

tar zxf e1000e- .tar.gz

Change to the driver src directory, where is the version number for the driver tar:

Compile the driver module:

The binary installs as:

The install location listed above is the default. Location may differ for various Linux distributions.

Load the module using either the insmod or modprobe command:

modprobe e1000e insmod e1000e

Note

You can use the insmod command for 2.6 kernels if you specify the full path to the driver module. For example: insmod /lib/modules/ /kernel/drivers/net/e1000e/e1000e.ko With 2.6 based kernels, make sure that older e1000e drivers are removed from the kernel before you load the new module: rmmod e1000e; modprobe e1000e

Assign an IP address to the interface by entering the following, where is the interface number:

Verify that the interface works. Enter the following, where is the IP address for another machine on the same subnet as the interface you’re testing:

ping

Some systems have trouble supporting MSI and/or MSI-X interrupts. If your system must disable this style of interrupt, build and install the driver with the command:

make CFLAGS_EXTRA=-DDISABLE_PCI_MSI install

Normally the driver generates an interrupt every two seconds. If you’re no longer seeing interrupts in cat /proc/interrupts for the ethX e1000e device, then this workaround may be necessary.

Note

Linux* e1000 base driver for Intel® PCI, PCI-X Gigabit Network Connection installation instructions

The Linux* e1000 driver supports Legacy (PCI, PCI-X*) Gigabit Network Connections.
For driver configuration details, see the ReadMe file in Download Center.

Note	The e1000 driver is no longer maintained as a standalone component. Request support from the maintainer of your Linux* distribution.

The Linux base drivers support the 2.4.x and 2.6.x kernels. These drivers include support for Intel® Itanium® 2 Processor-based systems.

These drivers are only supported as a loadable module. We don’t supply patches against the kernel source to allow for static linking of the drivers. For questions related to hardware requirements, refer to the documentation supplied with your Intel® Gigabit Adapter. All hardware requirements listed apply to use with Linux.

The following features are now available in supported kernels:

• Native VLANs
• Channel Bonding (teaming)
• SNMP

Channel Bonding documentation can be found in the Linux kernel source: /documentation/networking/bonding.txt.

The driver information previously displayed in the /proc file system isn’t supported in this release. Alternatively, you can use ethtool (version 1.6 or newer), lspci, and ifconfig to obtain the same information.

Note	The Intel® 82562V Fast Ethernet PHY 10/100 Network Connection only provides 10/100 support.

Building and installation

The steps below require elevated privileges.

Red Hat based platforms: CentOS, RHEL, or Fedora

• yum install gcc make
• yum install kernel kernel-devel

Ubuntu and Debian based platforms

• apt-get install linux-headers-$(uname -r)
• apt-get install gcc make

You may need to perform a general update and restart before the next steps.

Prerequisites

Download current e1000 package from Download Center. Move the base driver tar file to the directory of your choice.
For example, use /home/username/e1000 or /usr/local/src/e1000.

Untar/unzip the archive, where is the version number for the driver tar file:

tar zxf e1000- .tar.gz

Change to the driver src directory, where is the version number for the driver tar:

Compile the driver module:

The binary is installed as:

The install location listed above is the default location. This may differ for various Linux distributions.

Load the module using either the insmod or modprobe command:

modprobe e1000 insmod e1000

Note

For 2.6 kernels the insmod command can be used if the full path to the driver module is specified. For example: insmod /lib/modules/ /kernel/drivers/net/e1000/e1000.ko With 2.6 based, kernels also make sure that older e1000 drivers are removed from the kernel, before loading the new module: rmmod e1000; modprobe e1000

Assign an IP address to the interface by entering the following, where is the interface number:

Verify that the interface works. Enter the following, where is the IP address for another machine on the same subnet as the interface that’s being tested:

Источник

Читайте также:  Что такое windows dla