Hello everyone,
I needed to install manjaro for school and it seems great so far. I have a little experience with linux, so i am a noob to this, but i can not figure out why my boot is so slow as 15 minutes.
I have a i7 4770k and a SSD hard disk, so it should not take this long. I have seen others on this forum with slow boots (40 seconds), but mostly they get told to buy ssd because it just takes long.
Thank you for your time, i appreciate all help!
systemd-analyze:
Startup finished in 6.932s (firmware) + 5.294s (loader) + 1.841s (kernel) + 3.281s (userspace) = 17.349s
graphical.target reached after 2.092s in userspace
systemd-analyze blaze:
1.174s tlp.service
751ms lvm2-monitor.service
736ms apparmor.service
632ms dev-sda3.device
538ms snapd.service
394ms systemd-random-seed.service
357ms dev-loop1.device
308ms polkit.service
296ms dev-loop4.device
251ms var-lib-snapd-snap-arduino-61.mount
250ms var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1804-161.mount
248ms var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1515.mount
243ms var-lib-snapd-snap-core18-2074.mount
242ms dev-loop3.device
241ms var-lib-snapd-snap-snapd-12398.mount
221ms dev-loop2.device
215ms avahi-daemon.service
211ms dev-loop0.device
195ms NetworkManager.service
186ms udisks2.service
159ms systemd-logind.service
158ms systemd-udev-trigger.service
133ms systemd-journal-flush.service
126ms user@1000.service
97ms ModemManager.service
89ms systemd-journald.service
86ms snapd.apparmor.service
83ms cups.service
78ms upower.service
78ms systemd-udevd.service
61ms modprobe@drm.service
54ms boot-efi.mount
44ms systemd-tmpfiles-setup-dev.service
40ms systemd-fsck@dev-disk-by\x2duuid-2CF1\x2dC75C.service
39ms systemd-tmpfiles-clean.service
38ms tmp.mount
38ms systemd-modules-load.service
33ms modprobe@fuse.service
28ms linux-module-cleanup.service
25ms systemd-tmpfiles-setup.service
23ms sys-kernel-config.mount
21ms systemd-rfkill.service
18ms systemd-remount-fs.service
18ms systemd-binfmt.service
17ms bluetooth.service
17ms systemd-user-sessions.service
15ms wpa_supplicant.service
15ms dev-hugepages.mount
15ms systemd-update-utmp.service
15ms dev-mqueue.mount
14ms sys-kernel-debug.mount
13ms sys-kernel-tracing.mount
12ms kmod-static-nodes.service
11ms modprobe@configfs.service
10ms systemd-backlight@backlight:intel_backlight.service
9ms proc-sys-fs-binfmt_misc.mount
8ms user-runtime-dir@1000.service
7ms systemd-sysctl.service
5ms rtkit-daemon.service
4ms alsa-restore.service
3ms sys-fs-fuse-connections.mount
892us snapd.socket
vs
doesn’t add up.
The machine is booting fast enough, it certainly doesn’t take 15 minutes.
$ journalctl -b -p err
2 Likes
Since the it is not problem of the system services (they load in 20sec) I would rather say it is this KDE, which takes so long.
systemd-analyze just counts until it reach the graphical target. At this time SDDM and KDE starts.
1 Like
I have an hp laptop, so it shows the hp logo first, then when that disappears, 15 minutes later i’m in the login screen.
journalctl -b -p err:
Thanks! now i have some real errors to work with i’ll look them up online to see if i can find anything interesting
ah, makes sense. Thank you
Do you see the same behaviour when booting a live usb?https://wiki.manjaro.org/index.php/Manjaro_Kernels#Terminal_Commands
1 Like
I did not have these problems with live usb or other kernals. I have however found out that it is a video problem. if i wait 20 seconds for it to boot, it works. the screen is just black. i can fix it by closing and opening my laptop after those 20 seconds and it works. not the best solution, but it works like a charm and doesn’t seem to really effect performance or cause problems. Thank you everyone that gave advice and helped!
caho
17 July 2021 16:35
9
I had the same problem some times ago. The result was, that I had configured random background pictures-show from my nas in the system-settings. There are over 10.000 pictures and kde indicates these pictures every login. During this indication (more than 15 minutes) the computer was unusable.
My solution was to deactivate the picture-show and switch to a single background picture. Since this time the system starts very fast as expected.
Perhaps do you have the same problem …
1.701s systemd-random-seed.service
436ms apparmor.service
399ms tlp.service
364ms lvm2-monitor.service
362ms home-carsten-NAS\x2d2.mount
232ms dev-nvme0n1p2.device
203ms cups.service
180ms boot-efi.mount
172ms snapd.service
164ms user@1027.service
115ms polkit.service
96ms systemd-udev-trigger.service
84ms upower.service
76ms home-carsten-NAS\x2d2\x2dBilder.mount
75ms ModemManager.service
61ms systemd-journald.service
60ms avahi-daemon.service
56ms udisks2.service
55ms NetworkManager.service
52ms systemd-timesyncd.service
52ms systemd-udevd.service
51ms modprobe@drm.service
50ms systemd-journal-flush.service
48ms dev-disk-by\x2duuid-8ad2f757\x2d948e\x2d4040\x2dbe3a\x2d11e385ab1f21.swap
42ms systemd-logind.service
31ms systemd-tmpfiles-clean.service
30ms systemd-fsck-root.service
29ms colord.service
27ms systemd-modules-load.service
27ms snapd.apparmor.service
27ms systemd-fsck@dev-disk-by\x2duuid-A082\x2d2FA5.service
55ms NetworkManager.service
52ms systemd-timesyncd.service
52ms systemd-udevd.service
51ms modprobe@drm.service
50ms systemd-journal-flush.service
48ms dev-disk-by\x2duuid-8ad2f757\x2d948e\x2d4040\x2dbe3a\x2d11e385ab1f21.swap
42ms systemd-logind.service
31ms systemd-tmpfiles-clean.service
30ms systemd-fsck-root.service
29ms colord.service
27ms systemd-modules-load.service
27ms snapd.apparmor.service
27ms systemd-fsck@dev-disk-by\x2duuid-A082\x2d2FA5.service
24ms NetworkManager-wait-online.service
21ms modprobe@fuse.service
19ms systemd-tmpfiles-setup.service
18ms dev-hugepages.mount
17ms dev-mqueue.mount
17ms sys-kernel-debug.mount
17ms systemd-tmpfiles-setup-dev.service
16ms sys-kernel-tracing.mount
16ms systemd-binfmt.service
15ms kmod-static-nodes.service
14ms systemd-update-utmp.service
14ms bluetooth.service
13ms modprobe@configfs.service
13ms rtkit-daemon.service
12ms wpa_supplicant.service
11ms user-runtime-dir@1027.service
System: Kernel: 5.13.1-3-MANJARO x86_64 bits: 64 Desktop: KDE Plasma 5.22.3 Distro: Manjaro Linux
Machine: Type: Laptop System: TUXEDO product: TUXEDO Pulse 15 Gen1 v: Standard serial: <filter>
Mobo: TUXEDO s model: PULSE1501 v: Standard serial: <filter> UEFI: American Megatrends v: N.1.07.A02
date: 12/08/2020
Battery: ID-1: BAT0 charge: 81.6 Wh (89.1%) condition: 91.6/91.6 Wh (100.0%)
CPU: Info: 8-Core model: AMD Ryzen 7 4800H with Radeon Graphics bits: 64 type: MT MCP cache: L2: 4 MiB
Speed: 1397 MHz min/max: 1400/2900 MHz Core speeds (MHz): 1: 1397 2: 1838 3: 1397 4: 1397 5: 1397 6: 1397 7: 1397
8: 1397 9: 1289 10: 1394 11: 1273 12: 1279 13: 1393 14: 1298 15: 1397 16: 1397
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Renoir driver: amdgpu v: kernel
Device-2: Chicony HD Webcam type: USB driver: uvcvideo
Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati unloaded: modesetting resolution: 1920x1080~60Hz
OpenGL: renderer: AMD RENOIR (DRM 3.41.0 5.13.1-3-MANJARO LLVM 12.0.0) v: 4.6 Mesa 21.1.4
Audio: Device-1: Advanced Micro Devices [AMD/ATI] driver: snd_hda_intel
Device-2: Advanced Micro Devices [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor driver: N/A
Device-3: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel
Sound Server-1: ALSA v: k5.13.1-3-MANJARO running: yes
Sound Server-2: PulseAudio v: 14.2 running: yes
Network: Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi
IF: wlp1s0 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
IF: eno1 state: down mac: <filter>
Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb
Report: rfkill ID: hci0 rfk-id: 1 state: down bt-service: enabled,running rfk-block: hardware: no software: yes
address: see --recommends
Drives: Local Storage: total: 232.89 GiB used: 35.33 GiB (15.2%)
ID-1: /dev/nvme0n1 vendor: Kingston model: SA2000M8250G size: 232.89 GiB
Partition: ID-1: / size: 219.86 GiB used: 35.33 GiB (16.1%) fs: ext4 dev: /dev/nvme0n1p2
ID-2: /boot/efi size: 511 MiB used: 304 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1
Swap: ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) dev: /dev/nvme0n1p3
Sensors: System Temperatures: cpu: 36.5 C mobo: 35.0 C gpu: amdgpu temp: 35.0 C
Fan Speeds (RPM): N/A
Info: Processes: 311 Uptime: 22m Memory: 7.19 GiB used: 1.48 GiB (20.6%) Shell: Bash inxi: 3.3.05
regards
1 Like
I hadn’t done that yet. I tried it with both amdgpu and radeaon, but it didn’t change anything. I am okay with the way it works now though, i can at least use my laptop again.
I can see that taking a while hahaha. Thanks for the suggestion, but that is not happening in my case. i haven’t connected to the internet and only have the OS images on my laptop
1 Like