Le mercredi 28 décembre 2011 à 08:58 +0100, Anders Johansson a écrit :
On Tuesday 27 December 2011 21:09:37 Cristian wrote:
enable building of systemd-plymouth package, actually changing %build_plymouth variable in systemd.spec
Take a look to the initrd related code, as well as "cryptsetup" integration that looks somewhat strange currently.
Install "bootsplash" only with legacy sysvinit.
Does plymouth still require kms? If it does, I don't think it will be such a great idea to do away with bootsplash, and require people with nvidia cards to boot in text mode.
It does requires KMS for "supported" graphical chipset, ie Intel / ATI / Nouveau. For other, it fallbacks to what the kernel is providing : if it is booting with vga=xxx, it will use graphical framebuffer (so, you get a graphical boot for Nvidia or ATI proprietary drivers). Otherwise, it will fallback to text mode.
If we can make the installer clever enough to detect when plymouth will fail, and use bootsplash then, it might work, but dropping bootsplash completely I think would be a major mistake
No, we should drop bootsplash completely. We really don't want to maintain two splash implementations (in fact, three, since suspend is still using splashy to talk to framebuffer, but we could now use a patch I wrote when I switched Mandriva to plymouth so suspend can use plymouth do do a graphical suspend. -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org