Bug#897572: linux-image-4.16.0-1-amd64 breaks plymouth LUKS prompt

Manually installing kbl_dmc_ver1_04.bin and kbl_guc_ver9_39.bin from into /lib/firmware/i915 and running update-initramfs does not fix, so it it not a firmware issue. The firmware errors are removed, leaving

Bug#897572: linux-image-4.16.0-1-amd64 breaks plymouth LUKS prompt

Trying to switch consoles with Alt-F1 to Alt-F7 many time eventually causes the plymouth LUKS screen to appear. This does not seem to be deterministic. Kind regards, -- Ben Caradoc-Davies Director Transient Software Limited New Zealand

Bug#897572: linux-image-4.16.0-1-amd64 breaks plymouth LUKS prompt

And I should mention that my plymouth LUKS screen was working fine with kernels up to and including linux-image-4.15.0-3-amd64 4.15.17-1. Kind regards, -- Ben Caradoc-Davies Director Transient Software Limited New Zealand

Bug#897572: linux-image-4.16.0-1-amd64 breaks plymouth LUKS prompt

On 03/05/18 17:37, Ben Caradoc-Davies wrote: And I should mention that my plymouth LUKS screen was working fine with kernels up to and including linux-image-4.15.0-3-amd64 4.15.17-1. And to eliminate any other change on the system as a cause, I rebuilt initrd.img for both packages and the plym

Bug#897572: linux-image-4.16.0-1-amd64 breaks plymouth LUKS prompt

More findings: - Adding i915 to /etc/initramfs-tools/modules as described in #803658 ("boot hangs before cryptsetup passphrase prompt if i915 drm driver is not in initramfs") has no effect. - Pressing *any* key repeatedly is enough to eventually wake up the plymouth LUKS screen. For example,

Bug#897572: linux-image-4.16.0-1-amd64 breaks plymouth LUKS prompt

On Fri, 2018-05-04 at 12:20 +1200, Ben Caradoc-Davies wrote: > On 04/05/18 11:52, Ben Caradoc-Davies wrote: > > - Pressing *any* key repeatedly is enough to eventually wake up the > > plymouth LUKS screen. For example, pressing Backspace many times. > > Even a modifier key is sufficient. Without

Bug#897572: linux-image-4.16.0-1-amd64 breaks plymouth LUKS prompt

On 06/05/18 07:01, Ben Hutchings wrote: I wonder if this is related to the recent RNG changes. It seems that many programs have started using blocking RNG functions like getentropy(), and now that the kernel is more conservative in its initial entropy estimation they can block for a long time.

Bug#897572: linux-image-4.16.0-1-amd64 breaks plymouth LUKS prompt

On Sun, 2018-05-06 at 12:33 +1200, Ben Caradoc-Davies wrote: > On 06/05/18 07:01, Ben Hutchings wrote: > > I wonder if this is related to the recent RNG changes. It seems that > > many programs have started using blocking RNG functions like > > getentropy(), and now that the kernel is more conserv

Bug#897572: linux-image-4.16.0-1-amd64 breaks plymouth LUKS prompt

On Sat, 05 May 2018 20:01:45 +0100 Ben Hutchings wrote: > On Fri, 2018-05-04 at 12:20 +1200, Ben Caradoc-Davies wrote: > > On 04/05/18 11:52, Ben Caradoc-Davies wrote: > > > - Pressing *any* key repeatedly is enough to eventually wake up the > > > plymouth LUKS screen. For example, pressing Back

Bug#897572: linux-image-4.16.0-1-amd64 breaks plymouth LUKS prompt

On Sun, 2018-05-06 at 17:22 +0200, Laurent Bigonville wrote: > On Sat, 05 May 2018 20:01:45 +0100 Ben Hutchings > wrote: > > On Fri, 2018-05-04 at 12:20 +1200, Ben Caradoc-Davies wrote: > > > On 04/05/18 11:52, Ben Caradoc-Davies wrote: > > > > - Pressing *any* key repeatedly is enough to even

Bug#897572: linux-image-4.16.0-1-amd64 breaks plymouth LUKS prompt (missing Kaby Lake firmware?)

Package: linux Version: linux-image-4.16.0-1-amd64 Severity: normal Dear Maintainer, booting with linux-image-4.16.0-1-amd64 causes the plymouth LUKS prompt to not be displayed, preventing password entry and thus boot. System can still be rebooted with Ctrl-Alt-Del. The system is an Intel Kaby L