Comment 61 for bug 1370707

Yeah I know why my plymouth is not working (the seat problem) :)

Others like @Alexander seem to have a problem with not initialized devices etc etc...
Its a complex problem involving udev/systemd and plymouth code itself, so debugging and fixing is very time consuming....

As a whole one of the important and leading problems is the initrd's created...

genkernel-next-60
-----------------
Doesn't include any seat udev rules in initramfs. I added them manually with everything needed but still plymouth 0.9.0 (and git master 9999) got problems with the console input and other problems with seat tagging again. I applied some patches gotten from Ubuntu (http://packages.ubuntu.com/vivid/plymouth) like 007-udev-seat-tag, ubuntu-seat-terminal-may-be-null etc (one by one testing with every 0.9.0 and git version), but every of these patches resolved one problem and brought another one :(

dracut-040-r3
-------------
As for the dracut I tested 040-r3 version but it lacks support for uvesafb's user helper v86d, and though I managed to include it in dracut's initramfs, I couldn't manage to add statically to the img file the nodes /dev/zero, /dev/mem and /dev/tty (needed by the helper to run very early in boot - before any udev are settled), so I get a frozen system immediately after boot... That is why I cannot tell if dracut works with plymouth BUT still it is not the gentoo way of creating initramfs img, so plymouth in portage cannot rely on using/working only with dracut....

Since all these tests consume a lot of time I removed dracut and reverted back to plymouth-0.8.8-r5 and now everything is fine...

BTW genkernel-next lacks support for uvesafb too, so I tweaked some of the source to have it...