When I used OpenRC the plymouth has shown the boot progress (in progress bar and percentage). However on systemd it shows neither (it stays at 0% until gdm starts). Might be also related: - dracut asks about cryptsetup password in console
Seems like Systemd issue. Although it's strange since Plymouth was developed on Fedora which came with Systemd in the first place. Is it possible to somehow use both OpenRC and systemd? If so and you're somehow doing that, that might be a source of the problem. Please attach systemd and plymouth package versions with their use flags setup, grub.conf, /etc/plymouth/plymouthd.conf, log from dracut with -L=6 appended.
Created attachment 286559 [details] dracut.log Please note that this particular log is from non-Gentoo supported kernel but it is present on gentoo-sources as well.
% cat /etc/plymouth/plymouthd.conf # Administrator customizations go in this file #[Daemon] #Theme=fade-in grub.cfg is generated: % cat /etc/default/grub # Copyright 1999-2011 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 # $Header: /var/cvsroot/gentoo-x86/sys-boot/grub/files/grub.default,v 1.2 2011/08/30 06:45:04 scarabeus Exp $ # # To populate all changes in this file you need to regenerate your # grub configuration file afterwards: # 'grub2-mkconfig -o /boot/grub2/grub.cfg' # # See the grub info page for documentation on possible variables and # their associated values. GRUB_DEFAULT=0 GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=10 GRUB_CMDLINE_LINUX_DEFAULT="usbcore.autosuspend=5 init=/bin/systemd vconsole.keymap=uk vconsole.unicode=1 rd.lvm.vg=<VG> rd.lvm.lv=<LV> rd.md=0 rd.dm=0 rd.luks.uuid=<LUKS_UUID> splash=silent,fadein,fadeout,theme:natural_gentoo console=tty1 plymouth:force-splash quiet" GRUB_CMDLINE_LINUX="" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=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=640x480 # Background image used on graphical terminal. # Can be in various bitmap formats. #GRUB_BACKGROUND="/boot/grub2/mybackground.png" # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to kernel #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY=true
I don't see 'emerge --info systemd' here :P.
Actually(In reply to comment #4) > I don't see 'emerge --info systemd' here :P. Actually please attach output of "emerge --info systemd plymouth dracut openrc plymouth-plugin".
(In reply to comment #5) > Actually(In reply to comment #4) > > I don't see 'emerge --info systemd' here :P. > > Actually please attach output of "emerge --info systemd plymouth dracut openrc > plymouth-plugin". Typo. Should be: plymouth-openrc-plugin
Created attachment 286663 [details] cave info sys-apps/systemd plymouth dracut plymouth-openrc-plugin
(In reply to comment #7) > Created attachment 286663 [details] > cave info sys-apps/systemd plymouth dracut plymouth-openrc-plugin Why do you use plymouth-openrc-plugin? Systemd handles plymouth itself - probably much better (I guess plymouth main dev. has written support himself) than my rough plugin for OpenRC?
(In reply to comment #8) > (In reply to comment #7) > > Created attachment 286663 [details] > > cave info sys-apps/systemd plymouth dracut plymouth-openrc-plugin > > Why do you use plymouth-openrc-plugin? Systemd handles plymouth itself - > probably much better (I guess plymouth main dev. has written support himself) > than my rough plugin for OpenRC? Because I thought that plugin for OpenRC should not interfer with systemd.
> (In reply to comment #8) > > Why do you use plymouth-openrc-plugin? Systemd handles plymouth itself - > > probably much better (I guess plymouth main dev. has written support himself) > > than my rough plugin for OpenRC? > > Because I thought that plugin for OpenRC should not interfer with systemd. Hm, right. It should not. In fact it shouldn't be allowed to have systemd and plymouth-openrc-plugin. I'm blocking sys-apps/systemd for plymouth-openrc-plugin. Please use bare systemd support for plymouth. Does it solve the issue for you?
Since the bug is still open I add my experience: for me the progress bar works, and I use systemd to boot the OS. I used plymouth-0.8.8 (see bug #430478 I have bumped the ebuild myself). The only problem I have is: I think plymouth starts too late (when it asks me for the crypt password). But this is a dracut problem I think.
There is absolutely no need to block systemd in plymouth-openrc-plugin. Warning the user is enough. This makes impossible to use systemd as device manager while still booting with openrc.
Fixed in TOT.