Can't set Boot splash screen， setting boot splash in Appearance fails

ling · 9 October 2023 10:40

When I set a new splash from the options below, I can only see the configured content when shutting down, while during startup, there’s only a rotating circle.

what should I do? Thanks for everyone’s answers!

michaldybczak · 9 October 2023 17:02

Something is off based on your screenshot. You should have miniatures like that:

Also, you don’t have the default system splash screens like Breeze, Breath, that come from packages. It looks like you are missing some plasma core packages…

Ah, wait. You have Boot Splash Screen. That’s something atypical. Sorry, I’m not sure where did you get it from. Is that some optional package? If so, which one?

Zesko · 9 October 2023 17:25

I guess, he installed the package plymouth-kcm which requires its dependency plymouth but requires root permission.

ling · 10 October 2023 00:57

These are all the related packages of plymouth that I installed. They should come with the system. I have not installed other similar packages.

# sudo pacman -Qs plymouth                                                                                                                                                   
local/plymouth 22.02.122-14
    A graphical boot splash screen with kernel mode-setting support
local/plymouth-kcm 5.27.8-1 (plasma)
    KCM to manage the Plymouth (Boot) theme
local/plymouth-theme-manjaro 2.2-1
    Plymouth theme for Manjaro

ling · 10 October 2023 01:15

Also some info, I was having trouble solving another problem after running this command:

sudo mkinitcpio -P

this is the content of /etc/mkinitcpio.conf

# 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=(usbhid xhci_hcd)
MODULES=""

# 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 modconf block filesystems fsck)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev modconf block filesystems fsck)
#
##   This setup assembles a mdadm array with an encrypted root file system.
##   Note: See 'mkinitcpio -H mdadm_udev' for more information on RAID devices.
#    HOOKS=(base udev modconf keyboard keymap consolefont block mdadm_udev encrypt filesystems fsck)
#
##   This setup loads an lvm2 volume group.
#    HOOKS=(base udev modconf block lvm2 filesystems fsck)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr and fsck hooks.
HOOKS="base udev autodetect modconf block keyboard keymap consolefont plymouth filesystems fsck"

# 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="zstd"

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

# MODULES_DECOMPRESS
# Decompress kernel modules during initramfs creation.
# Enable to speedup boot process, disable to save RAM
# during early userspace. Switch (yes/no).
#MODULES_DECOMPRESS="yes"

and when I reinstall plymouth-theme-manjaro

sudo pacman -S plymouth-theme-manjaro

the output is

Set plymouth theme manjaro

==> Building image from preset: /etc/mkinitcpio.d/linux65.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.5-x86_64 -g /boot/initramfs-6.5-x86_64.img --microcode /boot/amd-ucode.img
==> Starting build: '6.5.5-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [plymouth]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.5-x86_64.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux65.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.5-x86_64 -g /boot/initramfs-6.5-x86_64-fallback.img -S autodetect --microcode /boot/amd-ucode.img
==> Starting build: '6.5.5-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [plymouth]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.5-x86_64-fallback.img'
==> Image generation successful

Done

cscs · 10 October 2023 02:02

No real ‘problems’ there. and plymouth is present.

Though you should make sure to run sudo update-grub after mkinitcpio.

ling · 10 October 2023 03:14

I referred to this page
wiki.archlinuxcn Plymouth
The method of using command line switching is effective

sudo plymouth-set-default-theme -R theme

If you only set it in the GUI, it will only take effect on the shutdown screen. This problem should be a systemsetting bug.

Aragorn · 10 October 2023 04:19

Wow, that syntax is already long outdated. Yes, it’ll work, but the syntax was already long ago changed from…

HOOKS="item1 item2 item3..."

… to…

HOOKS=( item1 item2 item3 ... )

This should have been evident from an earlier /etc/mkinitcpio.conf.pacnew file.

You must always inspect your .pacnew files and merge them in with your existing configuration files — do not blindly copy them over your existing configuration files, but look at them and merge in the changes if need be.

ling · 10 October 2023 04:32

The contents of this file are default and I have not modified them.

system · 12 October 2023 18:32

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