You are not logged in.

#1 2019-11-15 11:16:56

marcelsmudda
Member
Registered: 2015-09-14
Posts: 14

[Solved] Cannot find interface and Wired connection failing

Hi, I have two problems with my computer.
The first issue is that I cannot see one interface. My main board has three ethernet ports and I can only see two in ip link.

The other issue is that my computer started to not be able to connect via wired connections. It doesn't matter which port I use, all of them don't work. The only information I got is that the DHCP request times out and when I assign an IP address locally, my router is unable to see the PC and I cannot ping anything. This is the log that is repeated every time the connection fails...

Nov 15 20:09:08 BEAST NetworkManager[2899]: <warn>  [1573816148.8540] dhcp4 (eno1): request timed out
Nov 15 20:09:08 BEAST NetworkManager[2899]: <info>  [1573816148.8540] dhcp4 (eno1): state changed unknown -> timeout
Nov 15 20:09:08 BEAST NetworkManager[2899]: <info>  [1573816148.8907] dhcp4 (eno1): canceled DHCP transaction
Nov 15 20:09:08 BEAST NetworkManager[2899]: <info>  [1573816148.8907] dhcp4 (eno1): state changed timeout -> done
Nov 15 20:09:08 BEAST NetworkManager[2899]: <info>  [1573816148.8911] device (eno1): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Nov 15 20:09:08 BEAST NetworkManager[2899]: <warn>  [1573816148.8929] device (eno1): Activation: failed for connection 'Wired connection 1'
Nov 15 20:09:08 BEAST NetworkManager[2899]: <info>  [1573816148.8933] device (eno1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Nov 15 20:09:08 BEAST NetworkManager[2899]: <info>  [1573816148.8964] policy: auto-activating connection 'Wired connection 1' (3a26fe49-721d-3011-92fa-8641b1f7fe90)
Nov 15 20:09:08 BEAST NetworkManager[2899]: <info>  [1573816148.8969] device (eno1): Activation: starting connection 'Wired connection 1' (3a26fe49-721d-3011-92fa-8641b1f7fe90)
Nov 15 20:09:08 BEAST NetworkManager[2899]: <info>  [1573816148.8969] device (eno1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Nov 15 20:09:08 BEAST NetworkManager[2899]: <info>  [1573816148.8971] device (eno1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Nov 15 20:09:08 BEAST NetworkManager[2899]: <info>  [1573816148.8974] device (eno1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Nov 15 20:09:08 BEAST NetworkManager[2899]: <info>  [1573816148.8975] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)

Connecting via WiFi is no problem.

Last edited by marcelsmudda (2019-11-16 07:58:49)

Offline

#2 2019-11-15 14:36:28

seth
Member
Registered: 2012-09-03
Posts: 13,080

Re: [Solved] Cannot find interface and Wired connection failing

Please post the outputs of  "systemctl list-unit-files --state=enabled", "lspci", "lsusb" and "ip l" and a complete system journal (sudo journalctl -b, you can use https://wiki.archlinux.org/index.php/Pastebin to feed the output into as pastebin service)

Offline

#3 2019-11-15 16:55:10

marcelsmudda
Member
Registered: 2015-09-14
Posts: 14

Re: [Solved] Cannot find interface and Wired connection failing

~ [ systemctl list-unit-files --state=enabled 
UNIT FILE                                  STATE  
autovt@.service                            enabled
dbus-org.freedesktop.nm-dispatcher.service enabled
dbus-org.freedesktop.timesync1.service     enabled
dhcpcd.service                             enabled
display-manager.service                    enabled
gdm.service                                enabled
getty@.service                             enabled
NetworkManager-dispatcher.service          enabled
NetworkManager-wait-online.service         enabled
NetworkManager.service                     enabled
sshd.service                               enabled
systemd-timesyncd.service                  enabled
remote-fs.target                           enabled

13 unit files listed.
~ [ lspci
00:00.0 Host bridge: Intel Corporation 8th Gen Core 8-core Desktop Processor Host Bridge/DRAM Registers [Coffee Lake S] (rev 0a)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 0a)
00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10)
00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10)
00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10)
00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10)
00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #5 (rev f0)
00:1c.6 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #7 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Z390 Chipset LPC/eSPI Controller (rev 10)
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-V (rev 10)
01:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1470 (rev c1)
02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1471
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] (rev c1)
03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 HDMI Audio [Radeon Vega 56/64]
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Device 8125 (rev 01)
05:00.0 PCI bridge: ASMedia Technology Inc. ASM1184e PCIe Switch Port
06:01.0 PCI bridge: ASMedia Technology Inc. ASM1184e PCIe Switch Port
06:03.0 PCI bridge: ASMedia Technology Inc. ASM1184e PCIe Switch Port
06:05.0 PCI bridge: ASMedia Technology Inc. ASM1184e PCIe Switch Port
06:07.0 PCI bridge: ASMedia Technology Inc. ASM1184e PCIe Switch Port
07:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29)
08:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
0a:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
~ [ lsusb
Bus 002 Device 006: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 002 Device 004: ID 0781:5590 SanDisk Corp. Ultra Dual
Bus 002 Device 005: ID 045b:0210 Hitachi, Ltd 
Bus 002 Device 003: ID 045b:0210 Hitachi, Ltd 
Bus 002 Device 002: ID 278a:0004 MARSHAL SHELTER EXTERNAL HDD MARSHAL SHELTER EXTERNAL HDD
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 004: ID 1532:011a Razer USA, Ltd BlackWidow Ultimate 2013
Bus 001 Device 009: ID 041e:30ca Creative Technology, Ltd 
Bus 001 Device 005: ID 045b:0209 Hitachi, Ltd 
Bus 001 Device 003: ID 045b:0209 Hitachi, Ltd 
Bus 001 Device 002: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 001 Device 008: ID 8087:0025 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
~ [ ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp8s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 70:85:c2:b5:4b:a9 brd ff:ff:ff:ff:ff:ff
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 70:85:c2:b5:4b:ad brd ff:ff:ff:ff:ff:ff
4: wlp7s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
    link/ether 5a:af:97:e9:1b:c7 brd ff:ff:ff:ff:ff:ff

I'm sorry regarding the journalctl output but it was too long. I've cut a lot of lines (which were mainly repetitions of network manager trying to connect). When you see empty lines, that's where I cut something, sorry.
http://ix.io/21Qq

Offline

#4 2019-11-15 16:59:21

seth
Member
Registered: 2012-09-03
Posts: 13,080

Re: [Solved] Cannot find interface and Wired connection failing

You've two concurrent services activated.

dhcpcd.service                             enabled
…
NetworkManager-dispatcher.service          enabled
NetworkManager-wait-online.service         enabled
NetworkManager.service                     enabled

They'll get into a race over the interfaces and knock each other out. Stop and disable dhcpcd and report back.

Offline

#5 2019-11-15 17:49:17

marcelsmudda
Member
Registered: 2015-09-14
Posts: 14

Re: [Solved] Cannot find interface and Wired connection failing

It's still not working

Nov 16 02:46:29 BEAST sudo[82980]:    $user : TTY=pts/0 ; PWD=/home/$user ; USER=root ; COMMAND=/usr/bin/systemctl disable dhcpcd
Nov 16 02:46:29 BEAST sudo[82980]: pam_unix(sudo:session): session opened for user root by (uid=0)
Nov 16 02:46:29 BEAST systemd[1]: Reloading.
Nov 16 02:46:29 BEAST sudo[82980]: pam_unix(sudo:session): session closed for user root
Nov 16 02:46:38 BEAST sudo[83004]:    $user : TTY=pts/0 ; PWD=/home/$user ; USER=root ; COMMAND=/usr/bin/systemctl stop dhcpcd
Nov 16 02:46:38 BEAST sudo[83004]: pam_unix(sudo:session): session opened for user root by (uid=0)
Nov 16 02:46:38 BEAST systemd[1]: Stopping dhcpcd on all interfaces...
-- Subject: A stop job for unit dhcpcd.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit dhcpcd.service has begun execution.
-- 
-- The job identifier is 8225.
Nov 16 02:46:38 BEAST dhcpcd[83007]: sending signal TERM to pid 1008
Nov 16 02:46:38 BEAST dhcpcd[83007]: waiting for pid 1008 to exit
Nov 16 02:46:38 BEAST dhcpcd[83007]: sending signal TERM to pid 1008
Nov 16 02:46:38 BEAST dhcpcd[83007]: waiting for pid 1008 to exit
Nov 16 02:46:38 BEAST dhcpcd[1008]: received SIGTERM, stopping
Nov 16 02:46:38 BEAST dhcpcd[1008]: wlp7s0: removing interface
Nov 16 02:46:38 BEAST dhcpcd[1008]: eno1: removing interface
Nov 16 02:46:38 BEAST dhcpcd[1008]: enp8s0: removing interface
Nov 16 02:46:38 BEAST systemd[1]: dhcpcd.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit dhcpcd.service has successfully entered the 'dead' state.
Nov 16 02:46:38 BEAST systemd[1]: Stopped dhcpcd on all interfaces.
-- Subject: A stop job for unit dhcpcd.service has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit dhcpcd.service has finished.
-- 
-- The job identifier is 8225 and the job result is done.
Nov 16 02:46:38 BEAST audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dhcpcd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 16 02:46:38 BEAST kernel: audit: type=1131 audit(1573839998.258:232): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dhcpcd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 16 02:46:38 BEAST sudo[83004]: pam_unix(sudo:session): session closed for user root
Nov 16 02:46:45 BEAST NetworkManager[52738]: <info>  [1573840005.5427] device (eno1): Activation: starting connection 'Wired connection 1' (3a26fe49-721d-3011-92fa-8641b1f7fe90)
Nov 16 02:46:45 BEAST kernel: audit: type=1111 audit(1573840005.542:233): pid=52738 uid=0 auid=4294967295 ses=4294967295 msg='op=connection-activate uuid=3a26fe49-721d-3011-92fa-8641b1f7fe90 name=576972656420636F6E6E656374696F6E2031 pid=1471 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
Nov 16 02:46:45 BEAST audit[52738]: USYS_CONFIG pid=52738 uid=0 auid=4294967295 ses=4294967295 msg='op=connection-activate uuid=3a26fe49-721d-3011-92fa-8641b1f7fe90 name=576972656420636F6E6E656374696F6E2031 pid=1471 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
Nov 16 02:46:45 BEAST NetworkManager[52738]: <info>  [1573840005.5446] audit: op="connection-activate" uuid="3a26fe49-721d-3011-92fa-8641b1f7fe90" name="Wired connection 1" pid=1471 uid=1000 result="success"
Nov 16 02:46:45 BEAST NetworkManager[52738]: <info>  [1573840005.5456] device (eno1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Nov 16 02:46:45 BEAST gnome-shell[1471]: == Stack trace for context 0x563f44433390 ==
Nov 16 02:46:45 BEAST gnome-shell[1471]: #0   563f4d1cf780 i   resource:///org/gnome/shell/ui/status/network.js:1329 (7fc36eec89d0 @ 56)
Nov 16 02:46:45 BEAST gnome-shell[1471]: #1   563f4d1cf6e8 i   resource:///org/gnome/shell/ui/status/network.js:1346 (7fc36eec8a60 @ 113)
Nov 16 02:46:45 BEAST gnome-shell[1471]: #2   563f4d1cf648 i   resource:///org/gnome/shell/ui/status/network.js:2049 (7fc36eecadc0 @ 216)
Nov 16 02:46:45 BEAST gnome-shell[1471]: #3   7fff8f27e4a0 b   self-hosted:977 (7fc36ee380d0 @ 413)
Nov 16 02:46:45 BEAST gnome-shell[1471]: #4   7fff8f27e550 I   resource:///org/gnome/gjs/modules/signals.js:135 (7fc3bc0c6040 @ 376)
Nov 16 02:46:45 BEAST gnome-shell[1471]: #5   563f4d1cf5c0 i   resource:///org/gnome/shell/ui/status/network.js:204 (7fc36eec43a0 @ 37)
Nov 16 02:46:45 BEAST gnome-shell[1471]: #6   563f4d1cf548 i   resource:///org/gnome/shell/ui/status/network.js:273 (7fc36eec4940 @ 12)
Nov 16 02:46:45 BEAST gnome-shell[1471]: #7   7fff8f27fac0 I   resource:///org/gnome/gjs/modules/signals.js:135 (7fc3bc0c6040 @ 376)
Nov 16 02:46:45 BEAST gnome-shell[1471]: #8   563f4d1cf4b0 i   resource:///org/gnome/shell/ui/status/network.js:1389 (7fc36eec8c10 @ 179)
Nov 16 02:46:45 BEAST gnome-shell[1471]: #9   563f4d1cf408 i   resource:///org/gnome/shell/ui/status/network.js:1439 (7fc36eec8dc0 @ 161)
Nov 16 02:46:45 BEAST gnome-shell[1471]: #10   563f4d1cf348 i   resource:///org/gnome/shell/ui/status/network.js:1503 (7fc36eec93a0 @ 129)
Nov 16 02:46:45 BEAST gnome-shell[1471]: #11   563f4d1cf2b0 i   resource:///org/gnome/shell/ui/status/network.js:1851 (7fc36eeca3a0 @ 119)
Nov 16 02:46:45 BEAST gnome-shell[1471]: #12   7fff8f281d10 b   self-hosted:979 (7fc36ee380d0 @ 440)
Nov 16 02:46:45 BEAST NetworkManager[52738]: <info>  [1573840005.5469] device (eno1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Nov 16 02:46:45 BEAST gnome-shell[1471]: == Stack trace for context 0x563f44433390 ==
Nov 16 02:46:45 BEAST gnome-shell[1471]: #0   563f4d1cf480 i   resource:///org/gnome/shell/ui/status/network.js:1329 (7fc36eec89d0 @ 56)
Nov 16 02:46:45 BEAST gnome-shell[1471]: #1   563f4d1cf3e8 i   resource:///org/gnome/shell/ui/status/network.js:1346 (7fc36eec8a60 @ 113)
Nov 16 02:46:45 BEAST gnome-shell[1471]: #2   563f4d1cf348 i   resource:///org/gnome/shell/ui/status/network.js:2049 (7fc36eecadc0 @ 216)
Nov 16 02:46:45 BEAST gnome-shell[1471]: #3   563f4d1cf2b0 i   resource:///org/gnome/shell/ui/status/network.js:1853 (7fc36eeca3a0 @ 134)
Nov 16 02:46:45 BEAST gnome-shell[1471]: #4   7fff8f281d10 b   self-hosted:979 (7fc36ee380d0 @ 440)
Nov 16 02:46:45 BEAST gnome-shell[1471]: == Stack trace for context 0x563f44433390 ==
Nov 16 02:46:45 BEAST gnome-shell[1471]: #0   563f4d1cf358 i   resource:///org/gnome/gjs/modules/overrides/GObject.js:508 (7fc3bc0ad8b0 @ 25)
Nov 16 02:46:45 BEAST gnome-shell[1471]: #1   563f4d1cf2b0 i   resource:///org/gnome/shell/ui/status/network.js:1826 (7fc36eeca310 @ 111)
Nov 16 02:46:45 BEAST gnome-shell[1471]: #2   7fff8f281d10 b   self-hosted:979 (7fc36ee380d0 @ 440)
Nov 16 02:46:45 BEAST NetworkManager[52738]: <info>  [1573840005.5515] device (eno1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Nov 16 02:46:45 BEAST NetworkManager[52738]: <info>  [1573840005.5519] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
Nov 16 02:46:45 BEAST gnome-shell[1471]: Object NM.ActiveConnection (0x563f47d6f6a0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Nov 16 02:46:45 BEAST gnome-shell[1471]: JS ERROR: Exception in callback for signal: icon-changed: TypeError: connection.get_setting_ip4_config is not a function
                                         _isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25
                                         getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13
                                         _updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52
                                         _emit@resource:///org/gnome/gjs/modules/signals.js:135:27
                                         _iconChanged@resource:///org/gnome/shell/ui/status/network.js:204:9
                                         _addConnection/<@resource:///org/gnome/shell/ui/status/network.js:273:44
                                         _emit@resource:///org/gnome/gjs/modules/signals.js:135:27
                                         _sync@resource:///org/gnome/shell/ui/status/network.js:1389:9
                                         setActiveConnection@resource:///org/gnome/shell/ui/status/network.js:1439:9
                                         setActiveConnections@resource:///org/gnome/shell/ui/status/network.js:1503:13
                                         _syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1851:9
Nov 16 02:46:45 BEAST gnome-shell[1471]: Object NM.ActiveConnection (0x563f47d6f6a0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Nov 16 02:46:45 BEAST gnome-shell[1471]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function
                                         _isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25
                                         getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13
                                         _updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52
                                         _syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9
Nov 16 02:46:45 BEAST gnome-shell[1471]: Object NM.ActiveConnection (0x563f47d6f6a0), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Nov 16 02:46:45 BEAST gnome-shell[1471]: JS ERROR: Error: Argument 'instance' (type interface) may not be null
                                         _init/GObject.Object.prototype.disconnect@resource:///org/gnome/gjs/modules/overrides/GObject.js:508:16
                                         _syncMainConnection@resource:///org/gnome/shell/ui/status/network.js:1826:13
Nov 16 02:47:04 BEAST sudo[83052]:    $user : TTY=pts/0 ; PWD=/home/$user ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Nov 16 02:47:04 BEAST sudo[83052]: pam_unix(sudo:session): session opened for user root by (uid=0)
Nov 16 02:47:07 BEAST sudo[83052]: pam_unix(sudo:session): session closed for user root
Nov 16 02:47:09 BEAST sudo[83059]:    $user : TTY=pts/0 ; PWD=/home/$user ; USER=root ; COMMAND=/usr/bin/journalctl -xef
Nov 16 02:47:09 BEAST sudo[83059]: pam_unix(sudo:session): session opened for user root by (uid=0)
Nov 16 02:47:30 BEAST NetworkManager[52738]: <warn>  [1573840050.5251] dhcp4 (eno1): request timed out
Nov 16 02:47:30 BEAST NetworkManager[52738]: <info>  [1573840050.5252] dhcp4 (eno1): state changed unknown -> timeout
Nov 16 02:47:30 BEAST NetworkManager[52738]: <info>  [1573840050.5729] dhcp4 (eno1): canceled DHCP transaction
Nov 16 02:47:30 BEAST NetworkManager[52738]: <info>  [1573840050.5729] dhcp4 (eno1): state changed timeout -> done
Nov 16 02:47:30 BEAST NetworkManager[52738]: <info>  [1573840050.5734] device (eno1): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Nov 16 02:47:30 BEAST NetworkManager[52738]: <warn>  [1573840050.5767] device (eno1): Activation: failed for connection 'Wired connection 1'
Nov 16 02:47:30 BEAST NetworkManager[52738]: <info>  [1573840050.5776] device (eno1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Nov 16 02:47:30 BEAST NetworkManager[52738]: <info>  [1573840050.5794] policy: auto-activating connection 'Wired connection 1' (3a26fe49-721d-3011-92fa-8641b1f7fe90)
Nov 16 02:47:30 BEAST NetworkManager[52738]: <info>  [1573840050.5798] device (eno1): Activation: starting connection 'Wired connection 1' (3a26fe49-721d-3011-92fa-8641b1f7fe90)
Nov 16 02:47:30 BEAST NetworkManager[52738]: <info>  [1573840050.5798] device (eno1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Nov 16 02:47:30 BEAST NetworkManager[52738]: <info>  [1573840050.5800] device (eno1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Nov 16 02:47:30 BEAST NetworkManager[52738]: <info>  [1573840050.5803] device (eno1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Nov 16 02:47:30 BEAST NetworkManager[52738]: <info>  [1573840050.5804] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
Nov 16 02:47:30 BEAST gnome-shell[1471]: Object NM.ActiveConnection (0x563f47d6f6a0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Nov 16 02:47:30 BEAST gnome-shell[1471]: == Stack trace for context 0x563f44433390 ==
Nov 16 02:47:30 BEAST gnome-shell[1471]: #0   563f4d1cf780 i   resource:///org/gnome/shell/ui/status/network.js:1329 (7fc36eec89d0 @ 56)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #1   563f4d1cf6e8 i   resource:///org/gnome/shell/ui/status/network.js:1346 (7fc36eec8a60 @ 113)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #2   563f4d1cf648 i   resource:///org/gnome/shell/ui/status/network.js:2049 (7fc36eecadc0 @ 216)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #3   7fff8f27dad0 b   self-hosted:977 (7fc36ee380d0 @ 413)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #4   7fff8f27dbb0 b   resource:///org/gnome/gjs/modules/signals.js:135 (7fc3bc0c6040 @ 376)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #5   563f4d1cf5c0 i   resource:///org/gnome/shell/ui/status/network.js:204 (7fc36eec43a0 @ 37)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #6   563f4d1cf548 i   resource:///org/gnome/shell/ui/status/network.js:273 (7fc36eec4940 @ 12)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #7   7fff8f27f150 b   resource:///org/gnome/gjs/modules/signals.js:135 (7fc3bc0c6040 @ 376)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #8   563f4d1cf4b0 i   resource:///org/gnome/shell/ui/status/network.js:1389 (7fc36eec8c10 @ 179)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #9   563f4d1cf408 i   resource:///org/gnome/shell/ui/status/network.js:1439 (7fc36eec8dc0 @ 161)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #10   563f4d1cf348 i   resource:///org/gnome/shell/ui/status/network.js:1503 (7fc36eec93a0 @ 129)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #11   563f4d1cf2b0 i   resource:///org/gnome/shell/ui/status/network.js:1851 (7fc36eeca3a0 @ 119)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #12   7fff8f281560 b   self-hosted:979 (7fc36ee380d0 @ 440)
Nov 16 02:47:30 BEAST gnome-shell[1471]: == Stack trace for context 0x563f44433390 ==
Nov 16 02:47:30 BEAST gnome-shell[1471]: #0   563f4d1cf480 i   resource:///org/gnome/shell/ui/status/network.js:1329 (7fc36eec89d0 @ 56)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #1   563f4d1cf3e8 i   resource:///org/gnome/shell/ui/status/network.js:1346 (7fc36eec8a60 @ 113)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #2   563f4d1cf348 i   resource:///org/gnome/shell/ui/status/network.js:2049 (7fc36eecadc0 @ 216)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #3   563f4d1cf2b0 i   resource:///org/gnome/shell/ui/status/network.js:1853 (7fc36eeca3a0 @ 134)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #4   7fff8f281560 b   self-hosted:979 (7fc36ee380d0 @ 440)
Nov 16 02:47:30 BEAST gnome-shell[1471]: JS ERROR: Exception in callback for signal: icon-changed: TypeError: connection.get_setting_ip4_config is not a function
                                         _isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25
                                         getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13
                                         _updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52
                                         _emit@resource:///org/gnome/gjs/modules/signals.js:135:27
                                         _iconChanged@resource:///org/gnome/shell/ui/status/network.js:204:9
                                         _addConnection/<@resource:///org/gnome/shell/ui/status/network.js:273:44
                                         _emit@resource:///org/gnome/gjs/modules/signals.js:135:27
                                         _sync@resource:///org/gnome/shell/ui/status/network.js:1389:9
                                         setActiveConnection@resource:///org/gnome/shell/ui/status/network.js:1439:9
                                         setActiveConnections@resource:///org/gnome/shell/ui/status/network.js:1503:13
                                         _syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1851:9
Nov 16 02:47:30 BEAST gnome-shell[1471]: Object NM.ActiveConnection (0x563f47d6f6a0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Nov 16 02:47:30 BEAST gnome-shell[1471]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function
                                         _isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25
                                         getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13
                                         _updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52
                                         _syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9
Nov 16 02:47:30 BEAST gnome-shell[1471]: Object NM.ActiveConnection (0x563f47d6f6a0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Nov 16 02:47:30 BEAST gnome-shell[1471]: == Stack trace for context 0x563f44433390 ==
Nov 16 02:47:30 BEAST gnome-shell[1471]: #0   563f4d1cf780 i   resource:///org/gnome/shell/ui/status/network.js:1329 (7fc36eec89d0 @ 56)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #1   563f4d1cf6e8 i   resource:///org/gnome/shell/ui/status/network.js:1346 (7fc36eec8a60 @ 113)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #2   563f4d1cf648 i   resource:///org/gnome/shell/ui/status/network.js:2049 (7fc36eecadc0 @ 216)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #3   7fff8f27e440 b   self-hosted:977 (7fc36ee380d0 @ 413)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #4   7fff8f27e520 b   resource:///org/gnome/gjs/modules/signals.js:135 (7fc3bc0c6040 @ 376)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #5   563f4d1cf5c0 i   resource:///org/gnome/shell/ui/status/network.js:204 (7fc36eec43a0 @ 37)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #6   563f4d1cf548 i   resource:///org/gnome/shell/ui/status/network.js:273 (7fc36eec4940 @ 12)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #7   7fff8f27fac0 b   resource:///org/gnome/gjs/modules/signals.js:135 (7fc3bc0c6040 @ 376)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #8   563f4d1cf4b0 i   resource:///org/gnome/shell/ui/status/network.js:1389 (7fc36eec8c10 @ 179)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #9   563f4d1cf408 i   resource:///org/gnome/shell/ui/status/network.js:1439 (7fc36eec8dc0 @ 161)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #10   563f4d1cf348 i   resource:///org/gnome/shell/ui/status/network.js:1503 (7fc36eec93a0 @ 129)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #11   563f4d1cf2b0 i   resource:///org/gnome/shell/ui/status/network.js:1851 (7fc36eeca3a0 @ 119)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #12   7fff8f281d10 b   self-hosted:979 (7fc36ee380d0 @ 440)
Nov 16 02:47:30 BEAST gnome-shell[1471]: JS ERROR: Exception in callback for signal: icon-changed: TypeError: connection.get_setting_ip4_config is not a function
                                         _isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25
                                         getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13
                                         _updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52
                                         _emit@resource:///org/gnome/gjs/modules/signals.js:135:27
                                         _iconChanged@resource:///org/gnome/shell/ui/status/network.js:204:9
                                         _addConnection/<@resource:///org/gnome/shell/ui/status/network.js:273:44
                                         _emit@resource:///org/gnome/gjs/modules/signals.js:135:27
                                         _sync@resource:///org/gnome/shell/ui/status/network.js:1389:9
                                         setActiveConnection@resource:///org/gnome/shell/ui/status/network.js:1439:9
                                         setActiveConnections@resource:///org/gnome/shell/ui/status/network.js:1503:13
                                         _syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1851:9
Nov 16 02:47:30 BEAST gnome-shell[1471]: == Stack trace for context 0x563f44433390 ==
Nov 16 02:47:30 BEAST gnome-shell[1471]: #0   563f4d1cf480 i   resource:///org/gnome/shell/ui/status/network.js:1329 (7fc36eec89d0 @ 56)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #1   563f4d1cf3e8 i   resource:///org/gnome/shell/ui/status/network.js:1346 (7fc36eec8a60 @ 113)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #2   563f4d1cf348 i   resource:///org/gnome/shell/ui/status/network.js:2049 (7fc36eecadc0 @ 216)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #3   563f4d1cf2b0 i   resource:///org/gnome/shell/ui/status/network.js:1853 (7fc36eeca3a0 @ 134)
Nov 16 02:47:30 BEAST gnome-shell[1471]: #4   7fff8f281d10 b   self-hosted:979 (7fc36ee380d0 @ 440)
Nov 16 02:47:30 BEAST gnome-shell[1471]: Object NM.ActiveConnection (0x563f47d6f6a0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Nov 16 02:47:30 BEAST gnome-shell[1471]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function
                                         _isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25
                                         getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13
                                         _updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52
                                         _syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9

Offline

#6 2019-11-15 20:39:04

seth
Member
Registered: 2012-09-03
Posts: 13,080

Re: [Solved] Cannot find interface and Wired connection failing

eno1 has a carrier (connection detected) at least previously got up. Right now it doesn't get a response on the dhcp lease request.
I'd suggest to reboot the computer as well as the router (because the many previous lease requests might have the router gotten into a gfy mood towards the nic)

Other options are to try a different dhcp implementation
https://wiki.archlinux.org/index.php/Ne … HCP_client
as well as disabling MAC randomization
https://wiki.archlinux.org/index.php/Ne … domization
because these things often cause trouble in that area.

As for the third NIC:
The realtek chip should™ be configured by the 8169 module, but afaics only w/ linux 5.4, so you'd need to build a rc or git kernel (or wait until it hits the repos)

Offline

#7 2019-11-16 01:35:28

marcelsmudda
Member
Registered: 2015-09-14
Posts: 14

Re: [Solved] Cannot find interface and Wired connection failing

Cool thanks. A router restart helped!
Is there an ETA when the feature will be in the kernel or can I install a module that would enable the last interface?

Offline

#8 2019-11-16 07:55:14

seth
Member
Registered: 2012-09-03
Posts: 13,080

Re: [Solved] Cannot find interface and Wired connection failing

5.4 is already slightly late (upstream).
I'd assume "before December", but there's no deadline I'm aware of.

You could probably backport the relevant commits into a customized 5.3 but I'm afraid there's no "click to make that happen".

Offline

#9 2019-11-16 07:57:49

marcelsmudda
Member
Registered: 2015-09-14
Posts: 14

Re: [Solved] Cannot find interface and Wired connection failing

Thanks. Then I'll have to wait -.-

Offline

Board footer

Powered by FluxBB