Re: [PATCH] vt: Add boot param for setting default vt console
From: Greg Kroah-Hartman
Date: Thu Mar 12 2026 - 10:31:43 EST
On Sun, Mar 01, 2026 at 04:48:04PM -0500, Adam Saponara wrote:
> Presently the default console is hard-coded to vt1.
>
> The param allows for setting a different default. The param defaults to 0
> (vt1), preserving the current behavior. It is clamped by the constants
> `(MIN|MAX)_NR_CONSOLES`. If set `>= MIN`, `con_init` will initialize that
> vt as well (a couple extra kilobytes heap for the `vc_data` and
> `vc_screenbuf` structs).
>
> Without this feature, users achieve the same effect with an init
> script[0][1][2][3]. This works but requires an extra `chvt(1)` which can
> race with user interaction and flicker the screen at login.
What user interaction races? I'm loath to change this as I've not seen
any bug reports for this. What changed to cause this issue?
And this is for the "odd" systems that want a graphical login, BUT still
want to default to the console? That's a very odd configuration, and I
think that we should just stick with the fix that we have for those that
want to do this as adding more boot parameters that we need to support
for forever feels like a bad idea.
sorry,
greg k-h