From: Alper Nebi Yasak <alpernebiyasak@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>, Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Alper Nebi Yasak <alpernebiyasak@gmail.com>
Subject: [RFC PATCH 0/3] Prefer working VT console over SPCR and device-tree chosen stdout-path
Date: Mon, 23 Mar 2020 13:47:31 +0300 [thread overview]
Message-ID: <44156595-0eee-58da-4376-fd25b634d21b@gmail.com> (raw)
I recently experienced some trouble with setting up an encrypted-root
system, my Chromebook Plus (rk3399-gru-kevin, ARM64) would appear to
hang where it should have asked for an encryption passphrase; and I
eventually figured out that the kernel preferred the serial port
(inaccessible to me) over the built-in working display/keyboard and was
probably asking there.
Running plymouth in the initramfs solves that specific problem, but
both the documentation and tty-related kconfig descriptions imply that
/dev/console should be tty0 if graphics are working, CONFIG_VT_CONSOLE
is enabled and no explicit console argument is given in the kernel
commandline.
This patchset tries to ensure that VT is preferred in those conditions
even in the presence of firmware-mandated serial consoles. These should
be applicable onto next-20200323 without conflicts (also onto v5.6-rc7
with --3way minus the references to a "has_preferred_console" var).
More discussion due to or about the console confusion on ARM64:
- My Debian bug report about the initramfs prompts [0]
- Fedora test issue arising from ARM64 QEMU machines having SPCR [1]
- Debian-installer discussion on what to do with multiple consoles [2]
[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952452
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1661288
[2] https://lists.debian.org/debian-boot/2019/01/msg00184.html
Alper Nebi Yasak (3):
printk: Add function to set console to preferred console's driver
vt: Set as preferred console when a non-dummy backend is bound
printk: Preset tty0 as a pseudo-preferred console
drivers/tty/vt/vt.c | 7 +++++
include/linux/console.h | 1 +
kernel/printk/printk.c | 68 +++++++++++++++++++++++++++++++++++++++++
3 files changed, 76 insertions(+)
--
2.26.0.rc2
next reply other threads:[~2020-03-23 10:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 10:47 Alper Nebi Yasak [this message]
2020-03-23 10:48 ` [RFC PATCH 1/3] printk: Add function to set console to preferred console's driver Alper Nebi Yasak
2020-03-23 10:50 ` [RFC PATCH 2/3] vt: Set as preferred console when a non-dummy backend, is bound Alper Nebi Yasak
2020-03-23 10:50 ` [RFC PATCH 3/3] printk: Preset tty0 as a pseudo-preferred console Alper Nebi Yasak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44156595-0eee-58da-4376-fd25b634d21b@gmail.com \
--to=alpernebiyasak@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).