Ethernet suddenly stopped working completely

Support Network
1

I had posted here some months ago about my ethernet turning on and off at random times. I thought it was fixed for 1 day, but it wasnt so i honestly decided to just live with it. Yesterday it did the usual “Wired Connection 1 Deactivated”, but it never came back and ever since it tries to connect, constantly failing.
I tired systemctl restart --now NetworkManager.service, also looked through hundrends of threads both here and on arch linux forums with no luck.

Any help is greatly appreciated.
I know similar posts have been posted so many times but i just didnt seem to find a fix for me. I also don’t have wifi option.

Ip link show:

ip link show  ✔
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 fq_codel state
DOWN mode DEFAULT group default qlen 1000

Nmcli device status:

nmcli device status  ✔
DEVICE TYPE STATE CONNECTION
enp8s0 ethernet unavailable --
lo loopback unmanaged

Journalctl:

journalctl  ✔
Ιαν 20 02:28:50 noisefuck kernel: Linux version 5.15.12-1-MANJARO (builduser@fv-az39-353)
(gcc (GCC) 11.1.0, GNU ld>
Ιαν 20 02:28:50 noisefuck kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.15-x86_64
root=UUID=8ca01669-9c05-46de-b>
Ιαν 20 02:28:50 noisefuck kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point
registers'
Ιαν 20 02:28:50 noisefuck kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Ιαν 20 02:28:50 noisefuck kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Ιαν 20 02:28:50 noisefuck kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Ιαν 20 02:28:50 noisefuck kernel: x86/fpu: Enabled xstate features 0x7, context size is 832
bytes, using 'compacted>
Ιαν 20 02:28:50 noisefuck kernel: signal: max sigframe size: 1776
Ιαν 20 02:28:50 noisefuck kernel: BIOS-provided physical RAM map:
Ιαν 20 02:28:50 noisefuck kernel: BIOS-e820: [mem 0x0000000000000000-
0x000000000009ffff] usable
Ιαν 20 02:28:50 noisefuck kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff]
reserved
Ιαν 20 02:28:50 noisefuck kernel: BIOS-e820: [mem 0x0000000000100000-

0x0000000009e01fff] usable
Ιαν 20 02:28:50 noisefuck kernel: BIOS-e820: [mem 0x0000000009e02000-0x0000000009ffffff]
reserved
Ιαν 20 02:28:50 noisefuck kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff]
usable
Ιαν 20 02:28:50 noisefuck kernel: BIOS-e820: [mem 0x000000000a200000-
0x000000000a20afff] ACPI NVS
Ιαν 20 02:28:50 noisefuck kernel: BIOS-e820: [mem 0x000000000a20b000-0x000000000affffff]
usable
Ιαν 20 02:28:50 noisefuck kernel: BIOS-e820: [mem 0x000000000b000000-
0x000000000b01ffff] reserved
Ιαν 20 02:28:50 noisefuck kernel: BIOS-e820: [mem 0x000000000b020000-
0x00000000db651fff] usable
Ιαν 20 02:28:50 noisefuck kernel: BIOS-e820: [mem 0x00000000db652000-
0x00000000db767fff] reserved
Ιαν 20 02:28:50 noisefuck kernel: BIOS-e820: [mem 0x00000000db768000-
0x00000000dbbe8fff] usable
Ιαν 20 02:28:50 noisefuck kernel: BIOS-e820: [mem 0x00000000dbbe9000-
0x00000000dbcf9fff] ACPI NVS
Ιαν 20 02:28:50 noisefuck kernel: BIOS-e820: [mem 0x00000000dbcfa000-
0x00000000dcb43fff] reserved
Ιαν 20 02:28:50 noisefuck kernel: BIOS-e820: [mem 0x00000000dcb44000-
0x00000000dcbd4fff] type 20
Ιαν 20 02:28:50 noisefuck kernel: BIOS-e820: [mem 0x00000000dcbd5000-0x00000000deffffff]
usable
Ιαν 20 02:28:50 noisefuck kernel: BIOS-e820: [mem 0x00000000df000000-0x00000000dfffffff]
reserved
Ιαν 20 02:28:50 noisefuck kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff]
reserved
Ιαν 20 02:28:50 noisefuck kernel: BIOS-e820: [mem 0x00000000fd000000-0x00000000ffffffff]
reserved
Ιαν 20 02:28:50 noisefuck kernel: BIOS-e820: [mem 0x0000000100000000-0x00000001feffffff]
usable
Ιαν 20 02:28:50 noisefuck kernel: BIOS-e820: [mem 0x00000001ff000000-0x000000021effffff]
reserved
Ιαν 20 02:28:50 noisefuck kernel: NX (Execute Disable) protection: active
Ιαν 20 02:28:50 noisefuck kernel: efi: EFI v2.70 by American Megatrends

Ιαν 20 02:28:50 noisefuck kernel: efi: ACPI 2.0=0xdbc76000 ACPI=0xdbc76000
SMBIOS=0xdca2e000 SMBIOS 3.0=0xdca2d000 >
Ιαν 20 02:28:50 noisefuck kernel: SMBIOS 3.2.0 present.
Ιαν 20 02:28:50 noisefuck kernel: DMI: Gigabyte Technology Co., Ltd. B450M S2H/B450M S2H,
BIOS F50 11/27/2019
Ιαν 20 02:28:50 noisefuck kernel: tsc: Fast TSC calibration failed
Ιαν 20 02:28:50 noisefuck kernel: e820: update [mem 0x00000000-0x00000fff] usable ==>
reserved
Ιαν 20 02:28:50 noisefuck kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Ιαν 20 02:28:50 noisefuck kernel: last_pfn = 0x1ff000 max_arch_pfn = 0x400000000
Ιαν 20 02:28:50 noisefuck kernel: x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP
UC- WT
Ιαν 20 02:28:50 noisefuck kernel: e820: update [mem 0xe0000000-0xffffffff] usable ==>
reserved
Ιαν 20 02:28:50 noisefuck kernel: last_pfn = 0xdf000 max_arch_pfn = 0x400000000
Ιαν 20 02:28:50 noisefuck kernel: esrt: Reserving ESRT space from 0x00000000d7ed6518 to
0x00000000d7ed6550.
Ιαν 20 02:28:50 noisefuck kernel: e820: update [mem 0xd7ed6000-0xd7ed6fff] usable ==>
reserved
Ιαν 20 02:28:50 noisefuck kernel: Using GB pages for direct mapping
Ιαν 20 02:28:50 noisefuck kernel: Secure boot disabled
Ιαν 20 02:28:50 noisefuck kernel: RAMDISK: [mem 0x36e37000-0x37712fff]
Ιαν 20 02:28:50 noisefuck kernel: ACPI: Early table checksum verification disabled
Ιαν 20 02:28:50 noisefuck kernel: ACPI: RSDP 0x00000000DBC76000 000024 (v02 ALASKA)
Ιαν 20 02:28:50 noisefuck kernel: ACPI: XSDT 0x00000000DBC760B0 0000DC (v01 ALASKA
A M I 01072009 AMI 00010013)
Ιαν 20 02:28:50 noisefuck kernel: ACPI: FACP 0x00000000DBC7CE58 000114 (v06 ALASKA A
M I 01072009 AMI 00010013)
Ιαν 20 02:28:50 noisefuck kernel: ACPI: DSDT 0x00000000DBC76220 006C35 (v02 ALASKA A
M I 01072009 INTL 20160930)

inxi -Fayz:

inxi -Fayz  ✔

System:
Kernel: 5.15.21-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0

parameters: BOOT_IMAGE=/boot/vmlinuz-5.15-x86_64
root=UUID=8ca01669-9c05-46de-bcd2-d612d9820376 rw quiet apparmor=1
security=apparmor udev.log_priority=3
Desktop: KDE Plasma 5.23.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11
vt: 1 dm: SDDM Distro: Manjaro Linux base: Arch Linux
Machine:
Type: Desktop Mobo: Gigabyte model: B450M S2H v: x.x
serial: <superuser required> UEFI: American Megatrends v: F50
date: 11/27/2019
CPU:
Info: model: AMD Ryzen 3 2200G with Radeon Vega Graphics bits: 64 type: MCP
arch: Zen family: 0x17 (23) model-id: 0x11 (17) stepping: 0
microcode: 0x8101016
Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 384 KiB
desc: d-4x32 KiB; i-4x64 KiB L2: 2 MiB desc: 4x512 KiB L3: 4 MiB
desc: 1x4 MiB
Speed (MHz): avg: 2087 high: 2549 min/max: 1600/3500 boost: enabled
scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1546 2: 2011
3: 2549 4: 2242 bogomips: 27956
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP:

disabled, RSB filling

Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Mobile Series]
driver: amdgpu v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 ports:
active: HDMI-A-1 empty: DP-1,DVI-D-1 bus-ID: 09:00.0 chip-ID: 1002:15dd
class-ID: 0300
Display: x11 server: X.org v: 1.21.1.3 compositor: kwin_x11 driver: X:
loaded: amdgpu,ati unloaded: modesetting alternate: fbdev,vesa gpu: amdgpu
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-size: <missing: xdpyinfo>
Monitor-1: HDMI-A-0 mapped: HDMI-A-1 model: Samsung C24F390
serial: <filter> built: 2020 res: 1920x1080 dpi: 94 gamma: 1.2
size: 521x293mm (20.5x11.5") diag: 598mm (23.5") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
Message: Unable to show GL data. Required tool glxinfo missing.
Audio:
Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 09:00.1
chip-ID: 1002:15de class-ID: 0403
Device-2: AMD Family 17h HD Audio vendor: Gigabyte driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 09:00.6
chip-ID: 1022:15e3 class-ID: 0403
Device-3: Texas Instruments PCM2902 Audio Codec type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 3-2:2 chip-ID: 08bb:2902
class-ID: 0300
Sound Server-1: ALSA v: k5.15.21-1-MANJARO running: yes
Sound Server-2: JACK v: 1.9.20 running: no
Sound Server-3: PulseAudio v: 15.0 running: yes

Sound Server-4: PipeWire v: 0.3.45 running: no

Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Gigabyte driver: r8168 v: 8.049.02-NAPI modules: r8169 pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 08:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: enp8s0 state: down mac: <filter>
Drives:
Local Storage: total: 698.65 GiB used: 407.22 GiB (58.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WDS500G2B0A
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 90WD scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD2500BEVS-22UST0 size: 232.89 GiB block-size: physical: 512 B
logical: 512 B speed: 1.5 Gb/s type: N/A serial: <filter> rev: 1A01
scheme: GPT
Partition:
ID-1: / raw-size: 465.46 GiB size: 457.09 GiB (98.20%)
used: 177.18 GiB (38.8%) fs: ext4 dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 288 KiB (0.1%) fs: vfat dev: /dev/sda1 maj-min: 8:1
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 16.8 C mobo: N/A gpu: amdgpu temp: 34.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 216 Uptime: 19m wakeups: 0 Memory: 7.28 GiB
used: 1.76 GiB (24.2%) Init: systemd v: 250 tool: systemctl Compilers:

gcc: 11.1.0 clang: 13.0.1 Packages: 1351 pacman: 1342 lib: 357 flatpak: 0
snap: 9 Shell: Zsh v: 5.8 default: Bash v: 5.1.16 running-in: konsole
inxi: 3.3.13
1 Like
2

Hi @GrindFreak,

Please post the output of:

lspci | grep Ethernet
1 Like
3

It seems to be back for some reason… I didn’t even change anything.
I didn’t have a connection since last night thats why i posted.
Should i mark this as solved or wait to see if it happens again?

4

lspci | grep Ethernet

08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 16)
5

And of:

cat /etc/default/grub

Please.

1 Like
6

cat /etc/default/grub

GRUB_DEFAULT=saved
GRUB_TIMEOUT=5
GRUB_TIMEOUT_STYLE=hidden
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="quiet apparmor=1 security=apparmor udev.log_priority=3"
GRUB_CMDLINE_LINUX=""

# If you want to enable the save default function, uncomment the following
# line, and set GRUB_DEFAULT to saved.
GRUB_SAVEDEFAULT=true

# Uncomment to disable submenus in boot menu
#GRUB_DISABLE_SUBMENU=y

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y

# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console

# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command 'videoinfo'
GRUB_GFXMODE=auto

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true

# Uncomment this option to enable os-prober execution in the grub-mkconfig command
GRUB_DISABLE_OS_PROBER=false

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper
# modes only.  Entries specified as foreground/background.
GRUB_COLOR_NORMAL="light-gray/black"
GRUB_COLOR_HIGHLIGHT="green/black"

# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/usr/share/grub/background.png"
GRUB_THEME="/usr/share/grub/themes/manjaro/theme.txt"

# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"

# Uncomment to ensure that the root filesystem is mounted read-only so that
# systemd-fsck can run the check automatically. We use 'fsck' by default, which
# needs 'rw' as boot parameter, to avoid delay in boot-time. 'fsck' needs to be
# removed from 'mkinitcpio.conf' to make 'systemd-fsck' work.
# See also Arch-Wiki: https://wiki.archlinux.org/index.php/Fsck#Boot_time_checking
#GRUB_ROOT_FS_RO=true
7

Which branch do you use? Only testing and unstable got networkmanager updated and 1.36.0 seems to have some regressions.

8

According to this page:

Gigabyte Motherboard with Realtek 8111/8168/8411

With motherboards such as the Gigabyte GA-990FXA-UD3, booting with IOMMU off (which can be the default) will cause the network interface to be unreliable, often failing to connect or connecting but allowing no throughput. This will apply to the onboard NIC and to any other pci-NIC in the box because the IOMMU setting affects the entire network interface on the board. Enabling IOMMU and booting with the install media will throw AMD I-10/xhci page faults for a second, but then boots normally, resulting in a fully functional onboard NIC (even with the r8169 module).

When configuring the boot process for your installation, add iommu=soft as a kernel parameter to eliminate the error messages on boot and restore USB3.0 functionality.

So let’s try that. Open /etc/default/grub to edit. Let’s use nano:

sudo nano /etc/default/grub

Look for the line starting with:

GRUB_CMDLINE_LINUX_DEFAULT

And change it from:

GRUB_CMDLINE_LINUX_DEFAULT="quiet apparmor=1 security=apparmor udev.log_priority=3"

To:

GRUB_CMDLINE_LINUX_DEFAULT="quiet apparmor=1 security=apparmor udev.log_priority=3 iommu=soft"

Save the file, using Ctrl+O, and exit nano, using Ctrl+X.

Then you have to update grub:

sudo update-grub

If there were no error, reboot and test. Report back please.

Or that’s how I understand, anyway.

Also, take note of the instructions, should you need to undo it. Or something.

3 Likes
9

Ok so, on the first reply to original post i said that it started working out of nowhere again, however i still followed your instructions, because I suspected it would be unstable, as it has been for the past 3 months.
After following your instructions i rebooted and then no connection again. It kept trying to connect but failing each time. Then i changed it back to normal and still the same. By the time i’m writing this it seems to be back on it’s own. I feel like i have really tried everything and it’s getting really annoying not having a stable connection. I am now afraid that if i reboot it will disconnect again.

10

Which is a legitimate fear.

Let me ask you this, before giving my opinion: do you know if this happens in a live environment?

11

To be honest, I haven’t tried that.
But i remember when i was on windows with the same Eth cable there was no problems. I was on Arch linux(KDE) before manjaro aswell and the same problem happened there. Before that i was on Manjaro gnome and no problems. To me it seems to be something about kde? I’m probably very wrong here, in other DE’s this doesn’t happen. I don’t see myself moving to another DE, since i’ve fallen in love with kde.

12

Heh, well, KDE is worth it.

Try it in a live environment, if it still happens there, see if you can try with an earlier version, or a Gnome or Xfce edition. Might help narrowing the down problem.

1 Like
13

I have reinstalled so many times im honestly tired haha.
I also have so much work on this computer that especially now i cant afford a reinstall.
Will see in the future.

14

I honestly understand.

I didn’t mean for you to reinstall, just test in the live environments. From a working one, maybe it’s possible to find out which driver it uses…or something like that.

:man_shrugging:

15

I actually do have a manjaro KDE lying around!
I will test that later and come back to you.

1 Like
16

Also, see you use kernel 5.15:

Have you tried with a different version? Preferably 5.4 or 5.10? Seeing as they are the current LTS versions?

Also, just for giggles, it might be worth trying 5.16 or 5.17.

17

If you dual boot to Windows, a simple boot to Windows may fix random ethernet issue with this chip.

You can also shutdown the computer, and the modem/router for a few minutes, and restart them after everything has been shutdown.

Also if you’re using BPL plugs (Brodband over Power Line) make sure there is no energy saving feature enabled in their firmware as it can also create issues. I had a pair of adapters that were shutting themselves down if no network activity was detected and it was messing things up making the reconnection impossible without trying many random things.

PS: live environment will use the 8169 driver, apparently he installed the 8168 driver from Manjaro Settings → Hardware.

//EDIT: also your BIOS is outdated, may be worth updating it, if you have a live USB on hand to reinstall GRUB afterwards from live environment, because 99% sure you will not be able to boot after updating the BIOS, reinstalling GRUB from live environment is as simple as (text behind # are comments, not actual commands):

# we chroot
manjaro-chroot -a

# we reinstal  GRUB efi
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck
# or GRUB mbr where /dev/sdy is the target
# grub-install --force --target=i386-pc --recheck --boot-directory=/boot /dev/sdy

# we update GRUB
update-grub

# we exit chroot to unmount the system
exit

# we reboot
reboot
18

One of my laptops uses the same ether chip - and for unkown reasons the functionality is a hit and miss.

As I use the device to test run and install Manjaro ISO - I have experienced first hand how wacky that chip is - most likely it is kernel module regression.

I have no idea what causes it but it must be the built-in kernel module r8169 - because when I have this bug - installing the $KERNEL-r8618 get’s the chip back online.

1 Like
19

I have experienced lot of weirdness too especially the past years, but now I have a stable setup, after reconfiguring my BPL adapters, using 8168 driver, and probably doing something I forgot since then.

//EDIT: a common issue and fix I had was no network connection after a reboot → reboot = same thing → reboot = same thing → reboot to windows = network working on windows → reboot on Manjaro = network working on Manjaro.
I could also trigger the issue by rebooting to live USB, then to Manjaro where I would have then no network, and I had to try various things to get it working eventually, like removing the 8168 driver, and rebooting (or not sometime I would have network popping up on itself after that).
I think this Realtek chip on Gigabyte motherboard is not really robust on Linux.

1 Like
20

I have the pretty much the same motherboard and have the Realtek RTL8111/8168/8411 as well.I haven’t had any network issues but I have Fedora 35 installed.I just downloaded the latest Manjaro KDE minimal iso and booted to see if it had any issues and the network is working fine.I went into the bios settings and the IOMMU is set to auto so maybe that has something to do with it.Also the bios ver is 01/29/19.On this computer I have the same Realtek RTL8111/8168/8411 and it’s running Manjaro KDE unstable and also has never had any issues.You might check the power settings or see if you can set a static address to see if that solves the issue.Also check the connections and the eth cable to the router or modem.