Try to get the startup between plymouth and Weston on CONFIG_VT=n as …

…flickerfree as possible using plymouth deactivate

Plymouth deactivate is used before plymouth quit, it leaves the last frame up, but it allows something else to use the /dev/dri/cardx device so that there is no gap between Plymouth quitting, and the display server starting

Weston seems to blank the screen upon startup, so it's not 100% seamless, but the gap is shorter

git-svn-id: https://svn.code.sf.net/p/rebeccablackos/code@7588 b52b6941-3400-464c-9f42-43200397181c

rebeccablackos_files/etc/loginmanagerdisplay/loginmanagerdisplay.ini

@@ -4,6 +4,7 @@ pageflip-timeout=10000
 require-input=false
 
 [shell]
+startup-animation=none
 background-image=/usr/share/wallpapers/RBOS_Login/contents/images/1920x1200.png
 background-type=scale
 background-color=0x00000000

rebeccablackos_files/usr/lib/systemd/system/plymouth-deactivate.service

@@ -0,0 +1,9 @@
+[Unit]
+Description=Deactivate Plymouth Boot Screen
+After=rc-local.service plymouth-start.service systemd-user-sessions.service
+Before=plymouth-quit.service plymouth-quit-wait.service 
+
+[Service]
+ExecStart=-/opt/bin/plymouth deactivate
+Type=oneshot
+TimeoutSec=20

rebeccablackos_files/usr/lib/systemd/system/waylandloginmanager.service

@@ -1,8 +1,9 @@
 [Unit]
 Description=The multi-seat Wayland Login Manager for RebeccaBlackOS
-Before=getty@tty1.service plymouth.service
-After=systemd-user-sessions.service
-Conflicts=plymouth-quit-wait.service
+Wants=plymouth-deactivate.service
+Conflicts=plymouth-quit.service plymouth-quit-wait.service
+Before=getty@tty1.service plymouth.service plymouth-quit-wait.service plymouth-quit.service
+After=systemd-user-sessions.service plymouth-deactivate.service
 
 [Service]
 #Use TTY63 to support text mode fallback if there is no kernel mode setting or framebuffer support