Ethernet issues

[frank nebula]

Hi, good day. Some days ago in some familiar's home, i tried to connect my pc to the internet and it didnt worked at all. It was constantly disconnecting and connecting. I simply decided to use wifi. However, today, while being at my home, i had too many fights with my pc as the gpu kept failing to start and as soon as that is solved, my ethernet decided to die again. This time it was worse because the whole weekend ive been using this exact same ethernet cable and didnt had much issues if any at all. At first i was able to solve the connection issues with just restarting, but now nothing i do works. it got so bad that my internet died and then my whole pc crashed. As today ive got 3 instances where kde plasma shell just randomly crashes (taskbar disappeared for a bit and all the windows "blinked"). Ive no clue if those could be related to it but its worth mentioning it.
I've tried using systemctl restart networkmanager but the best I get is that it connects to the network but no internet access, just to disconnect fully shortly after. In ip a I see the enp3s0 is up but I get errors saying "IP configuration was unavailable for enp3s0" through a kde error notif. I've also tried deleting from KDE's settings menu the wired connections (all I could see) and rebooting the PC but it didn't worked. I see however that it creates 2 wired connections. I don't know if that might be relevant, but with nmcli connection show i see that theres 2 ethernet connections but only one has colour and says its device is enp3s0. also, both of them have completely different uuid.
I don't know what to do, the whole day my ethernet has been fine and this pc has not moved at all to say it could have been the cable getting damaged. Everything is updated so i dont know if it could be a driver issue or what. I tried chatgpt because i didnt know who to ask but it tells me to delet enp3s0, which i cant even do and sincerely im not understanding at all what it wants me to do

[real ocean]

Concrete chronicles clearly conquer crude characterisations, so perhaps post a precise log of pivotal particulars?

journalctl -o short-iso -p4 -S -1w > journal.log

This will export logs from the past week, including log levels from emergency to warning.

[frank nebula]

im sorry for the late reply, this is the file it created, but is it a journal of all my pc or what exactly is it?

also i wanted to mention, i got this log saved from the other day, although its only for networkmanager:

[sudo] password for fugu:
Mar 31 00:01:59 Cinnamoroll NetworkManager[834]: <info>  [1743372119.9102] device (enp3s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Mar 31 00:01:59 Cinnamoroll NetworkManager[834]: <info>  [1743372119.9111] dhcp4 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
Mar 31 00:02:44 Cinnamoroll NetworkManager[834]: <info>  [1743372164.8922] device (enp3s0): state change: ip-config -> failed (reason 'ip-config-unavailable', managed-type: 'full')
Mar 31 00:02:44 Cinnamoroll NetworkManager[834]: <info>  [1743372164.8932] manager: NetworkManager state is now DISCONNECTED
Mar 31 00:02:44 Cinnamoroll NetworkManager[834]: <warn>  [1743372164.8937] device (enp3s0): Activation: failed for connection 'Wired connection 1'
Mar 31 00:02:44 Cinnamoroll NetworkManager[834]: <info>  [1743372164.8943] device (enp3s0): state change: failed -> disconnected (reason 'none', managed-type: 'full')
Mar 31 00:02:44 Cinnamoroll NetworkManager[834]: <info>  [1743372164.9081] dhcp4 (enp3s0): canceled DHCP transaction
Mar 31 00:02:44 Cinnamoroll NetworkManager[834]: <info>  [1743372164.9082] dhcp4 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
Mar 31 00:02:44 Cinnamoroll NetworkManager[834]: <info>  [1743372164.9082] dhcp4 (enp3s0): state changed no lease
Mar 31 00:02:44 Cinnamoroll NetworkManager[834]: <info>  [1743372164.9096] manager: startup complete
Mar 31 00:03:56 Cinnamoroll NetworkManager[834]: <info>  [1743372236.5086] device (enp3s0): Activation: starting connection 'Wired connection 1' (958b3c44-3ff8-3201-a9c2-097054c08cf5)```

Mar 31 00:03:56 Cinnamoroll NetworkManager[834]: <info>  [1743372236.5088] device (enp3s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Mar 31 00:03:56 Cinnamoroll NetworkManager[834]: <info>  [1743372236.5090] manager: NetworkManager state is now CONNECTING
Mar 31 00:03:56 Cinnamoroll NetworkManager[834]: <info>  [1743372236.5091] device (enp3s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Mar 31 00:03:56 Cinnamoroll NetworkManager[834]: <info>  [1743372236.5095] device (enp3s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Mar 31 00:03:56 Cinnamoroll NetworkManager[834]: <info>  [1743372236.5098] dhcp4 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
Mar 31 00:04:11 Cinnamoroll NetworkManager[834]: <info>  [1743372251.3084] device (enp3s0): carrier: link connected
Mar 31 00:04:15 Cinnamoroll NetworkManager[834]: <info>  [1743372255.5658] device (enp3s0): carrier: link connected
Mar 31 00:04:22 Cinnamoroll NetworkManager[834]: <info>  [1743372262.3406] device (enp3s0): carrier: link connected
Mar 31 00:04:41 Cinnamoroll NetworkManager[834]: <info>  [1743372281.8932] device (enp3s0): state change: ip-config -> failed (reason 'ip-config-unavailable', managed-type: 'full')```

Mar 31 00:04:41 Cinnamoroll NetworkManager[834]: <warn>  [1743372281.8939] device (enp3s0): Activation: failed for connection 'Wired connection 1'
Mar 31 00:04:41 Cinnamoroll NetworkManager[834]: <info>  [1743372281.8943] device (enp3s0): state change: failed -> disconnected (reason 'none', managed-type: 'full')
Mar 31 00:04:41 Cinnamoroll NetworkManager[834]: <info>  [1743372281.9052] dhcp4 (enp3s0): canceled DHCP transaction
Mar 31 00:04:41 Cinnamoroll NetworkManager[834]: <info>  [1743372281.9052] dhcp4 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
Mar 31 00:04:41 Cinnamoroll NetworkManager[834]: <info>  [1743372281.9052] dhcp4 (enp3s0): state changed no lease```

[real ocean]

logs of your pc with level equal to or above warning since last week. network manager issues may just be the effect not the cause, so full log is more useful.

[frank nebula]

this was 2 attempts to connect yesterday. i did cought up that it could have been a dhcp error and from reading other threads here, i got the package of dhcpcd but it didnt helped at all so i ended up removing it as after a reboot it was just loaded but not active or anything

[frank nebula]

ah i see, although what confuses me the most is that today is working fine. i didnt do nything special as after yesterday i was too tired and just went to sleep. however i dont want to trust my pc anymore in case the ethernet randomly dies again

[real ocean]

2025-03-30T15:41:57+02:00 Cinnamoroll kernel: r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control

and rtl_rxtx_empty_cond == 0

[frank nebula]

im reading the archwiki and tbh its the first time i read about it. I dont mess much with power management because this laptop is practically always plugged in

how do i know if i need it? ove looked into the bios before of my pc and i dont recall seeing something about it, but should i look for it?

besides, is this the reason my ethernet dies? power management says that it will randomly turn off the network card? if so how is it that wifi still worked when ethernet died?

im sorry if im making too many questions, im just really confused about all this

[real ocean]

They are unrelated. Your WiFi card is from Intel, hence the iwlwifi driver, and your Ethernet card is a Realtek one.

It is usually a driver problem with r8169; if so, you can try the out-of-tree driver r8168 to see what happens.

[frank nebula]

hey, sorry for my late reply. because of work i dont have much access to this pc. And yeah, today that i started using it i got more issues. At first it was fine, my ethernet seemed to work fine but after a bit of time it decided to randomly die. following your comment of the r8169, i found this thread: https://bbs.archlinux.org/viewtopic.php?id=262604. However im confused about something: neither r8169 nor r8168 come up if i search for them in the wiki, only the r8168-lts. I dont know if theres much difference but i still went with the lts but i cant modprove it nor blacklist the r8169 as the thread mentions. i still ran the mkinitcipio tho. i also made sure to check that windows is not the issue. It has been a long time since i used it but i made sure to leave it in airplane mode without the ethernet cable connected and let my pc be for like 5-10 min resting after i turned off windows. In the very least its now running again but im unsure how to proceed with the r8168 or 9 driver. I also found this https://aur.archlinux.org/packages/r8169aspm-dkms in the aur but its old as hell so i dont think it will help much, will it?