Plymouth custom initrd problems

[Ray Strode]

Hi,


>> > Here's a snippet of the relevant part of the debugging output from
>> "plymouthd --debug" after issuing the "plymouth --show-splash"
>> command:
>> you can also do plymouth:debug / plymouth:nolog on the kernel command
>> line, or type ctrl-v while it's running to get debug spew
>
> I've attached a screenshot of the full log output. Should it be trying to
> load the details theme first? The default is set to "charge".
It should.  The only times it wouldn't try to load the default theme are if

1) "rhgb" or "splash" is missing from kernel command line
2) You have init=/bin/sh or something on the kernel command line.

[...]
> The kernel command line looks like:
>
>  init=/init rw quiet vga=0x318 rhgb

So it's probably the init=/init here that's the problem.

Plymouth does something like:

if (strstr (kernel_command_line, " init=") != NULL)
  dump_captured_output_to_screen_and_quit ();

It does this so that plymouth won't take control of the console when
the user is typing at a shell.

--Ray