Boot waits 4 seconds after basic.target with no activity

Jujube548 · 2026-01-22 11:35:14

seth wrote:

You could test the behavior w/ various life systems to get different kernels and userspace stacks (eg. the install isos of various distros, grml, knoppix, …)
If they all come back w/ the 4s break it's exceedingly likely a peculiarity of your HW

Major thanks for the help.
I doubt it‘s absolutely a hardware thing because from time to time (every 20 boots or so) I get an instant one without the delay…
I‘ll try some other live isos, but I love arch and my setup so I probably won’t switch.

Last edited by Jujube548 (2026-01-22 11:35:58)

seth · 2026-01-22 14:43:01

I‘ll try some other live isos, but I love arch and my setup so I probably won’t switch.

The main purpose is to rule out that this is specific to your local configuration - if every live distro gives you the same result this points towards a hardware problem.

because from time to time (every 20 boots or so) I get an instant one

Do you happen to have a journal for such boot?

Jujube548 · 2026-01-22 15:09:50

seth wrote:

I‘ll try some other live isos, but I love arch and my setup so I probably won’t switch.
The main purpose is to rule out that this is specific to your local configuration - if every live distro gives you the same result this points towards a hardware problem.
because from time to time (every 20 boots or so) I get an instant one
Do you happen to have a journal for such boot?

Yes, I do want to try other distros.
Any fresh installation of arch has resulted in this.
I‘ll try booting my laptop a few dozen times and if I catch one of those occasions then I will save the journalctl and post it here. One way I‘ve found of increasing the likelihood of it is blacklisting amdgpu, booting without it, then re-enabling it and rebooting. Sometimes that causes a no delay boot while still having graphics acceleration.
Thank you!

Jujube548 · 2026-01-22 21:43:27

seth wrote:

because from time to time (every 20 boots or so) I get an instant one
Do you happen to have a journal for such boot?

Just got one boot with no such lag
https://0x0.st/PPVO.txt
EDIT: somehow my last 5 boots have been without delay as well. Suspect this won't last forever as multiple times before it seemed to be fixed out of nowhere and then restarted acting up. Even if it lasts, i'll only mark this as solved if I figure out the reason for the sudden fix.
EDIT 2: yup back to 4 second wait times.

Last edited by Jujube548 (2026-01-22 22:08:28)

seth · 2026-01-23 10:51:37

Jan 22 22:06:12 archlinux kernel: Linux version 6.18.5-arch1-1 (linux@archlinux) (gcc (GCC) 15.2.1 20260103, GNU ld (GNU Binutils) 2.45.1) #1 SMP PREEMPT_DYNAMIC Sun, 11 Jan 2026 17:10:53 +0000
Jan 22 22:06:14 archlinux systemd-logind[327]: New seat seat0.
Jan 22 22:06:14 archlinux systemd[1]: Started User Login Management.
Jan 22 22:06:14 archlinux iwd[321]: Wireless daemon version 3.10
…
Jan 22 22:06:18 archlinux iwd[321]:         Supported iftypes: ad-hoc station ap
Jan 22 22:06:19 archlinux systemd-logind[327]: New session 'c1' of user 'jules' with class 'user' and type 'wayland'.
Jan 22 22:06:19 archlinux kernel: [drm] amdgpu kernel modesetting enabled.

kms enabled 7s into that boot, *after* your wayland session started.
You might even have been running wayland on the simpledrm device at that point (software emulation)

Idk why amdgpu loads to incredibly late but recommend to add it to the initramfs via the MODULES section of mkinitcpio.conf - screw the 4s dealy, you don't want to run the system on CPU rendering.

Jujube548 · 2026-01-23 16:47:15

seth wrote:

Jan 22 22:06:12 archlinux kernel: Linux version 6.18.5-arch1-1 (linux@archlinux) (gcc (GCC) 15.2.1 20260103, GNU ld (GNU Binutils) 2.45.1) #1 SMP PREEMPT_DYNAMIC Sun, 11 Jan 2026 17:10:53 +0000
Jan 22 22:06:14 archlinux systemd-logind[327]: New seat seat0.
Jan 22 22:06:14 archlinux systemd[1]: Started User Login Management.
Jan 22 22:06:14 archlinux iwd[321]: Wireless daemon version 3.10
…
Jan 22 22:06:18 archlinux iwd[321]:         Supported iftypes: ad-hoc station ap
Jan 22 22:06:19 archlinux systemd-logind[327]: New session 'c1' of user 'jules' with class 'user' and type 'wayland'.
Jan 22 22:06:19 archlinux kernel: [drm] amdgpu kernel modesetting enabled.
kms enabled 7s into that boot, *after* your wayland session started.
You might even have been running wayland on the simpledrm device at that point (software emulation)
Idk why amdgpu loads to incredibly late but recommend to add it to the initramfs via the MODULES section of mkinitcpio.conf - screw the 4s dealy, you don't want to run the system on CPU rendering.

Understood.
Thank you for the help
Looking into budget intel cpu/igpu laptops.
I don’t need a fast laptop or a lot of RAM, just a fast boot. 8GB of ram is plenty for my light use. Any heavy workloads are done on my desktop anyways

Arch Linux

#26 2026-01-22 11:35:14

Re: Boot waits 4 seconds after basic.target with no activity

#27 2026-01-22 14:43:01

Re: Boot waits 4 seconds after basic.target with no activity

#28 2026-01-22 15:09:50

Re: Boot waits 4 seconds after basic.target with no activity

#29 2026-01-22 21:43:27

Re: Boot waits 4 seconds after basic.target with no activity

#30 2026-01-23 10:51:37

Re: Boot waits 4 seconds after basic.target with no activity

#31 2026-01-23 16:47:15

Re: Boot waits 4 seconds after basic.target with no activity

Board footer