Intel I219-V Ethernet keeps disconnecting reconnecting

I have been having this issue couple past weeks. Ethernet will keep disconnecting and connecting. It should not be a HW issue because when I booted to windows on same machine it worked fine. This usually happens right after boot but can sometimes happen randomly during usage. Dmesg is not very helpful al all…

[ 0.000000] efi: Not removing mem72: MMIO range=[0xfec00000-0xfec00fff] (4KB) - Pastebin.com dmesg log

System:
Kernel: 6.13.7-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/vmlinuz-linux-zen
root=UUID=657901d0-2af4-4b27-83f9-ebc013c73770 rw rootflags=subvol=@
quiet rd.luks.uuid=1142304e-afaf-4a1e-bffc-7b1e5da946cf quiet
rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
usbcore.autosuspend=-1 ibt=off
Desktop: KDE Plasma v: 6.3.3 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: N/A
Mobo: ASUSTeK model: PRIME H510M-A v: Rev 1.xx serial: <filter>
part-nu: SKU uuid: 7e879200-015f-fb0e-cec7-fc34971214b0
UEFI: American Megatrends v: 0404 date: 02/05/2021
Battery:
Device-1: hidpp_battery_0 model: Logitech MX Ergo Multi-Device Trackball
serial: <filter> charge: 100% (should be ignored) rechargeable: yes
status: discharging
CPU:
Info: model: Intel Core i7-10700K socket: LGA1200 bits: 64 type: MT MCP
arch: Comet Lake gen: core 10 level: v3 note: check built: 2020
process: Intel 14nm family: 6 model-id: 0xA5 (165) stepping: 5
microcode: 0xFC
Topology: cpus: 1x dies: 1 clusters: 8 cores: 8 threads: 16 tpc: 2
smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 2 MiB
desc: 8x256 KiB L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 800 min/max: 800/5100 base/boost: 3762/5100 scaling:
driver: intel_pstate governor: powersave volts: 1.0 V ext-clock: 100 MHz
cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 9: 800
10: 800 11: 800 12: 800 13: 800 14: 800 15: 800 16: 800 bogomips: 121596
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Vulnerabilities: <filter>
Graphics:
Device-1: Intel CometLake-S GT2 [UHD Graphics 630] vendor: ASUSTeK
driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
ports: active: DP-1,HDMI-A-1 empty: DP-2,HDMI-A-2 bus-ID: 00:02.0
chip-ID: 8086:9bc5 class-ID: 0300
Display: unspecified server: X.Org v: 24.1.6 with: Xwayland v: 24.1.6
compositor: kwin_wayland driver: X: loaded: modesetting
alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: :1 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x286mm (40.00x11.26")
s-diag: 1055mm (41.55")
Monitor-1: DP-1 pos: right model: Asus VE247 serial: <filter> built: 2014
res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 94 gamma: 1.2
size: 521x293mm (20.51x11.54") diag: 598mm (23.5") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
Monitor-2: HDMI-A-1 pos: primary,left model: Asus VE247 serial: <filter>
built: 2014 res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 92 gamma: 1.2
size: 531x299mm (20.91x11.77") diag: 609mm (24") ratio: 16:9 modes:
max: 1920x1080 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 x11: drv: iris
inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.0.1-arch1.2
glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics 630 (CML
GT2) device-ID: 8086:9bc5 memory: 15.2 GiB unified: yes
API: Vulkan v: 1.4.304 layers: 5 device: 0 type: integrated-gpu name: Intel
UHD Graphics 630 (CML GT2) driver: N/A device-ID: 8086:9bc5
surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe (LLVM 19.1.7 256
bits) driver: N/A device-ID: 10005:0000 surfaces: xcb,xlib
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel vendor: ASUSTeK driver: snd_hda_intel v: kernel
alternate: snd_soc_avs bus-ID: 00:1f.3 chip-ID: 8086:f0c8 class-ID: 0403
API: ALSA v: k6.13.7-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.4.1 status: n/a (root, process) 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: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15fa class-ID: 0200
IF: eno1 state: down mac: <filter>
Info: services: NetworkManager, smbd, sshd, systemd-timesyncd
Drives:
Local Storage: total: 465.76 GiB used: 287.39 GiB (61.7%)
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SA2000M8500G
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: S5Z42105 temp: 34.9 C
scheme: GPT
SMART: yes health: PASSED on: 1y 189d 1h cycles: 246
read-units: 23,897,581 [12.2 TB] written-units: 13,959,925 [7.14 TB]
Partition:
ID-1: / raw-size: 363.49 GiB size: 363.49 GiB (100.00%)
used: 287.18 GiB (79.0%) fs: btrfs block-size: 4096 B dev: /dev/dm-0
maj-min: 254:0 mapped: luks-1142304e-afaf-4a1e-bffc-7b1e5da946cf
ID-2: /boot raw-size: 1024 MiB size: 1022 MiB (99.80%)
used: 220.3 MiB (21.6%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p5
maj-min: 259:5
ID-3: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
used: 316 KiB (0.1%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p7
maj-min: 259:7
ID-4: /home raw-size: 363.49 GiB size: 363.49 GiB (100.00%)
used: 287.18 GiB (79.0%) fs: btrfs block-size: 4096 B dev: /dev/dm-0
maj-min: 254:0 mapped: luks-1142304e-afaf-4a1e-bffc-7b1e5da946cf
ID-5: /var/log raw-size: 363.49 GiB size: 363.49 GiB (100.00%)
used: 287.18 GiB (79.0%) fs: btrfs block-size: 4096 B dev: /dev/dm-0
maj-min: 254:0 mapped: luks-1142304e-afaf-4a1e-bffc-7b1e5da946cf
ID-6: /var/tmp raw-size: 363.49 GiB size: 363.49 GiB (100.00%)
used: 287.18 GiB (79.0%) fs: btrfs block-size: 4096 B dev: /dev/dm-0
maj-min: 254:0 mapped: luks-1142304e-afaf-4a1e-bffc-7b1e5da946cf
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.13 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 16
dev: /dev/zram0
ID-2: swap-2 type: partition size: 2 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/nvme0n1p6 maj-min: 259:6
Sensors:
System Temperatures: cpu: 31.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB available: 31.13 GiB used: 8.44 GiB (27.1%)
igpu: 64 MiB
Processes: 371 Power: uptime: 4m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.43 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1668 libs: 449 tools: pakku,paru,yay Compilers:
clang: 19.1.7 gcc: 14.2.1 Shell: garuda-inxi (sudo) default: Bash v: 5.2.37
running-in: konsole inxi: 3.3.37
Garuda (2.7.2-1):
System install date:     2023-06-08
Last full system update: 2025-03-19
Is partially upgraded:   Yes
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Yes
Failed units:            mnt-bach-bachdata.mount mnt-bach-servis.mount mnt-bach-temp.mount

It would help knowing if you’re wired or wireless. If WiFi the info inthe below thread may be of use to you. If WiFI the issue isn’t distro specific. I have Garuda, Reborn, and Arch and had the issue in all three, now with what’s in that thread Once connected it stays but it’s still about a minute after landing on the desktop before it actually connects instead of just being on.


Network:
Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15fa class-ID: 0200
IF: eno1 state: down mac: <filter>
Info: services: NetworkManager, smbd, sshd, systemd-timesyncd
2 Likes

ethernet so it’s wired

1 Like

Welcome to the Garuda forum @Enerccio. :waving_hand: :smiley:

Below are some very effective Ethernet troubleshooting tips you should try:

Be sure to restart both your computer and your router.

Test an alternate router if you could borrow one or have an old router in storage.

Make sure the firmware on your router is up to date.

Test different cable ports on the switch/router.

Try assigning your computer a static IP address via MAC address association through your router configuration utility.

ALWAYS test your connection with a high grade Ethernet cable replacement, (Cat6e or preferably Cat7e).

Test numerous alternate kernels.

Make sure your bios is up to date.

Test your connection using wifi if you have a WiFi dongle available. Does the same thing happen when using WiFi?

Test your connection using USB tethering with your Cel phone. Does the same thing happen when using USB phone tethering?

Test an alternate driver, (if available). There should be an alternate e1000e driver for Intel, and an alternate r8168 driver for Realtek Ethernet adapters.

Test several different Garuda live boot environments including xfce to see if your network connection performs properly there. If so, record important network componets that are in use on any live version that works correctly.

Test the linux-firmware-git package, (and reboot).

Power down your computer, then remove all AC & DC power sources. Unplug your Ethernet cable. Leave the computer without power for five minutes then restart.

Disable wake on LAN (WOL) if it is enabled.

Test different kernel boot parameters, such as:

 pcie_port_pm=off pcie_aspm.policy=performance

Test the above kernel parameters together, or test the kernel parameter below by itself:

pcie_aspm=off 

When all else fails, reset your bios and router to the factory defaults. You will need to change some bios settings afterwards for proper Linux compatability. Usually you can save a backup of your current settings if performing a factory reset is worrisome.

Be sure to report on all suggestions that you try in detail.



Edit:



@Enerccio, It has been a week since your last response on your request for assistance. I provided you with a fairly extensive list of possible solutions you could try. As I have already mentioned, you need to report back on the results of suggestions forum assistants have put to you. Without proper feedback it is very difficult to assist you with finding a solution to your problem.

If you have already found a fix to your problem, please post back with your solution. That way other users dealing with similar issues can benefit from your findings. This helps to expand our forum’s reference and knowledge base, which benefits all Linux users.



5 Likes

Unfortunately none of those helped. There is zero issue when booted to windows so it can’t be technical issue with “router” or "cable. I can’t test various things because it is a work computer.

Power down your computer, then remove all AC & DC power sources. Unplug your Ethernet cable. Leave the computer without power for five minutes then restart.

How would this help?

That’s simple. You have a power supply. The supply need time to go on 0 V DC (capacitors)
If you measure over “earth”..you have a small DC..after some time..example a led goes then out. It can take from seconds to minutes.

To do: Pls make a bios update

1 Like

Btw do you have maybe secure boot turned on bios?

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.