Comment 9 for bug 526321

On Thu, Feb 25, 2010 at 05:13:46PM -0000, Claudio Moretti wrote:
> sudo ls -la /dev/.initramfs returns the following:

> root@Jarvis:/dev/.initramfs# ls -la
> totale 0
> drwxr-xr-x 2 root root 40 2010-02-25 13:14 .
> drwxr-xr-x 16 root root 3880 2010-02-25 15:50 ..

That's actually inconclusive, because once upstart has read the PID file, it
deletes it.

> I have also found this:

> root@Jarvis:/var/log# grep plymouth daemon.log*
> daemon.log:Feb 22 09:46:28 Jarvis init: plymouth-splash pre-start process
> (1258) terminated with status 111

"111" is "connection refused", which strongly implies plymouth is not
running at this point; but brings us no closer to understanding why.

> Please let me know if there's something else I can provide.

What happens when you boot with 'splash'?

What's the output of: 'zcat /boot/initrd.img | cpio -t |grep plymouth'?

Can you add a script to /usr/share/initramfs-tools/scripts/init-bottom which
checks for /dev/.initramfs/plymouth.pid, and records the result to another
file under /dev/ ? (The script needs to be marked executable, and after
adding it you will need to run 'sudo update-initramfs -u' to have it take
effect).

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>