View previous topic :: View next topic |
Author |
Message |
widremann Veteran
Joined: 14 Mar 2005 Posts: 1314
|
Posted: Sat May 19, 2012 3:40 pm Post subject: Systemd + Plymouth: plymouth goes away too early |
|
|
Note, this is entirely an aesthetic issue. The system boots just fine and plymouth does show up for a while. It just doesn't wait until the X server has started and KDM has a screen up. So I see the tty1 login screen for a second or two. Does anybody know what controls when plymouth shuts itself down? And if so, how can I make it stick around until the graphical login screen is up? |
|
Back to top |
|
|
popsUlfr Tux's lil' helper
Joined: 27 Feb 2011 Posts: 80
|
Posted: Sat May 19, 2012 6:31 pm Post subject: |
|
|
Hello,
which KMS module are you using with plymouth? I assume you put
Code: | rc_interactive="NO" |
in your rc.conf?
Does the package install its own openrc service file? It seems that plymouth is killed too soon... |
|
Back to top |
|
|
widremann Veteran
Joined: 14 Mar 2005 Posts: 1314
|
Posted: Sat May 19, 2012 11:52 pm Post subject: |
|
|
popsUlfr wrote: | Hello,
which KMS module are you using with plymouth? I assume you put
Code: | rc_interactive="NO" |
in your rc.conf?
Does the package install its own openrc service file? It seems that plymouth is killed too soon... |
I'm using systemd. |
|
Back to top |
|
|
popsUlfr Tux's lil' helper
Joined: 27 Feb 2011 Posts: 80
|
Posted: Sun May 20, 2012 8:57 am Post subject: |
|
|
widremann wrote: | I'm using systemd. |
I totally missed that, didn't I? My bad. |
|
Back to top |
|
|
MetalGod Bodhisattva
Joined: 10 Mar 2003 Posts: 816 Location: Portugal
|
Posted: Thu May 31, 2012 7:00 pm Post subject: Re: Systemd + Plymouth: plymouth goes away too early |
|
|
widremann wrote: | Note, this is entirely an aesthetic issue. The system boots just fine and plymouth does show up for a while. It just doesn't wait until the X server has started and KDM has a screen up. So I see the tty1 login screen for a second or two. Does anybody know what controls when plymouth shuts itself down? And if so, how can I make it stick around until the graphical login screen is up? |
same here using gdm... if you find out please post here. _________________ ex: Gentoo Linux Developer: amd64 media-optical sound gnome
ex: Portuguese Moderator
------------------------------------------------------------------------------
God Doesn't Play Dice |
|
Back to top |
|
|
MetalGod Bodhisattva
Joined: 10 Mar 2003 Posts: 816 Location: Portugal
|
Posted: Thu May 31, 2012 8:54 pm Post subject: |
|
|
I got almost there just modify you gdm.service to this:
[Unit]
Description=GNOME Display Manager
#After=systemd-user-sessions.service
After=syslog.target local.service
Conflicts=getty@tty1.service plymouth-quit.service
After=getty@tty1.service plymouth-quit.service
[Service]
ExecStart=/usr/bin/gdm --nodaemon
Type=dbus
BusName=org.gnome.DisplayManager
[Install]
WantedBy=graphical.target
Restart=always
RestartSec=0
IgnoreSIGPIPE=no
also add --retain-splash to plymouth-quit.service.
This at least doesn't show the console login but i'm still seeing the black screen from gdm, so not a real smooth transaction. _________________ ex: Gentoo Linux Developer: amd64 media-optical sound gnome
ex: Portuguese Moderator
------------------------------------------------------------------------------
God Doesn't Play Dice |
|
Back to top |
|
|
bingquick n00b
Joined: 04 Oct 2012 Posts: 2
|
Posted: Thu Oct 04, 2012 11:10 pm Post subject: |
|
|
MetalGod wrote: | I got almost there just modify you gdm.service to this:
[Unit]
Description=GNOME Display Manager
#After=systemd-user-sessions.service
After=syslog.target local.service
Conflicts=getty@tty1.service plymouth-quit.service
After=getty@tty1.service plymouth-quit.service
[Service]
ExecStart=/usr/bin/gdm --nodaemon
Type=dbus
BusName=org.gnome.DisplayManager
[Install]
WantedBy=graphical.target
Restart=always
RestartSec=0
IgnoreSIGPIPE=no
also add --retain-splash to plymouth-quit.service.
This at least doesn't show the console login but i'm still seeing the black screen from gdm, so not a real smooth transaction. |
You need to make gdm/kdm to run on vt1 as Plymouth use vt1. In gdm 3.6 overlay ebuild it's set to vt7, I just changed it to vt1 and got a smooth transition. I also disabled getty@tty1.service. By the way the current Systemd in gentoo doesn't have Plymouth unit files, so you need a newer Plymouth 0.86 that has these files. |
|
Back to top |
|
|
ZeuZ_NG Guru
Joined: 10 Sep 2008 Posts: 453 Location: Near /dev/urandom | /dev/null
|
Posted: Sat Oct 06, 2012 10:14 pm Post subject: |
|
|
How do you achieve the last? _________________ | Intel Core i7 920. | Intel DX58SO Extreme. |
| 8gb DDR3 1666mHz | 1TB 7200 RPM WD HDD.|
Unix´s guru view of sex:
unzip ; strip ; touch ; grep ; finger ; \
mount ; fsck ; more ; yes ; umount ; sleep. |
|
Back to top |
|
|
bingquick n00b
Joined: 04 Oct 2012 Posts: 2
|
Posted: Sun Oct 07, 2012 10:40 am Post subject: |
|
|
ZeuZ_NG wrote: | How do you achieve the last? |
After mucking a little bit more with plymouth, you can actually tell it to use vt7. So you don't need to touch gdm ebuild. Just use the following the ebuild to build plymouth-0.8.6, then remove getty@tty1.service & plymouth-quit.service links (if any) in multi-user.target.wants directories under /etc/systemd/system & /usr/lib/systemd/system. Code: |
diff plymouth-0.8.4.ebuild plymouth-0.8.6.ebuild
-------------------
7c7
< inherit autotools-utils
---
> inherit autotools-utils systemd
19c19
< IUSE="${IUSE_VIDEO_CARDS} debug gdm +libkms +openrc +pango static-libs"
---
> IUSE="${IUSE_VIDEO_CARDS} debug +gdm +libkms +openrc +pango static-libs systemd"
39a40,43
> local PATCHES=(
> "${FILESDIR}"/plymouth-0.8.6-systemd-install-unit.patch
> )
>
47a52,53
> --with-boot-tty=/dev/tty7
> --with-shutdown-tty=/dev/tty7
51a58
> $(use_enable systemd systemd-integration)
71a79,91
> fi
>
> if use systemd; then
> # FIXME gentoo systemd unit files are in /usr/$(get_libdir)/systemd
> mv "${D}"/lib/systemd "${D}/usr/$(get_libdir)"/systemd
> # FIXME link /usr/bin/systemd-tty-ask-password-agent to /bin, should be
> # done at systemd ebuild
> dosym ../usr/bin/systemd-tty-ask-password-agent bin/systemd-tty-ask-password-agent
> fi
>
> if use gdm; then
> # remove plymouth-quit.service to avoid plymouth quit before gdm start
> rm -f "${D}/usr/$(get_libdir)"/systemd/system/multi-user.target.wants/plymouth-quit.service
---------------
cat files/plymouth-0.8.6-systemd-install-unit.patch
----------------
diff --git a/systemd-units/Makefile.am b/systemd-units/Makefile.am
index 16d132c..e3c3566 100644
--- a/systemd-units/Makefile.am
+++ b/systemd-units/Makefile.am
@@ -12,7 +12,36 @@ systemd_unit_templates = \
if ENABLE_SYSTEMD_INTEGRATION
systemdunitdir=$(SYSTEMD_UNIT_DIR)
-systemdunit_DATA = $(systemd_unit_templates:.service.in=.service)
+systemdunit_DATA = $(systemd_unit_templates:.in=)
+install-data-hook:
+ $(MKDIR_P) -m 0755 \
+ $(DESTDIR)$(SYSTEMD_UNIT_DIR)/sysinit.target.wants \
+ $(DESTDIR)$(SYSTEMD_UNIT_DIR)/multi-user.target.wants \
+ $(DESTDIR)$(SYSTEMD_UNIT_DIR)/reboot.target.wants \
+ $(DESTDIR)$(SYSTEMD_UNIT_DIR)/kexec.target.wants \
+ $(DESTDIR)$(SYSTEMD_UNIT_DIR)/poweroff.target.wants \
+ $(DESTDIR)$(SYSTEMD_UNIT_DIR)/halt.target.wants
+ ( cd $(DESTDIR)$(SYSTEMD_UNIT_DIR)/sysinit.target.wants && \
+ rm -f plymouth-start.service plymouth-read-write.service && \
+ $(LN_S) ../plymouth-start.service plymouth-start.service && \
+ $(LN_S) ../plymouth-read-write.service plymouth-read-write.service )
+ ( cd $(DESTDIR)$(SYSTEMD_UNIT_DIR)/multi-user.target.wants && \
+ rm -f plymouth-quit.service plymouth-quit-wait.service && \
+ $(LN_S) ../plymouth-quit.service plymouth-quit.service && \
+ $(LN_S) ../plymouth-quit-wait.service plymouth-quit-wait.service )
+ ( cd $(DESTDIR)$(SYSTEMD_UNIT_DIR)/reboot.target.wants && \
+ rm -f plymouth-reboot.service && \
+ $(LN_S) ../plymouth-reboot.service plymouth-reboot.service )
+ ( cd $(DESTDIR)$(SYSTEMD_UNIT_DIR)/kexec.target.wants && \
+ rm -f plymouth-kexec.service && \
+ $(LN_S) ../plymouth-kexec.service plymouth-kexec.service )
+ ( cd $(DESTDIR)$(SYSTEMD_UNIT_DIR)/poweroff.target.wants && \
+ rm -f plymouth-poweroff.service && \
+ $(LN_S) ../plymouth-poweroff.service plymouth-poweroff.service )
+ ( cd $(DESTDIR)$(SYSTEMD_UNIT_DIR)/halt.target.wants && \
+ rm -f plymouth-halt.service && \
+ $(LN_S) ../plymouth-halt.service plymouth-halt.service )
+
endif
EXTRA_DIST = $(systemd_unit_templates) $(systemdunit_DATA)
------------- |
[Moderator edit: added [code] tags to preserve output layout; disabled bogus mailto on systemd target.
Advice: always use -u when preparing diff files for public consumption. -Hu] |
|
Back to top |
|
|
klas Tux's lil' helper
Joined: 30 Aug 2017 Posts: 104 Location: Manchester
|
Posted: Thu Sep 14, 2017 8:00 pm Post subject: |
|
|
well, I am doing same where is located the gdm.service file in gentoo? |
|
Back to top |
|
|
|