Network connection causes large boot time

Support Network
1

Hi

I need help to fix large boot time

systemd-analyze
Startup finished in 2.186s (kernel) + 1min 36.933s (userspace) = 1min 39.120s 
graphical.target reached after 1min 35.784s in userspace.

I think that the issue is related to this output

journalctl -b | grep wlan0.conf
oct. 29 17:48:51 family-pc systemd[1]: Expecting device /sys/subsystem/net/devices/wlan0.conf...
oct. 29 17:50:21 family-pc systemd[1]: sys-subsystem-net-devices-wlan0.conf.device: Job sys-subsystem-net-devices-wlan0.conf.device/start timed out.
oct. 29 17:50:21 family-pc systemd[1]: Timed out waiting for device /sys/subsystem/net/devices/wlan0.conf.
oct. 29 17:50:21 family-pc systemd[1]: Dependency failed for WPA supplicant daemon (for interface wlan0.conf).
oct. 29 17:50:21 family-pc systemd[1]: wpa_supplicant@wlan0.conf.service: Job wpa_supplicant@wlan0.conf.service/start failed with result 'dependency'.
oct. 29 17:50:21 family-pc systemd[1]: sys-subsystem-net-devices-wlan0.conf.device: Job sys-subsystem-net-devices-wlan0.conf.device/start failed with result 'timeout'.

there is no wlan0 device

System:
  Kernel: 6.6.107-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64
    root=UUID=1325cf9e-d1ce-4793-982f-ab936c92fb48 rw quiet
    resume=UUID=bce1ed1a-aada-49c9-a865-88443882d3db
  Console: pty pts/0 DM: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: BIOSTAR model: H61MGV3 v: 7.0 serial: N/A
    uuid: 03000200-0400-0500-0006-000700080009 BIOS: American Megatrends v: 4.6.5
    date: 03/20/2014
CPU:
  Info: model: Intel Core i3-3220 socket: BGA1155 bits: 64 type: MT MCP
    arch: Ivy Bridge gen: core 3 level: v2 built: 2012-15 process: Intel 22nm
    family: 6 model-id: 0x3A (58) stepping: 9 microcode: 0x21
  Topology: cpus: 1x dies: 1 clusters: 2 cores: 2 threads: 4 tpc: 2
    smt: enabled cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB
    desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 1597 min/max: 1600/3300 base/boost: 3300/3800 scaling:
    driver: intel_cpufreq governor: schedutil volts: 3.3 V ext-clock: 100 MHz
    cores: 1: 1597 2: 1597 3: 1597 4: 1597 bogomips: 26350
  Flags-basic: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: conditional; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds status: Not affected
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics
    vendor: Biostar Microtech Intl Corp driver: i915 v: kernel arch: Gen-7
    process: Intel 22nm built: 2012-13 ports: active: VGA-1 empty: none
    bus-ID: 00:02.0 chip-ID: 8086:0152 class-ID: 0300
  Display: unspecified server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
    driver: X: loaded: modesetting alternate: fbdev,vesa dri: crocus gpu: i915
    tty: 150x35
  Monitor-1: VGA-1 model: Samsung SA300/SA350 serial: <filter> built: 2011
    res: 1600x900 dpi: 92 gamma: 1.2 size: 443x249mm (17.44x9.8")
    diag: 508mm (20") ratio: 16:9 modes: max: 1600x900 min: 720x400
  API: EGL v: 1.5 hw: drv: intel crocus platforms: device: 0 drv: crocus
    device: 1 drv: swrast gbm: drv: crocus surfaceless: drv: crocus
    inactive: wayland,x11
  API: OpenGL v: 4.5 compat-v: 4.2 vendor: mesa v: 25.2.3-arch1.2
    note: console (EGL sourced) renderer: Mesa Intel HD Graphics 2500 (IVB GT1),
    llvmpipe (LLVM 20.1.8 256 bits)
  Info: Tools: api: eglinfo,glxinfo de: kscreen-console,kscreen-doctor
    x11: xprop,xrandr
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio
    vendor: Biostar Microtech Intl Corp driver: snd_hda_intel v: kernel
    bus-ID: 00:1b.0 chip-ID: 8086:1c20 class-ID: 0403
  API: ALSA v: k6.6.107-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.8 status: off with: pipewire-media-session
    status: off tools: pw-cli
  Server-3: PulseAudio v: 17.0-43-g3e2bb status: off with: 1: pulseaudio-alsa
    type: plugin 2: pulseaudio-jack type: module tools: pacat,pactl
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Biostar Microtech Intl Corp driver: r8168 v: 8.055.00-NAPI
    modules: r8169 pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000
    bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp2s0 state: down mac: <filter>
  Device-2: Ralink RT2870/RT3070 Wireless Adapter driver: rt2800usb type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-1.1:3
    chip-ID: 148f:3070 class-ID: 0000 serial: <filter>
  IF: wlp0s29u1u1 state: up mac: <filter>
  Info: services: NetworkManager, sshd, systemd-timesyncd, wpa_supplicant
Drives:
  Local Storage: total: 931.51 GiB used: 127.23 GiB (13.7%)
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10EZEX-00WN4A0
    family: Blue (CMR) size: 931.51 GiB block-size: physical: 4096 B
    logical: 512 B sata: 3.1 speed: 3.0 Gb/s tech: HDD rpm: 7200
    serial: <filter> fw-rev: 1A01 temp: 36 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 1y 342d 14h cycles: 1608
Partition:
  ID-1: / raw-size: 50.78 GiB size: 49.68 GiB (97.84%) used: 39.03 GiB (78.6%)
    fs: ext4 block-size: 4096 B dev: /dev/sda5 maj-min: 8:5
  ID-2: /home raw-size: 210.11 GiB size: 205.76 GiB (97.93%)
    used: 88.2 GiB (42.9%) fs: ext4 block-size: 4096 B dev: /dev/sda7
    maj-min: 8:7
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 10.74 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sda6 maj-min: 8:6
Sensors:
  System Temperatures: cpu: 30.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 4 GiB available: 3.73 GiB used: 648.7 MiB (17.0%) igpu: 64 MiB
  Processes: 137 Power: uptime: 21m states: freeze,standby,mem,disk
    suspend: s2idle avail: shallow wakeups: 0 hibernate: platform avail: shutdown,
    reboot, suspend, test_resume image: 1.48 GiB Init: systemd v: 257
    default: graphical tool: systemctl
  Packages: 1758 pm: dpkg pkgs: 0 tools: apt,apt-get pm: pacman pkgs: 1751
    libs: 476 tools: octopi,pamac,yay pm: flatpak pkgs: 7 Compilers:
    clang: 20.1.8 gcc: 15.2.1 Shell: Bash (su) v: 5.3.3
    running-in: pty pts/0 (SSH) inxi: 3.3.39
2

That seems awfully over-specific.
Rather, examine the whole log - all entries - around that time frame - not just the lines where this file name is mentioned in.
Donā€™t filter for lines with this pattern only ā€¦

Might provide better context.

Your Wlan device doesnā€™t have this name - it is called
wlp0s29u1u1
as per your inxi output

So: where would that insistence to start a non existent device
wlan0
come from?

systemd-analyze blame

could shed some more light as well

3

thanks for the replying . Should I post all the journalctl -b output ?

sorry for my english

4

You should look at it - around that time frame where the issue seems to occur.
And if you canā€™t make sense of it - you may post it.
But not all of it - just the relevant time frame.

Post here
or to some file sharing web site -
they will give you a link to what you uploaded
which you can post here.

5

I feel lost. I donā€™t know where to start!!!

6

As of now, you donā€™t even know that what you think the problem is with your long boot time
is actually the real problem.

That the culprit is this wlan0.conf is, so far, just an assumption.

I donā€™t know either.

I would start by examining the whole log:
journalctl -b
and then search within that for any errors - or for your wlan0.conf
to find the time where this occurs - and see the context, the messages around that, before and after.

You can search by putting in a slash (/), followed by the search term.
ā€¦ that is how you can search the contents of the log that is currently being listed.

You appear to be using Plasma - there may be some GUI tools to examine the logs
instead of this terminal approach.
I donā€™t know - Iā€™m nor familiar enough with Plasma to give advice where to find these tools.

If it is any consolation:
I, too, have only a spinning disk in my machine.
And the cold boot time is ā€¦ not very fast.

A minute and a half is normal - and then another minute or so to go from login to a functional browser (it needs to start, then ask for the password to unlock the encrypted passwords store ā€¦)

It takes time to ā€œscrapeā€ all that from a spinning disk. :smiling_face_with_sunglasses:

Spinning disks are reliable - but slow.

and your systen has got only 4 GB of RAM
for a system running Plasma that is very scarce.

I have twice that (8 GB) - and that is already precious little -
and I use half of that (4 GB) to run virtual machines.

ā€¦ the VMā€™s start up way faster than the host system does ā€¦ - the virtual disks are smaller and more contiguous ā€¦
Not so much (disk head) searching/moving required.

With a spinning disk, it is very much a mechanical system.

Reliable - but it takes time.
An SSD doesnā€™t have this limitation.

7

there is an error at time 17:50:21 related to sys-subsystem-net-devices-wlan0.conf.device time out but I canā€™ figure out what trigged the wlan0.conf.device

oct. 29 17:49:03 family-pc NetworkManager[542]: <info>  [1761756543.5932] device (wlp0s29u1u1): state change: ip-config -> ip-check (reason 'none', managed-type: 'ful>
oct. 29 17:49:03 family-pc NetworkManager[542]: <info>  [1761756543.5955] device (wlp0s29u1u1): state change: ip-check -> secondaries (reason 'none', managed-type: 'f>
oct. 29 17:49:03 family-pc NetworkManager[542]: <info>  [1761756543.5958] device (wlp0s29u1u1): state change: secondaries -> activated (reason 'none', managed-type: '>
oct. 29 17:49:03 family-pc NetworkManager[542]: <info>  [1761756543.5963] manager: NetworkManager state is now CONNECTED_SITE
oct. 29 17:49:03 family-pc NetworkManager[542]: <info>  [1761756543.5971] device (wlp0s29u1u1): Activation: successful, device activated.
oct. 29 17:49:04 family-pc NetworkManager[542]: <info>  [1761756544.1357] manager: NetworkManager state is now CONNECTED_GLOBAL
oct. 29 17:49:04 family-pc NetworkManager[542]: <info>  [1761756544.7734] manager: startup complete
oct. 29 17:49:06 family-pc NetworkManager[542]: <info>  [1761756546.9667] dhcp6 (wlp0s29u1u1): activation: beginning transaction (timeout in 45 seconds)
oct. 29 17:49:06 family-pc avahi-daemon[544]: Leaving mDNS multicast group on interface wlp0s29u1u1.IPv6 with address fe80::19c0:9faa:b6e3:f79.
oct. 29 17:49:06 family-pc avahi-daemon[544]: Joining mDNS multicast group on interface wlp0s29u1u1.IPv6 with address fd80::6695:8d03:c8f:aba6.
oct. 29 17:49:06 family-pc NetworkManager[542]: <info>  [1761756546.9680] policy: set 'Reseau300' (wlp0s29u1u1) as default for IPv6 routing and DNS
oct. 29 17:49:06 family-pc avahi-daemon[544]: Registering new address record for fd80::6695:8d03:c8f:aba6 on wlp0s29u1u1.*.
oct. 29 17:49:06 family-pc avahi-daemon[544]: Withdrawing address record for fe80::19c0:9faa:b6e3:f79 on wlp0s29u1u1.
oct. 29 17:49:07 family-pc NetworkManager[542]: <info>  [1761756547.0398] dhcp6 (wlp0s29u1u1): state changed new lease
oct. 29 17:49:08 family-pc systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
oct. 29 17:49:26 family-pc systemd-timesyncd[307]: Contacted time server 162.159.200.123:123 (2.manjaro.pool.ntp.org).
oct. 29 17:49:26 family-pc systemd-timesyncd[307]: Initial clock synchronization to Wed 2025-10-29 17:49:26.324941 CET.
oct. 29 17:49:27 family-pc systemd[1]: systemd-hostnamed.service: Deactivated successfully.
oct. 29 17:50:21 family-pc systemd[1]: sys-subsystem-net-devices-wlan0.conf.device: Job sys-subsystem-net-devices-wlan0.conf.device/start timed out.
oct. 29 17:50:21 family-pc kernel: fbcon: Taking over console
oct. 29 17:50:21 family-pc systemd[1]: Timed out waiting for device /sys/subsystem/net/devices/wlan0.conf.
oct. 29 17:50:21 family-pc systemd[1]: Dependency failed for WPA supplicant daemon (for interface wlan0.conf).
oct. 29 17:50:21 family-pc systemd[1]: wpa_supplicant@wlan0.conf.service: Job wpa_supplicant@wlan0.conf.service/start failed with result 'dependency'.
oct. 29 17:50:21 family-pc systemd[1]: sys-subsystem-net-devices-wlan0.conf.device: Job sys-subsystem-net-devices-wlan0.conf.device/start failed with result 'timeout'.
oct. 29 17:50:21 family-pc systemd[1]: Reached target Network.
oct. 29 17:50:21 family-pc systemd[1]: Starting CUPS Scheduler...
oct. 29 17:50:21 family-pc systemd[1]: Starting OpenSSH Daemon...
oct. 29 17:50:21 family-pc systemd[1]: Starting Permit User Sessions...
oct. 29 17:50:21 family-pc kernel: Console: switching to colour frame buffer device 200x56
oct. 29 17:50:21 family-pc systemd[1]: systemd-vconsole-setup.service: Deactivated successfully.
oct. 29 17:50:21 family-pc systemd[1]: Stopped Virtual Console Setup.
oct. 29 17:50:21 family-pc systemd[1]: Stopping Virtual Console Setup...
oct. 29 17:50:21 family-pc systemd[1]: Starting Virtual Console Setup...
oct. 29 17:50:21 family-pc systemd[1]: Finished Virtual Console Setup.
oct. 29 17:50:21 family-pc systemd[1]: Finished Permit User Sessions.
oct. 29 17:50:21 family-pc systemd[1]: Started Command Scheduler.
oct. 29 17:50:21 family-pc systemd[1]: Started Simple Desktop Display Manager.
oct. 29 17:50:21 family-pc sshd[652]: Server listening on 0.0.0.0 port 22.
8

your actual network device was mentioned and activated
the other one (wherever it came from ) didnā€™t induce significant slow down

I canā€™t either.

But before you embark on a journey to find the cause:

is this the cause that causes your slow boot?

My answer:
no, it isnā€™t.

You use an HDD - as I do.
A spinning disk.

They are slow.

A minute or two until you get to the desktop ā€¦ is normal.

as I said earlier

1 Like
9

May be Iā€™m wrong but I thing the issue is related to the waiting time for the mentioned device

`oct. 29 17:50:21 family-pc systemd[1]: Timed out waiting for device /sys/subsystem/net/devices/wlan0.conf.`

as there is a jump in the time from 17:49:27 to 17:50:21

oct. 29 17:49:27 family-pc systemd[1]: systemd-hostnamed.service: Deactivated successfully.
oct. 29 17:50:21 family-pc systemd[1]: sys-subsystem-net-devices-wlan0.conf.device: Job sys-subsystem-net-devices-wlan0.conf.device/start timed out.
10

You are not wrong.
But your conclusion, that that is the reason for your long boot time.
is still wrong - at least: inconclusive

Where is the useless wlan0.conf come from?

I donā€™t know.

Itā€™s still not the reason for your slow boot ā€¦

maybe you are - maybe you are not
I donā€™t think you are.
But I donā€™t know for sure.

11

Whatā€™s in this file, if it exists?:

cat /sys/subsystem/net/devices/wlan0.conf
12

No such file or directory

2 Likes
13

There is some configuration you have which wants to start a device which you donā€™t even have - or which you do not have anymore.
I do not know how to find it.
Somewhere in /etc probably ā€¦

I searched for the message
sys subsystem net devices timeout
and read through some of the results.

here are a few that could be relevant - I canā€™t help further

[SOLVED] Timed out waiting for device sys-subsystem-net-devices- / Newbie Corner / Arch Linux Forums

netctl - ArchWiki
(this one should not be active, I think - NetworkManager is the default in Manjaro)

[SOLVED] a start job is running for sys-subsystem-net-devices.. / Newbie Corner / Arch Linux Forums

Solved: systemd boot waits 90 seconds on net-devices-eth0

14

@hafid

If you are unfamiliar with using the command-line to produce logs, manjaro-log-helper (a GUI application) may be helpful.

sudo pacman -S manjaro-log-helper

There is also this tutorial with focus on the more traditional methods for generating logs via a terminal:

15

I am guessing that you have an invalid configuration pointing to a non-existing network interface.

This could be caused by following a guide from somewhere on the interweb which assumes the wifi network device is wlan0 - which it rarely is - except maybe for a raspberry pi.

4 Likes
16

Probably! I donā€™t remember! may be a long time ago and just now I figure out that there is a boot time issue. I want to cancel the faulty configuration but I donā€™t know how.

17

Iā€™d have advised to use mc or some other file managers search function ā€¦
Did you think of that?

It may be clumsy, but these commands should find something:

Search the entire /etc directory recursively for a file with that string (wlan0 or wlan0.conf) in it:

sudo grep -rnwl /etc/ -e wlan0

See what comes up.

Search for a file named wlan0.conf anywhwere in the /etc directory:

sudo find /etc -type f -name "wlan0.conf"

Search other directories instead of /etc
for example where all the default systemd service files are

sudo grep -rnwl /usr/lib/systemd/ -e wlan0

sudo find /usr/lib/systemd -type f -name "wlan0.conf"

7 Likes
18

You could try to search for a file with wlan0 as part of the filename

find /etc -name '*wlan0*'

Or for a file containing a reference to wlan0

grep -rl /etc 'wlan0'

Donā€™t be rash with the rm command - inspect the file - it could be innocent..

Note: expect permission errors if a file or folder is only accessible to a specific user or group.

4 Likes
19

I found the file /etc/systemd/system/multi-user.target.wants/wpa_supplicant@wlan0.conf.service

I have disabled the systemd service and reboot

systemd-analyze
Startup finished in 2.567s (kernel) + 16.490s (userspace) = 19.057s 
graphical.target reached after 14.812s in userspace.

which is much much better! So thanks to everyone for the valuable help

3 Likes
20

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.