plymouth in raring causes system hardlock if console_setup is not run in the initramfs on nexus7 prior to starting plymouthd

[Oliver Grawert]

while i can see the splash fine if i add a break= statement to my kernel commandline and manually ctrl-d out of the initrd shell,
using plymouth without a break statement causes a hard reboot of the system.

[Oliver Grawert (ogra)]

doing some research it seems the panic() function that is called by maybe_break in the initramfs scripts executes /scripts/panic/console_setup. calling /scripts/panic/console_setup from /init right before the run-init execution makes boots without break= possible and fixes the splash (well, apart from it being in portrait mode despite the tty being in landscape, but thats a different bug)

[Oliver Grawert (ogra)]

worked around in ubuntu-defaults-nexus7 through setting FRAMEBUFFER=y ...
(it would still be good to know why plymouth needs console_setup to run on this hardware)

[Oliver Grawert (ogra)]

please do not randomly set bug statuses to fix-released without poining to the actual upload that fixed the issue ...
this particular bug is not fixed yet, it just has a workaround.

[Rolf Leggewie (r0lf)]

raring has seen the end of its life and is no longer receiving any updates. Marking the raring task for this ticket as "Won't Fix".

[Oliver Grawert (ogra)]

ubuntu-defaults-nexus7 is long gone from the archive ... invalidating the bug task for it