Ubuntu
network-manager package

Network shows Cable Unplugged

Bug #1725865 reported by Luis Alvarado on 2017-10-22

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	NetworkManager	Unknown	Medium	gnome-bugs #792506
	network-manager (Ubuntu)	Invalid	Low	Unassigned

Bug Description

This was working perfectly on 17.04, but after installing 17.10 from scratch, the wired network is not detected. It simply shows as Cable Unplugged when in fact there is the same cable still connected directly to the router. This same computer has Windows 10 and it detects the network correctly. I also tested Fedora and it detected the network correctly (The wired one). I am currently using only the Wireless connection because of this.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Sat Oct 21 17:59:31 2017
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2017-10-19 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
IpRoute:
default via 192.168.1.1 dev wlp9s0 proto static metric 600
169.254.0.0/16 dev wlp9s0 scope link metric 1000
192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.2 metric 600
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
wlp9s0 wifi connected /org/freedesktop/NetworkManager/Devices/3 Linux ecb8e125-48ff-4994-94c8-bdf3731334ce /org/freedesktop/NetworkManager/ActiveConnection/13
enp0s31f6 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- -- --
lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- --
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
running 1.8.4 connected started full enabled enabled enabled enabled enabled

Tags:

Revision history for this message

Luis Alvarado (luisalvarado) wrote on 2017-10-22:

CRDA.txt Edit (289 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (4.7 KiB, text/plain; charset="utf-8")
IpAddr.txt Edit (842 bytes, text/plain; charset="utf-8")
IwConfig.txt Edit (539 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (123.2 KiB, text/plain; charset="utf-8")
NetDevice.enp0s31f6.txt Edit (831 bytes, text/plain; charset="utf-8")
NetDevice.lo.txt Edit (247 bytes, text/plain; charset="utf-8")
NetDevice.wlp9s0.txt Edit (935 bytes, text/plain; charset="utf-8")
NetworkManager.conf.txt Edit (97 bytes, text/plain; charset="utf-8")
PciNetwork.txt Edit (4.4 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (288 bytes, text/plain; charset="utf-8")
RfKill.txt Edit (113 bytes, text/plain; charset="utf-8")
WifiSyslog.txt Edit (251.3 KiB, text/plain; charset="utf-8")
nmcli-con.txt Edit (1.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Sebastien Bacher (seb128) wrote on 2017-10-23:

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Changed in network-manager (Ubuntu):
importance:	Undecided → Low

Revision history for this message

Luis Alvarado (luisalvarado) wrote on 2018-01-14:

Hi Sebastien, I have added the corresponding bug here https://bugzilla.gnome.org/show_bug.cgi?id=792506

Is this what it was needed buddy?

Bug Watch Updater (bug-watch-updater) on 2018-01-15

Changed in network-manager:
importance:	Unknown → Medium

Luis Alvarado (luisalvarado) on 2018-01-16

Changed in network-manager (Ubuntu):
status:	New → Invalid

Revision history for this message

Vonschutter (stephan-schutter) wrote on 2018-10-09:

To re enable the network after suspended mode I found that this works:

22:07:23-root@Seth:~$ rmmod r8169
22:11:22-root@Seth:~$ modprobe r8169

Unloading the driver and then reloading it brings the interface back up. unplugging the cable did not, nor did any network manager commands that I tried.

My take on this is that the driver is not properly loaded back up after the PC has suspended. This problem must be in the kernel somehow since pulling the driver and re-inserting it worked.