Bug#952452: initramfs-tools: prefers serial console over framebuffer console

From	Alper Nebi Yasak <alpernebiyasak@gmail.com>
Newsgroups	linux.debian.bugs.dist, linux.debian.kernel
Subject	Bug#952452: initramfs-tools: prefers serial console over framebuffer console
Date	2020-02-26 15:20 +0100
Message-ID	<zE5Hz-84D-1@gated-at.bofh.it> (permalink)
References	<zDpfj-57Q-1@gated-at.bofh.it> <zDpfj-57Q-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

On 24/02/2020 19:50, Alper Nebi Yasak wrote:
> I'm using Debian on an arm64 chromebook, and not setting "console=tty1"
> in the kernel command line results in a number of weird behaviours
> related to the initramfs.

Turns out my device-tree has (for debugging purposes?):

     chosen {
             stdout-path = "serial2:115200n8";
     };

Removing that makes everything work on the screen again, but that's a 
worse way to solve it compared to adding a kernel cmdline arg.

QEMU on aarch64 does a similar thing according to [0]:

     $ sudo dmesg | grep -i console
     [    0.000000] ACPI: SPCR: console: pl011,mmio,0x9000000,9600
     ...

[0] https://bugzilla.redhat.com/show_bug.cgi?id=1661288#c35

Those seem to be the root cause.

Thread

Bug#952452: initramfs-tools: prefers serial console over framebuffer console Alper Nebi Yasak <alpernebiyasak@gmail.com> - 2020-02-24 18:00 +0100
  Bug#952452: initramfs-tools: prefers serial console over framebuffer console Alper Nebi Yasak <alpernebiyasak@gmail.com> - 2020-02-26 15:20 +0100
  Bug#952452: marked as done (initramfs-tools: prefers serial  console over framebuffer console) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2020-02-27 00:20 +0100
  Bug#952452: initramfs-tools: prefers serial console over framebuffer console Alper Nebi Yasak <alpernebiyasak@gmail.com> - 2020-02-28 16:10 +0100
    Bug#952452: initramfs-tools: prefers serial console over framebuffer console Ben Hutchings <ben@decadent.org.uk> - 2020-02-28 21:50 +0100

csiph-web