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. 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. Hope this helps, Cheers. -- Stefano Zacchiroli . . . . . . . z...@upsilon.cc . . . . o . . . o . o Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o Former Debian Project Leader . . . . . @zacchiro . . . . o o o . . . o . « the first rule of tautology club is the first rule of tautology club »
