🔍 See Original Answer on Ask Ubuntu 🔗
Replugging network cable doesn't reconnect
October 27, 2018
Edited: October 27, 2018
November 24, 2022
Copy to clipboard: false
From this Dell LAN problem with TLP: Wired network not working after resuming from suspend (Ubuntu 16.04) #222
Edit TLP configuration using:
sudo -H gedit /etc/default/tlp
Locate these lines:
# Disable wake on LAN: Y/N WOL_DISABLE=Y
- Change “
Y” to “
Locate your USB_BLACKLIST lines (if any) and un-blacklist them by placing
# at beginning:
- Save file and exit
- Restart TLP with command:
sudo tlp start
Second option: Disable PCIe power management
From: TLP Troubleshooting:
Disable Runtime Power Management completely
Comment both related config lines with a leading ‘
When the problem disappears, uncomment above lines and continue with the next section.
Otherwise the cause is not a PCIe device – proceed to USB.
Here are some related bugs that will interest R8169 users:
Mar 21, 2018 - Fix Runtime PM for r8169:
r8169 stays in D0 even when no ethernet cable is plugged in. This drains lots of power (~3W). The
tested laptop uses 5.5W when r8169 is in D0,
1.8W when r8169 is in D3. The power saved is substantial.
Improved rumtime PM logic to let the device gets suspended (D3)
when the port is not in used and the link is down.
July 3, 2018 - r8169 no internet after suspending:
r8169 failed to establish connection after the fix for LP: #1752772 landed.
Accepts BIOS WoL settings again, and disables MSI-X for certain
March 2, 2018 - r8169 ethernet card don’t work after returning from suspension
This bug affects 127 people:
Ethernet r8169 stops working after system resumed from suspend.
User confirmed these patches fix the issue. r8169 continues to
work after resume from suspend.
Medium. The fix is limited to one device, all
patches are in mainline. The WOL default change might cause regression
for users that depend on BIOS settings. We can advice them to use
userspace tool (systemd, ethtool, etc.) instead.
There have been quite a few bugs with r8169 in 2018. I’m using a kernel from 2017 (
4.13.0-36) so I haven’t experienced the same problems with TLP. It is more difficult to fix bugs I’m not experiencing. The kernel developers do have time to install new kernels, test for bugs and come up with solutions. I can do a little but, time constraints prevent installation of newer kernels.