You are not logged in.

Pages: 1

#1 2024-07-16 13:45:37

pure_bliss
Member
Registered: 2021-04-17
Posts: 32

[SOLVED] Network not available for ~10-20 seconds after booting

Hi! Every time I boot my PC the wired network is not available for ~10-~20 seconds.

Network manager logs:

Jul 09 13:14:52 harczos systemd[1]: Starting Network Manager...
Jul 09 13:14:52 harczos NetworkManager[558]: <info>  [1720523692.8359] NetworkManager (version 1.48.2-1) is starting... (boot:796c82ab-aef5-4b47-87ae-56c57dacaf2c)
Jul 09 13:14:52 harczos NetworkManager[558]: <info>  [1720523692.8359] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf) (etc: default-wifi-powersave-on.conf)
Jul 09 13:14:52 harczos NetworkManager[558]: <info>  [1720523692.8395] manager[0x614ce49bab50]: monitoring kernel firmware directory '/lib/firmware'.
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0186] hostname: hostname: using hostnamed
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0186] hostname: static hostname changed from (none) to "harczos"
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0189] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0195] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:01.2/0000:02:00.2/0000:03:08.0/0000:29:00.0/ieee80211/phy0/rfkill1) (driver iwlwifi)
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0196] manager[0x614ce49bab50]: rfkill: Wi-Fi hardware radio set disabled
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0196] manager[0x614ce49bab50]: rfkill: WWAN hardware radio set enabled
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0232] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.48.2-1/libnm-device-plugin-wifi.so)
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0251] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.48.2-1/libnm-device-plugin-wwan.so)
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0364] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.48.2-1/libnm-device-plugin-team.so)
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0368] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.48.2-1/libnm-device-plugin-ovs.so)
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0371] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.48.2-1/libnm-device-plugin-bluetooth.so)
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0374] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.48.2-1/libnm-device-plugin-adsl.so)
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0375] manager: rfkill: Wi-Fi disabled by radio killswitch; disabled by state file
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0375] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0376] manager: Networking is enabled by state file
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0380] settings: Loaded settings plugin: keyfile (internal)
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0494] dhcp: init: Using DHCP client 'internal'
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0495] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0500] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0503] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0506] device (lo): Activation: starting connection 'lo' (ceb04847-271d-4a36-8f93-a898d23ec118)
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0509] manager: (enp42s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0514] settings: (enp42s0): created default wired connection 'Wired connection 2'
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0514] device (enp42s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.2666] device (wlo1): driver supports Access Point (AP) mode
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.2670] manager: (wlo1): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.2673] device (wlo1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.2677] device (wlo1): set-hw-addr: set MAC address to 62:86:36:47:51:1C (scanning)
Jul 09 13:14:53 harczos systemd[1]: Started Network Manager.
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.2764] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.2777] ovsdb: disconnected from ovsdb
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.2778] device (lo): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.2780] device (lo): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.2781] device (lo): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.2787] device (lo): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.2796] device (lo): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.2797] device (lo): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.2799] device (lo): Activation: successful, device activated.
Jul 09 13:14:59 harczos NetworkManager[558]: <info>  [1720523699.2667] manager: startup complete
Jul 09 13:15:08 harczos NetworkManager[558]: <info>  [1720523708.9976] device (enp42s0): carrier: link connected
Jul 09 13:15:08 harczos NetworkManager[558]: <info>  [1720523708.9978] device (enp42s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Jul 09 13:15:08 harczos NetworkManager[558]: <info>  [1720523708.9983] policy: auto-activating connection 'Wired connection 2' (d04b9710-e458-341c-bb5a-5e0d5687adfa)
Jul 09 13:15:08 harczos NetworkManager[558]: <info>  [1720523708.9986] device (enp42s0): Activation: starting connection 'Wired connection 2' (d04b9710-e458-341c-bb5a-5e0d5687adfa)
Jul 09 13:15:08 harczos NetworkManager[558]: <info>  [1720523708.9987] device (enp42s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jul 09 13:15:08 harczos NetworkManager[558]: <info>  [1720523708.9988] manager: NetworkManager state is now CONNECTING
Jul 09 13:15:08 harczos NetworkManager[558]: <info>  [1720523708.9989] device (enp42s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jul 09 13:15:08 harczos NetworkManager[558]: <info>  [1720523708.9994] device (enp42s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jul 09 13:15:08 harczos NetworkManager[558]: <info>  [1720523708.9997] dhcp4 (enp42s0): activation: beginning transaction (timeout in 45 seconds)
Jul 09 13:15:18 harczos NetworkManager[558]: <info>  [1720523718.0482] dhcp4 (enp42s0): state changed new lease, address=192.168.1.201, acd pending
Jul 09 13:15:18 harczos NetworkManager[558]: <info>  [1720523718.2130] dhcp4 (enp42s0): state changed new lease, address=192.168.1.201
Jul 09 13:15:18 harczos NetworkManager[558]: <info>  [1720523718.2133] policy: set 'Wired connection 2' (enp42s0) as default for IPv4 routing and DNS
Jul 09 13:15:18 harczos NetworkManager[558]: <info>  [1720523718.2429] device (enp42s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jul 09 13:15:18 harczos NetworkManager[558]: <info>  [1720523718.2440] device (enp42s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jul 09 13:15:18 harczos NetworkManager[558]: <info>  [1720523718.2441] device (enp42s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jul 09 13:15:18 harczos NetworkManager[558]: <info>  [1720523718.2444] manager: NetworkManager state is now CONNECTED_SITE
Jul 09 13:15:18 harczos NetworkManager[558]: <info>  [1720523718.2446] device (enp42s0): Activation: successful, device activated.
Jul 09 13:15:18 harczos NetworkManager[558]: <info>  [1720523718.3507] manager: NetworkManager state is now CONNECTED_GLOBAL

I have a local DHCP server and pi-hole, which works fine on other devices. I have a laptop with arch linux, and on the same network with same DHCP server it connects instantly. Using wi-fi on the same device works without delay, only wired connection seems to be delayed.

Please let me know what other logs would be usefull for debugging this issue.

Last edited by pure_bliss (2024-09-06 12:35:38)

Offline

#2 2024-07-16 15:07:49

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,808

Re: [SOLVED] Network not available for ~10-20 seconds after booting

Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0514] device (enp42s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')

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

General rule, never filter the journal unless you already know what you're looking for. Otherwise you end up filtering away what you're looking for…

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2024-07-16 15:13:11

twelveeighty
Member
Registered: 2011-09-04
Posts: 1,451

Re: [SOLVED] Network not available for ~10-20 seconds after booting

What NIC/driver are you running? Post "lspci -v" for the NIC. You can also try force loading the module at boot to see if udev activation is causing the delay.

Offline

#4 2024-07-16 17:07:26

pure_bliss
Member
Registered: 2021-04-17
Posts: 32

Re: [SOLVED] Network not available for ~10-20 seconds after booting

seth wrote:
Jul 09 13:14:53 harczos NetworkManager[558]: <info>  [1720523693.0514] device (enp42s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')

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

General rule, never filter the journal unless you already know what you're looking for. Otherwise you end up filtering away what you're looking for…

I know what I was looking for, but turns out I was wrong smile

~ $ find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
avahi-daemon.service                     | multi-user.target.wants
avahi-daemon.socket                      | sockets.target.wants
bluetooth.service                        | bluetooth.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.Avahi.service       | system
dbus-org.freedesktop.NetworkManager.service | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service   | system
display-manager.service                  | system
earlyoom.service                         | multi-user.target.wants
fstrim.timer                             | timers.target.wants
getty@tty1.service                       | getty.target.wants
haveged.service                          | sysinit.target.wants
lm_sensors.service                       | multi-user.target.wants
NetworkManager.service                   | multi-user.target.wants
p11-kit-server.socket                    | sockets.target.wants
paccache.timer                           | timers.target.wants
pipewire-media-session.service           | pipewire.service.wants
pipewire-pulse.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
smb.service                              | multi-user.target.wants
sshd.service                             | multi-user.target.wants
systemd-timesyncd.service                | sysinit.target.wants
xdg-user-dirs-update.service             | default.target.wants
twelveeighty wrote:

What NIC/driver are you running? Post "lspci -v" for the NIC. You can also try force loading the module at boot to see if udev activation is causing the delay.

~ $ sudo lspci -v
...
2a:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 15)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7c95
	Flags: bus master, fast devsel, latency 0, IRQ 36, IOMMU group 15
	I/O ports at f000 [size=256]
	Memory at fcc04000 (64-bit, non-prefetchable) [size=4K]
	Memory at fcc00000 (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=4 Masked-
	Capabilities: [d0] Vital Product Data
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Virtual Channel
	Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00
	Capabilities: [170] Latency Tolerance Reporting
	Capabilities: [178] L1 PM Substates
	Kernel driver in use: r8169
	Kernel modules: r8169
...

If I understood the force loading part correctly I needed to do this:

~ $ /usr/bin/cat /etc/modules-load.d/r8169.conf
r8169

But it didn't help sad `ip a` doesn't show that I'm connected, and takes a while to be able to load pages in firefox.

Offline

#5 2024-07-16 20:10:04

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,808

Re: [SOLVED] Network not available for ~10-20 seconds after booting

You do not seem to have a competing network manager running … which is odd.
But the r8169 chips recently showed up w/ a slow start, you could add the module to the initramfs (MODULES arrain in mkinitcpio.conf)
Otherwise please post your complete system journal for the boot: 

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

so we can see what's going on there.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#6 2024-07-17 09:40:44

pure_bliss
Member
Registered: 2021-04-17
Posts: 32

Re: [SOLVED] Network not available for ~10-20 seconds after booting

seth wrote:

You do not seem to have a competing network manager running … which is odd.
But the r8169 chips recently showed up w/ a slow start, you could add the module to the initramfs (MODULES arrain in mkinitcpio.conf)
Otherwise please post your complete system journal for the boot: 

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

so we can see what's going on there.

Adding "r8169" to "MODULES" in "/etc/mkinitcpio.conf" and running "mkinitcpio -p linux" didn't fix the problem sad

Here is the system journal: http://0x0.st/X9mw.txt

Offline

#7 2024-07-17 11:44:08

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,808

Re: [SOLVED] Network not available for ~10-20 seconds after booting

Jul 17 11:36:51 harczos kernel: Generic FE-GE Realtek PHY r8169-0-2a00:00: Downshift occurred from negotiated speed 1Gbps to actual speed 100Mbps, check cabling!

Plugs are part of the cable, somtimed the latch protection collides with the case and prevents a complete insertion.
In doubt replace the cable

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#8 2024-07-17 15:27:24

twelveeighty
Member
Registered: 2011-09-04
Posts: 1,451

Re: [SOLVED] Network not available for ~10-20 seconds after booting

@pure_bliss: I forgot to ask - did this problem start recently (after having worked as expected before), or has it always been like this?

Offline

#9 2024-07-19 13:33:12

pure_bliss
Member
Registered: 2021-04-17
Posts: 32

Re: [SOLVED] Network not available for ~10-20 seconds after booting

seth wrote:
Jul 17 11:36:51 harczos kernel: Generic FE-GE Realtek PHY r8169-0-2a00:00: Downshift occurred from negotiated speed 1Gbps to actual speed 100Mbps, check cabling!

Plugs are part of the cable, somtimed the latch protection collides with the case and prevents a complete insertion.
In doubt replace the cable

I'll try with a different cable / ports then, I'll just have to get a new cable.

twelveeighty wrote:

@pure_bliss: I forgot to ask - did this problem start recently (after having worked as expected before), or has it always been like this?

I used wifi before, which connected instantly, but had some other connectivity issues, that's why I switched to cable, and had this issue from the start

Offline

#10 2024-07-19 15:16:01

kocey
Member
Registered: 2024-07-15
Posts: 5

Re: [SOLVED] Network not available for ~10-20 seconds after booting

Do you have any VMs running on this machine?

https://bbs.archlinux.org/viewtopic.php?id=207379

Last edited by kocey (2024-07-19 15:18:57)

Offline

#11 2024-07-19 16:49:44

pure_bliss
Member
Registered: 2021-04-17
Posts: 32

Re: [SOLVED] Network not available for ~10-20 seconds after booting

kocey wrote:

Do you have any VMs running on this machine?

https://bbs.archlinux.org/viewtopic.php?id=207379

No there aren't. I don't think that there is anything related to this issue that could cause issues other than my local DHCP server and the pihole, but there are no issues with wifi

Offline

#12 2024-09-06 12:38:05

pure_bliss
Member
Registered: 2021-04-17
Posts: 32

Re: [SOLVED] Network not available for ~10-20 seconds after booting

Update: got new cable, problem solved. Old one was Cat 5E, new is Cat 6. Old was is very used condition.

Offline

Pages: 1

Board footer

Powered by FluxBB