| View previous topic :: View next topic |
| Author |
Message |
Pipeng
Tux's lil' helper
Joined: 23 Jul 2013
Posts: 87
|
 Posted: Tue Nov 11, 2014 3:56 am Post subject: Plymouth can't start |
 |
|
Hi all, i have a little problem with plymouth, first i follow the wikis of gentoo and someone of funtoo, but when i boot i recive this message of plymouth:
| Code: | nov 10 18:18:16 localhost systemd[2510]: Failed at step EXEC spawning /usr/sbin/plymouthd: No such file or directory
nov 10 18:18:16 localhost systemd[1]: plymouth-start.service: control process exited, code=exited status=203
nov 10 18:18:16 localhost systemd[1]: Failed to start Show Plymouth Boot Screen. |
and the file exist, in the right directory, and i check the service of plymouth and all the paths looks good, here is the service file:
| Code: | Type=forking
Restart=no
NotifyAccess=none
RestartUSec=100ms
TimeoutStartUSec=1min 30s
TimeoutStopUSec=1min 30s
WatchdogUSec=0
WatchdogTimestampMonotonic=0
StartLimitInterval=10000000
StartLimitBurst=5
StartLimitAction=none
FailureAction=none
PermissionsStartOnly=no
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=0
ControlPID=0
Result=success
ExecMainStartTimestamp=lun 2014-11-10 18:18:25 CLST
ExecMainStartTimestampMonotonic=11694806
ExecMainExitTimestamp=lun 2014-11-10 18:18:47 CLST
ExecMainExitTimestampMonotonic=33413721
ExecMainPID=4010
ExecMainCode=1
ExecMainStatus=0
ExecStart={ path=/usr/sbin/plymouthd ; argv[]=/usr/sbin/plymouthd --mode=boot --pid-file=/var/run/plymouth/pid --attach-to-session ; ignore_errors=no ; start_time=[lun 2014-11-10 18:18:24 CLST] ; stop_time=[lun 2014-11-10 18:18:25 CLST] ; pid=4007 ; code=exited ; status=0 }
ExecStartPost={ path=/usr/bin/plymouth ; argv[]=/usr/bin/plymouth show-splash ; ignore_errors=yes ; start_time=[lun 2014-11-10 18:18:25 CLST] ; stop_time=[lun 2014-11-10 18:18:25 CLST] ; pid=4011 ; code=exited ; status=0 }
Slice=system.slice
CPUAccounting=no
CPUShares=18446744073709551615
StartupCPUShares=18446744073709551615
CPUQuotaPerSecUSec=(null)
BlockIOAccounting=no
BlockIOWeight=18446744073709551615
StartupBlockIOWeight=18446744073709551615
MemoryAccounting=no
MemoryLimit=18446744073709551615
DevicePolicy=auto
UMask=0022
LimitCPU=18446744073709551615
LimitFSIZE=18446744073709551615
LimitDATA=18446744073709551615
LimitSTACK=18446744073709551615
LimitCORE=18446744073709551615
LimitRSS=18446744073709551615
LimitNOFILE=4096
LimitAS=18446744073709551615
LimitNPROC=30645
LimitMEMLOCK=65536
LimitLOCKS=18446744073709551615
LimitSIGPENDING=30645
LimitMSGQUEUE=819200
LimitNICE=0
LimitRTPRIO=0
LimitRTTIME=18446744073709551615
OOMScoreAdjust=0
Nice=0
IOScheduling=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SecureBits=0
CapabilityBoundingSet=18446744073709551615
MountFlags=0
PrivateTmp=no
PrivateNetwork=no
PrivateDevices=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=0
RuntimeDirectoryMode=0755
KillMode=none
KillSignal=15
SendSIGKILL=no
SendSIGHUP=no
Id=plymouth-start.service
Names=plymouth-start.service
Wants=systemd-ask-password-plymouth.path systemd-vconsole-setup.service system.slice
WantedBy=sysinit.target
Before=systemd-ask-password-console.path systemd-ask-password-console.service systemd-ask-password-plymouth.service systemd-ask-password-plymouth.path plymouth-quit.service plymouth-quit-wait.service rescue.service
After=systemd-vconsole-setup.service systemd-udev-trigger.service systemd-udevd.service systemd-journald.socket system.slice
Description=Show Plymouth Boot Screen
LoadState=loaded
ActiveState=inactive
SubState=dead
FragmentPath=/usr/lib64/systemd/system/plymouth-start.service
UnitFileState=disabled
InactiveExitTimestamp=lun 2014-11-10 18:18:24 CLST
InactiveExitTimestampMonotonic=10894285
ActiveEnterTimestamp=lun 2014-11-10 18:18:25 CLST
ActiveEnterTimestampMonotonic=11903750
ActiveExitTimestamp=lun 2014-11-10 18:18:47 CLST
ActiveExitTimestampMonotonic=33413806
InactiveEnterTimestamp=lun 2014-11-10 18:18:47 CLST
InactiveEnterTimestampMonotonic=33413806
CanStart=yes
CanStop=yes
CanReload=no
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=no
OnFailureJobMode=replace
IgnoreOnIsolate=no
IgnoreOnSnapshot=no
NeedDaemonReload=no
JobTimeoutUSec=0
ConditionResult=yes
ConditionTimestamp=lun 2014-11-10 18:18:24 CLST
ConditionTimestampMonotonic=10894081
Transient=no |
i'm using dracut for generate the initramfs and the modules are ok, plymouth don't start but i can start the system with the image of dracut, and i'm using systemd, here is my ls of /usr/sbin:
| Code: | ls -l /usr/sbin/plymouthd
-rwxr-xr-x 1 root root 48552 nov 10 10:01 /usr/sbin/plymouthd |
here the uses of the packages:
| Code: |
sys-kernel/dracut-040 +systemd
sys-boot/plymouth-0.9.0 gdm gtk libkms pango
sys-apps/systemd-215-r3 acl firmware-loader gudev instrospection kmod pam policykit python python_single_target_python2_7 python_targets_python2_7 python_targets_python3_3 seccomp
|
And i have active the plymouth module in dracut, and i try with a lot of version of dracut and plymouth but nothing change u.u
Thx all |
|
| Back to top |
|
 |
Mgiese
Veteran
Joined: 23 Mar 2005
Posts: 1609
Location: indiana
|
| Posted: Thu Jan 29, 2015 12:10 pm Post subject: |
|
|
i ran into this problem : "Failed at step EXEC spawning /bin/plymouth" when putting
| Code: | | /dev/sdc1 /mnt/phone auto noatime 0 1 |
into /etc/fstab
but | Code: | # ls -l /usr/sbin/plymouthd
ls: cannot access /usr/sbin/plymouthd: No such file or directory |
and
| Code: | # /bin/plymouth
bash: /bin/plymouth: No such file or directory
|
let me suggest i actually dont have it ... if i remove the fstab line, system boots just fine without recovery
_________________
I do not have a Superman complex, for I am God not Superman 
Ryzen9 7950x ; Geforce1650 ; kernel 6.5 ; XFCE |
|
| Back to top |
|
|
Mgiese
Veteran
Joined: 23 Mar 2005
Posts: 1609
Location: indiana
|
| Posted: Thu Jan 29, 2015 12:57 pm Post subject: |
|
|
after emerging plymouth, that error went away but i still run into recovery mode if mobile is not plugged in
more here : https://forums.gentoo.org/viewtopic-p-7691844.html#7691844
_________________
I do not have a Superman complex, for I am God not Superman
Ryzen9 7950x ; Geforce1650 ; kernel 6.5 ; XFCE |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Other Things Gentoo
