Eric Doviak wrote:
Luis Mondesi wrote:
When $resume is not set, does Splashy start from initramfs init-top?
Why does Splashy starts "late"?
When "$resume" is not set, Splashy does not start from "init-top". It
appears to start from "init-bottom". My guess is that Splashy starts
"late" because the script is waiting for information about "$resume".
I tried adding the "case" structure from "local-premount/resume", but
I didn't have any luck.
- Eric
Just to clarify ... Simply testing this condition:
> if [ ! -z "${resume}" ]; then
> SPLASH=false
> fi
causes Splashy to start late. That's why I created the "laptop" kernel
argument.
When I tested my hack by not passing the "laptop" kernel argument,
Splashy starts from "init-top" (like it is supposed to), but I can only
start-up, shutdown and suspend. I cannot resume. The "laptop" kernel
argument fixes the "resume bug," but it causes Splashy to start late on
start-up.
- Eric
