Ethernet connection missing with r8169

Support Network
1

After latest system update (earlier this week), I’m experiencing weird problems with ethernet connection. After reboot the network interface remains down. To get internet connection I need to:

sudo rmmod r8169 
sudo modprobe r8169 
sudo systemctl start NetworkManager

So far I can’t find what causes this behaviour. There is no blacklistings (in /etc/modprobe.d/) , no alternative drivers (r8168) installed. Switching between different kernels doesn’t help either. Before update the system worked fine.

inxi -zv8 gives following results;

after reboot:

Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Micro-Star MSI X570-A PRO driver: r8169 v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 27:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: enp39s0 state: down mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
WAN IP: No WAN IP found. Connected to web? SSL issues? Try enabling dig

After reloading kernel module:

Network: Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI X570-A PRO driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 27:00.0 chip-ID: 10ec:8168 class-ID: 0200 
IF: enp39s0 state: up speed: 1000 Mbps duplex: full mac:  IP v4:  type: dynamic noprefixroute scope: global broadcast:  IP v6:  type: noprefixroute scope: link IF-ID-1: br-59c6e7f6c861 state: down mac:  IP v4:  scope: global broadcast:  IF-ID-2: docker0 state: down mac:  IP v4:  scope: global broadcast:  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant WAN IP:

Any ideas what to do?

Mod edit: Members are expected to format any **code** or **command output**, according to forum guidelines. This has been done for you in this instance. No charge.

Please see below :point_down: for helpful instructions.

[Mini-HowTo] Present code or command output

Note: Grave accent (or, backtick) characters are used. :eyes:

For inline code or to show a single command:

  • please follow this simple example: code here.

For multi-line command output:

  • place text beween two rows of three (```) backtick characters to form a scrollable text box, or …
  • use the </> button in the Compose window to achieve the same result.

The empty row between these rows of backtick characters is where to paste any multi-line command output (such as inxi).

An example of a pre-formatted text enclosure:

What is a Quark?

A. In Physics, an elementary particle and fundamental constituent of matter. 
B. A character from the Star Trek: "Deep Space Nine" television series.
C. A soft, creamy, usually unsalted cheese traditional to central Europe.
2

If you install r8168 driver with Manjaro Hardware Detection:

sudo mhwd -i pci network-r8168

or Manjaro Settings Manager > Hardware Configuration

mhwd-r8168
mhwd-r8168684×472 45.1 KB

it should install kernel specific drivers, kernel headers and blacklist the r8169 driver

1 Like
3

Yes, thanks. I did that as well (find this also somewhere in this forum) and the result was that r8169 was removed and r8168 installed, but I still didn’t had ethernet connection :frowning:

4

You didn’t include ALL the details of inxi -zv8, this is important for troubleshooting a problem.

Is your machine a laptop? And does it have a BIOS setting and/or a quick toggle similar to aeroplane mode? It could be that your BIOS is restricting the device from being enabled by default.

1 Like
5

Here is full inxi -zv8 output directly after reboot. Hope, it helps to resolve the mystery

❯ sudo inxi -zv8

System:
  Kernel: 7.0.3-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-7.0-x86_64
    root=UUID=1bfb8850-1040-491f-9b86-f5deccb4ed3d rw quiet splash apparmor=1
    security=apparmor udev.log_priority=3 usbcore.autosuspend=-1
    pcie_aspm=off
  Desktop: GNOME v: 50.1 tk: GTK v: 3.24.52 wm: gnome-shell
    tools: gsd-screensaver-proxy dm: GDM v: 50.0 Distro: Manjaro
    base: Arch Linux
Machine:
  Type: Desktop Mobo: Micro-Star model: X570-A PRO (MS-7C37) v: 3.0
    serial: <filter> uuid: c738c9ee-8cae-6815-a860-00d861d0b9b0 Firmware: UEFI
    vendor: American Megatrends LLC. v: H.O0 date: 07/15/2024
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 32 GiB available: 31.26 GiB used: 1.95 GiB (6.2%)
  Array-1: capacity: 128 GiB slots: 4 modules: 1 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: Channel-A DIMM 0 type: no module installed
  Device-2: Channel-A DIMM 1 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 32 GiB speed: 3600 MT/s volts: curr: 1.2 min: 1.2
    max: 1.2 width (bits): data: 64 total: 64 manufacturer: N/A
    part-no: 3600 C18 Series serial: <filter>
  Device-3: Channel-B DIMM 0 type: no module installed
  Device-4: Channel-B DIMM 1 type: no module installed
PCI Slots:
  Slot: 0 type: PCIe status: in use info: J6B2 length: long volts: 3.3
    bus-ID: 00:01.0
  Slot: 1 type: PCIe status: in use info: J6B1 length: short volts: 3.3
    bus-ID: 00:1c.3
  Slot: 2 type: PCIe status: in use info: J6D1 length: short volts: 3.3
    bus-ID: 00:1c.4
  Slot: 3 type: PCIe status: in use info: J7B1 length: short volts: 3.3
    bus-ID: 00:1c.5
  Slot: 4 type: PCIe status: in use info: J8B4 length: short volts: 3.3
    bus-ID: 00:1c.6
  Slot: 5 type: PCIe status: in use info: J8D1 length: short volts: 3.3
    bus-ID: 00:1c.7
  Slot: 6 type: PCI status: in use info: J8B3 length: short volts: 3.3
    bus-ID: 00:1e.0
  Slot: 12 type: PCIe status: in use info: J10 length: short volts: 3.3
    bus-ID: 00:03.1 children: 1: 2d:00.0 class-ID: 0604 type: bridge children:
    1: 2e:00.0 class-ID: 0604 type: bridge children: 1: 2f:00.0 class-ID: 0300
    type: display 2: 2f:00.1 class-ID: 0403 type: audio
  Slot: 13 type: PCIe status: available info: J3600 length: short volts: 3.3
    bus-ID: 00:1f.7
  Slot: 2 type: PCIe status: available info: J3708 length: short volts: 3.3
    bus-ID: 00:1f.7
  Slot: 3 type: PCIe status: available info: J3702 length: short volts: 3.3
    bus-ID: 00:1f.7
  Slot: 4 type: PCIe status: in use info: J3703 length: short volts: 3.3
    bus-ID: 21:04.0
  Slot: 5 type: PCIe status: in use info: J3701, M.2 length: short
    volts: 3.3 bus-ID: 21:05.0
  Slot: 14 type: PCIe status: in use info: M.2 length: short volts: 3.3
    bus-ID: 00:01.1 children: 1: 01:00.0 class-ID: 0108 type: mass-storage
CPU:
  Info: model: AMD Ryzen 5 3600 socket: AM4 bits: 64 type: MT MCP arch: Zen 2
    gen: 2 level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
    family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701034
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 6 threads: 12 tpc: 2
    smt: enabled cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB
    desc: 6x512 KiB L3: 32 MiB desc: 2x16 MiB
  Speed (MHz): avg: 3599 min/max: 558/4208 boost: enabled
    base/boost: 3600/4200 scaling: driver: amd-pstate-epp governor: performance
    volts: 1.1 V ext-clock: 100 MHz cores: 1: 3599 2: 3599 3: 3599 4: 3599
    5: 3599 6: 3599 7: 3599 8: 3599 9: 3599 10: 3599 11: 3599 12: 3599
    bogomips: 86399
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
    constant_tsc cpb cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
    cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists extapic extd_apicid
    f16c flushbyasid fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb ibs
    irperf lahf_lm lbrv lm mba mca mce misalignsse mmx mmxext monitor movbe
    msr mtrr mwaitx nonstop_tsc nopl npt nrip_save nx osvw overflow_recov pae
    pat pausefilter pclmulqdq pdpe1gb perfctr_core perfctr_llc perfctr_nb
    pfthreshold pge pni popcnt pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a
    rdtscp rep_good sep sev sev_es sha_ni skinit smap smca smep ssbd sse sse2
    sse4_1 sse4_2 sse4a ssse3 stibp succor svm svm_lock syscall tce topoext
    tsc tsc_scale umip v_spec_ctrl v_vmsave_vmload vgif vmcb_clean vme
    vmmcall wbnoinvd wdt x2apic xgetbv1 xsave xsavec xsaveerptr xsaveopt
    xtopology
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: old_microcode status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP
    protection
  Type: spec_rstack_overflow mitigation: Safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; STIBP:
    always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 33 [Radeon RX 7600/7600
    XT/7600M XT/7600S/7700S / PRO W7600] vendor: Gigabyte driver: amdgpu
    v: kernel arch: RDNA-3 code: Navi-3x process: TSMC n6 (6nm) built: 2023+
    pcie: gen: 4 speed: 16 GT/s lanes: 8 ports: active: DP-2 empty: DP-1,
    HDMI-A-1, HDMI-A-2, Writeback-1 bus-ID: 2f:00.0 chip-ID: 1002:7480
    class-ID: 0300
  Display: unspecified server: X.org v: 1.21.1.22 with: Xwayland v: 24.1.11
    compositor: gnome-shell driver: X: loaded: N/A failed: nvidia gpu: amdgpu
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-size: <missing: xdpyinfo>
  Monitor-1: DP-2 model: Dell AW2724DM serial: <filter> built: 2023 res:
    mode: 2560x1440 hz: 60 scale: 100% (1) dpi: 108 gamma: 1.2 chroma: red:
    x: 0.686 y: 0.310 green: x: 0.267 y: 0.663 blue: x: 0.145 y: 0.047 white:
    x: 0.314 y: 0.329 size: 600x340mm (23.62x13.39") diag: 685mm (27")
    ratio: 16:9 modes: 2560x1440, 1920x1080, 1600x900, 1280x1024, 1152x864,
    1280x720, 1024x768, 800x600, 720x576, 720x480, 640x480, 720x400
  EDID-Warnings: 1: parse_edid: unknown tag 112
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: radeonsi surfaceless: drv: radeonsi x11:
    drv: radeonsi inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 26.0.6-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 7600 XT (radeonsi
    navi33 ACO DRM 3.64 7.0.3-1-MANJARO) device-ID: 1002:7480
    memory: 15.62 GiB unified: no
  API: Vulkan v: 1.4.341 layers: 6 device: 0 type: discrete-gpu name: AMD
    Radeon RX 7600 XT (RADV NAVI33) driver: mesa radv v: 26.0.6-arch1.1
    device-ID: 1002:7480 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo gpu: lact
    x11: xprop,xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 31 HDMI/DP Audio
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 8
    bus-ID: 2f:00.1 chip-ID: 1002:ab30 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
    vendor: Micro-Star MSI X570-A PRO driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 31:00.4 chip-ID: 1022:1487
    class-ID: 0403
  API: ALSA v: k7.0.3-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 1.6.4 status: n/a (root, process) with:
    1: pipewire-pulse status: active 2: wireplumber status: active
    3: pipewire-alsa type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Micro-Star MSI X570-A PRO driver: r8169 v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 27:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: enp39s0 state: down mac: <filter>
  IF-ID-1: br-59c6e7f6c861 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IF-ID-2: docker0 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: No WAN IP found. Connected to web? SSL issues? Try enabling dig
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 11.08 TiB used: 4.77 TiB (43.1%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:5 vendor: Gigabyte
    model: GP-GSM2NE3128GNTD size: 119.24 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: EDFM00.2 temp: 31.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Crucial model: CT1000T500SSD8
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: P8CR002 temp: 45.9 C
    scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Patriot model: P210 2048GB
    size: 1.86 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 404 scheme: GPT
  ID-4: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 QVO 4TB
    size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 2B6Q scheme: GPT
  ID-5: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST31000524AS
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: JC4B scheme: MBR
  ID-6: /dev/sdd maj-min: 8:48 vendor: Seagate model: ST4000DM004-2CV104
    size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 5425 serial: <filter> fw-rev: 0001
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 195.31 GiB size: 191.19 GiB (97.89%)
    used: 95.24 GiB (49.8%) fs: ext4 block-size: 4096 B dev: /dev/nvme1n1p2
    maj-min: 259:2 label: N/A uuid: 1bfb8850-1040-491f-9b86-f5deccb4ed3d
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 328 KiB (0.1%) fs: vfat block-size: 512 B dev: /dev/nvme1n1p1
    maj-min: 259:1 label: N/A uuid: 8BEE-43DC
  ID-3: /home raw-size: 1.86 TiB size: 1.83 TiB (98.38%)
    used: 855.4 GiB (45.6%) fs: ext4 block-size: 4096 B dev: /dev/sda1
    maj-min: 8:1 label: PatriotSSD-2TB
    uuid: e097afbc-f024-4ef0-9d02-e880e27e59a0
  ID-4: /home/fotod raw-size: 3.64 TiB size: 3.58 TiB (98.40%)
    used: 3.32 TiB (92.6%) fs: ext4 block-size: 4096 B dev: /dev/sdb1
    maj-min: 8:17 label: Samsung4TbSSD
    uuid: c8aac3da-7091-49ef-828b-6b53f1c6c23b
  ID-5: /home/<filter>/filmid raw-size: 3.64 TiB size: 3.58 TiB (98.40%)
    used: 214.35 GiB (5.8%) fs: ext4 block-size: 4096 B dev: /dev/sdd
    maj-min: 8:48 label: N/A uuid: 5fe4cc92-11a8-444b-95e8-f0c0ead20d91
  ID-6: /home/ketas raw-size: 931.51 GiB size: 915.82 GiB (98.32%)
    used: 166.14 GiB (18.1%) fs: ext4 block-size: 4096 B dev: /dev/sdc1
    maj-min: 8:33 label: 2ketas uuid: 2a52ce55-25a1-41b7-85ca-397f4b74fc1b
  ID-7: /home/m2kiire_suur raw-size: 716.38 GiB size: 704.06 GiB (98.28%)
    used: 94.28 GiB (13.4%) fs: ext4 block-size: 4096 B dev: /dev/nvme1n1p4
    maj-min: 259:4 label: N/A uuid: 009ec2aa-0571-40d4-a524-dade2792f866
  ID-8: /home/mangud raw-size: 119.24 GiB size: 116.81 GiB (97.96%)
    used: 62.41 GiB (53.4%) fs: ext4 block-size: 4096 B dev: /dev/nvme0n1p1
    maj-min: 259:6 label: Gigabyte128
    uuid: 2a636898-ef69-4296-88db-4bf69c238f48
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 19.53 GiB used: 0 KiB (0.0%)
    priority: -1 dev: /dev/nvme1n1p3 maj-min: 259:3 label: N/A
    uuid: 567ce54a-5d9b-48e9-95f0-7c1a486da5b1
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 6 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-1:2 info: Samsung SCX-4600 Series type: printer driver: usblp
    interfaces: 2 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0
    power: 2mA chip-ID: 04e8:3433 class-ID: 0701 serial: <filter>
  Device-2: 1-2:3 info: SteelSeries ApS Rival 5 type: HID,mouse
    driver: hid-generic,usbhid interfaces: 4 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 200mA chip-ID: 1038:183c class-ID: 0300
  Device-3: 1-5:4 info: ROCCAT Vulcan Pro type: keyboard,HID
    driver: hid-generic,usbhid interfaces: 4 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 1e7d:30f7 class-ID: 0300
  Hub-2: 2-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 6 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 3-1:2 info: Logitech Unifying Receiver type: keyboard,mouse,HID
    driver: logitech-djreceiver,usbhid interfaces: 3 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 98mA
    chip-ID: 046d:c52b class-ID: 0300
  Device-2: 3-4:3 info: Google Nexus/Pixel Device (MTP) type: still imaging
    driver: usbfs interfaces: 1 rev: 2.1 speed: 480 Mb/s (57.2 MiB/s) lanes: 1
    mode: 2.0 power: 500mA chip-ID: 18d1:4ee1 class-ID: 0601 serial: <filter>
  Device-3: 3-5:4 info: Micro Star MYSTIC LIGHT type: HID
    driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 1462:7c37 class-ID: 0300
    serial: <filter>
  Hub-4: 3-6:5 info: Genesys Logic Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0608 class-ID: 0900
  Hub-5: 4-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-6: 5-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-7: 6-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 56.2 C mobo: N/A gpu: amdgpu temp: 50.0 C
    mem: 42.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Repos:
  Packages: 2743 pm: pacman pkgs: 2699 libs: 580 tools: gnome-software,pamac
    pm: flatpak pkgs: 44
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://mirror.nyist.edu.cn/manjaro/stable/$repo/$arch
    2: https://mirror.xenyth.net/manjaro/stable/$repo/$arch
    3: https://gsl-syd.mm.fcix.net/manjaro/stable/$repo/$arch
    4: https://mirror.easyname.at/manjaro/stable/$repo/$arch
    5: https://fosszone.csd.auth.gr/manjaro/stable/$repo/$arch
    6: https://mirror.alpix.eu/manjaro/stable/$repo/$arch
    7: https://mirror.xeonbd.com/manjaro/stable/$repo/$arch
    8: https://mirror.init7.net/manjaro/stable/$repo/$arch
    9: https://manjaro.repo.cure.edu.uy/stable/$repo/$arch
    10: https://mirror.dkm.cz/manjaro/stable/$repo/$arch
    11: https://repo.ialab.dsu.edu/manjaro/stable/$repo/$arch
    12: https://ftp.free.org/mirrors/repo.manjaro.org/repos/stable/$repo/$arch
    13: https://manjaro.mirror.liquidtelecom.com/stable/$repo/$arch
    14: https://ct.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
    15: https://mirror.alwyzon.net/manjaro/stable/$repo/$arch
    16: https://mirrors.cicku.me/manjaro/stable/$repo/$arch
    17: https://cofractal-ewr.mm.fcix.net/manjaro/stable/$repo/$arch
    18: https://mirror.it4i.cz/manjaro/stable/$repo/$arch
    19: https://mirror.yandex.ru/mirrors/manjaro/stable/$repo/$arch
    20: https://mirrors.manjaro.org/repo/stable/$repo/$arch
    21: https://mirrors.up.pt/pub/manjaro/stable/$repo/$arch
    22: https://ftp.nluug.nl/pub/os/Linux/distr/manjaro/stable/$repo/$arch
    23: https://mirror.csclub.uwaterloo.ca/manjaro/stable/$repo/$arch
    24: https://mirrors.ocf.berkeley.edu/manjaro/stable/$repo/$arch
    25: https://mirrors.gigenet.com/manjaro/stable/$repo/$arch
    26: https://manjaro.ipacct.com/manjaro/stable/$repo/$arch
    27: https://volico.mm.fcix.net/manjaro/stable/$repo/$arch
    28: http://ossmirror.mycloud.services/os/linux/manjaro/stable/$repo/$arch
    29: https://ftp.psnc.pl/linux/manjaro/stable/$repo/$arch
    30: https://mirrors.ft.uam.es/manjaro/stable/$repo/$arch
    31: https://manjaro.mirrors.uk2.net/stable/$repo/$arch
    32: https://ohioix.mm.fcix.net/manjaro/stable/$repo/$arch
    33: https://ftp.snt.utwente.nl/pub/linux/manjaro/stable/$repo/$arch
    34: https://manjaro.ynh.ovh/stable/$repo/$arch
    35: https://linorg.usp.br/manjaro/stable/$repo/$arch
    36: https://mirrors.tuna.tsinghua.edu.cn/manjaro/stable/$repo/$arch
    37: https://mirrors2.manjaro.org/stable/$repo/$arch
    38: https://nocix.mm.fcix.net/manjaro/stable/$repo/$arch
    39: https://distrohub.kyiv.ua/manjaro/stable/$repo/$arch
    40: https://mirror.2degrees.nz/manjaro/stable/$repo/$arch
    41: https://mirrors.ucr.ac.cr/manjaro/stable/$repo/$arch
    42: https://ftp.belnet.be/mirrors/manjaro/repos/stable/$repo/$arch
    43: https://manjaro.mirror-services.net/pub/stable/$repo/$arch
    44: https://mirror.math.princeton.edu/pub/manjaro/stable/$repo/$arch
    45: https://mirrors.dotsrc.org/manjaro/stable/$repo/$arch
    46: https://mirror.truenetwork.ru/manjaro/stable/$repo/$arch
    47: https://kartolo.sby.datautama.net.id/manjaro/stable/$repo/$arch
    48: https://ask4.mm.fcix.net/manjaro/stable/$repo/$arch
    49: https://mirror.23m.com/manjaro/stable/$repo/$arch
    50: https://ziply.mm.fcix.net/manjaro/stable/$repo/$arch
    51: https://ftp.lysator.liu.se/pub/manjaro/stable/$repo/$arch
    52: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
    53: https://manjaro.mirror.garr.it/manjaro/stable/$repo/$arch
    54: https://mirrors.xtom.jp/manjaro/stable/$repo/$arch
    55: https://irltoolkit.mm.fcix.net/manjaro/stable/$repo/$arch
    56: https://manjaro.mirror.wearetriple.com/stable/$repo/$arch
    57: https://nnenix.mm.fcix.net/manjaro/stable/$repo/$arch
    58: https://opencolo.mm.fcix.net/manjaro/stable/$repo/$arch
    59: https://mirrors.atlas.net.co/manjaro/stable/$repo/$arch
    60: https://mirrors.sjtug.sjtu.edu.cn/manjaro/stable/$repo/$arch
    61: https://mirror.dimensiondata.com/mirrors/manjaro.org/stable/$repo/$arch
    62: https://mirror.datacenter.by/pub/mirrors/manjaro/stable/$repo/$arch
    63: https://mirrors.eric.ovh/manjaro/stable/$repo/$arch
    64: https://mirror.kamtv.ru/manjaro/stable/$repo/$arch
    65: https://muug.ca/mirror/manjaro/stable/$repo/$arch
    66: https://mirrors.sonic.net/manjaro/stable/$repo/$arch
    67: https://ba.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
    68: https://ftp.yz.yamagata-u.ac.jp/pub/linux/manjaro/stable/$repo/$arch
    69: https://mirror.fcix.net/manjaro/stable/$repo/$arch
    70: https://mirror.raiolanetworks.com/manjaro/stable/$repo/$arch
    71: https://ftp.tu-chemnitz.de/pub/linux/manjaro/stable/$repo/$arch
    72: https://mirror.netcologne.de/manjaro/stable/$repo/$arch
    73: https://mirror.futureweb.be/manjaro/stable/$repo/$arch
    74: https://coresite.mm.fcix.net/manjaro/stable/$repo/$arch
    75: https://mirror.bakertelekom.fr/manjaro/stable/$repo/$arch
    76: https://mirror.vinehost.net/manjaro/stable/$repo/$arch
    77: https://manjaro.c3sl.ufpr.br/stable/$repo/$arch
    78: https://codingflyboy.mm.fcix.net/manjaro/stable/$repo/$arch
    79: https://ftp.caliu.cat/pub/distribucions/manjaro/stable/$repo/$arch
    80: https://mirror.freedif.org/Manjaro/stable/$repo/$arch
    81: https://ftp.halifax.rwth-aachen.de/manjaro/stable/$repo/$arch
    82: https://forksystems.mm.fcix.net/manjaro/stable/$repo/$arch
    83: https://mirror.dc.uz/manjaro/stable/$repo/$arch
    84: https://mirror.telepoint.bg/manjaro/stable/$repo/$arch
    85: https://southfront.mm.fcix.net/manjaro/stable/$repo/$arch
    86: https://mirror.phoepsilonix.love/manjaro/stable/$repo/$arch
    87: https://www.mirrorservice.org/sites/repo.manjaro.org/repos/stable/$repo/$arch
    88: https://ftp.tsukuba.wide.ad.jp/Linux/manjaro/stable/$repo/$arch
    89: https://manjaro.grena.ge/stable/$repo/$arch
    90: https://ftpmirror1.infania.net/mirror/manjaro/stable/$repo/$arch
    91: https://mirror.bouwhuis.network/manjaro/stable/$repo/$arch
    92: http://ftp.uni-kl.de/pub/linux/manjaro/stable/$repo/$arch
    93: https://ftp.linux.org.tr/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 392
  1: cpu: 100% command: ps pid: 6087 mem: 4.25 MiB (0.0%)
  2: cpu: 17.5% command: fprintd pid: 6063 mem: 13.6 MiB (0.0%)
  3: cpu: 15.3% command: gnome-shell pid: 2912 mem: 287.6 MiB (0.8%)
  4: cpu: 11.4% command: localsearch-3 pid: 3273 mem: 48.7 MiB (0.1%)
  5: cpu: 11.1% command: ibus-extension-gtk3 pid: 3239 mem: 48.8 MiB (0.1%)
  Memory top: 5 of 392
  1: mem: 287.6 MiB (0.8%) command: gnome-shell pid: 2912 cpu: 15.3%
  2: mem: 92.7 MiB (0.2%) command: evolution-alarm-notify pid: 3272
    cpu: 1.1%
  3: mem: 91.5 MiB (0.2%) command: mutter-x11-frames pid: 4073 cpu: 0.9%
  4: mem: 80.7 MiB (0.2%) command: dockerd pid: 5709 cpu: 1.0%
  5: mem: 70.4 MiB (0.2%) command: rclone pid: 3179 cpu: 0.5%
Info:
  Processes: 392 Power: uptime: 1m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.44 GiB services: gsd-power,
    power-profiles-daemon, upowerd Init: systemd v: 260 default: graphical
    tool: systemctl
  Compilers: clang: 22.1.3 gcc: 15.2.1 Shell: Sudo (sudo) v: 1.9.17p2
    default: Bash v: 5.3.9 running-in: gnome-terminal inxi: 3.3.40
6

Does it work with a live .iso?
Are you connected via a router?
If you are connected via a router, have you ruled out router configuration issue (s)?
If you are using a router, can you successfully connect when plugged directly to the modem?
Does it work with a different kernel? Have you tried with a LTS kenel, e.g. 6.18.xx?

1 Like
7

You mean after booting there is no internet connection? Was removing and adding the kernel module the first thing you tried? What is the output of sudo systemctl status NetworkManager after booting when the network connection isn’t there.

Did you try to use ip to connect?

ip link show  # to determine the interface
sudo ip link set [interface] up

Any error output?

1 Like
9

@jrichard326
I haven’t tried to boot from live iso. Changing kernels doesn’t help, computer connected directly to modem. Updated motherboard BIOS and that didn’t help either.

@jofi
Here is the output of
sudo systemctl status NetworkManager

● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; p>
     Active: active (running) since Mon 2026-05-18 11:44:45 EEST; 1min 24s ago
 Invocation: 1a7089498d114f2ea2ed57b3a2c7226b
       Docs: man:NetworkManager(8)
   Main PID: 980 (NetworkManager)
      Tasks: 4 (limit: 38229)
     Memory: 19.1M (peak: 19.9M)
        CPU: 79ms
     CGroup: /system.slice/NetworkManager.service
             └─980 /usr/bin/NetworkManager --no-daemon

mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4440] d>
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4441] d>
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4441] d>
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4575] d>
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4576] d>
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4577] m>
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4578] d>
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4581] d>
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4582] d>
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4584] d>
lines 1-22/22 (END)...skipping...
● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; preset: disabled)
     Active: active (running) since Mon 2026-05-18 11:44:45 EEST; 1min 24s ago
 Invocation: 1a7089498d114f2ea2ed57b3a2c7226b
       Docs: man:NetworkManager(8)
   Main PID: 980 (NetworkManager)
      Tasks: 4 (limit: 38229)
     Memory: 19.1M (peak: 19.9M)
        CPU: 79ms
     CGroup: /system.slice/NetworkManager.service
             └─980 /usr/bin/NetworkManager --no-daemon

mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4440] device (br-59c6e7f6c861): state change: prepare -> config (reason 'none', managed-type: 'external')
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4441] device (br-59c6e7f6c861): state change: config -> ip-config (reason 'none', managed-type: 'external')
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4441] device (br-59c6e7f6c861): state change: ip-config -> ip-check (reason 'none', managed-type: 'external')
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4575] device (docker0): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4576] device (docker0): state change: secondaries -> activated (reason 'none', managed-type: 'external')
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4577] manager: NetworkManager state is now CONNECTED_LOCAL
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4578] device (docker0): Activation: successful, device activated.
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4581] device (br-59c6e7f6c861): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4582] device (br-59c6e7f6c861): state change: secondaries -> activated (reason 'none', managed-type: 'external')
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4584] device (br-59c6e7f6c861): Activation: successful, device activated.
~
~
lines 1-22/22 (END)
● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; preset: disabled)
     Active: active (running) since Mon 2026-05-18 11:44:45 EEST; 1min 24s ago
 Invocation: 1a7089498d114f2ea2ed57b3a2c7226b
       Docs: man:NetworkManager(8)
   Main PID: 980 (NetworkManager)
      Tasks: 4 (limit: 38229)
     Memory: 19.1M (peak: 19.9M)
        CPU: 79ms
     CGroup: /system.slice/NetworkManager.service
             └─980 /usr/bin/NetworkManager --no-daemon

mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4440] device (br-59c6e7f6c861): state change: prepare -> config (reason 'none', managed-type: 'external')
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4441] device (br-59c6e7f6c861): state change: config -> ip-config (reason 'none', managed-type: 'external')
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4441] device (br-59c6e7f6c861): state change: ip-config -> ip-check (reason 'none', managed-type: 'external')
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4575] device (docker0): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4576] device (docker0): state change: secondaries -> activated (reason 'none', managed-type: 'external')
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4577] manager: NetworkManager state is now CONNECTED_LOCAL
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4578] device (docker0): Activation: successful, device activated.
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4581] device (br-59c6e7f6c861): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4582] device (br-59c6e7f6c861): state change: secondaries -> activated (reason 'none', managed-type: 'external')
mai   18 11:45:46 heikki-nexus NetworkManager[980]: <info>  [1779093946.4584] device (br-59c6e7f6c861): Activation: successful, device activated.

Mod edit: Consecutive posts merged.

10

This shows it isn’t connected to the internet. There are missing dhcp logs and instead of enp39s0 its ID br-59c6e7f6c861 is used. Anyway, what happens if you do

sudo ip link set enp39s0 up

What’s the output of ip link show?

11

Sorry, forgot to add this part.

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: enp39s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:d8:61:d0:b9:b0 brd ff:ff:ff:ff:ff:ff
    altname enx00d861d0b9b0
❯ sudo ip link set enp39s0 up
[sudo] password for *****: 
❯ ping www.neti.ee
ping: www.neti.ee: Temporary failure in name resolution
12

You should do them in this order. You want to see if the link is up after you ask it to be up.

13

Here is the output.

sudo ip link set enp39s0 up
[sudo] password for heikki: 
❯ 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: enp39s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 00:d8:61:d0:b9:b0 brd ff:ff:ff:ff:ff:ff
    altname enx00d861d0b9b0

But I also found, that I don’t need to make three steps and I can skip restarting of NetworkManager. Just removing and reloading of the kernel module does the trick.

14

What could be the reason for this? I mean how this should have any effect? Or wasn’t the module loaded to begin with? What was the output of rmmod r8169?

If the interface was down before calling sudo ip link set enp39s0 up then it was set to “UP” successfully and it should be connected to the internet. So instead of touching the kernel module calling the command to connect should do (which makes more sense to me). Question would be still why the interface is “DOWN” after booting up.

1 Like
15

A common cause would be a race condition. :thinking:

16

r8168 driver can be installed using Manjaro Settings Manager - Hardware Configuration GUI or Manjaro HardWare Detection command:

sudo mhwd --install pci network-r8168

Install process also creates /etc/modprobe.d/ blacklist for the r8169 driver.
Reboot system to load drivers and blacklist

If the r8168 driver does not resolve ethernet connection issue it can be removed:

sudo mhwd --remove pci network-r8168
1 Like
17

Tried that once again. No internet with r8168 either.

18

But does the interface come up on boot?

Just to be sure, you are connected to an ethernet port and not something else?

1 Like
19

If the dirver module would be the problem there would be no internet but there is (although removing and adding the module doesn’t make sense to me). Let’s keep the working r8169. The module should be loaded on demand. So what is the output of rmmod r8169? Was it loaded at start-up? Also you didn’t verify whether sudo ip link set enp39s0 up worked. I presume it did (hence it wouldn’t be about the driver).

1 Like
20

I still would try with a live .iso, because so much has been altered during this process, it might be difficult to undo.

Does booting up as a different user make any difference?

I don’t think trying r8168 is the way to go, but… I see that there is kernel module software available. Have you tried installing linux70-r8168?

1 Like
21

There is a chance this is a bug, that may get fixed eventually.

If all you got to do is that, you could just automate it for the time being.

Over the years I’ve had to do workarounds just like this … or worse. :laughing:

Create the file:

/etc/systemd/system/reset-r8169.service

[Unit]
Description=Reset r8169
After=network.target NetworkManager.service
Wants=NetworkManager.service

[Service]
Type=oneshot
ExecStartPre=/usr/bin/sleep 0
ExecStart=/usr/bin/sh -c '/usr/bin/rmmod r8169 && /usr/bin/modprobe r8169'
ExecStartPost=/usr/bin/systemctl restart NetworkManager

[Install]
WantedBy=multi-user.target

Note: I put a sleep 0 in there, and you can probably remove that line entirely.

As this won’t start until the network is up, it should work, but you can put a delay in there if you need it.

2 Likes