Updating brakes internet connection

Garuda Mokka

When i update with pacman or garuda-update the internet connection brakes for the whole PC, for example: when I try to update the connection brakes on Garuda and the update stops and won’t come back, then I reboot to my Windows 11 on the same PC and the problem is still there. Then I reboot the router and the internet is back.

On the first boot of Garuda, always, I can’t update - the update doesn’t start. Then I reboot and it works. But that was in the past. Now no matter how much I reboot the update won’t finish.

I have this problem for atlest a month.

Hi there, welcome to the forum.
Please post your garuda-inxi as requested by the template.

LAN or WLAN?

Error messages and/or logs?

It’s not a good idea to ignore a problem forever instead of fixing it. If issues occur that you cannot resolve yourself within a short time, then it makes sense to open a topic promptly. :wink:

3 Likes

Sorry, I was in rush and didn’t read.

System:
  Kernel: 6.14.4-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=f983a1d7-c333-4083-84d8-5e3a9914bbbd rw rootflags=subvol=@
    vt.default_red=30,243,166,249,137,245,148,186,88,243,166,249,137,245,148,166
    vt.default_grn=30,139,227,226,180,194,226,194,91,139,227,226,180,194,226,173
    vt.default_blu=46,168,161,175,250,231,213,222,112,168,161,175,250,231,213,200
    quiet resume=UUID=3ba9f6bb-0233-435c-ba3b-278098810b10 loglevel=3 ibt=off
  Desktop: KDE Plasma v: 6.3.4 tk: Qt v: N/A info: frameworks v: 6.13.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
  Type: Desktop Mobo: Gigabyte model: B550 AORUS ELITE V2 v: x.x
    serial: <superuser required> uuid: <superuser required> UEFI: American
    Megatrends LLC. v: FF date: 03/22/2024
CPU:
  Info: model: AMD Ryzen 7 5700X bits: 64 type: MT MCP arch: Zen 3+ gen: 3
    level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
    model-id: 0x21 (33) stepping: 2 microcode: 0xA201210
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
    smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB
    desc: 8x512 KiB L3: 32 MiB desc: 1x32 MiB
  Speed (MHz): avg: 3368 min/max: 550/3401 boost: enabled scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 3368 2: 3368 3: 3368
    4: 3368 5: 3368 6: 3368 7: 3368 8: 3368 9: 3368 10: 3368 11: 3368 12: 3368
    13: 3368 14: 3368 15: 3368 16: 3368 bogomips: 108599
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
  Vulnerabilities: <filter>
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 22 [Radeon RX 6700/6700
    XT/6750 XT / 6800M/6850M XT] vendor: XFX driver: amdgpu v: kernel
    arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie:
    gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-3,HDMI-A-1
    empty: DP-1,DP-2,Writeback-1 bus-ID: 07:00.0 chip-ID: 1002:73df
    class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
    compositor: kwin_wayland driver: X: loaded: amdgpu
    unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
    gpu: amdgpu d-rect: 3840x1080 display-ID: 0
  Monitor-1: DP-3 pos: primary,left model: ASUS VA27EHE serial: <filter>
    built: 2020 res: mode: 1920x1080 hz: 75 scale: 100% (1) dpi: 82 gamma: 1.2
    size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  Monitor-2: HDMI-A-1 pos: right model: LED serial: <filter> built: 2021
    res: mode: 1920x1080 hz: 75 scale: 100% (1) dpi: 94 gamma: 1.2
    size: 527x296mm (20.75x11.65") diag: 605mm (23.8") ratio: 15:9 modes:
    max: 1920x1080 min: 720x400
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
    wayland: drv: radeonsi x11: drv: radeonsi
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.0.4-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6700 (radeonsi navi22
    LLVM 19.1.7 DRM 3.61 6.14.4-zen1-1-zen) device-ID: 1002:73df
    memory: 9.77 GiB unified: no display-ID: :1.0
  API: Vulkan v: 1.4.309 layers: 9 device: 0 type: discrete-gpu name: AMD
    Radeon RX 6700 (RADV NAVI22) driver: mesa radv v: 25.0.4-arch1.1
    device-ID: 1002:73df surfaces: xcb,xlib,wayland device: 1 type: cpu
    name: llvmpipe (LLVM 19.1.7 256 bits) driver: mesa llvmpipe
    v: 25.0.4-arch1.1 (LLVM 19.1.7) device-ID: 10005:0000
    surfaces: xcb,xlib,wayland
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 21/23 HDMI/DP Audio
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 07:00.1 chip-ID: 1002:ab28 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
    vendor: Gigabyte driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
    lanes: 16 bus-ID: 09:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: HP HyperX SoloCast driver: hid-generic,snd-usb-audio,usbhid
    type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-1:2
    chip-ID: 03f0:078b class-ID: 0300
  API: ALSA v: k6.14.4-zen1-1-zen status: kernel-api tools: N/A
  Server-1: PipeWire v: 1.4.2 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: f000 bus-ID: 04:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: eno1 state: up speed: 100 Mbps duplex: full mac: <filter>
  IF-ID-1: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
  Info: services: NetworkManager, smbd, systemd-timesyncd
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
    v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-2:3
    chip-ID: 0a12:0001 class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.0
    lmp-v: 6 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
  Local Storage: total: 2.47 TiB used: 191.18 GiB (7.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SNV3S1000G
    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: P3BR0A23 temp: 44.9 C
    scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37240G
    size: 223.57 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: J4.3 scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 vendor: Kingston model: SA400S37480G
    size: 447.13 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: K1B3 scheme: GPT
  ID-4: /dev/sdc maj-min: 8:32 vendor: Toshiba model: MQ04ABF100
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B type: USB
    rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: HDD rpm: 5400
    serial: <filter> fw-rev: JU00 scheme: MBR
Partition:
  ID-1: / raw-size: 914.13 GiB size: 914.13 GiB (100.00%)
    used: 191.18 GiB (20.9%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 612 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 914.13 GiB size: 914.13 GiB (100.00%)
    used: 191.18 GiB (20.9%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-4: /var/log raw-size: 914.13 GiB size: 914.13 GiB (100.00%)
    used: 191.18 GiB (20.9%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 914.13 GiB size: 914.13 GiB (100.00%)
    used: 191.18 GiB (20.9%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: partition size: 17.09 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
  ID-2: swap-2 type: zram size: 15.53 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 16
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 33.9 C mobo: 28.0 C gpu: amdgpu temp: 43.0 C
    mem: 46.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
  Memory: total: 16 GiB available: 15.53 GiB used: 4.41 GiB (28.4%)
  Processes: 443 Power: uptime: 2m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.2 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Packages: pm: pacman pkgs: 1666 libs: 415 tools: octopi,paru,yay
    Compilers: gcc: 14.2.1 Shell: garuda-inxi default: Zsh v: 5.9
    running-in: kitty inxi: 3.3.38
Garuda (2.7.2-1):
  System install date:     2025-04-11
  Last full system update: 2025-04-30
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:            

LAN


This is now insane to me. When I tried updating now, it updated normal. I have like 15 to 20 seconds kernel load time.

In Rani i got this. This appeared also the first the issues came up. I have never seen whit pacdiff. I am not sure what I did the last time there. I am not very familiar with this part of Arch, but nothing ever broke on Arch for me before (I have been using it for 1 year maybe).

Just in case, have you already tried using a different cable?

I don’t think this is related to your issue, but consider updating your BIOS.

It is explained here:

Basically, you have to carefully merge the updates in the new configuration files into your current files, avoiding to simply overwrite your files, otherwise you’d loose your configurations.
Anyway, for the mirrorlist, this merge is not so important, because the mirrors are selected automatically during garuda-update by rate-mirrors, so we don’t select them manually.

3 Likes

I didn’t, will try

Okay

I assume your issue is with Ethernet, as there is no WiFi adapter in your inxi output. 95% of Ethernet issues are related to cabling. I would highly suggest replacing your cable with a new high grade cat6e cable, (cat7e would be preferable).

You are currently using the r8169 kernel module as a driver for your Ethernet adapter. A better choice would be to install the following driver from the AUR, (or the Chaotic Aur, if available there).

Install:

Other things to try:

Test an alternate kernel.

Test out alternate DNS servers.

Assign your computer a fixed IP address through your router. Usually you can do this easily in your router’s config using the MAC Address association feature. Be sure you set different static IP address’ for your Linux and Windows installations to avoid conflicts.

Another, one of the problems of running Linux concurrently with Windows, is that Windows often causes conflicts with Linux at the hardware level. Be sure fast boot/fast startup is disabled in Windows and in your bios. Ensure that any power saving options for your Ethernet driver in Windows have been disabled in the advanced driver properties in the Windows Control Panel. These type of conflicts often occur when Windows is used on the same computer as Linux. That is one of the reasons we highly discourage dual booting with the disease carrier Windows.

Another method to fix Windows conflicts when it arises is to fully purge all power from your motherboard. To do this, shut down your computer completely, then unplug all power sources from your computer. Allow the computer to sit a few minutes with no power, then press and hold down your computer’s power button for 20 secs. This should drain all residual power from your mobo. This method often helps when Windows is interfering with network components when booting Linux.

There a lot of other suggestion I could give but that’s enough for you to work through for now. Search the forum or Internet for any terms you are not familiar with, and do yourself a favor and drop Windows like a hot potato.

6 Likes

Sorry for responding late and thank you, I can’t assign static Ip trought the router but i have done it with Network Manager. I will try the other thing you mentioned. I have Windows on a separete drive, but i must use it for University.