Le 29/11/15 14:23, Laurent Bigonville a écrit :
Le 28/11/15 12:46, Stefano Zacchiroli a écrit :
On Thu, Nov 26, 2015 at 11:41:55AM +0100, Stefano Zacchiroli wrote:
I'll eagerly wait feedback from the Plymouth maintainers on how to
help them debug this further :)
[ Following up with information that Laurent asked via IRC. ]
I've done "update-initramfs -k 3.16.0-4-amd64 -u" and I confirm that
after that also 3.16 became broken: it hangs before asking the LUKS
password, whereas it used to work before update-initramfs.
At least this is consistent /o\
Linux 4.1 still boots properly (asking the password via askpass),
because I haven't update-initramfs'd it.
So it is something that sneaks in upon initramfs creation, and that used
not to sneak in with older plymouth versions.
I can also confirm that the workaround of passing plymouth.enable=0 on
the kernel cmdline sidesteps the problem. I'm now running 4.3 from
experimental, which boots properly with plymouth.enable=0.
Do you have a KMS driver loaded in the initramfs?
I'm a bit surprised by the error message that I see in your 3rd
picture, I cannot reproduce this on my laptop even with plymouth
completely disabled. Did you modify anything in the initramfs scripts?
({/etc,/usr/share}/initramfs-tools/scripts)
You can also try to add plymouth.debug to the kernel cmdline (or
plymouth.debug=stream:/dev/kmsg)
Cheers,
Laurent Bigonville
