[Solved] Ethernet remains connected but stops working.

phoenix324 · 2023-08-24 06:24:48

To solve the issue ( temporarily) I need to execute

nmcli device down enp3s0 && nmcli device up enp3s0

or alternatively, unplug and then replug the Ethernet cable to restore functionality.

Interestingly, even when I can't access the internet on my primary device due to this problem, if I share my internet using the linux-wifi-hotspot package, other devices connected to the hotspot can use the internet without any issues.

For additional context:
- I have a dual-boot setup with Windows, where the Ethernet connection works flawlessly.
- To rule out installation-specific issues, I installed a second instance of Arch OS and observed the same Ethernet problem there as well.
- Based on suggestions from the Arch Wiki on Network Configuration for Ethernet, I tried solutions under sections 3.5, 3.6, and 3.7, but none resolved the issue.

Sysem Information:
- OS: Arch Linux x86_64
- Host: GL65 Leopard 9SDK REV:1.0
- Kernel: 6.4.11-arch2-1
- CPU: Intel i7-9750H (12) @ 4.500GHz
- GPU: Intel CoffeeLake-H GT2 [UHD Graphics
- GPU: NVIDIA GeForce GTX 1660 Ti Mobile

Some Terminal Commands Ouput for debugging ->

[phoenix@ArchLinux ~]$ sudo dmidecode -t 2
[sudo] password for phoenix: 
# dmidecode 3.5
Getting SMBIOS data from sysfs.
SMBIOS 3.2.1 present.

Handle 0x0003, DMI type 2, 15 bytes
Base Board Information
    Manufacturer: Micro-Star International Co., Ltd.
    Product Name: MS-16U7
    Version: REV:1.0
    Serial Number: #######
    Asset Tag: Default string
    Features:
        Board is a hosting board
        Board is replaceable
    Location In Chassis: Default string
    Chassis Handle: 0x0004
    Type: Motherboard
    Contained Object Handles: 0

[phoenix@ArchLinux ~]$ cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=######## rw loglevel=3 intel_iommu=on iommu=pt iommu=soft resume=/dev/nvme0n1p2 nouveau.modeset=0 module_blacklist=r8169

[phoenix@ArchLinux report]$ sudo dmesg | grep r8169
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=######### rw loglevel=3 intel_iommu=on iommu=pt iommu=soft resume=/dev/nvme0n1p2 nouveau.modeset=0 module_blacklist=r8169
[    0.049999] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=########## rw loglevel=3 intel_iommu=on iommu=pt iommu=soft resume=/dev/nvme0n1p2 nouveau.modeset=0 module_blacklist=r8169
[phoenix@ArchLinux report]$ sudo dmesg | grep r8168
[    3.964724] r8168 Gigabit Ethernet driver 8.051.02-NAPI loaded
[    3.978206] r8168: This product is covered by one or more of the following patents: US6,570,884, US6,115,776, and US6,327,625.
[    3.980271] r8168  Copyright (C) 2022 Realtek NIC software team <nicfae@realtek.com> 
[    4.077443] r8168 0000:03:00.0 enp3s0: renamed from eth0
[    7.407002] r8168: enp3s0: link up

[phoenix@ArchLinux report]$  sudo lspci -v
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
	Subsystem: Micro-Star International Co., Ltd. [MSI] RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
	Flags: bus master, fast devsel, latency 0, IRQ 18, IOMMU group 13
	I/O ports at 3000 [size=256]
	Memory at a5204000 (64-bit, non-prefetchable) [size=4K]
	Memory at a5200000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
	Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [70] Express Endpoint, MSI 01
	Capabilities: [b0] MSI-X: Enable+ Count=4 Masked-
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Virtual Channel
	Capabilities: [160] Device Serial Number ##########
	Capabilities: [170] Latency Tolerance Reporting
	Capabilities: [178] L1 PM Substates
	Kernel driver in use: r8168
	Kernel modules: r8169, r8168

I can also provide output of `journalctl -b` but i am confused wether it contains sensitive information or not and how to clean them.

Last edited by phoenix324 (2023-08-25 04:43:38)

seth · 2023-08-24 06:41:30

I have a dual-boot setup with Windows

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

i am confused wether it contains sensitive information or not

It's not supposed to, sudo calls are audited, so if you used sudo on … errhem… "private" data, that'll be exposed.

Start w/ the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

phoenix324 · 2023-08-24 07:59:16

Hibernate and FastStartup in windows disabled, i double checked.

[phoenix@ArchLinux ~]$ find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
bluetooth.service                        | bluetooth.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service   | system
dhcpcd.service                           | multi-user.target.wants
display-manager.service                  | system
fstrim.timer                             | timers.target.wants
getty@tty1.service                       | getty.target.wants
input-remapper.service                   | default.target.wants
mullvad-daemon.service                   | multi-user.target.wants
mullvad-early-boot-blocking.service      | mullvad-daemon.service.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-pulse.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
reflector.timer                          | timers.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-timesyncd.service                | sysinit.target.wants
wireplumber.service                      | pipewire.service.wants
xdg-user-dirs-update.service             | default.target.wants

seth · 2023-08-24 08:02:11

Yeah…

dhcpcd.service                           | multi-user.target.wants
…
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants

Pick one, disable the other. Symptoms already fit that.

If not, disable the VPN and see whether that's the cause.

phoenix324 · 2023-08-24 08:06:55

Sorry, i am confused which one to choose between ?

is it between dhcpcd.service and NetworkManager.service ? or is it actually between -> dhcpcd.service OR (NetworkManager.service & NetworkManager-wait-online.service).
Can you help me with some docs so i can learn more about them as why are they conflicting ?

For VPN, its not actually active right now , and i installed vpn wayafter the problem started occuring, in the meantime i was using wifi and was procastinating to solve this issue.

phoenix324 · 2023-08-24 08:10:42

Ok got it , it is as you said dhcpcd.service OR (NetworkManager.service & NetworkManager-wait-online.service) , i will disable dhcpcd and will report if it worked. Thank you

Last edited by phoenix324 (2023-08-24 08:13:27)

phoenix324 · 2023-08-25 04:35:15

Thank You it worked.

Arch Linux

#1 2023-08-24 06:24:48

[Solved] Ethernet remains connected but stops working.

#2 2023-08-24 06:41:30

Re: [Solved] Ethernet remains connected but stops working.

#3 2023-08-24 07:59:16

Re: [Solved] Ethernet remains connected but stops working.

#4 2023-08-24 08:02:11

Re: [Solved] Ethernet remains connected but stops working.

#5 2023-08-24 08:06:55

Re: [Solved] Ethernet remains connected but stops working.

#6 2023-08-24 08:10:42

Re: [Solved] Ethernet remains connected but stops working.

#7 2023-08-25 04:35:15

Re: [Solved] Ethernet remains connected but stops working.

Board footer