Solve the problem that the NIC cannot be found after Dell T3620 installs CentOS7.1.1503

Source: Internet
Author: User

Solve the problem that the NIC cannot be found after Dell T3620 installs CentOS7.1.1503

Dell T3620InstallCentOS7.1.1503The NIC cannot be found.

Problem:

On this day, the company purchased a Dell graphics workstation (T3620) for the design department because of the use

The design software was developed on the CentOS platform, so I installed Centos 7.1.1503 on a new machine.

However, after the system is installed, the network cannot be connected normally.

Processing Process:

First, I thought that the NIC driver may not be properly installed. Previously purchased by the company

I bought a T1700 Dell graphics workstation. After CentOS7.1.1503 is installed, the network connection is normal. Inspected

It was found that the network control chip used by T1700 was an Intel I217-LM, while the network control chip of T3620 was an Intel I217-LM.

T1700

[Root @ Design3 ~] # Lspci-vvv | grep Ethernet

. 0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 04)

T3620

[Root @ design5 ~] # Lspci-vvv | grep Ethernet

00: 1f. 6 Ethernet controller: Intel configurationethernet Connection (2) I219-LM (rev 31)

--

So it seems that the CentOS 7.1.1503 version only integrates the I217-LM driver, and does not integrate the I219-LM driver.

I called Dell and told the other party that Nic drivers under CentOS were not officially provided (the eyes were full of stars *** and Khan ~).

Fortunately, I found a PCI slot on the T3620 motherboard, and I felt a lot more steadfast.

Plug in a universal built-in NIC (Realtek 8139) for T3620 and connect to the network after it is started.

Is it always using the installed Nic ~? There is always a piece of reluctance in my heart, and I will not try again, I said to myself.

So I tried to execute (command: yum update) on T3620, And the yum update is

There is a lot of risk, but this is just a Failover machine, and the machine only runs a design software, so there is no concern.

After the upgrade, I was very happy to find that the system recognized the integrated Nic.

[Root @ design5 ~] # Cat/etc/redhat-release

CentOS Linux release 7.2.1511 (Core)

I'm glad to know that I'm a little curious about the driver used by the Integrated Nic. (Let's take a look at the driver information ~) :

[Root @ design5 ~] # Lspci-vvv

00: 1f. 6 Ethernet controller: Intel Corporation EthernetConnection (2) I219-LM (rev 31)

Subsystem: Dell Device 06b7

Control: I/O-Mem + BusMaster + SpecCycle-MemWINV-VGASnoop-ParErr-Stepping-SERR + FastB2B-DisINTx +

Status: Cap + 66 MHz-UDF-FastB2B-ParErr-DEVSEL = fast> TAbort-<MAbort-> SERR-<PERR-INTx-

Latency: 0

Interrupt: pin A routed to IRQ 125

Region0: Memory at f7100000 (32-bit, non-prefetchable) [size = 128 K]

Capabilities: [c8] Power Management version 3

Flags: PMEClk-DSI + D1-D2-AuxCurrent = 0mA PME (D0 +, D1-, D2-, D3hot +, D3cold +)

Status: D0 NoSoftRst + PME-Enable-DSel = 0 DScale = 1 PME-

Capabilities: [d0] MSI: Enable + Count = 1/1 Maskable-64bit +

Address: 00000000fee00398 Data: 0000

Capabilities: [e0] PCI Advanced Features

AFCap: TP + FLR +

AFCtrl: FLR-

AFStatus: TP-

Kerneldriver in use: e1000e

From the above information, the driver belongs to the e1000e module (we can execute the lsmod command to view the module currently loaded by the System)

For more information about the e1000e module, run the modinfoe1000e command.

[Root @ design5 ~] # Modinfo e1000e

Filename:/lib/modules/3.10.0-327.36.1.el7.x86 _ 64/kernel/drivers/net/ethernet/intel/e1000e/e1000e. ko

Version: 3.2.5-k

License: GPL

Description: Intel (R) PRO/1000 Network Driver

Author: Intel Corporation <linux.nics@intel.com>

Rhelversion: 7.2.

Srcversion: 7097C005F85B5C9D374D3FB

.

.

.

Alias: pci: vda-8086dda-105fsv * sd * bc * SC * I *

Alias: pci: vda-8086dda-105esv * sd * bc * SC * I *

Depends: ptp

Intree: Y

Vermagic: 3.10.0-327.36.1.el7.x86 _ 64SMP mod_unload modversions

Signer: CentOS Linux kernel signing key

Sig_key: 7F: 74: 0F: 3F: 87: 67: 80: 2E: E9: 3B: A2: 3F: 10: EA: 75: 8D: 2F: 6C: AB: e3

Sig_hashalgo: sha256

Parm: debug: Debug level (0 = none,..., 16 = all) (int)

Parm: copybreak: Maximum size of packetthat is copied to a new buffer on receive (uint)

Parm: TxIntDelay: Transmit Interrupt Delay (array of int)

Parm: TxAbsIntDelay: Transmit AbsoluteInterrupt Delay (array of int)

Parm: RxIntDelay: Receive Interrupt Delay (array of int)

Parm: RxAbsIntDelay: Receive AbsoluteInterrupt Delay (array of int)

Parm: InterruptThrottleRate: InterruptThrottling Rate (array of int)

Parm: IntMode: Interrupt Mode (array ofint)

Parm: SmartPowerDownEnable: Enable PHYsmart power down (array of int)

Parm: KumeranLockLoss: Enable Kumeran lockloss workaround (array of int)

Parm: WriteProtectNVM: Write-protect NVM [WARNING: disabling this can lead to initialize upted NVM] (array of int)

Parm: CrcStripping: Enable CRC Stripping, disable if your BMC needs the CRC (array of int)

[Root @ design5 ~] #

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.