Hello hello everyone
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
im super noob sorry and im not good enough in english but i will learn how to use linux under your help
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 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.
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
GRUB_TIMEOUT="1"
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?
~ output of systemd-analyze
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
Preparing…
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
~
~ timeout in /etc/default/grub
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.
done
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.
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
GRUB_TIMEOUT="5"
so modify the line to
GRUB_TIMEOUT="1"
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.
@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
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.