1minute 30seconds boot up oFresh Arch Linux Install w/ caelestia dots

drd019 · 2026-05-11 16:16:08

Let me start this message with I am a noob,
I know Linux a bit since I've tried and used Linux, Mint Pop OS, Nobara Linux, and Bazzite for the past year and a half(ish?)
and I know how to do some of the basics.

I Installed arch since it is Lightweight and to be honest it looked pretty friggin cool.
Also sidenote: I have escaped the paradox I already have a fiance (though unofficial for now cuz we still a teeny bit underage)
That aside i tried the manual Install. but I got pretty bored so I just wiped my drive and Used ArhInstall and I know to some that is a crime for a noob but hey I wanted to understand the main parts of it first then go back to the basics and strengthen it so kinda like doing the endgame quests before going back to the main starter quest.

My bad if I'm yapping too long, anyways:
connected myself to the wifi using iwctl
then used archinstall

this is just a speculation but i think it may be the swap (i forgot if I made one or not) or the fact that I selected to copy the wifi from the installation medium

I booted it up and set up caelestia dots and I noticed from the start that it took 1m30s to boot up w/o caelestia but now it's just becoming a hassel

anyways I watched some yt and Ima past some of the stuff yall might need for context

systemd-analyze blame | head -n 20
1.804s dev-mapper-root.device 1.055s systemd-tmpfiles-setup-dev-early.service 955ms systemd-userdbd.service 531ms NetworkManager.service 463ms ldconfig.service 400ms systemd-journal-flush.service 378ms upower.service 336ms systemd-udev-trigger.service 318ms systemd-udevd.service 282ms systemd-networkd.service 267ms systemd-vconsole-setup.service 226ms systemd-tmpfiles-setup.service 211ms user@1000.service 205ms systemd-resolved.service 194ms systemd-journal-catalog-update.service 150ms systemd-update-utmp.service 146ms systemd-journald.service 137ms bluetooth.service 134ms wpa_supplicant.service 131ms power-profiles-daemon.service

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 32.311s
└─multi-user.target @1min 32.310s
└─getty.target @1min 32.309s
└─getty@tty1.service @1min 32.308s
└─systemd-user-sessions.service @1min 32.274s +29ms
└─network.target @1min 32.270s
└─NetworkManager.service @1min 31.737s +531ms
└─basic.target @1min 31.735s
└─dbus-broker.service @1min 31.654s +58ms
└─dbus.socket @1min 31.640s +82us
└─sysinit.target @1min 31.637s
└─systemd-pcrproduct.service @1min 31.620s +16ms
└─systemd-pcrnvdone.service @1min 31.603s +15ms
└─systemd-tpm2-setup.service @1min 31.583s +18ms
└─systemd-tpm2-setup-early.service @1min 31.561s +20ms
└─tpm2.target @1min 31.540s

OS: Arch Linux x86_64
TravelMate P249-G2-M V1.40
Kernel: 7.0.5-arch1-1
Shell: bash 5.3.
Resolution: 1366x768
DE: Hyprland
Terminal: foot
CPU: Intel i5-7200U (4) @ 3.100GHz
GPU: Intel Kaby Lake-U GT2 [HD Graphics 620]

if y'all need more context just tell me and I'll provide and it's not really much of an issue now more like a friggin hassle so I guess I can put up with it a bit for a while

Anybody who helps is much appreciated

Last edited by drd019 (2026-05-12 00:52:00)

seth · 2026-05-11 19:56:45

Please use [code][/code] tags. Edit your post in this regard.

90s is the default systemd timeout, it seems to be the tpm2.target

systemctl status tpm2.target

and in doubt please post your complete system journal for the boot:

sudo journalctl -b | curl -s -H "Accept: application/json, */*" --upload-file - 'https://paste.c-net.org/'

drd019 · 2026-05-12 00:43:46

alright I'll paste the outputs here in a sec

Last edited by drd019 (2026-05-12 00:50:38)

drd019 · 2026-05-12 01:16:58

tpm2.target - Trusted Platform Module
     Loaded: loaded (/usr/lib/systemd/system/tpm2.target; 
enabled-runtime; preset: disabled)
     Active: active since Tue 2026-05-12 08:57:42 PST; 17min ago
 Invocation: 92dbdb572c2f46ed983e06298519b403
       Docs: man:systemd.special(7)

May 12 08:57:42 daydream019 systemd[1]: Reached target Trusted Platform Module.

https://termbin.com/erq4

seth · 2026-05-12 05:50:05

May 12 08:56:12 daydream019 kernel: tpm_crb MSFT0101:00: error -EBUSY: can't request region for resource [mem 0x8ae74000-0x8ae7402f]
May 12 08:56:12 daydream019 kernel: tpm_crb MSFT0101:00: probe with driver tpm_crb failed with error -16
…
May 12 08:56:19 daydream019 systemd[1]: systemd-rfkill.service: Deactivated successfully.
May 12 08:57:42 daydream019 systemd[1]: dev-tpm0.device: Job dev-tpm0.device/start timed out.
May 12 08:57:42 daydream019 systemd[1]: Timed out waiting for device /dev/tpm0.
May 12 08:57:42 daydream019 systemd[1]: dev-tpm0.device: Job dev-tpm0.device/start failed with result 'timeout'.
May 12 08:57:42 daydream019 systemd[1]: dev-tpmrm0.device: Job dev-tpmrm0.device/start timed out.
May 12 08:57:42 daydream019 systemd[1]: Timed out waiting for device /dev/tpmrm0.
May 12 08:57:42 daydream019 systemd[1]: dev-tpmrm0.device: Job dev-tpmrm0.device/start failed with result 'timeout'.
May 12 08:57:42 daydream019 systemd[1]: Reached target Trusted Platform Module.

https://bbs.archlinux.org/viewtopic.php?id=296699
https://github.com/systemd/systemd/issu … ine_page=1

drd019 · 2026-05-12 11:34:42

thank you very much

drd019 · 2026-05-13 14:45:28

the solution worked how do I edit this thing to say it's solved

seth · 2026-05-13 14:47:10

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.

Arch Linux

#1 2026-05-11 16:16:08

1minute 30seconds boot up oFresh Arch Linux Install w/ caelestia dots

#2 2026-05-11 19:56:45

Re: 1minute 30seconds boot up oFresh Arch Linux Install w/ caelestia dots

#3 2026-05-12 00:43:46

Re: 1minute 30seconds boot up oFresh Arch Linux Install w/ caelestia dots

#4 2026-05-12 01:16:58

Re: 1minute 30seconds boot up oFresh Arch Linux Install w/ caelestia dots

#5 2026-05-12 05:50:05

Re: 1minute 30seconds boot up oFresh Arch Linux Install w/ caelestia dots

#6 2026-05-12 11:34:42

Re: 1minute 30seconds boot up oFresh Arch Linux Install w/ caelestia dots

#7 2026-05-13 14:45:28

Re: 1minute 30seconds boot up oFresh Arch Linux Install w/ caelestia dots

#8 2026-05-13 14:47:10

Re: 1minute 30seconds boot up oFresh Arch Linux Install w/ caelestia dots

Board footer