[Splashy-users] splashy hangs on boot

Luis lemsx1 at gmail.com
Thu May 18 03:24:44 UTC 2006


Hello Andrew,

Please see my response below.

On 5/17/06, Andrew Pasquale <andrew at elytra.net> wrote:
> Hi,  I've installed splashy 0.1.8-0+31 on sid.  It works well on shutdown and
> using '/sbin/splashy test', but during boot it hangs.  The graphics and
> progress bar appear, but the progress bar never changes.  I can see the hard
> disk access light flashing and eventually the Wireless light flashes on.  I
> suspect this is the initramfs continuing to load.  The keyboard won't respond
> during this process.  Eventually, after more than a minute I see on VT1:
>

This is a known problem on Debian/Ubuntu. When the system goes from
initramfs to init, it calls unicode_start (or unicode_stop depending
on your locales) from the keymap setting scripts. This causes the boot
process to stop.

We have not been able to identify exactly what causes this problem
(and this is the main reason why splashy 0.1.8 has not been released).

Splashy is meant to timeout after 2 min of not being able to read from
the fifo file.

I'm about to commit to svn some code that should move us in the right
direction about this issue. Essentially, we are trying to close all
open filehandles to ensure that Splashy becomes a true "daemon"
process. There might be something else tying the Splashy process to
the terminal though... If you have insights as to how that should be
handled, please join us at #splashy on irc.freenode.net.

> FATAL: module fbcon not found
> FATAL: module vesafb not found
>

You may disregard those.

> I suspect these aren't related to the problem since the framebuffer is working
> fine.  vesafb is compiled in, and I'm using vga=792 as a kernel option in
> grub.
>
> I can then switch to VT2 where I can see the output from udev loading.  If I
> hit enter here, the init process continues normally, without splashy.
>

Yep. 1 month with this problem already. We are stuck.

> I was not able to use the update-initramfs -u tool since it says:
> '/boot/initrd.img-2.6.16 has been altered.  Cannot update.'  Instead I've
> used 'mkinitramfs -o /boot/initrd.img-2.6.16'.  I'm running a custom kernel
> because my laptop has a SATA hard drive and I've compiled in all the relevant
> modules.

update-initramfs -k `uname -r` -t -u  ought to do the trick ( -t is
"take over" ). If that doesn't do it, then use -c to create a new
initramfs and -t to take over.

>
> I've seen the following error message, but it seems not to affect the
> performance of splashy.  I think it might only happen on some themes.  I can
> try to reproduce if it might be important.
>
> ** (process:8363): CRITICAL **: _xml_parser_compare_element: assertion
> `_node->got_text == TRUE' failed
>

Make sure that the theme.xml file you are using validates against our
themes.xsd (schema) file. There is a Perl script included to validate
themes, but you can use any XML validator (that allows you to specify
a theme. like xmllint)

> I like the way splashy looks and I'd like to get it working on my machine.
> I'd appreciate any suggestions to troubleshoot this problem.
>

Splashy is awesome. ;-)


-- 
----)(-----
Luis Mondesi
*NIX Guru

Kiskeyix.org

"We think basically you watch television to turn your brain off, and
you work on your computer when you want to turn your brain on" --
Steve Jobs in an interview for MacWorld Magazine 2004-Feb

No .doc: http://www.gnu.org/philosophy/no-word-attachments.es.html


More information about the Splashy-users mailing list