NetworkManager delayed connection - new archinstall

kerosene8902 · 2025-12-06 17:27:16

Fresh archinstall, selected NetworkManager. There is a ~10-14 second delay before network is accessible if I login immediately. The tray icon has a green spinning animation until connected and switched to ethernet icon.
I was hoping to eliminate this delay. I did not experience it on other distros. Can't find anything about this anywhere.

Looked into a few things already. Saw that competing network manager can cause this, which shouldn't be the case on fresh archinstall but confirmed here:

 
$ find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
apparmor.service                         | multi-user.target.wants
auditd.service                           | multi-user.target.wants
bluetooth.service                        | bluetooth.target.wants
cronie.service                           | multi-user.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service   | system
display-manager.service                  | system
fstrim.timer                             | timers.target.wants
getty@tty1.service                       | getty.target.wants
gnome-keyring-daemon.socket              | sockets.target.wants
grub-btrfsd.service                      | multi-user.target.wants
lactd.service                            | multi-user.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
systemd-timesyncd.service                | sysinit.target.wants
systemd-userdbd.socket                   | sockets.target.wants
wireplumber.service                      | pipewire.service.wants
xdg-user-dirs.service                    | graphical-session-pre.target.wants

Also saw a concern about NIC drivers (although this seems unlikely to me as Fedora did not have this connection delay):

 
$ sudo lspci -v
...
0c:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
	DeviceName: Realtek RTL8125BG LAN
	Subsystem: ASUSTeK Computer Inc. Device 87d7
	Flags: bus master, fast devsel, latency 0, IRQ 24, IOMMU group 20
	I/O ports at e000 [size=256]
	Memory at 80000000 (64-bit, non-prefetchable) [size=64K]
	Memory at 80010000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
	Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
	Capabilities: [70] Express Endpoint, IntMsgNum 1
	Capabilities: [b0] MSI-X: Enable+ Count=32 Masked-
	Capabilities: [d0] Vital Product Data
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [148] Virtual Channel
	Capabilities: [168] Device Serial Number 01-00-00-00-68-4c-e0-00
	Capabilities: [178] Transaction Processing Hints
	Capabilities: [204] Latency Tolerance Reporting
	Capabilities: [20c] L1 PM Substates
	Capabilities: [21c] Vendor Specific Information: ID=0002 Rev=4 Len=100 <?>
	Kernel driver in use: r8169
	Kernel modules: r8169
...

My journalctl -u NetworkManager output (multiple boots today):
http://0x0.st/KvTL.txt

Full journalctl -b output
http://0x0.st/KvTf.txt

edit: BTW I also tried masking NetworkManager-wait-online.service, so it's not related to that either.

Really appreciate the help!

Last edited by kerosene8902 (2025-12-07 21:32:24)

Lone_Wolf · 2025-12-07 10:30:12

For clarity :

Did you use the official installation guide or the archinstall script on the install iso ?

In the 2nd case please report this post and request the thread to be moved to the Arch Linux Guided Installer subboard.

Lone_Wolf · 2025-12-07 12:17:50

Moderator Note
Moved to Arch Linux Guided Installer subforum as requested.

seth · 2025-12-07 15:14:06

Please use [code][/code] tags, not "quote" tags. Edit your post in this regard.

Dec 06 10:30:33 archlinux NetworkManager[2528]: <info>  [1765035033.0028] dhcp: init: Using DHCP client 'internal'
Dec 06 10:30:36 archlinux NetworkManager[2528]: <info>  [1765035036.1276] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
Dec 06 10:31:10 archlinux NetworkManager[2528]: <info>  [1765035070.6469] dhcp4 (eno1): state changed new lease, address=192.168.50.191, acd pending
Dec 06 10:31:10 archlinux NetworkManager[2528]: <info>  [1765035070.7767] dhcp4 (eno1): state changed new lease, address=192.168.50.191

The dhcp response takes almost 45s, this is either the dhcp server¹ or

Dec 06 10:30:32 archlinux kernel: r8169 0000:0c:00.0 eth0: RTL8125B, a0:36:bc:ad:d7:dc, XID 641, IRQ 129

but there're no signs for problems w/ the NIC.
Do you get the same behavior w/ the LTS kernel?
You can also try to use a different https://wiki.archlinux.org/title/Networ … HCP_client

¹ There's an nvme and 3 SATA disks? Is there a parallel windows installation?

kerosene8902 · 2025-12-07 21:38:50

seth wrote:

...
The dhcp response takes almost 45s, this is either the dhcp server¹ or
Dec 06 10:30:32 archlinux kernel: r8169 0000:0c:00.0 eth0: RTL8125B, a0:36:bc:ad:d7:dc, XID 641, IRQ 129
but there're no signs for problems w/ the NIC.
Do you get the same behavior w/ the LTS kernel?

Will try in a bit.

seth wrote:

You can also try to use a different https://wiki.archlinux.org/title/Networ … HCP_client
¹ There's an nvme and 3 SATA disks? Is there a parallel windows installation?

You are probably on to something with that. I believe I came across something else that pointed that way that made sense.

Not sure about the 3 SATA, I do have one basically just hanging out, still plugged in. I used to use it for a Windows VM with drive and GPU passthrough. And there were two USB drives plugged in at the same time. My nvme is LUKS encrypted and shows as two in Dolphin so maybe has something to do with it?

seth · 2025-12-07 21:42:50

If there's still a windows installation see the 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

You might also try to reboot the dhcp server (in doubt your ISP issued routermodemswitch combo device )

kerosene8902 · 2025-12-07 22:38:00

LTS kernel has same behavior.

Apologies I wasn't clear about the drive. It is a LUKS Linux partition only with a qcow file on it. I'm not even mounting it anymore with my new archinstall. It wasn't a bare windows install. So I don't think it should interfere with anything. I could always unplug it as I'm not using it anymore.

I'll play with the dhcp when I have some more time. Thanks!!

Arch Linux

#1 2025-12-06 17:27:16

NetworkManager delayed connection - new archinstall

#2 2025-12-07 10:30:12

Re: NetworkManager delayed connection - new archinstall

#3 2025-12-07 12:17:50

Re: NetworkManager delayed connection - new archinstall

#4 2025-12-07 15:14:06

Re: NetworkManager delayed connection - new archinstall

#5 2025-12-07 21:38:50

Re: NetworkManager delayed connection - new archinstall

#6 2025-12-07 21:42:50

Re: NetworkManager delayed connection - new archinstall

#7 2025-12-07 22:38:00

Re: NetworkManager delayed connection - new archinstall

Board footer