Slow boot time compared to windows

[omano]

got you for the hybrid setup

plymouth, yeah maybe that adds up to your boot time

[Avinash]

@nanoone

Does that affect the boot time? If so, can you explain why?
Sorry I just wanna know what that is and why that affects on the system

changing the compression can help in boot time depending upon what’s the bottleneck I/O or decompression time. For me LZ4 gives the best result.

@nanoone

Yes I use a plymouth. I really love it. How much time does that take?

I have noticed a difference by disabling the splash screen on my machine.
Also i have noticed increase in boot times when modules are added in mkinitcpio

[Frenchy]

Yes KDE Plasma desktop DOES take quite some time to boot up, notwithstanding rebooting after big updates which are exasperatingly LONG…! But, hey, it’s as full-featured as it gets and isn’t sluggish when in use. So, some pains, but some big gains!

[nanoone]

Thanks so much for your helpful information

@Avinash

changing the compression can help in boot time depending upon what’s the bottleneck I/O or decompression time. For me LZ4 gives the best result.

How can I accomplish that?

[nanoone]

What’s the difference between splash screen in kde settings and splash in grub?

[Avinash]

@nanoone

# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

Uncomment the line for LZ4, save the file and run the command
sudo mkinitcpio -P

Also test XZ and CAT(uncompressed), for CAT you will have add a line

COMPRESSION="cat"

Keep only one compression uncommented at a time

[TriMoon]

FYI:

@nanoone

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(piix ide_disk reiserfs)
MODULES="amdgpu nvidia nvidia_drm nouveau"

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=""

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect block filesystems)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev block filesystems)
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS=(base udev block mdadm encrypt filesystems)
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS=(base udev block lvm2 filesystems)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS="base udev plymouth autodetect modconf block keyboard keymap resume filesystems"

# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

You should be converting those strings into bash arrays soon, the latest version uses bash arrays instead of strings, they might drop the support for string arrays in future…
An example of a conversion:

• MODULES="amdgpu nvidia nvidia_drm nouveau"
  Would become:

  MODULES=(
     amdgpu
     nvidia
     nvidia_drm
     nouveau
  )
  

  PS: I have these for my single nVidia card:
  • nvidia
  • nvidia_modeset
  • nvidia_uvm
  • nvidia_drm

[Avinash]

Splash screen in KDE setting is like welcome screen in windows and splash in GRUB is like the Windows screen.

I was suggesting to disable the one in KDE settings, GRUB splash screen may also have impact on boot times but i haven’t tested it.

[nanoone]

@TriMoon

the latest version uses bash arrays instead of strings, they might drop the support for string arrays in future

OMG!
Shouldn’t the system do that automatically?!
I mean lots of users like me don’t know that right?

[nanoone]

Thanks so much

[TriMoon]

@nanoone

I mean lots of users like me don’t know that right?

Well it is documented inside the comments if one reads them
But yea i guess they should automate it also…

[nanoone]

Yeah you’re right but I mean lots of people don’t even know about that thing

[TriMoon]

@nanoone

What’s the difference between splash screen in kde settings and splash in grub ?

The splash in KDE is the one you get after clicking the login button while your session is being setup.
The one in grub is during computer boot.

I personally use bootsplash-systemd + bootsplash-theme-manjaro because i don’t use grub as active bootloader but instead use sd-boot…

But anyhow…
Your system boots faster as M$ afaict, if you want it even faster you might try using hibernation like M$ does also…

[nanoone]

Thanks so much for your help

@TriMoon

if you want it even faster you might try using hibernation like M$ does also

Really?!
Windows doesn’t shut down the computer?!

Another question
Bootsplash is the same as plymouth?

[XRaTiX]

@nanoone

Really?!
Windows doesn’t shut down the computer?!

Yes,Windows only hibernate when you press the shutdown button by saving all the processes and other stuff to the disk everytime,you only do a complete shutdown if you hold the shift button and then press the shutdown button,or when you press the restart button.

Shutting Down Doesn’t Fully Shut Down Windows 10 (But Restarting Does)

[nanoone]

OOOOOMMMMMMGGGGGGGG
I didn’t know that
Thanks for informing me

[omano]

And that’s also why you do NOT (and can not by default) access a Win 10 disk from Linux as the file system is in a ‘dirty state’. You need to disable this functionality in windows first to be able to access the disk properly without risking damaging anything from Linux.

PS: also you’re assuming that Linux is one unique thing when talking about Linux being faster than Windows. This is not the case as depending on your desktop environment or the packages installed, this can change a lot the boot time and ‘performance’.

[TriMoon]

@nanoone

Another question
Bootsplash is the same as plymouth?

No they are different.

• Bootsplash is implemented in the kernel (when compiled in)
• Plymouth is a user-space framework.

[nanoone]

Isn’t there such a thing in linux?
I really wanna see a very smooth and flicker-free boot on linux
Because even when I hibernate, after powering my laptop on I can see laggish plymouth
Also another thing
When logging in on sddm, system takes a little bit time to show the titles and icons(my panel is hidden)

[linux-aarhus]

It looks quite normal - but you can’t quite trust that statistic.

The final result depends on how fast you are to input username/password at the graphical login.

You can’t judge by Windows either because Windows uses it’s own fast-boot (which you may or may not have disabled) which swaps the vital memory parts to disk then loads the whole #! from disk - which pretty much skips a lot of device initialization - as device states are among the swapped memory.