[Solved] Wired network keeps disconnecting on fresh install

j@s0n · 2025-03-30 23:32:09

I installed using archinstall yesterday on a machine that was previously running windows for a year or two with no hardware problems.
I chose to have the installer copy the ISO networking configuration (it didn't specify what it was). While installing and configuring today, I'd experience network disconnections. ip addr shows the same IP address, but my Unifi control panel doesn't show the computer. I can't ping anything by IP address.
I installed NetworkManager, because that's what I was running on the computer it replaced, as well as this one, and it has always worked well. NetworkManager connection showed a connection, but starting, stopping, and restarting NetworkManager didn't change anything, even after I restarted the system.

Do I potentially have another network management tool running? How do I figure out if I do and what it is?

Last edited by j@s0n (2025-04-01 17:44:35)

j@s0n · 2025-03-31 01:31:33

I did more looking and found out I had systemd-networkd running. I disabled that, thinking it might be controlling the network interface. It's still disconnecting after 20-30 minutes though.

seth · 2025-03-31 07:25:51

Please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

j@s0n · 2025-03-31 14:21:50

❮ find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.resolve1.service    | system
dbus-org.freedesktop.timesync1.service   | system
fstrim.timer                             | timers.target.wants
getty@tty1.service                       | getty.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-pulse.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
sshd.service                             | multi-user.target.wants
systemd-resolved.service                 | sysinit.target.wants
systemd-timesyncd.service                | sysinit.target.wants
systemd-userdbd.socket                   | sockets.target.wants
wireplumber.service                      | pipewire.service.wants

j@s0n · 2025-03-31 14:25:35

The only difference between this and my notebook is my notebook doesn't have systemd-resolved.service running.

seth · 2025-03-31 14:30:20

You're not running concurrent services, please post your complete system journal for a boot covering such disconnects, eg.

sudo journalctl -b | curl -F 'file=@-' 0x0.st

for the current one.

j@s0n · 2025-03-31 14:46:11

❮ sudo journalctl -b | curl -F 'file=@-' 0x0.st
http://0x0.st/82PS.txt

I don't think that's what you're looking for though. That doesn't seem useful as output. Did you mean something other than curl?

Last edited by j@s0n (2025-03-31 14:47:25)

seth · 2025-03-31 15:37:24

If you open the link you'll see your journal - there's no indication of any network loss, though.
You get a connection 10:19, 10:26 you stop resolved and 10:44 you log in on a console (not necessary, btw - you can just use some graphical TE) and draw the journal.

When about did you lose the network during that boot?

j@s0n · 2025-03-31 15:50:26

I assume it's the most recent boot, which still has the network connection active. Sometimes it will function for hours.

seth · 2025-03-31 15:52:16

… journalctl -b -δ …

will go back δ boots

j@s0n · 2025-03-31 16:13:33

http://0x0.st/82Zu.txt

-thc · 2025-03-31 16:28:10

This looks like a glitch in Asus branded Gigabit network hardware running with the igc driver.

Others running into that problem fixed it by tweaking the network cards power management through adding

pcie_port_pm=off pcie_aspm.policy=performance

to the kernel command line.

j@s0n · 2025-04-01 01:14:54

I just restarted with that kernel parameter. Fingers crossed.

j@s0n · 2025-04-01 17:44:07

It's been running fine for 16.5 hours, so I'm going to consider this fixed.
Thanks all

Arch Linux

#1 2025-03-30 23:32:09

[Solved] Wired network keeps disconnecting on fresh install

#2 2025-03-31 01:31:33

Re: [Solved] Wired network keeps disconnecting on fresh install

#3 2025-03-31 07:25:51

Re: [Solved] Wired network keeps disconnecting on fresh install

#4 2025-03-31 14:21:50

Re: [Solved] Wired network keeps disconnecting on fresh install

#5 2025-03-31 14:25:35

Re: [Solved] Wired network keeps disconnecting on fresh install

#6 2025-03-31 14:30:20

Re: [Solved] Wired network keeps disconnecting on fresh install

#7 2025-03-31 14:46:11

Re: [Solved] Wired network keeps disconnecting on fresh install

#8 2025-03-31 15:37:24

Re: [Solved] Wired network keeps disconnecting on fresh install

#9 2025-03-31 15:50:26

Re: [Solved] Wired network keeps disconnecting on fresh install

#10 2025-03-31 15:52:16

Re: [Solved] Wired network keeps disconnecting on fresh install

#11 2025-03-31 16:13:33

Re: [Solved] Wired network keeps disconnecting on fresh install

#12 2025-03-31 16:28:10

Re: [Solved] Wired network keeps disconnecting on fresh install

#13 2025-04-01 01:14:54

Re: [Solved] Wired network keeps disconnecting on fresh install

#14 2025-04-01 17:44:07

Re: [Solved] Wired network keeps disconnecting on fresh install

Board footer