Intel Ethernet stopped working

Support Network
22

Hey, thanks for replying!

I had to find sometime to work on the steps you suggested.

  1. Unfortunately, it does not make a difference. I have tried all shutdown+reboot combinations and they do not fix the problem.

  2. They are both off, results are the same.

  3. sudo modprobe -r e1000e ; sudo modprobe e1000e did not solve the problem.

  4. sudo dmesg | grep e1000e

[ 3.955764] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[ 3.955766] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 3.955960] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 4.031482] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock
[ 4.110526] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 74:d0:2b:2c:04:1b
[ 4.110532] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 4.110557] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF
[ 4.182027] e1000e 0000:00:19.0 eno1: renamed from eth0
[ 9.631077] e1000e 0000:00:19.0 eno1: NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
[ 9.631082] e1000e 0000:00:19.0 eno1: 10/100 speed: disabling TSO

  1. /sys/kernel/debug/dynamic_debug does not exist on my system (I did not take the extra step to create it).

echo '0000:00:10.0' | sudo tee /sys/bus/pci/drivers/e1000e/unbind

0000:00:10.0
tee: /sys/bus/pci/drivers/e1000e/unbind: No such device

echo '0000:00:10.0' | sudo tee /sys/bus/pci/drivers/e1000e/bind

0000:00:10.0
tee: /sys/bus/pci/drivers/e1000e/bind: No such device

  1. The workarounds suggested have been tried in previous steps. In addition, my problem is not WiFi related so I could not try the WiFi specific remedies.

  2. THIS WORKED!!!. Ethernet started working after the suggestion in step 7!!!

Wow, thanks a lot!
By means of the working solution, what seems to be the problem?
I am genuinely curious.

Ninja edit:
I just realised I did not provide a complete answer for your 4th suggestion (since I’d have to also provide the dmesg output when the Ethernet works). Apologies. However, I don’t think it matters since I guess we were able to kinda track the problem down.

2 Likes