Control: tag -1 moreinfo

On Fri, 24 Aug 2018 at 22:45:40 +0200, Matthias Klumpp wrote:
> Obviously no Plymouth was shown here. The log looks normal to me.

Ah right, plymouthd isn't started yet when you're dropped into the
initramfs shell, so you'll need to start it manually:
`/scripts/init-premount/plymouth`.

Are you able to reproduce this in a Debian system?  I just fired a fresh
& minimal sid VM with cryptsetup-initramfs 2:2.0.4-2 and plymouth
0.9.3-3 and

    root@kvm-23941:~# cat /etc/crypttab 
    root_crypt UUID=69498061-2e79-48a3-b637-655690cb4d16 none luks
    root@kvm-23941:~# cat /etc/fstab 
    /dev/vda1 /boot ext2 defaults 0 2
    UUID=67d6c067-545f-40e5-8f7d-e852e2490f0a none swap sw 0 0
    UUID=9945b9d7-bade-4df5-bd7c-8822a1a37274 / ext4 defaults 0 1
    /dev/sr0 /media/cdrom iso9660 ro,noauto 0 0
    root@kvm-23941:~# cat /proc/cmdline 
    BOOT_IMAGE=/vmlinuz-4.17.0-3-amd64 
root=UUID=9945b9d7-bade-4df5-bd7c-8822a1a37274 ro quiet splash

In that VM I only get the plymouth prompt (if I remove ‘splash’ I get a
single console prompt).

Are you sure the first (dummy) prompt comes from `/scripts/local-top/cryptroot`,
and not from another initramfs script?  What is being prompted exactly?

Also, your busybox doesn't seem to include fold(1), unlike the one from
buster.  But that's most likely unrelated.

-- 
Guilhem.

Attachment: signature.asc
Description: PGP signature

Reply via email to