Start, restart or shutdown too too slow

Hello hello everyone :slight_smile:
I’ve recently installed Manjaro Linux Kde Plasma it takes long time when i start,restart or shutdown
i was planning to install it again :pleading_face:
im super noob sorry and im not good enough in english but i will learn how to use linux under your help :innocent:

    ~  inxi --full --verbosity=7 --filter --no-host              ✔ 
  Kernel: 5.13.19-2-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0
  Desktop: KDE Plasma 5.23.3 tk: Qt 5.15.2 wm: kwin_x11 vt: 1
  dm: SDDM Distro: Manjaro Linux base: Arch Linux
  Type: Desktop Mobo: ASRock model: Z370 Gaming K6
  serial: <superuser required> UEFI: American Megatrends v: P1.20
  date: 10/26/2017
  Message: No system battery data found. Is one present?
  RAM: total: 15.55 GiB used: 2.92 GiB (18.8%)
  RAM Report:
  permissions: Unable to run dmidecode. Root privileges required.
  Info: 6-Core model: Intel Core i7-8700K bits: 64 type: MT MCP
  arch: Kaby Lake note: check rev: A cache: L1: 384 KiB L2: 1.5 MiB
  L3: 12 MiB bogomips: 88824
  Speed: 1923 MHz min/max: 800/4700 MHz Core speeds (MHz): 1: 800
  2: 800 3: 865 4: 1936 5: 1677 6: 815 7: 1091 8: 1537 9: 2187
  10: 1652 11: 1403 12: 800
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
  arch_perfmon art avx avx2 bmi1 bmi2 bts clflush clflushopt cmov
  constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts
  epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
  fsgsbase fxsr hle ht hwp hwp_act_window hwp_epp hwp_notify ibpb
  ibrs ida intel_pt invpcid invpcid_single lahf_lm lm mca mce
  md_clear mmx monitor movbe mpx msr mtrr nonstop_tsc nopl nx pae pat
  pbe pcid pclmulqdq pdcm pdpe1gb pebs pge pln pni popcnt pse pse36
  pti pts rdrand rdseed rdtscp rep_good rtm sdbg sep smap smep smx ss
  ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow
  tsc tsc_adjust tsc_deadline_timer vme vmx vnmi vpid x2apic xgetbv1
  xsave xsavec xsaveopt xsaves xtopology xtpr
  Device-1: NVIDIA GP104 [GeForce GTX 1080] vendor: Micro-Star MSI
  driver: nvidia v: 495.44 bus-ID: 01:00.0 chip-ID: 10de:1b80
  class-ID: 0300
  Display: x11 server: X.Org compositor: kwin_x11 driver:
  loaded: nvidia resolution: 1920x1080 s-dpi: 81
  OpenGL: renderer: NVIDIA GeForce GTX 1080/PCIe/SSE2
  v: 4.6.0 NVIDIA 495.44 direct render: Yes
  Device-1: Intel 200 Series PCH HD Audio vendor: ASRock
  driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a2f0
  class-ID: 0403
  Device-2: NVIDIA GP104 High Definition Audio vendor: Micro-Star MSI
  driver: snd_hda_intel v: kernel bus-ID: 01:00.1 chip-ID: 10de:10f0
  class-ID: 0403
  Device-3: Creative Sound BlasterX H7 type: USB
  driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-1:2
  chip-ID: 041e:3242 class-ID: 0300 serial: <filter>
  Sound Server-1: ALSA v: k5.13.19-2-MANJARO running: yes
  Sound Server-2: JACK v: 1.9.19 running: no
  Sound Server-3: PulseAudio v: 15.0 running: yes
  Sound Server-4: PipeWire v: 0.3.40 running: yes
  Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e
  v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8
  class-ID: 0200
  IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
  broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  Device-2: Intel I211 Gigabit Network vendor: ASRock driver: igb
  v: kernel port: c000 bus-ID: 05:00.0 chip-ID: 8086:1539
  class-ID: 0200
  IF: enp5s0 state: down mac: <filter>
  WAN IP: <filter>
  Message: No bluetooth data found.
  Message: No logical block device data found.
  Message: No RAID data found.
  Local Storage: total: 1.38 TiB used: 25.5 GiB (1.8%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB512HAJQ-000H1
  size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 type: SSD
  serial: <filter> rev: EXA72H1Q temp: 38.9 C scheme: GPT
  ID-2: /dev/sda vendor: Western Digital model: WD10EZRZ-00HTKB0
  size: 931.51 GiB speed: 6.0 Gb/s type: HDD rpm: 5400
  serial: <filter> rev: 1A01 scheme: MBR
  Message: No optical or floppy data found.
  ID-1: / size: 468.09 GiB used: 25.5 GiB (5.4%) fs: ext4
  dev: /dev/nvme0n1p2 label: N/A
  uuid: 1c8d7b9c-7d11-41f3-b9f3-8b660cf28d00
  ID-2: /boot/efi size: 299.4 MiB used: 288 KiB (0.1%) fs: vfat
  dev: /dev/nvme0n1p1 label: NO_LABEL uuid: 340B-00F4
  Alert: No swap data was found.
  ID-1: /dev/sda1 size: 931.51 GiB fs: ntfs label: Karim
  uuid: 9C700C9E700C816E
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 16 rev: 2.0
  speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 1-1:2 info: Creative Sound BlasterX H7 type: Audio,HID
  driver: hid-generic,snd-usb-audio,usbhid interfaces: 4 rev: 2.0
  speed: 12 Mb/s power: 100mA chip-ID: 041e:3242 class-ID: 0300
  serial: <filter>
  Hub-2: 1-3:3 info: ASMedia ASM1074 High-Speed hub ports: 4 rev: 2.1
  speed: 480 Mb/s power: 100mA chip-ID: 174c:2074 class-ID: 0900
  Device-1: 1-9:4 info: Corsair K95 RGB Platinum Keyboard [RGP0056]
  type: Keyboard,HID driver: hid-generic,usbhid interfaces: 2
  rev: 2.0 speed: 12 Mb/s power: 500mA chip-ID: 1b1c:1b2d
  class-ID: 0300 serial: <filter>
  Device-2: 1-11:5 info: Cooler Master ARGB LED Controller
  type: HID,Keyboard driver: hid-generic,usbhid interfaces: 2
  rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 2516:1011
  class-ID: 0300 serial: <filter>
  Hub-3: 2-0:1 info: Super-speed hub ports: 10 rev: 3.0 speed: 5 Gb/s
  chip-ID: 1d6b:0003 class-ID: 0900
  Hub-4: 2-7:2 info: ASMedia ASM1074 SuperSpeed hub ports: 4 rev: 3.0
  speed: 5 Gb/s power: 8mA chip-ID: 174c:3074 class-ID: 0900
  Hub-5: 3-0:1 info: Hi-speed hub with single TT ports: 2 rev: 2.0
  speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 3-2:2 info: ASUSTek ROG Gladius II Origin type: Mouse,HID
  driver: hid-generic,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s
  power: 98mA chip-ID: 0b05:1877 class-ID: 0300
  Hub-6: 4-0:1 info: Super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s
  chip-ID: 1d6b:0003 class-ID: 0900
  System Temperatures: cpu: 29.0 C mobo: N/A gpu: nvidia temp: 59 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
  Processes: 289 Uptime: 2h 10m wakeups: 0 Init: systemd v: 249
  Compilers: gcc: 11.1.0 Packages: pacman: 1214 Shell: Zsh v: 5.8
  default: Bash v: 5.1.8 running-in: konsole inxi: 3.3.09
    ~                                                            ✔

What do you call long time exactly?

Also not that it will solve anything but you can give output of these commands:

sudo journalctl -p 3 -xb-1
systemd-analyze blame
systemd-analyze critical-chain

1 Like

Usually on windows when i start, restart or shutdown it takes 2/4 sec
Now when i start, restart or shutdown i feel like the system is freezing i take somtimes about 10/15 sec for the screen to stop display and more 4/6 sec to completely shutdown

– Journal begins at Sun 2021-12-05 21:47:42 CET, ends at Tue 2021-12-07 17:38:44 CET. –
ديسمبر 07 06:38:41 SaiBot kernel: x86/cpu: SGX disabled by BIOS.
ديسمبر 07 06:38:41 SaiBot kernel:
ديسمبر 07 06:39:49 SaiBot pulseaudio[1151]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service ‘org.bluez’: timed out (service_start_timeout=25000ms)
ديسمبر 07 07:50:41 SaiBot pulseaudio[1151]: Error opening PCM device hdmi:1,2: No such file or directory
ديسمبر 07 07:50:41 SaiBot pulseaudio[1151]: Error opening PCM device front:2: No such file or directory
ديسمبر 07 07:50:41 SaiBot pulseaudio[1151]: Error opening PCM device iec958:0: No such file or directory
ديسمبر 07 07:50:41 SaiBot pulseaudio[1151]: Error opening PCM device front:2: No such file or directory

   ~  systemd-analyze blame  :heavy_check_mark:
1.421s systemd-random-seed.service
801ms snapd.service
721ms systemd-modules-load.service
333ms apparmor.service
325ms tlp.service
172ms dev-nvme0n1p2.device
134ms boot-efi.mount
87ms ModemManager.service
80ms user@1000.service
70ms lvm2-monitor.service
64ms systemd-journal-flush.service
63ms polkit.service
59ms udisks2.service
57ms systemd-udev-trigger.service
47ms systemd-udevd.service
42ms upower.service
38ms avahi-daemon.service
35ms NetworkManager.service
35ms systemd-logind.service
33ms systemd-journald.service
30ms systemd-tmpfiles-clean.service
23ms cups.service
16ms systemd-tmpfiles-setup.service
13ms systemd-fsck@dev-disk-by\x2duuid-340B\x2d00F4.service
11ms snapd.apparmor.service
11ms systemd-tmpfiles-setup-dev.service
10ms modprobe@fuse.service
10ms systemd-binfmt.service
8ms dev-hugepages.mount
8ms dev-mqueue.mount
8ms sys-kernel-debug.mount
7ms sys-kernel-tracing.mount
6ms tmp.mount
6ms systemd-remount-fs.service
6ms kmod-static-nodes.service
5ms modprobe@configfs.service
5ms modprobe@drm.service
5ms systemd-sysctl.service
4ms user-runtime-dir@1000.service
4ms systemd-update-utmp.service
4ms systemd-user-sessions.service
4ms alsa-restore.service
4ms linux-module-cleanup.service
2ms rtkit-daemon.service
2ms proc-sys-fs-binfmt_misc.mount
1ms sys-kernel-config.mount
1ms sys-fs-fuse-connections.mount
489us snapd.socket

   ~  systemd-analyze critical-chain  :heavy_check_mark:
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. @1.732s
└─ @1.732s
└─snapd.service @930ms +801ms
└─ @924ms
└─ @924ms
└─snapd.socket @923ms +489us
└─ @921ms
└─systemd-sysctl.service @916ms +5ms
└─systemd-modules-load.service @193ms +721ms
└─systemd-journald.socket @186ms
└─system.slice @176ms
└─-.slice @176ms

From the commands output we can see it loads pretty quick, a couple seconds to reach the desktop (and the PulseAudio errors I guess it is the similar error I get since recently, when you shutdown but that shouldn’t add time to shutdown/reboot).

What can take some time is the GRUB menu at start. You can reduce the wait time (even if the GRUB menu is hidden it will still exist and wait for what is configured in its config), to do so, modify the timeout in /etc/default/grub, for example


and then run sudo update-grub to apply the change.

About Windows, by default it does not shutdown, it hibernates so that makes a huge difference on startup time.

What is output of systemd-analyze before modifying anything?

1 Like

i delete windows i have only manjaro now

   ~  output of systemd-analyze  :heavy_check_mark:
The application output is not installed. It may be found in the following packages:
community/4ti2 1.6.9-2 /usr/bin/output
Do you want to Install package 4ti2? (y/N) y
Executing command: pamac install 4ti2
Synchronizing package databases…
Resolving dependencies…
Checking inter-conflicts…

To install (2):
glpk 5.0-1 (Required By: 4ti2) extra 1.1 MB
4ti2 1.6.9-2 community 933.7 kB

Total download size: 2.1 MB
Total installed size: 4.9 MB

Apply transaction ? [y/N] y
Download of 4ti2 (1.6.9-2) started
Download of glpk (5.0-1) started
Download of 4ti2 (1.6.9-2) finished
Download of glpk (5.0-1) finished
Checking keyring… [2/2]
Checking integrity… [2/2]
Loading packages files… [2/2]
Checking file conflicts… [2/2]
Checking available disk space… [2/2]
Installing glpk (5.0-1)… [1/2]
Installing 4ti2 (1.6.9-2)… [2/2]
Running post-transaction hooks…
Arming ConditionNeedsUpdate… [1/2]
Refreshing PackageKit… [2/2]
Transaction successfully finished.
   ~  GRUB_TIMEOUT=“1”  127 ✘  50s 
   ~   :heavy_check_mark:
   ~  timeout in /etc/default/grub  :heavy_check_mark:
timeout: invalid time interval ‘in’
Try ‘timeout --help’ for more information.
   ~  sudo update-grub  125 ✘
[sudo] password for abdelkrim:
Generating grub configuration file …
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.13-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.13-x86_64.img
Found initrd fallback image: /boot/initramfs-5.13-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.

If you’re not trolling, look what I wrote and look what you wrote… You literally copied my sentence in the terminal, instead of the obviously highlighted command, the one you previously typed before… And you blindly installed a package too…

Give output of command systemd-analyze

Do not randomly copy pieces of sentences and type them in the terminal. Do not do things you do not understand and do not install random things when your terminal interprets sentences you copy from the internet as unknown commands.

1 Like

ok and thx i really appreciate your help

   ~  systemd-analyze  :heavy_check_mark:
Startup finished in 10.207s (firmware) + 5.191s (loader) + 1.795s (kernel) + 1.838s (userspace) = 19.032s reached after 1.604s in userspace

This is your BIOS starting up, you can’t really do anything about it

This should be the GRUB menu I was talking about, we may be able to reduce that a little bit.

This is the kernel loading, it’s pretty fast

This is the “desktop” starting loading, pretty fast too.

So if you want to reduce the timeout time for GRUB you can edit the GRUB config file, make sure to not do random things I did not tell you to do. Open the config file with command kate /etc/default/grub it should open the file in the graphical text editor Kate.

Find the line where the timeout is defined, and modify it, I think in your default config file it should be a value of 5 seconds, so modify it to 1 for example.

So if it was 5 seconds, it should look like this


so modify the line to


Click the save button, it will ask for your password because it is a system protected file.

When the file is saved, close the Kate text editor, and in the terminal run the command sudo update-grub to apply the changes.

Then reboot, and run the command systemd-analyze again to see the result. It should boot faster now.

1 Like

@omano god bless you thank you for your time it is much better now

for the bios what if i update bios to the last version is there a chance for a little change in performance is no i prefer not to update

and this is my first and the most important lesson i save it
Do not randomly copy pieces of sentences and type them in the terminal. Do not do things you do not understand and do not install random things when your terminal interprets sentences you copy from the internet as unknown commands
i will and thx again :innocent:

1 Like

I doubt updating the BIOS update would change anything regarding the boot time. Also updating the BIOS has the side effect to reset the OS boot option, and most motherboard can not auto detect the Manjaro installation automatically, and you would probably need to have a live Manjaro USB ready on hand to detect and boot on Manjaro after BIOS update, and restore GRUB from there.

1 Like

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