You are not logged in.

#1 2014-06-09 13:50:25

joseribeiro
Member
Registered: 2013-02-17
Posts: 70

[SOLVED] Plymouth doesn't work

Hello!
Plymouth doesn't work.
I installed plymouth, added plymouth to HOOKS array in /etc/mkinitcpio.conf file, added "quiet splash" to /etc/default/grub file and ran "sudo grub-mkconfig -o /boot/grub/grub.cfg" followed by "sudo plymouth-set-default-theme -R solar".


File /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="piix ide_disk reiserfs"
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 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 filesystems keyboard fsck nvidia"

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

File /etc/default/grub

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable Hidden Menu, and optionally hide the timeout count
#GRUB_HIDDEN_TIMEOUT=5
#GRUB_HIDDEN_TIMEOUT_QUIET=true

# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console

# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=auto

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter 
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx" 
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper 
# modes only.  Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"

# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/path/to/wallpaper"
#GRUB_THEME="/path/to/gfxtheme"

# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"

#GRUB_SAVEDEFAULT="true"

No sucess. Any help?

Last edited by joseribeiro (2015-07-05 18:52:17)

Offline

#2 2014-06-10 06:06:45

Padfoot
Member
Registered: 2010-09-03
Posts: 381

Re: [SOLVED] Plymouth doesn't work

1stly, you haven't specified which video driver you are using. This makes a difference as if it is not a frame-buffer (required with proprietary drivers), you need to set early KMS (open drivers), and early KMS is most certainly not set in your mkinitcpio.conf.

2ndly, have a look at the package coments for plymouth. The newly released 0.9.0 is mostly broken for the majority of Arch users.

Offline

#3 2014-06-10 13:02:28

joseribeiro
Member
Registered: 2013-02-17
Posts: 70

Re: [SOLVED] Plymouth doesn't work

I am using nvidia proprietary driver and plymouth version is 0.9.0-1.

Offline

#4 2014-06-10 15:34:13

Pse
Member
Registered: 2008-03-15
Posts: 383

Re: [SOLVED] Plymouth doesn't work

I don't use Plymouth, but if you edit /etc/mkinitcpio.conf you need to run (as root):

mkinitcpio -p linux

for the changes to take effect.

Offline

#5 2014-06-10 17:06:08

joseribeiro
Member
Registered: 2013-02-17
Posts: 70

Re: [SOLVED] Plymouth doesn't work

When I edit /etc/mkinitcpio.conf I run

sudo plymouth-set-default-theme -R solar

That way I set solar as plymouth theme and rebuild initrd.

Offline

#6 2014-06-10 17:38:35

clfarron4
Member
From: London, UK
Registered: 2013-06-28
Posts: 2,162
Website

Re: [SOLVED] Plymouth doesn't work

joseribeiro wrote:

When I edit /etc/mkinitcpio.conf I run

sudo plymouth-set-default-theme -R solar

That way I set solar as plymouth theme and rebuild initrd.

You still need to run the following command (as Pse said):

mkinitcpio -p linux

Claire is fine.
Problems? I have dysgraphia, so clear and concise please.
My public GPG key for package signing
My x86_64 package repository

Offline

#7 2014-06-10 18:26:46

joseribeiro
Member
Registered: 2013-02-17
Posts: 70

Re: [SOLVED] Plymouth doesn't work

I disagree.
I don't need to run mkinitcpio -p linux if I ran plymouth-set-default-theme -R solar.

See the following terminal output:

# mkinitcpio -p linux

==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.14.6-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [plymouth]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
  -> Running build hook: [nvidia]
Building nvidia modules for 3.14.6-1-ARCH kernel...
Module nvidia/337.25 already installed on kernel 3.14.6-1-ARCH/x86_64
Ok.
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.14.6-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [plymouth]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: smsmdtv
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
  -> Running build hook: [nvidia]
Building nvidia modules for 3.14.6-1-ARCH kernel...
Module nvidia/337.25 already installed on kernel 3.14.6-1-ARCH/x86_64
Ok.
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful

# plymouth-set-default-theme -R solar

==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.14.6-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [plymouth]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
  -> Running build hook: [nvidia]
Building nvidia modules for 3.14.6-1-ARCH kernel...
Module nvidia/337.25 already installed on kernel 3.14.6-1-ARCH/x86_64
Ok.
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.14.6-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [plymouth]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: smsmdtv
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
  -> Running build hook: [nvidia]
Building nvidia modules for 3.14.6-1-ARCH kernel...
Module nvidia/337.25 already installed on kernel 3.14.6-1-ARCH/x86_64
Ok.
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful

They are equivalents. wink

Last edited by joseribeiro (2014-06-10 18:37:29)

Offline

#8 2014-06-10 20:41:16

clfarron4
Member
From: London, UK
Registered: 2013-06-28
Posts: 2,162
Website

Re: [SOLVED] Plymouth doesn't work

OK, I admit I was wrong there.

In that case, what Padfoot says applies.


Claire is fine.
Problems? I have dysgraphia, so clear and concise please.
My public GPG key for package signing
My x86_64 package repository

Offline

#9 2014-06-10 22:00:26

Padfoot
Member
Registered: 2010-09-03
Posts: 381

Re: [SOLVED] Plymouth doesn't work

joseribeiro wrote:

I am using nvidia proprietary driver and plymouth version is 0.9.0-1.

Ok, using the Nvidia proprietary driver means you do not have KMS, so plymouth will require a frame-buffer device.
Is your system booting with EFI or MBR? If EFI, there should be an EFI frame-buffer already. If MBR, then you need to install a framebuffer (see the wiki for uvesafb).

And my second point still holds, plymouth-0.9.0 is mostly broken for the majority of Arch users at the moment, so expect just a blank screen when using it (how do I know? I am the maintainer of the package).

Cheers.

Offline

#10 2014-06-10 22:00:46

joseribeiro
Member
Registered: 2013-02-17
Posts: 70

Re: [SOLVED] Plymouth doesn't work

I downgraded plymouth to version 0.8.8 release 7. I found the package in http://pkgbuild.com/git/aur-mirror.git/.
Now, plymouth works again.
I think my system boots with MBR but I had no need to install a framebuffer.
Thank you, Padfoot. wink

Last edited by joseribeiro (2014-06-11 12:07:41)

Offline

Board footer

Powered by FluxBB