Arch Linux

ntldr

Member

Registered: 2017-01-04

Posts: 65

Wired connection problem

Hey

so when I get to the DE my NM keeps saying "wired connection deactivated" spam for 1-2 minutes until it finally finds it. If I click disconnect from the networkmanager-applet it takes same long to find it or only solution is to reboot machine until it finds it again.

unit-files log: https://bpaste.net/raw/m4_t

ip link: https://bpaste.net/raw/pZyi

journal: https://bpaste.net/raw/NTvx

let me know what else you'd need I can't think anything else top of my head.

➜ "lspci"
00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07)
00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller
00:16.0 Communication controller: Intel Corporation 200 Series PCH CSME HECI #1
00:17.0 SATA controller: Intel Corporation 200 Series PCH SATA controller [AHCI mode]
00:1b.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #17 (rev f0)
00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #1 (rev f0)
00:1c.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #5 (rev f0)
00:1c.6 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #7 (rev f0)
00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #9 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Z370 Chipset LPC/eSPI Controller
00:1f.2 Memory controller: Intel Corporation 200 Series/Z370 Chipset Family Power Management Controller
00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio
00:1f.4 SMBus: Intel Corporation 200 Series/Z370 Chipset Family SMBus Controller
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V
01:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GP102 HDMI Audio Controller (rev a1)
04:00.0 USB controller: ASMedia Technology Inc. ASM2142 USB 3.1 Host Controller
05:00.0 USB controller: ASMedia Technology Inc. ASM2142 USB 3.1 Host Controller

ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether b2:f8:20:d6:d1:71 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.180/24 brd 192.168.1.255 scope global dynamic noprefixroute enp0s31f6
       valid_lft 42996sec preferred_lft 42996sec
    inet6 2001:14ba:80e5:a500::6d5/128 scope global dynamic noprefixroute 
       valid_lft 15137sec preferred_lft 6137sec
    inet6 fd1e:a1a7:3cfa::6d5/128 scope global noprefixroute 
       valid_lft forever preferred_lft forever
    inet6 fd1e:a1a7:3cfa:0:fca3:b4a7:d4d9:3528/64 scope global temporary dynamic 
       valid_lft 6996sec preferred_lft 1596sec
    inet6 fd1e:a1a7:3cfa:0:f9a9:9e42:219d:7e08/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 6996sec preferred_lft 1596sec
    inet6 2001:14ba:80e5:a500:fca3:b4a7:d4d9:3528/64 scope global temporary dynamic 
       valid_lft 6996sec preferred_lft 1596sec
    inet6 2001:14ba:80e5:a500:d164:f407:94ae:f6f/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 6996sec preferred_lft 1596sec
    inet6 fe80::c5c:8b9f:77be:6a5e/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

[➜ sudo journalctl -b
[sudo] password for root: 
-- Logs begin at Wed 2018-06-27 14:33:15 EEST, end at Sun 2019-09-22 20:00:03 EEST. --
Sep 22 19:52:57 Kisu-Archlinux kernel: microcode: microcode updated early to revision 0xb4, date = 2019-04-01
Sep 22 19:52:57 Kisu-Archlinux kernel: Linux version 5.3.1-arch1-1-ARCH (builduser@heftig-3999379) (gcc version 9.1.0 (GCC)) #1 SMP PREEM>
Sep 22 19:52:57 Kisu-Archlinux kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=83c85ef9-11d6-441f-b9fa-4db79c6c8db8 rw
Sep 22 19:52:57 Kisu-Archlinux kernel: KERNEL supported cpus:
Sep 22 19:52:57 Kisu-Archlinux kernel:   Intel GenuineIntel
Sep 22 19:52:57 Kisu-Archlinux kernel:   AMD AuthenticAMD
Sep 22 19:52:57 Kisu-Archlinux kernel:   Hygon HygonGenuine
Sep 22 19:52:57 Kisu-Archlinux kernel:   Centaur CentaurHauls
Sep 22 19:52:57 Kisu-Archlinux kernel:   zhaoxin   Shanghai  
Sep 22 19:52:57 Kisu-Archlinux kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Sep 22 19:52:57 Kisu-Archlinux kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Sep 22 19:52:57 Kisu-Archlinux kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Sep 22 19:52:57 Kisu-Archlinux kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
Sep 22 19:52:57 Kisu-Archlinux kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
Sep 22 19:52:57 Kisu-Archlinux kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Sep 22 19:52:57 Kisu-Archlinux kernel: x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
Sep 22 19:52:57 Kisu-Archlinux kernel: x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
Sep 22 19:52:57 Kisu-Archlinux kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
Sep 22 19:52:57 Kisu-Archlinux kernel: BIOS-provided physical RAM map:
Sep 22 19:52:57 Kisu-Archlinux kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
Sep 22 19:52:57 Kisu-Archlinux kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
Sep 22 19:52:57 Kisu-Archlinux kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009efff] usable
Sep 22 19:52:57 Kisu-Archlinux kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
Sep 22 19:52:57 Kisu-Archlinux kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007fbddfff] usable
Sep 22 19:52:57 Kisu-Archlinux kernel: BIOS-e820: [mem 0x000000007fbde000-0x000000007fbdefff] ACPI NVS
Sep 22 19:52:57 Kisu-Archlinux kernel: BIOS-e820: [mem 0x000000007fbdf000-0x000000007fbdffff] reserved
Sep 22 19:52:57 Kisu-Archlinux kernel: BIOS-e820: [mem 0x000000007fbe0000-0x000000008c8fdfff] usable
Sep 22 19:52:57 Kisu-Archlinux kernel: BIOS-e820: [mem 0x000000008c8fe000-0x000000008e1bafff] reserved
Sep 22 19:52:57 Kisu-Archlinux kernel: BIOS-e820: [mem 0x000000008e1bb000-0x000000008e1fefff] ACPI data
Sep 22 19:52:57 Kisu-Archlinux kernel: BIOS-e820: [mem 0x000000008e1ff000-0x000000008e5f0fff] ACPI NVS
Sep 22 19:52:57 Kisu-Archlinux kernel: BIOS-e820: [mem 0x000000008e5f1000-0x000000008f6d8fff] reserved
Sep 22 19:52:57 Kisu-Archlinux kernel: BIOS-e820: [mem 0x000000008f6d9000-0x000000008f7a1fff] type 20
Sep 22 19:52:57 Kisu-Archlinux kernel: BIOS-e820: [mem 0x000000008f7a2000-0x000000008f7fffff] usable
Sep 22 19:52:57 Kisu-Archlinux kernel: BIOS-e820: [mem 0x000000008f800000-0x000000008fffffff] reserved
Sep 22 19:52:57 Kisu-Archlinux kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Sep 22 19:52:57 Kisu-Archlinux kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved

Last edited by ntldr (2019-09-22 17:00:47)

seth

Member

Registered: 2012-09-03

Posts: 51,045

Re: Wired connection problem

The journal you posted is capped and the one you pasted limited to errors, use https://wiki.archlinux.org/index.php/Pastebin to directly feed the output into a pastebin service.
However your error journal reveals that dhcpcd is running what's not necessarily hinted by the enabled units.

If you didn't configure NM to use dhcpcd, that's your problem. Otherwise please paste a complete journal.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

ntldr

Member

Registered: 2017-01-04

Posts: 65

Re: Wired connection problem

The journal you posted is capped and the one you pasted limited to errors, use https://wiki.archlinux.org/index.php/Pastebin to directly feed the output into a pastebin service.
However your error journal reveals that dhcpcd is running what's not necessarily hinted by the enabled units.

If you didn't configure NM to use dhcpcd, that's your problem. Otherwise please paste a complete journal.

here you go https://bpaste.net/raw/hon6 I also noticed that is old log with dhcpcd it isn't actually running anymore and I believe it shouldn't be coz NM uses it's own? tho by default I seem to be using ipv6 that is issue for NM?

another problem I have noticed that before when I started up my pc and landed on desktop by that time I already had the wired connection on but now I need to wait for it to find it.. how do I make it like it was before?

here's NM log: http://ix.io/1Wyo

Last edited by ntldr (2019-09-23 12:48:22)

seth

Member

Registered: 2012-09-03

Posts: 51,045

Re: Wired connection problem

That's the session journal, use "sudo journalctl -b" to gain access to the system journal.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

ntldr

Member

Registered: 2017-01-04

Posts: 65

Re: Wired connection problem

That's the session journal, use "sudo journalctl -b" to gain access to the system journal.

here you go http://ix.io/1WyC

seth

Member

Registered: 2012-09-03

Posts: 51,045

Re: Wired connection problem

Repeatedly:

Sep 23 15:16:18 Kisu-Archlinux NetworkManager[607]: <info>  [1569240978.8163] manager: NetworkManager state is now CONNECTING
Sep 23 15:16:18 Kisu-Archlinux NetworkManager[607]: <info>  [1569240978.9050] device (enp0s31f6): set-hw-addr: set-cloned MAC address to B2:F8:20:D6:D1:71 (B2:F8:20:D6:D1:71)
Sep 23 15:16:18 Kisu-Archlinux NetworkManager[607]: <info>  [1569240978.9050] device (enp0s31f6): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 23 15:16:18 Kisu-Archlinux NetworkManager[607]: <info>  [1569240978.9052] device (enp0s31f6): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Sep 23 15:16:18 Kisu-Archlinux NetworkManager[607]: <info>  [1569240978.9054] dhcp4 (enp0s31f6): activation: beginning transaction (timeout in 45 seconds)
Sep 23 15:16:24 Kisu-Archlinux NetworkManager[607]: <info>  [1569240984.9059] device (enp0s31f6): state change: ip-config -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
Sep 23 15:16:24 Kisu-Archlinux NetworkManager[607]: <info>  [1569240984.9305] dhcp4 (enp0s31f6): canceled DHCP transaction
Sep 23 15:16:24 Kisu-Archlinux NetworkManager[607]: <info>  [1569240984.9306] dhcp4 (enp0s31f6): state changed unknown -> done
Sep 23 15:16:24 Kisu-Archlinux NetworkManager[607]: <info>  [1569240984.9318] device (enp0s31f6): set-hw-addr: reset MAC address to 18:31:BF:2B:75:0F (deactivate)
Sep 23 15:16:24 Kisu-Archlinux NetworkManager[607]: <info>  [1569240984.9333] manager: NetworkManager state is now DISCONNECTED
Sep 23 15:16:24 Kisu-Archlinux NetworkManager[607]: <info>  [1569240984.9715] device (enp0s31f6): carrier: link connected
Sep 23 15:16:24 Kisu-Archlinux NetworkManager[607]: <info>  [1569240984.9719] device (enp0s31f6): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')

Looks like https://bbs.archlinux.org/viewtopic.php?id=248915
You have an NTFS partition so it's likely https://wiki.archlinux.org/index.php/Du … t_Start-Up

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

ntldr

Member

Registered: 2017-01-04

Posts: 65

Re: Wired connection problem

Repeatedly:

Sep 23 15:16:18 Kisu-Archlinux NetworkManager[607]: <info>  [1569240978.8163] manager: NetworkManager state is now CONNECTING
Sep 23 15:16:18 Kisu-Archlinux NetworkManager[607]: <info>  [1569240978.9050] device (enp0s31f6): set-hw-addr: set-cloned MAC address to B2:F8:20:D6:D1:71 (B2:F8:20:D6:D1:71)
Sep 23 15:16:18 Kisu-Archlinux NetworkManager[607]: <info>  [1569240978.9050] device (enp0s31f6): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 23 15:16:18 Kisu-Archlinux NetworkManager[607]: <info>  [1569240978.9052] device (enp0s31f6): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Sep 23 15:16:18 Kisu-Archlinux NetworkManager[607]: <info>  [1569240978.9054] dhcp4 (enp0s31f6): activation: beginning transaction (timeout in 45 seconds)
Sep 23 15:16:24 Kisu-Archlinux NetworkManager[607]: <info>  [1569240984.9059] device (enp0s31f6): state change: ip-config -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
Sep 23 15:16:24 Kisu-Archlinux NetworkManager[607]: <info>  [1569240984.9305] dhcp4 (enp0s31f6): canceled DHCP transaction
Sep 23 15:16:24 Kisu-Archlinux NetworkManager[607]: <info>  [1569240984.9306] dhcp4 (enp0s31f6): state changed unknown -> done
Sep 23 15:16:24 Kisu-Archlinux NetworkManager[607]: <info>  [1569240984.9318] device (enp0s31f6): set-hw-addr: reset MAC address to 18:31:BF:2B:75:0F (deactivate)
Sep 23 15:16:24 Kisu-Archlinux NetworkManager[607]: <info>  [1569240984.9333] manager: NetworkManager state is now DISCONNECTED
Sep 23 15:16:24 Kisu-Archlinux NetworkManager[607]: <info>  [1569240984.9715] device (enp0s31f6): carrier: link connected
Sep 23 15:16:24 Kisu-Archlinux NetworkManager[607]: <info>  [1569240984.9719] device (enp0s31f6): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')

Looks like https://bbs.archlinux.org/viewtopic.php?id=248915
You have an NTFS partition so it's likely https://wiki.archlinux.org/index.php/Du … t_Start-Up

Yes I have NTFS ssd which has windows 10 installed my setup goes like this

SSD with Arch Linux on it and separate SSD with windows 10 on it your guess it's likely that this is the issue even tho they are on different SSDs?

seth

Member

Registered: 2012-09-03

Posts: 51,045

Re: Wired connection problem

The SSDs don't matter, the problem would be that windows is hibernating and leaves the NIC in an garbled state. Please see the link I posted.

However there's maybe something creeping up: https://bbs.archlinux.org/viewtopic.php?id=249406

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

ntldr

Member

Registered: 2017-01-04

Posts: 65

Re: Wired connection problem

The SSDs don't matter, the problem would be that windows is hibernating and leaves the NIC in an garbled state. Please see the link I posted.

However there's maybe something creeping up: https://bbs.archlinux.org/viewtopic.php?id=249406

I tried to turn off the fast boot feature it didn't have any effect on my system. For yolo I tried to switch the ethernet cable and that also didn't have any effect on the issue.

I am starting to feel like this is kernel 5.3 issue rather than being issue in my end since Wireguard also has a problem with ipv6 connection making my whole system crashed this has been issue with several other people with 5.3 kernel and ipv6.. so I wouldn't be surprised if this is kernel issue now.

sakalisc

Member

Registered: 2019-10-08

Posts: 1

Re: Wired connection problem

I've run into the same problem since updating my system a few days ago. It happens even when I go Linux -> Shutdown/Restart -> Linux, so I don't think it's a problem caused by Windows.

StarFleetCPTN

Member

Registered: 2019-10-15

Posts: 1

Re: Wired connection problem

I'm having the same issue when using Linux 5.3. The only way for me to get around it is to use 5.2 or older.

loqs

Member

Registered: 2014-03-06

Posts: 17,323

Re: Wired connection problem

I'm having the same issue when using Linux 5.3. The only way for me to get around it is to use 5.2 or older.

Please do not do that.

duzun

Member

Registered: 2019-10-20

Posts: 2

Re: Wired connection problem

Well, actually that is helpful at least to me, cause I'm having exactly the same issue, and reverting to the previous kernel is the only working solution for me so far.
This indicates that the issue is somehow related to the new kernel.

seth

Member

Registered: 2012-09-03

Posts: 51,045

Re: Wired connection problem

What loqs told StarFleetCPTN not to do and what you just did is https://wiki.archlinux.org/index.php/Co … mpty_posts …

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc