wrong kernel commandline after classic install with canary image

[Steve Langasek]

After install with the canary image a classic install (no tpm fde) has the wrong kernel commandline, with 'quiet splash' missing. As a result no splash screen is shown at boot, the user gets text scroll instead.

[Steve Langasek (vorlon)]

I have confirmed this does not happen with daily-live 20230825.

[Steve Langasek (vorlon)]

I believe this is because 'quiet splash' boot options are missing from the canary image itself, via debian-cd:

            elif [ "$SUBPROJECT" = "canary" ]; then
                # temporarily, disable quiet and splash for canary images
                KERNEL_PARAMS="${KERNEL_PARAMS:+$KERNEL_PARAMS }layerfs-path=standard.live.squashfs ---"

so I expect this will resolve itself when merged into daily-live.

[Steve Langasek (vorlon)]

Well, except the full difference between the grub.cfg of the two installs shows:

- search --no-floppy --fs-uuid --set=root 5815784e-26c9-4408-9dea-ccb2398a1f9a
- linux /boot/vmlinuz-6.3.0-7-generic root=UUID=5815784e-26c9-4408-9dea-ccb2398a1f9a ro
+ search --no-floppy --fs-uuid --set=root 877df776-8c5a-45ff-817a-08d88d25d97b
+ linux /boot/vmlinuz-6.3.0-7-generic root=UUID=877df776-8c5a-45ff-817a-08d88d25d97b ro quiet splash $vt_handoff

And the $vt_handoff does *not* come from debian-cd. So it appears we have a difference here that probably wouldn't fix itself in the merge to daily-live.

[Steve Langasek (vorlon)]

I was surprised to see a splash screen after doing an install with Spanish as the language.

[Steve Langasek (vorlon)]

oops, sorry, the splash screen was when doing an fde install not a classic install. commandline is correct for an fde install.

[Steve Langasek (vorlon)]

the vt_handoff is appended by grub code *if* splash is present in the list of default options in /etc/default/grub.

Updating debian-cd to no longer treat canary specially wrt kernel commandline, so we can confirm everything works as expected when using the target options.

[Jean-Baptiste Lallement (jibel)]

This is fixed 20230829

[Steve Langasek (vorlon)]

Confirmed that this is resolved with the 20230829 canary image.