How to "reactivate" the e1000e driver that is no longer working on a network device?

Issues related to configuring your network
Post Reply
darcyr
Posts: 2
Joined: 2020/01/24 15:16:58

How to "reactivate" the e1000e driver that is no longer working on a network device?

Post by darcyr » 2020/01/24 15:30:32

I'm very confused! I have two open ports enp4s0 and eno1. One is DHCP and one is a static IP and both have been working smoothly up until a few days ago.

Suddenly, the eno1 NIC seems to have disappeared. It's still being identified but it's missing the e1000e driver somehow, or perhaps it's not using the driver properly.

Here are some of the commands I've run to attempt to troubleshoot:

Code: Select all

[root@home network-scripts]# nmcli d
DEVICE  TYPE      STATE      CONNECTION
enp4s0  ethernet  connected  enp4s0
lo      loopback  unmanaged  --

Code: Select all

[root@home ~]# ls /etc/sysconfig/network-scripts/ifcfg*
/etc/sysconfig/network-scripts/ifcfg-eno1  /etc/sysconfig/network-scripts/ifcfg-enp4s0  /etc/sysconfig/network-scripts/ifcfg-lo
Running the `ifup eno1` command or `ifconfig eno1 up` don't appear to work:

Code: Select all

[root@home ~]# ifup eno1
Error: Connection activation failed: No suitable device found for this connection (device enp4s0 not available because profile is not compatible with device (mismatching interface name)).
[root@home ~]# ifconfig eno1 up
eno1: ERROR while getting interface flags: No such device
Clearly the network manager does not see this device.

I see an unclaimed Ethernet controller when I run `lshw -class network`:

Code: Select all

*-network UNCLAIMED
       description: Ethernet controller
       product: Ethernet Connection (7) I219-LM
       vendor: Intel Corporation
       physical id: 1f.6
       bus info: pci@0000:00:1f.6
       version: 10
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi cap_list
       configuration: latency=0
       resources: memory:a1300000-a131ffff
Here is the output from `lspci -k`:

Code: Select all

00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-LM (rev 10)
	Subsystem: ASRock Incorporation Device 15bb
	Kernel modules: e1000e
04:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
	Subsystem: ASRock Incorporation Device 1533
	Kernel driver in use: igb
	Kernel modules: igb
Note - on FUNCTIONING devices, the Device 15bb contains the line `Kernel driver in use: e1000e`.

Which indicates to me that the driver is not being loaded or used for this connection.

There is also a clear error message from `dmesg`:

Code: Select all

[ 7321.758557] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[ 7321.758560] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 7321.758762] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 7321.758785] e1000e 0000:00:1f.6: irq 500 for MSI/MSI-X
[ 7322.764417] e1000e: probe of 0000:00:1f.6 failed with error -2
I've also tried listing modules `lsmod | grep e1000e` looking for that driver:

Code: Select all

[root@home ~]# lsmod | grep e1000e
e1000e                248519  0
ptp                    19231  2 igb,e1000e
Which is the same output that I receive on functioning devices...

Is there something in the BIOS settings? (I hope not as I am managing this device remotely)...

Or any other troubleshooting steps? I've downloading `elrepo1` and attempted to attach `kmod-e1000e` to no avail - or possibly, I'm not doing it properly... Any help would be greatly appreciated as I've gotten to my wits' end with this one.

User avatar
TrevorH
Forum Moderator
Posts: 27727
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: How to "reactivate" the e1000e driver that is no longer working on a network device?

Post by TrevorH » 2020/01/24 17:23:06

Have you tried powering the machine down completely and removing the power lead from it for 30s or so? Hardware does sometimes go off into limbo and needs that sort of thing done to it to resuscitate it!
CentOS 6 will die in November 2020 - migrate sooner rather than later!
CentOS 5 has been EOL for nearly 3 years and should no longer be used for anything!
Full time Geek, part time moderator. Use the FAQ Luke

darcyr
Posts: 2
Joined: 2020/01/24 15:16:58

Re: How to "reactivate" the e1000e driver that is no longer working on a network device?

Post by darcyr » 2020/01/24 20:22:51

TrevorH wrote:
2020/01/24 17:23:06
Have you tried powering the machine down completely and removing the power lead from it for 30s or so? Hardware does sometimes go off into limbo and needs that sort of thing done to it to resuscitate it!
Yes, we've tried this, to no avail. :cry:

User avatar
TrevorH
Forum Moderator
Posts: 27727
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: How to "reactivate" the e1000e driver that is no longer working on a network device?

Post by TrevorH » 2020/01/25 11:32:28

A lot of the hits I found on google for that error message were blaming hardware failure. I would suggest booting the original DVD that you used to install the system in rescue mode (an option off the initial Troubleshooting menu) and see if the device is working then. You will need to bring up the interface manually since it won't do so on its own. That will boot a kernel that you know used to work with this device and if it's still broken then it points to either some change in settings on the hardware itself (BIOS option?) or to broken hardware. You could also try a different o/s and see if that is also unable to use the device.
CentOS 6 will die in November 2020 - migrate sooner rather than later!
CentOS 5 has been EOL for nearly 3 years and should no longer be used for anything!
Full time Geek, part time moderator. Use the FAQ Luke

Post Reply

Return to “CentOS 7 - Networking Support”