[RESOLVED] Boot times at almost two minutes!

ThreeOfSpades001 · 2026-02-01 01:44:30

While i know this was posted before, the answer I found there did not match my problem. the output of some important commands for this issue are:

 $systemd-analyze
Startup finished in 11.374s (firmware) + 6.109s (loader) + 774ms (kernel) + 3.076s (initrd) + 1min 30.632s (userspace) = 1min 51.966s 
graphical.target reached after 1min 30.631s in userspace.

and...

$ systemd-analyze critical-chain 
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @1min 30.631s
└─gdm.service @1min 30.603s +28ms
  └─systemd-user-sessions.service @1min 30.490s +111ms
    └─network.target @1min 30.488s
      └─wpa_supplicant@wlo1.service @1.553s
        └─basic.target @1.537s
          └─dbus-broker.service @1.473s +47ms
            └─dbus.socket @1.463s +76us
              └─sysinit.target @1.462s
                └─systemd-vconsole-setup.service @1min 30.497s +111ms
                  └─systemd-journald.socket
                    └─system.slice
                      └─-.slice

there doesn't seem to be any absurd times in the output from

 systemd-analize blame

the highest times are only around 3 seconds.
oh, and this only started once i set up wpa_supplicant. that's probably important.

Last edited by ThreeOfSpades001 (2026-02-01 15:00:50)

seth · 2026-02-01 10:16:52

The gap is

    └─network.target @1min 30.488s
      └─wpa_supplicant@wlo1.service @1.553s

and 90s is the systemd timeout. Check the system journal for whether and which service fails.
Sanity check:
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

ThreeOfSpades001 · 2026-02-01 14:38:10

Firstly, the requested command:

$ find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
bluetooth.service                        | bluetooth.target.wants
dbus-org.bluez.service                   | system
dhcpcd.service                           | multi-user.target.wants
display-manager.service                  | system
getty@tty1.service                       | getty.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
seatd.service                            | multi-user.target.wants
systemd-userdbd.socket                   | sockets.target.wants
wireplumber.service                      | pipewire.service.wants
wpa_supplicant@wlo1.conf.service         | multi-user.target.wants
wpa_supplicant@wlo1.service              | multi-user.target.wants
xdg-user-dirs.service                    | graphical-session-pre.target.wants

and now for the relevant failure:

systemd[1]: Timed out waiting for device /sys/subsystem/net/devices/wlo1.conf.

Scimmia · 2026-02-01 14:42:03

Because you have wpa_supplicant@wlo1.conf.service enabled for some reason. There is obviously no device by that name.

ThreeOfSpades001 · 2026-02-01 14:45:25

literally not a clue how that happened, considering i never enabled any wpa_supplicant service other than wpa_supplicant@wlo1.service

Last edited by ThreeOfSpades001 (2026-02-01 14:45:45)

seth · 2026-02-01 14:50:21

The predictable device names and only very theoretically predictable.

ip l

https://wiki.archlinux.org/title/Networ … face_names - if there's only one wifi chip it will return to extremely predictably being wlan0

Scimmia · 2026-02-01 14:53:10

Nothing to do with predictable names, they literally enabled the service for a device called 'wlo1.conf'.

ThreeOfSpades001 · 2026-02-01 14:54:10

mind you, I never enabled it!

seth · 2026-02-01 14:58:50

D'oh.

mind you, I never enabled it!

It din't create itself either - so you enabled it in doubt by running some bogus tool that enabled it.
Disable it and see whether it returns.

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

ThreeOfSpades001 · 2026-02-01 15:02:27

the only tool i used to enable anything was systemctl. now that the device was disabled, boot times are back to normal. if i'm not mistaken, the first time i enabled wpa_supplicant i got a second symlink creation message. for some reason.

seth · 2026-02-01 15:04:39

You could consult your shells history.

ThreeOfSpades001 · 2026-02-01 15:09:52

from the root user, with whom i do many tasks:

# history | grep wpa_supplicant@wlo1.conf.service
  308  systemctl disable wpa_supplicant@wlo1.conf.service
  318  history | grep wpa_supplicant@wlo1.conf.service

and from my own user, with whom i do much less:

$ history | grep wpa_supplicant@wlo1.conf.service
  113  history | grep wpa_supplicant@wlo1.conf.service

quite the mystery.

Arch Linux

#1 2026-02-01 01:44:30

[RESOLVED] Boot times at almost two minutes!

#2 2026-02-01 10:16:52

Re: [RESOLVED] Boot times at almost two minutes!

#3 2026-02-01 14:38:10

Re: [RESOLVED] Boot times at almost two minutes!

#4 2026-02-01 14:42:03

Re: [RESOLVED] Boot times at almost two minutes!

#5 2026-02-01 14:45:25

Re: [RESOLVED] Boot times at almost two minutes!

#6 2026-02-01 14:50:21

Re: [RESOLVED] Boot times at almost two minutes!

#7 2026-02-01 14:53:10

Re: [RESOLVED] Boot times at almost two minutes!

#8 2026-02-01 14:54:10

Re: [RESOLVED] Boot times at almost two minutes!

#9 2026-02-01 14:58:50

Re: [RESOLVED] Boot times at almost two minutes!

#10 2026-02-01 15:02:27

Re: [RESOLVED] Boot times at almost two minutes!

#11 2026-02-01 15:04:39

Re: [RESOLVED] Boot times at almost two minutes!

#12 2026-02-01 15:09:52

Re: [RESOLVED] Boot times at almost two minutes!

Board footer