[Splashy-devel] Bug#486400: a hack that WORKS !!!

[Luis Mondesi]

On Thu, Jul 3, 2008 at 10:39 PM, Eric Doviak <eric at doviak.net> wrote:
> Luis Mondesi wrote:
>
> When $resume is not set, does Splashy start from initramfs init-top? Why
> does Splashy starts "late"?
>
> Hi Luis,
>
> I ran some diagnostics using the hack that I sent yesterday.
>
> Specifically, I ran "splashy_config -s kubuntusplashy" but I did NOT run
> "update-initramfs -u". That enables me to see when Splashy is running from
> the initial RAM disk and when it is running from the regular file system.
> When I see "debian-moreblue," then I know that Splashy is running from the
> initial RAM disk. When I see "kubuntusplashy," then I know that Splashy is
> running from the regular file system.
>
> Or more simply: "'Debian' is right. 'Kubuntu' is wrong." ;-)
>
>
> When I pass the arguments "vga=791 splashy", I see:

if you pass "splashy" then Splashy won't work. You need to pass
"splash" as a kernel parameter. Is this a typo on this email or are
you actually using this keyword?

Back to the drawing board?

Thanks for your help on this though. I'm trying to reproduce this on
my own system.

-- 
----)(-----
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) ------