Re: OT: console-setup (Re: Bug#796603: closed by Anton Zinoviev <email@example.com> (Bug#796603: fixed in console-setup 1.138))
On Sun, Mar 20, 2016 at 11:46:30AM +0300, Adam Wilson wrote:
> On Sat, 19 Mar 2016 12:55:41 +0300
> Anton Zinoviev <firstname.lastname@example.org> wrote:
> > On Wed, Mar 16, 2016 at 03:22:42PM -0300, Felipe Sateler wrote:
> > > Yet another one would be to have setupcon itself detect the
> > > existence of the cached scripts.
> > The only reason there are cached scripts is that people are
> > complaining that console-setup is slow at boot. The cached scripts
> > contain the mininum configuration sufficient to configure the
> > console. If we run setupcon, we don't need cached scripts.
> Is console-setup the thing which initialises the console fonts and
Yes, it is. Not using console-setup is much faster and the so called
"normal"-fonts are used. Maybe console-setup is changing that behavior
But! When "normal"-fonts are set on TTY 2-6 by systemD and finishes
kernel is not ready. Maybe some grace period because of checking
fat partitions on slow USB-sticks? And so, TTY1 gets a change in
using console-setup. How could that get logged?
> Is its slowness the reason why, on boot, it takes a few
> seconds for the text-mode screen to transition to a virtual terminal,
> which then has its font changed a few seconds later to the more
> readable Debian default?
> Why is console-setup so slow?
Who could get that out? And how?