Plymouth is working! How to have a great splash in your box

vorbote · 2012-01-10 15:43:20

priapism wrote:

This is the biggest problem of all: When plymouth is in the hooks, my computer will not shut down or reboot. It gets stuck at the following message: "Unmounting Non-API Filesystems" I have no idea what I'm doing wrong.

I'm having this problem too (similar, though not equal, hardware) and plymouth works fine *only* if you use systemd instead of sysvinit.

h31 · 2012-02-07 21:14:24

vorbote wrote:

priapism wrote:
This is the biggest problem of all: When plymouth is in the hooks, my computer will not shut down or reboot. It gets stuck at the following message: "Unmounting Non-API Filesystems" I have no idea what I'm doing wrong.
I'm having this problem too (similar, though not equal, hardware) and plymouth works fine *only* if you use systemd instead of sysvinit.

I also had it. Try to use the latest git version of plymouth and rebuild initrd. This worked for me.

vorbote · 2012-02-08 00:34:40

h31 wrote:

vorbote wrote:
priapism wrote:
This is the biggest problem of all: When plymouth is in the hooks, my computer will not shut down or reboot. It gets stuck at the following message: "Unmounting Non-API Filesystems" I have no idea what I'm doing wrong.
I'm having this problem too (similar, though not equal, hardware) and plymouth works fine *only* if you use systemd instead of sysvinit.
I also had it. Try to use the latest git version of plymouth and rebuild initrd. This worked for me.

Well, I've always used the git version and the problem went away a couple of weeks back when I did a manual recompile, forcing a fresher snapshot. (Forgot to report here, sorry).

RomaHagen · 2012-02-27 02:49:50

Hi guys,

I've read the whole thread but still did not get it...

Is systemd needed to have a transition from plymouth to X with xf86-video-intel-plymouth and lxdm?

Thanks!

pepedopolous · 2012-04-15 16:53:35

I love Plymouth- when it works! Has anyone else had plymouth break after a recompile???

It works on my Kubuntu partition and it *was* working with Arch until I recompiled Plymouth. I just get a black screen and systemd-fsck messages until ksplash starts...
I have the nvidia proprietary driver and use uvesafb as a framebuffer. I use systemd for init.

I'm pretty darn sure I have everything configured correctly (uvesafb.conf, mkinitcpio.conf, grub.cfg) confugured correctly.
I've tried testing in a tty but nothing happens. Before I had uvesafb sorted there would be an error message but now- nothing.

Many thanks
P

qwerty12 · 2012-04-16 14:40:28

pepedopolous wrote:

Has anyone else had plymouth break after a recompile???

I had plymouth-git break for me the first time I installed it - and this is with a laptop that has an Intel GMA so it's not going to be likely that Plymouth would conflict with my IGP... After trying various orders of the mkinitcpio hook, playing with systemd unit files and trying to invoke it manually in tty2 which failed, I came to the conclusion that a commit must've broken it. I arbitrarily picked this (http://cgit.freedesktop.org/plymouth/co … f989db2c7e) commit and told the plymouth-git package to checkout said commit.

yaourt -G plymouth-git
cd plymouth-git && patch -p0 << "EOF"
--- PKGBUILD 2012-02-17 13:10:20.000000000 +0000
+++ PKGBUILD 2012-04-16 15:23:30.408666932 +0100
@@ -87,11 +87,13 @@
     cd ${_gitname} && git pull origin && cd ..
     msg "The local files are updated."
   else
-    git clone --depth 1 ${_gitroot} ${_gitname}
+    git clone ${_gitroot} ${_gitname}
   fi
   msg "GIT checkout done. Preparing sources..."
 
   cd "${srcdir}"
+  cd ${_gitname} && git checkout 032a30c489ad658bd03b4145806da2f989db2c7e
+  cd "${srcdir}"
   rm -rf ${_gitname}-build
   cp -r ${_gitname} ${_gitname}-build
 
EOF

Now I just need to figure out how I can get it to transition to LightDM properly - I'm sure that LightDM has Plymouth support since I've seen it done in Xubuntu...

Last edited by qwerty12 (2012-04-16 15:24:41)

pepedopolous · 2012-04-16 15:52:46

Thank you! I wouldn't know how to do that on my own, but it worked perfectly and I won't recompile Plymouth unless I really have to.

As much as I like to have cutting-edge stuff, lightdm was slower for me than kdm so I'm gonna stick with that for a while.

qwerty12 · 2012-04-17 19:15:51

pepedopolous wrote:

Thank you!

No problem

As much as I like to have cutting-edge stuff, lightdm was slower for me than kdm so I'm gonna stick with that for a while.

Yeah, KDM is actually my favourite DM but I switched from KDE to XFCE so using KDM now would be overkill...

qwerty12 wrote:

Now I just need to figure out how I can get it to transition to LightDM properly - I'm sure that LightDM has Plymouth support since I've seen it done in Xubuntu...

I couldn't figure this one out (built Ubuntu's Plymouth with all their patches and got a blank screen upon boot for my troubles) but I did get a "psuedo transition" going on. I used Plymouth's configure-time option to use /dev/tty7 which stopped it from going back to tty1 after it was done and set LightDM's GTK Greeter's background to black. With this poor systemd service definition file, when Plymouth's boot animation ends, I see a dark screen and then a cursor followed by LightDM's login prompt.

[Unit]
Description=LightDM Display Manager
After=systemd-user-sessions.service

Conflicts=plymouth-quit.service
After=plymouth-quit.service

[Service]
ExecStart=/usr/sbin/lightdm
StandardOutput=syslog

[Install]
WantedBy=graphical.target

fdservices · 2012-05-13 17:00:50

I have installed plymouth on my netbook which has an intel video chip and I seem to be getting this same problem with the screen going black after a few seconds:

KlavKalashj #147 wrote:

With the 2.14.0 driver I got the same result as with .15 and .16. The only difference I notice from the one in [core] is that the patched ones keep the plymouth background until login screen appears. With the one in [core] the screen repaints with black when X starts.

My problem is that if I try to make the xf86-video-intel-plymouth 2.16.0-1 package I get an error

i810_driver.c:274:23: error: 'struct _vgaHWRec' has no member named 'PIOOffset'

it seems like I need this, can you give me any guidance on how to fix the problem?

Andrew

KlavKalashj · 2012-05-13 18:50:10

fdservices wrote:

I have installed plymouth on my netbook which has an intel video chip and I seem to be getting this same problem with the screen going black after a few seconds:
KlavKalashj #147 wrote:
With the 2.14.0 driver I got the same result as with .15 and .16. The only difference I notice from the one in [core] is that the patched ones keep the plymouth background until login screen appears. With the one in [core] the screen repaints with black when X starts.
My problem is that if I try to make the xf86-video-intel-plymouth 2.16.0-1 package I get an error
i810_driver.c:274:23: error: 'struct _vgaHWRec' has no member named 'PIOOffset'
it seems like I need this, can you give me any guidance on how to fix the problem?
Andrew

Sorry, I abandoned both systemd and plymouth a long time ago, and I actually installed Ubuntu when 12.04 was released (was in the mood for a change) so I don't even use Arch atm. The package you are trying to build is currently unmaintained and hasn't been updated since 28 aug 2011... Try asking Zephyr!

fdservices · 2012-05-13 19:50:20

Zephyr?

qwerty12 · 2012-05-16 17:27:19

fdservices wrote:

Zephyr?

The maintainer (well, not any more, I guess) of the the xf86-video-intel-plymouth package. Anyway, I just tried Zephyr's patches against xf86-video-intel 2.19.0-1 (the version currently in extra) and they applied fine, with only one minor change needed. I don't see a black screen and a switch to tty1 anymore; the Plymouth splash (running on tty7 - as set via its configure parameter) remains on my screen until it's replaced by the KDE splash screen (LightDM is set to automatically log me in). If you want to have a try, (bearing in mind that the patches are intended for a earlier version of xf86-video-intel so oddities may occur - use at your own risk) grab xf86-video-intel from ABS - yaourt -G xf86-video-intel is easier if you have Yaourt installed - and apply this patch to the PKGBUILD:

--- PKGBUILD	2012-05-16 17:52:32.834944306 +0100
+++ PKGBUILD	2012-05-16 18:09:30.414163035 +0100
@@ -18,6 +18,243 @@ sha1sums=('131934cf5e90bd48c883804cc644c
 
 build() {
   cd "${srcdir}/${pkgname}-${pkgver}"
+  patch -Np1 << "EOF"
+Index: xserver-xorg-video-intel/src/intel.h
+===================================================================
+--- xserver-xorg-video-intel.orig/src/intel.h	2011-08-09 10:04:02.184071019 +1000
++++ xserver-xorg-video-intel/src/intel.h	2011-08-09 21:39:33.292370844 +1000
+@@ -436,6 +436,7 @@
+ 	OptionInfoPtr Options;
+ 
+ 	/* Driver phase/state information */
++	Bool starting;
+ 	Bool suspended;
+ 
+ 	enum last_3d last_3d;
+@@ -465,6 +466,7 @@
+ extern int intel_get_pipe_from_crtc_id(drm_intel_bufmgr *bufmgr, xf86CrtcPtr crtc);
+ extern int intel_crtc_id(xf86CrtcPtr crtc);
+ extern int intel_output_dpms_status(xf86OutputPtr output);
++extern void intel_copy_fb(ScrnInfoPtr scrn);
+ 
+ enum DRI2FrameEventType {
+ 	DRI2_SWAP,
+Index: xserver-xorg-video-intel/src/intel_display.c
+===================================================================
+--- xserver-xorg-video-intel.orig/src/intel_display.c	2011-08-09 10:04:02.164071017 +1000
++++ xserver-xorg-video-intel/src/intel_display.c	2011-08-09 21:40:03.962371167 +1000
+@@ -36,6 +36,8 @@
+ #include <errno.h>
+ #include <poll.h>
+ 
++#include <sys/ioctl.h>
++
+ #include "xorgVersion.h"
+ 
+ #include "intel.h"
+@@ -937,6 +939,13 @@
+ 	drmModeConnectorPtr koutput = intel_output->mode_output;
+ 	struct intel_mode *mode = intel_output->mode;
+ 	int i;
++	intel_screen_private *intel = intel_get_screen_private(output->scrn);
++
++	/* xf86Crtc.c calls dpms off in set desired modes, so ignore
++	 * the request if we're starting up. */
++
++	if (intel->starting)
++		return;
+ 
+ 	for (i = 0; i < koutput->count_props; i++) {
+ 		drmModePropertyPtr props;
+@@ -1630,6 +1639,11 @@
+ 	}
+ 
+ 	intel->modes = mode;
++
++#if GET_ABI_MAJOR(ABI_VIDEODRV_VERSION) < 9
++	scrn->canDoBGNoneRoot = TRUE;
++#endif
++
+ 	return TRUE;
+ }
+ 
+@@ -1699,3 +1713,100 @@
+ 	struct intel_crtc *intel_crtc = crtc->driver_private;
+ 	return intel_crtc->pipe;
+ }
++
++static PixmapPtr
++intel_create_pixmap_for_fbcon(ScrnInfoPtr scrn)
++{
++	xf86CrtcConfigPtr xf86_config = XF86_CRTC_CONFIG_PTR(scrn);
++	struct intel_crtc *intel_crtc = xf86_config->crtc[0]->driver_private;
++	ScreenPtr pScreen = screenInfo.screens[scrn->scrnIndex];
++	struct intel_mode *mode = intel_crtc->mode;
++	intel_screen_private *intel = intel_get_screen_private(scrn);
++	drmModeFBPtr fbcon = NULL;
++	struct drm_gem_flink flink;
++	drm_intel_bo *bo;
++	PixmapPtr pixmap = NULL;
++	int i;
++
++	for (i = 0; i < mode->mode_res->count_crtcs; i++) {
++		intel_crtc = xf86_config->crtc[i]->driver_private;
++		if (intel_crtc->mode_crtc->buffer_id == 0)
++			continue;
++		fbcon = drmModeGetFB(mode->fd,
++				     intel_crtc->mode_crtc->buffer_id);
++		if (fbcon != NULL)
++			break;
++	}
++	if (i == mode->mode_res->count_crtcs)
++		return NULL;
++
++	flink.handle = fbcon->handle;
++	if (ioctl(mode->fd, DRM_IOCTL_GEM_FLINK, &flink) < 0) {
++		xf86DrvMsg(scrn->scrnIndex, X_ERROR,
++			   "Couldn't flink fbcon handle\n");
++		return NULL;
++	}
++
++	bo = drm_intel_bo_gem_create_from_name(intel->bufmgr,
++					       "fbcon", flink.name);
++	if (bo == NULL) {
++		xf86DrvMsg(scrn->scrnIndex, X_ERROR,
++			   "Couldn't allocate bo for fbcon handle\n");
++		return NULL;
++	}
++	if (!CreateScratchPixmapsForScreen(pScreen->myNum))
++		return NULL;
++
++	pixmap = GetScratchPixmapHeader(pScreen,
++					fbcon->width, fbcon->height,
++					fbcon->depth, fbcon->bpp,
++					fbcon->pitch, NULL);
++	if (pixmap == NULL) {
++		xf86DrvMsg(scrn->scrnIndex, X_ERROR,
++			   "Couldn't allocate pixmap fbcon contents\n");
++		return NULL;
++	}
++
++	intel_set_pixmap_bo(pixmap, bo);
++	drm_intel_bo_unreference(bo);
++	drmModeFreeFB(fbcon);
++
++	return pixmap;
++}
++
++void intel_copy_fb(ScrnInfoPtr scrn)
++{
++	ScreenPtr pScreen = screenInfo.screens[scrn->scrnIndex];
++	intel_screen_private *intel = intel_get_screen_private(scrn);
++	PixmapPtr src, dst;
++	unsigned int pitch = scrn->displayWidth * intel->cpp;
++
++	src = intel_create_pixmap_for_fbcon(scrn);
++	if (src == NULL) {
++		xf86DrvMsg(scrn->scrnIndex, X_ERROR,
++			   "Couldn't create pixmap for fbcon\n");
++		return;
++	}
++
++	/* We dont have a screen Pixmap yet */
++	dst = GetScratchPixmapHeader(pScreen,
++				     scrn->virtualX, scrn->virtualY,
++				     scrn->depth, scrn->bitsPerPixel,
++				     pitch,
++				     NULL);
++	intel_set_pixmap_bo(dst, intel->front_buffer);
++
++	intel->uxa_driver->prepare_copy(src, dst, -1, -1, GXcopy, FB_ALLONES);
++
++	intel->uxa_driver->copy(dst, 0, 0, 0, 0,
++				scrn->virtualX, scrn->virtualY);
++
++	intel->uxa_driver->done_copy(dst);
++
++	intel_batch_submit(scrn);
++
++	(*pScreen->DestroyPixmap)(src);
++	(*pScreen->DestroyPixmap)(dst);
++	FreeScratchPixmapsForScreen(pScreen->myNum);
++}
++
+Index: xserver-xorg-video-intel/src/intel_driver.c
+===================================================================
+--- xserver-xorg-video-intel.orig/src/intel_driver.c	2011-08-09 10:04:02.144071018 +1000
++++ xserver-xorg-video-intel/src/intel_driver.c	2011-08-09 21:39:33.292370844 +1000
+@@ -942,6 +942,10 @@
+ 		intel->directRenderingType = DRI_DRI2;
+ #endif
+ 
++#if GET_ABI_MAJOR(ABI_VIDEODRV_VERSION) >= 9
++	screen->canDoBGNoneRoot = TRUE;
++#endif
++
+ 	if (!intel_init_initial_framebuffer(scrn))
+ 		return FALSE;
+ 
+@@ -950,6 +954,8 @@
+ 	if (INTEL_INFO(intel)->gen >= 40)
+ 		gen4_render_state_init(scrn);
+ 
++	intel->starting = FALSE;
++
+ 	miClearVisualTypes();
+ 	if (!miSetVisualTypes(scrn->depth,
+ 			      miGetDefaultVisualMask(scrn->depth),
+@@ -1085,6 +1091,7 @@
+ 
+ 	intel_mode_init(intel);
+ 
++	intel->starting = FALSE;
+ 	intel->suspended = FALSE;
+ 
+ #if HAVE_UDEV
+@@ -1154,6 +1161,8 @@
+ 
+ 	intel_set_gem_max_sizes(scrn);
+ 
++	intel_copy_fb(scrn);
++
+ 	if (!xf86SetDesiredModes(scrn))
+ 		return FALSE;
+ 
+EOF
+
+  patch -Np1 << "EOF"
+diff --git a/src/i965_render.c b/src/i965_render.c
+index b1ac6ba..c5eb611 100644
+--- a/src/i965_render.c
++++ b/src/i965_render.c
+@@ -1126,6 +1126,9 @@ i965_set_picture_surface_state(intel_screen_private *intel,
+ 	uint32_t write_domain, read_domains;
+ 	int offset;
+ 
++	if (!priv)
++		return;
++
+ 	if (is_dst) {
+ 		write_domain = I915_GEM_DOMAIN_RENDER;
+ 		read_domains = I915_GEM_DOMAIN_RENDER;
+EOF
+
+  patch -Np1 << "EOF"
+--- a/src/intel.h  2012-05-16 18:07:46.128940169 +0100
++++ b/src/intel.h 2012-05-16 18:07:51.969009414 +0100
+@@ -70,6 +70,8 @@ SOFTWARE OR THE USE OR OTHER DEALINGS IN
+ #include "intel_driver.h"
+ #include "intel_list.h"
+ 
++#include "uxa/uxa.h"
++
+ #if HAVE_UDEV
+ #include <libudev.h>
+ #endif
+
+EOF
+
+  autoreconf
   ./configure --prefix=/usr --enable-dri
   make
 }

Run "makepkg -si" and install. If you want to automate the above for updates (bear in mind that the patches may break when a newer version comes out), grab customizepkg-patching from the AUR and save the above as /etc/customizepkg.d/xf86-video-intel.

Last edited by qwerty12 (2012-05-16 17:27:51)

fdservices · 2012-05-17 06:56:31

Thanks for the reply, it seems clear enough except for:

running on tty7 - as set via its configure parameter

I have not found how to set this parameter in all my searches yet. Can you explain please?

I will keep looking.

Andrew

Last edited by fdservices (2012-05-17 06:57:11)

fdservices · 2012-05-17 07:47:46

I am not sure if I am on the right track now. The symptoms of my problem are that I see the grub screen in low resolution, then the "Booting Arch Linux" text in low resolution, then the plymouth splash screen in high resolution, then the "Booting Arch Linux" text in high resolution and finally the kdm theme. All is fine except the two appearances of the text screen, especially the second one.

What would be nice is to see the grub screen in high resolution, followed by the plymouth splash, followed by the kdm theme.

I am runnning on an HP-DM1 laptop, intel chipset, cpu: U2300 2-core, video: intel GM45 express, network: Realtek RTL8101E/8102E, Wifi: Broadcom BCM4312

Thanks for any pointers.

Andrew

Last edited by fdservices (2012-05-19 07:10:56)

Zenettii · 2012-05-18 14:34:00

Isn't your concern with Grub, not Plymouth ?
Grub2 for example gives you a very high rez screen.
Using a vga=xxx would normally be the option in grub to increase your resolution.
https://wiki.archlinux.org/index.php/Gr … hical_boot

Last edited by Zenettii (2012-05-18 14:34:33)

fdservices · 2012-05-19 07:43:47

No, I don't think so. The three stages are:

"Booting Arch Linux" text in low resolution
The plymouth splash screen in high resolution
"Booting Arch Linux" text in high resolution

The first stage is grub while linux is loadig when no parameters have been read, the second is in high resolution, as it should be. The "vga=" parameter loads the vesa framebuffer, whereas I am using KMS, so expect the intel framebuffer, which appears to be loaded correctly:

fbcon: inteldrmfb (fb0) is primary device
fb0: inteldrmfb frame buffer device

The third is the main problem, where plymouth switches out and I get the text screen again.

Thanks for the reply

Andrew

donniezazen · 2012-07-21 19:10:04

Any of you have problems rebooting or shutting down after enabling Plymouth (splash in kernel boot line)?

Last edited by donniezazen (2012-07-21 19:10:17)

fdservices · 2012-07-22 07:34:11

Sorry, dropped plymouth in favour of fbsplash which seems to work fine

Andrew

Berseker · 2012-08-18 12:30:01

I think plymouth is the best splash screen out there.
I've made a nice theme for it, based on this one but with fixed logo and colors

here it is
http://www.sendspace.com/file/20yj79

martadinata · 2012-08-19 13:44:06

@berseker thanks great theme

donniezazen · 2012-08-19 15:55:45

@berseker It does look good. My Plymouth only shows for a few seconds and not as a consistent screen. It does Thinkpad-Screen-->Grub-->Loading hooks-->PLYMOUTH-->Loading hooks-->GDM

mcarni · 2012-09-04 06:46:47

Hi guys!

I just upgraded one of my computers (arch=i386, systemd, compiz DE) and I was wondering if there is a way to have a smooth transition from plymouth to slim.
After installing plymouth a saw a note about replacing the DM.service unit with DM-plymouth.service but I couldn't find the slim-plymouth one.

probably I am missing something obvious, but could anybody point me in the right direction?

thanks a lot

M

EDIT: 04/09/2012-16:20 typos

Last edited by mcarni (2012-09-04 14:20:38)

Primoz · 2012-12-03 15:40:54

After reading the thread, I know why my plymouth isn't working well, and I'll repair that. But I need to know. There was mentioned that you shouldn't use autologin on KDM.
Does this still hold? Because I'm the only user and got really used to autologin into KDE.

I'm guessing this goes for seamless log-in, which I'd really like to have. So if anyone has any work around for that please do share.
While troubleshooting it I did set KDM to not use any theme, hopefully this will make the log-in process a bit more seamless, as the plymouth will transfer to black and then to KDE.
I'll see what happens and see if there's anything that can be done to make it more seamless.

EDIT: Well that didn't work at all. I still have the same problem than before, I guess things in this thread aren't up-to-date.
My plymouth splash first looses background, then just turns off completely. Any help?

EDIT2: Meh decided I don't need plymouth. And I have a suspicion that all my problems were due to proprietary ATI driver, which I have to use.

Last edited by Primoz (2012-12-03 19:38:40)

nsetyo · 2014-01-21 15:02:14

Hi, i am newbie here, sorry for may bad english
i am using for couple of month without boot splash, now i try plymouth, everything is installed without error but plymouth isn't show up when boot
here is my mkinitpcio

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

# 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 uresume filesystems keyboard 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_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""

and here is my default grub kernel line

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX="resume=/dev/sda5"

my boot log said that plymouth is running

[  OK  ] Started Show Plymouth Boot Screen.
         Starting Load/Save Screen Backlight Brightness of acpi_video0...
[  OK  ] Reached target Sound Card.
[  OK  ] Reached target Bluetooth.
[  OK  ] Started Load/Save Screen Backlight Brightness of acpi_video0.
[  OK  ] Found device WDC_WD3200BEVT-60A23T0.
         Mounting /media/bridge...
[  OK  ] Found device WDC_WD3200BEVT-60A23T0.
         Activating swap /dev/sda5...
[  OK  ] Found device WDC_WD3200BEVT-60A23T0.
         Starting File System Check on /dev/sda7...
[  OK  ] Activated swap /dev/sda5.
[  OK  ] Reached target Swap.
         Mounting FUSE Control File System...
[  OK  ] Mounted FUSE Control File System.
systemd-fsck[294]: home: recovering journal
[  OK  ] Mounted /media/bridge.
systemd-fsck[294]: home: Clearing orphaned inode 1450008 (uid=1000, gid=1000, mode=0100644, size=32768)
systemd-fsck[294]: home: Clearing orphaned inode 1441661 (uid=1000, gid=1000, mode=0100600, size=340)
systemd-fsck[294]: home: Clearing orphaned inode 1449997 (uid=1000, gid=1000, mode=0100644, size=32768)
systemd-fsck[294]: home: Clearing orphaned inode 1449996 (uid=1000, gid=1000, mode=0100600, size=4508)
systemd-fsck[294]: home: Clearing orphaned inode 1048641 (uid=1000, gid=1000, mode=0100644, size=2511)
systemd-fsck[294]: home: clean, 250114/3654672 files, 6606700/14618368 blocks
[  OK  ] Started File System Check on /dev/sda7.
         Mounting /home...
[  OK  ] Mounted /home.
[  OK  ] Reached target Local File Systems.
         Starting Recreate Volatile Files and Directories...
         Starting Trigger Flushing of Journal to Persistent Storage...
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Recreate Volatile Files and Directories.
         Starting Update UTMP about System Reboot/Shutdown...
[  OK  ] Started Trigger Flushing of Journal to Persistent Storage.
[  OK  ] Started Update UTMP about System Reboot/Shutdown.
[  OK  ] Reached target System Initialization.
[  OK  ] Reached target Paths.
[  OK  ] Listening on CUPS Printing Service Sockets.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Timers.
         Starting Restore Sound Card State...
[  OK  ] Reached target Basic System.
         Starting MariaDB database server...
         Starting Network Manager...
         Starting Login Service...
         Starting CUPS Printing Service...
[  OK  ] Started CUPS Printing Service.
         Starting D-Bus System Message Bus...
[  OK  ] Started D-Bus System Message Bus.
         Starting Permit User Sessions...
[  OK  ] Started Restore Sound Card State.
[  OK  ] Started Permit User Sessions.
         Starting Terminate Plymouth Boot Screen...
         Starting Wait for Plymouth Boot Screen to Quit...

i am installing plymouth-git version 0.8.8.116.g33b4e15-1
i have no idea why plymouth isn't show up, from dmesg i think KMS is enabled
I beg for help

rabcor · 2014-01-24 02:02:25

I'm having the same problem as above poster

Here's a bug report on ubuntu from 4 years ago

Supposedly you can fix it with this PKGBUILD

That is, downgrading to 8.50.

But apparently that fails on plymouth-update-initrd.patch.

Unstable shit, i'm giving up on it and just using fbsplash or splashy

Last edited by rabcor (2014-01-24 02:23:42)

Arch Linux

#201 2012-01-10 15:43:20

Re: Plymouth is working! How to have a great splash in your box

#202 2012-02-07 21:14:24

Re: Plymouth is working! How to have a great splash in your box

#203 2012-02-08 00:34:40

Re: Plymouth is working! How to have a great splash in your box

#204 2012-02-27 02:49:50

Re: Plymouth is working! How to have a great splash in your box

#205 2012-04-15 16:53:35

Re: Plymouth is working! How to have a great splash in your box

#206 2012-04-16 14:40:28

Re: Plymouth is working! How to have a great splash in your box

#207 2012-04-16 15:52:46

Re: Plymouth is working! How to have a great splash in your box

#208 2012-04-17 19:15:51

Re: Plymouth is working! How to have a great splash in your box

#209 2012-05-13 17:00:50

Re: Plymouth is working! How to have a great splash in your box

#210 2012-05-13 18:50:10

Re: Plymouth is working! How to have a great splash in your box

#211 2012-05-13 19:50:20

Re: Plymouth is working! How to have a great splash in your box

#212 2012-05-16 17:27:19

Re: Plymouth is working! How to have a great splash in your box

#213 2012-05-17 06:56:31

Re: Plymouth is working! How to have a great splash in your box

#214 2012-05-17 07:47:46

Re: Plymouth is working! How to have a great splash in your box

#215 2012-05-18 14:34:00

Re: Plymouth is working! How to have a great splash in your box

#216 2012-05-19 07:43:47

Re: Plymouth is working! How to have a great splash in your box

#217 2012-07-21 19:10:04

Re: Plymouth is working! How to have a great splash in your box

#218 2012-07-22 07:34:11

Re: Plymouth is working! How to have a great splash in your box

#219 2012-08-18 12:30:01

Re: Plymouth is working! How to have a great splash in your box

#220 2012-08-19 13:44:06

Re: Plymouth is working! How to have a great splash in your box

#221 2012-08-19 15:55:45

Re: Plymouth is working! How to have a great splash in your box

#222 2012-09-04 06:46:47

Re: Plymouth is working! How to have a great splash in your box

#223 2012-12-03 15:40:54

Re: Plymouth is working! How to have a great splash in your box

#224 2014-01-21 15:02:14

Re: Plymouth is working! How to have a great splash in your box

#225 2014-01-24 02:02:25

Re: Plymouth is working! How to have a great splash in your box

Board footer