Ethernet connection suddenly stopped working, no solutions I've found helped

Ask Fedora
, , , ,
1

Hello all,

Recently switched from ubuntu (prior to this date i’ve been using ubuntu for a year and a half) to fedora, but i’m still pretty new to linux overall. I’ve been reading several boards on similar issues and they’ve been helpful in understanding how to diagnose the issue, but no solutions have helped me so far.

As the title says, my ethernet connection stopped working suddenly, after about a month of switching to Fedora. Up until now, it worked with windows, ubuntu, and fedora: my ethernet connection is through a plc ethernet device, as I am in the farthest corner from my router. I am currently writing from tethered wifi.

I’m running Fedora Linux 44 (Workstation Edition). Here’s a complete modprobe of my system. Relevant TL;DR is that I’m running an ASUS TUF Z270 MARK-2 with an intel E100E Ethernet Connection (2) I219-V card.

Here’s a pastebin with the most commonly asked information, including lspci, nmcli, dhcpd, ipaddr, ethtool, dmesg, etc. The checksum is valid, the link is up, it just fails to get a DHCP offer and seems to not be able to set an ipv4 address.

Things I’ve tried:

  • Resetting the router, changing the router port, changing the ethernet cable from the plc adapter to my pc, and also from the router to the plc adapter (on the other side of the house)
  • Changing into a fixed IP address, changing MAC address
  • Turning autoneg on and off, setting dhclient in the main section of the network manager config (and reapplying configs, using nmcli down/up, setting the ipv4 protocol
  • Deleting the ethernet connection profile and making a new one
  • Checking the ethernet lights in my internet card: card light is green and unblinking, ethernet port lights are yellow and orange respectively.
  • Checked if ethernet worked with a live fedora usb: it still shows the same error.

I’m at a loss as to what to do. I’ve seen some forum threads that suggest building the driver itself might work, but I’m unsure it might be the issue.

Am I missing something? Can I check for anything else?

2

Please post the output of inxi -ezxx here as preformatted text so we know what the hardware is.

3

Hello! I’ve updated my post with more information + hardware probes + other outputs.

Here’s the output you’ve asked for:

System:
  Kernel: 6.19.10-300.fc44.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 16.0.1
  Desktop: GNOME v: 50.0 tk: GTK v: 3.24.52 wm: gnome-shell dm: GDM
    Distro: Fedora Linux 44 (Workstation Edition)
Machine:
  Type: Desktop Mobo: ASUSTeK model: TUF Z270 MARK 2 v: Rev 1.xx
    serial: <superuser required> part-nu: SKU Firmware: UEFI-[Legacy]
    vendor: American Megatrends v: 0906 date: 03/22/2017
CPU:
  Info: quad core model: Intel Core i7-7700K bits: 64 type: MT MCP
    arch: Kaby Lake rev: 9 cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  Speed (MHz): avg: 4365 min/max: 800/4500 cores: 1: 4365 2: 4365 3: 4365
    4: 4365 5: 4365 6: 4365 7: 4365 8: 4365 bogomips: 67200
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT
    / 6900 XT] vendor: Sapphire driver: amdgpu v: kernel arch: RDNA-2 pcie:
    speed: 16 GT/s lanes: 16 ports: active: DP-3,HDMI-A-1
    empty: DP-1,DP-2,Writeback-1 bus-ID: 03:00.0 chip-ID: 1002:73bf
  Display: wayland server: Xwayland v: 24.1.9 compositor: gnome-shell
    driver: gpu: amdgpu display-ID: 0
  Monitor-1: DP-3 model: Asus VX279 res: 1920x1080 dpi: 81
    diag: 690mm (27.2")
  Monitor-2: HDMI-A-1 model: Artist 24 Pro res: 2560x1440 dpi: 123
    diag: 604mm (23.8")
  API: OpenGL v: 4.6 vendor: amd mesa v: 26.1.7 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: AMD Radeon RX 6800 XT (radeonsi navi21 ACO DRM
    3.64 6.19.10-300.fc44.x86_64) device-ID: 1002:73bf display-ID: :0.0
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: api: glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a2f0
  Device-2: Advanced Micro Devices [AMD/ATI] Navi 21/23 HDMI/DP Audio
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: 03:00.1 chip-ID: 1002:ab28
  Device-3: RODE Microphones RØDE NT-USB Mini
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
    lanes: 1 bus-ID: 1-1:2 chip-ID: 19f7:0015
  API: ALSA v: k6.19.10-300.fc44.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.6.2 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8
  IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: <filter>
  Device-2: Qualcomm Atheros AR9287 Wireless Network Adapter driver: ath9k
    v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 08:00.0 chip-ID: 168c:002e
  IF: wlp8s0 state: up mac: <filter>
Drives:
  Local Storage: total: 3.87 TiB used: 1.74 TiB (44.9%)
  ID-1: /dev/nvme0n1 vendor: Seagate model: WDC WDS256G1X0C-00ENX0
    size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 55.9 C
  ID-2: /dev/sda vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB
    speed: 6.0 Gb/s serial: <filter>
  ID-3: /dev/sdb vendor: Western Digital model: WD1003FZEX-00K3CA0
    size: 931.51 GiB speed: 6.0 Gb/s serial: <filter>
  ID-4: /dev/sdc vendor: Western Digital model: WD20SDRW-11VUUS0
    size: 1.82 TiB type: USB rev: 3.1 spd: 5 Gb/s lanes: 1 serial: <filter>
Partition:
  ID-1: / size: 236.46 GiB used: 38.31 GiB (16.2%) fs: btrfs dev: /dev/dm-0
    mapped: luks-07d1dc4b-5121-4845-8d3c-15298e013d31
  ID-2: /boot size: 1.9 GiB used: 418.2 MiB (21.5%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /home size: 236.46 GiB used: 38.31 GiB (16.2%) fs: btrfs
    dev: /dev/dm-0 mapped: luks-07d1dc4b-5121-4845-8d3c-15298e013d31
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 116 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 52.0 C mobo: N/A gpu: amdgpu temp: 51.0 C
    mem: 56.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
  Memory: total: 32 GiB available: 31.27 GiB used: 12.83 GiB (41.0%)
  Processes: 482 Power: uptime: 23h 13m wakeups: 4 Init: systemd v: 259
    default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 22
    Compilers: gcc: 16.0.1 Shell: Bash v: 5.3.9 running-in: ptyxis-agent
    inxi: 3.3.41
4

Is there a newer Bios/Firmware available? Did you check that.
Did you test disabling IPv6?

Does resolvectl show some dns?

Have you tested with an older Kernel?

5

Does it work from the Fedora Workstation 44 ISO as a live USB?

If not, then that would rule out a few things (like updates to Fedora, or config changes, being responsible).

6

Hi!

@ilikelinux When booting I’ve seen that aside from my current kernel there’s a backup/recovery image. Is that enough? How can I download and test in an older kernel?

Here’s resolvectl output:

ruins@fedora ~/Downloads [1]> resolvectl
Global
         Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
  resolv.conf mode: stub

Link 2 (enp0s31f6)
    Current Scopes: none
         Protocols: -DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
     Default Route: no

Link 3 (wlp8s0)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
         Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.53.171
       DNS Servers: 192.168.53.171
     Default Route: yes

@pg-tips
Thanks for asking, I’ve tested using the same live USB I used to install Fedora and it still showed the issue. Added this to my OP.

7

Your dmesg output suggests the connection is always 100 Mbps, which is surprising for that card (unless the router or something else in your hardware can’t support more).

You already tried changing the cable, which would have been my first go-to :thinking:

8

What do you mean by surprising? Should it be more? What other value could I try?

9

The card should be capable of 1 Gbps.

However I think your ethtool output already answers it, actually. The “link partner” (router or whatever device you’re connecting to) only supports 100 Mbps. So not necessarily so surprising!

## ETHTOOL
Settings for enp0s31f6:
	Supported ports: [ TP ]
	Supported link modes:   10baseT/Half 10baseT/Full
	                        100baseT/Half 100baseT/Full
	                        1000baseT/Full
	Supported pause frame use: Symmetric Receive-only
	Supports auto-negotiation: Yes
	Supported FEC modes: Not reported
	Advertised link modes:  10baseT/Half 10baseT/Full
	                        100baseT/Half 100baseT/Full
	                        1000baseT/Full
	Advertised pause frame use: Symmetric Receive-only
	Advertised auto-negotiation: Yes
	Advertised FEC modes: Not reported
	Link partner advertised link modes:  10baseT/Half 10baseT/Full
	                                     100baseT/Half 100baseT/Full
	Link partner advertised pause frame use: Symmetric Receive-only
	Link partner advertised auto-negotiation: Yes
	Link partner advertised FEC modes: Not reported
10

When reporting an issue you should update both Fedora and vendor firmware so that a) you aren’t chasing a solved problem, and b) it is easier for others with access to similar hardware to reproduce the issue.

11

Hi @gnwiii, thanks for pointing that out. I thought I had updated, but it seems like the GUI for updates does not let me download if i’m under tethered wifi. I’ll try updating fedora regardless, is there any other firmware that I should be updating?

12

If the connection had never worked on Fedora, I’d agree.

But in this case:

  • the connection worked in the past
  • then it stopped working, and still doesn’t work when reverting to the original release version of F44 (via Live USB).

This seems like an issue outside of Fedora, and doing firmware updates (unless they’re reverting a change that might have caused the previously working system to break) adds more variables to the equation.

13

What is this device? It just resolves locally, right. You need a dns which resolves the addresses into the internet? Do you have a device like a raspberry pi in between? If yes you have to look if the RPi lets you resolve the address.

192.168.53.171
14

That’s my tethered wifi connection, aka my phone’s hotspot wifi-- otherwise I would have no way to respond through my desktop pc and/or update things.

I don’t have a RPi inbetween my router/eth connection and my pc: the only thing I do have is a PLC ethernet device, but (afaik) that only transmits the internet signal through the electrical current.

15

Could it be that the Provider has changed something if you use internet over power line.

16

You mean the internet provider? Highly unlikely-- they even have a blog post on their website talking about the advantages of using PLC.

If you mean something else, I’m afraid I don’t understand what you mean. Regardless I do want to buy a ridiculously long ethernet cable to directly hook up my destkop to the router, no plc involved, but that’d have to wait until next week as I’m out of town starting tomorrow. :frowning:

17

Have you tried changing the cable from the router to the powerline adapter?

18

Just did. Issue still persists. Edited OP to list this attempt too.

19

You mentioned that the Ethernet connection not works anymore? Over your handy it works with usb tethering.

Now I get it. You use a internal PLC at your home. And this connection to the router not works anymore. So best is to bring your computer closer to the router and test from there with a physical network cable.

When you try to connect over plc, can you ping the router?
You should repeat the resolvctl when being connected over PLC, to see if you can resolve (dns) outside of your router.

Also a traceroute helps to see till where you can get with the PLC connection. Have you restarted the PLC connection on both sides? When a mac adress changes it might not lets you connect?

With PLC we are talking about that:

right?

20

Yes, that’s what I mean by PLC.

Regarding the mac address change: I did not change my mac address until after the problems started. Do you mean that such change might be an issue? I changed my mac address and there were no changes, so it should mean the router has not blocked the connection, right?

I will try to restart the PLC connection, but I’m afraid I cannot move my pc closer to the router. A networking colleague suggested moving the router closer to my pc instead and hook it up directly. Even if that would not give me internet, it should at least give me an IP and a DNS, right?

Also: I’ve updated Fedora and the problem still persists. :frowning: