[Splashy-devel] Bug#455872: splashy: Fails to initialize, messes up loading other modules

[Luis Mondesi]

On Dec 15, 2007 12:05 PM, Alessio Gaeta <alga777 at libero.it> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I can confirm this bug, it happens on my machine too. The problem shows
> itself only when the parameter "splashy" is passed to the kernel. If I
> remove it, the system boots normally, but for the bug #455685 (Splashy
> makes GDM initscript fail.
>
> Symptoms are the same: splashy fails to start with error code
> - -3 from splashy_start_splashy(), no sound, no usbhid, no networking...
> Hotplugging doesn't work at all, modules aren't automatically loaded and
> modprobe rules aren't satisfied (i.e. I have a rule to load usbnet whith
> cdc_subset, but when I plug my Linux Ipaq in the cradle the module
> cdc_subset isn't loaded; if I probe the module manually the module
> usbnet isn't automatically loaded.
>
> I noted that when starting without the parameter "splashy" i can see the
> log line
>
> Waiting for /dev to be fully populated...done.
>
> but with splashy activated that line doesn't appear. So I guess it is a
> udev (odd-)interaction problem (or maybe a more complicated
> splashy/udev/initramfs-tool, seen problems of update-initramfs with
> udev...).
>
> Moreover, it happens that if I reboot and temporary delete the initrd
> line from GRUB (my kernel can boot without initrd, but I need it for
> uswsuspend), boot fails because /dev is completely screwed up.
>
>
Hello,

Sorry for taking so long to reply (holidays are almost here!)

Can you do a test for me?

As root, run the following on your system:

mv /usr/share/initramfs-tools/scripts/init-top/splashy
/usr/share/initramfs-tools/scripts/init-bottom/z_splashy
update-initramfs -u

make sure that you put back "splash vga=791" to your kernel boot parameters.
Note that it's not "splashy" but "splash".

Also, I have attached 2 scripts to this email. /etc/lsb-base-logging.sh and
/etc/console-tools/config.d/splashy. Please use this scripts to replace the
ones that you have. These come straight from our Git repository (See more
here http://splashy.alioth.debian.org/wiki/developers).

Please report back your experience.

If this is too much for you to do, then you can hold on for the next Splashy
revision (which should come out pretty quickly).

Regards,

-- 
----)(-----
Luis Mondesi
Maestro Debiano

----- START ENCRYPTED BLOCK (Triple-ROT13) ------
Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner
jbeyq.
----- END ENCRYPTED BLOCK (Triple-ROT13) ------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/splashy-devel/attachments/20071217/cf2cb6f1/attachment.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: console-tools_config.d_splashy
Type: application/octet-stream
Size: 454 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/splashy-devel/attachments/20071217/cf2cb6f1/attachment.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: etc_lsb-base-logging.sh
Type: application/x-sh
Size: 5723 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/splashy-devel/attachments/20071217/cf2cb6f1/attachment.sh