Internet Connection down after first update

Issues & Assistance Networking Support
1

I installed the Mocca ISO, and in both the live mode and at the initial boot, it supported an internet connection.

I had my phone connected via USB tethering.
I updated, and once the update was done, I rebooted.

After the reboot, I wanted to do the pacdiff merge, since the welcome app suggested me to do it.

I tried, but I received no promised merge application. After I inputted my password, just nothing happened. So I opened the Terminal via the button on the top of Radi, and it said I had no internet. Low and behold, I had no active connection.

Checked the phone, all was fine. Added an external Wifi dongle, the network widget wouldn’t recognize it.

I restarted NetworkManager by hand, nothing.

OK, lets look into the pacman log. The entire /var/log is empty. What?

I have a perfectly running Garuda (Dragonite) running on my laptop, nothing like that happened.

(I was also not promted to merge some pacdiff there, but this shouldn’t matter)

Due to a mistake of myself, we have no snapshot anymore as I booted into the second oldest, to see if that is recent enough to re-establish the connection (there were three entries) and somehow came to the decision, to save that snapshot before making sure the internet is really back.

I forgot that this resets all the snapshots, as this is now the only remaining one (somehow weird decision to delete all other snapshots then, I could swear that wasn’t the case previously)

Let me upload the logs and inxi that I have, I used journalctl -b -r and garuda-inxi.

Sadly, there is no pacman log, as mentioned.

Edit by nepti:

System:
  Kernel: 6.14.3-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=0b421a7e-9fa7-4e60-ae14-db4cabee95a5 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 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 with: krunner vt: 1 dm: SDDM Distro: Garuda
    base: Arch Linux
Machine:
  Type: Desktop System: FUJITSU product: ESPRIMO Q556/2 v: N/A
    serial: <superuser required> Chassis: type: 3 serial: <superuser required>
  Mobo: FUJITSU model: D3403-U1 v: S26361-D3403-U1
    serial: <superuser required> uuid: <superuser required>
    UEFI-[Legacy]: FUJITSU // American Megatrends v: 5.0.0.12 R1.31.0 for
    D3403-U1x date: 08/29/2022
CPU:
  Info: model: Intel Core i5-6500T bits: 64 type: MCP arch: Skylake-S
    gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6
    model-id: 0x5E (94) stepping: 3 microcode: 0xF0
  Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 smt: <unsupported> cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
    L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 1200 min/max: 800/3100 scaling: driver: intel_pstate
    governor: powersave cores: 1: 1200 2: 1200 3: 1200 4: 1200 bogomips: 19999
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel HD Graphics 530 vendor: Fujitsu Solutions driver: i915
    v: kernel arch: Gen-9 process: Intel 14n built: 2015-16 ports: active: DP-1
    empty: DP-2,HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:1912
    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: modesetting
    alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: 0
  Monitor-1: DP-1 model: HP Z24i serial: <filter> built: 2015 res:
    mode: 1920x1200 hz: 60 scale: 100% (1) dpi: 94 gamma: 1.2
    size: 518x324mm (20.39x12.76") diag: 611mm (24.1") ratio: 16:10 modes:
    max: 1920x1200 min: 720x400
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
    drv: iris x11: drv: iris
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.0.4-arch1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 530 (SKL GT2)
    device-ID: 8086:1912 memory: 3.71 GiB unified: yes display-ID: :1.0
  API: Vulkan v: 1.4.309 layers: 5 device: 0 type: integrated-gpu name: Intel
    HD Graphics 530 (SKL GT2) driver: N/A device-ID: 8086:1912
    surfaces: xcb,xlib,wayland device: 1 type: cpu name: llvmpipe (LLVM
    19.1.7 256 bits) driver: N/A 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: Intel 100 Series/C230 Series Family HD Audio
    vendor: Fujitsu Solutions driver: snd_hda_intel v: kernel
    alternate: snd_soc_avs bus-ID: 00:1f.3 chip-ID: 8086:a170 class-ID: 0403
  API: ALSA v: k6.14.3-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 RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Fujitsu Solutions driver: r8169 v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 01:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: enp1s0 state: down mac: <filter>
  Info: services: NetworkManager,systemd-timesyncd
Drives:
  Local Storage: total: 119.24 GiB used: 10.82 GiB (9.1%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Fanxiang model: S101 128GB
    size: 119.24 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: D1.2 scheme: MBR
Partition:
  ID-1: / raw-size: 119.24 GiB size: 119.24 GiB (100.00%)
    used: 10.82 GiB (9.1%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
  ID-2: /home raw-size: 119.24 GiB size: 119.24 GiB (100.00%)
    used: 10.82 GiB (9.1%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
  ID-3: /var/log raw-size: 119.24 GiB size: 119.24 GiB (100.00%)
    used: 10.82 GiB (9.1%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
  ID-4: /var/tmp raw-size: 119.24 GiB size: 119.24 GiB (100.00%)
    used: 10.82 GiB (9.1%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 7.59 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 4
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 55.0 C pch: 62.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 8 GiB available: 7.59 GiB used: 1.78 GiB (23.5%)
  Processes: 232 Power: uptime: 2m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 3.03 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Packages: pm: pacman pkgs: 1231 libs: 357 tools: octopi,paru Compilers:
    gcc: 14.2.1 Shell: garuda-inxi default: fish v: 4.0.2 running-in: konsole
    inxi: 3.3.37
Garuda (2.7.2-1):
  System install date:     2025-04-21
  Last full system update: 2025-04-21
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       <superuser required>
  Failed units:
2

From the topic template:

  • After rebooting, post the FULL output of garuda-inxi in the body of the post (not linked externally, or collapsed with the “hide details” feature)
  • Format terminal output (including your garuda-inxi) as a code block by clicking the preformatted text button (</>), or put three tildes (~) above and below the text

I’ve fixed it for you. :wink:

2 Likes
3

I reinstalled the system. Could reproduce. I suspect something with the kernel or network stack. Since the device is already quite old, I doubt its something on the driver level, personally.

I will use NixOS and see if its the same.
Thanks for the help so far.

Edit: NixOS doesn’t bother to come up with working internet even in live mode.
I tried the current 2024.11 ISO, and that puzzles me, since Broadwing was released after that. (There is currently no way to see the release date, since the Blog is down, but I remember it was just a month ago, or so)

So if the NixOS release from November 2024 does have this issue, the March release from Garuda does not, and some update after that (re)introduces it - I dont know what to say. ^^

Also, it seems the WiFi dongle is not even recognized by lsusb, so maybe its broken. (Its lights are on, but that does not mean its good)

That means, maybe its something in the stack, that handles the usb tethering (I know nothing about that) so I am going to try to find a way to connect this machine by some other means to the internet.

4

In this case it is always recommended to test another kernel first - for example linux-lts + linux-lts-headers.

2 Likes
5

Yes, true. Now I just need to find a way to do that without internet. :squinting_face_with_tongue:

Will move the files from the other computer or get the internet running somehow else.

Issues like these are the worst, since you are so limited with bug tracking due to the very issue itself. Alone moving the logs from the computer to my main machine in order to upload them, was a pain. xD

Thanks for helping

6

Since the issue obviously only occurs after the first system update, install Garuda Linux and simply do not perform a system update. Instead, install the linux lts kernel:

sudo pacman -S linux-lts linux-lts-headers

Then reboot and select linux lts in the grub menu and boot with it. Then open the “Garuda Boot Options”, set the lts kernel as default under “Boot to”, click on Apply and Close.
Then run garuda-update, reboot and check if everything works without issues.

7

I connected it via Ethernet to one of my access points, and it worked. Download the LTS now, but its safe to say its something with the USB or Wifi probably.

Edit: No success. Booting with LTS does not solve the issue.
Additionally, I plugged in another Wifi dongle, that does work on my main machine, and that one is also not showing up in the widget.

It does show up on lsusb, though.

The way the USB subsystem handles data packets is different. Ethernet uses MAC addresses and operates at layer 2, while USB tethering would encapsulate network traffic within USB packets, handled by the appropriate kernel modules.

Since the device itself is recognized (both the phone and the second WiFi dongle) I assume its about the way USB internet is handled.

Afaik, it could be about some USB powersave mode, maybe? I could play with sysfs or tlp to see, although I am fine with using an Ethernet from my access point for now.

Afaik, USB network stuff creates its own virtual interface, while ethernet works right on a physical port.

8

Try the suggestions below:

Disconnect any network devices other than the wifi adapter you wish to get working properly.. This includes LAN Ethernet cables, USB to Ethernet adapters, other USB wifi dongles, and USB phone tethering. Disconnect any USB peripherals connected to the computer such as powered USB hubs.

Then, power down the computer and remove the power plug from the PSU or the wall power socket. Let the computer sit without power for a few minutes. Then, hold down the power button for approximately 30 seconds. Pressing and holding the power button will drain any residual power from the computer’s motherboard, which can often help fix strange hardware issues.

After that procedure is complete, reattach the AC power cord and restart the computer. After rebooting, hopefully your wifi adapter will be working properly. If not follow the instructions below.

Resetting the BIOS back to the factory default settings sometimes helps to get a troublesome wifi adapter working again. Boot into your BIOS utility and reset the BIOS back to the factory default settings. Save the default settings, and power down the computer. After the factory reset you will need to ensure the Linux compatibility bios settings are set correctly again. You will likely need to disable secure boot and fast boot, and be sure the sata controller is set to AHCI mode.

You may think those suggestions are unlikely to help, but that procedure often corrects many hardware issues.

Good luck.

4 Likes