On Wednesday 25 of June 2014, One Thousand Gnomes wrote: > On Wed, 18 Jun 2014 11:27:31 +0200 > > Tomasz Torcz <to...@pipebreaker.pl> wrote: > > >From ea7cf47e3230eda63aa6c46092719437f9bbae8e Mon Sep 17 00:00:00 2001 > > > > From: Tomasz Torcz <to...@pipebreaker.pl> > > Date: Wed, 18 Jun 2014 11:18:06 +0200 > > Subject: [PATCH] vt: disable console blanking by default > > > > Remove default 10 minute blank interval. Instead: never blank by > > default. > > "Screensaving" is no longer useful. Today it only provides > > obstacle when interacting with text console, especially through > > remote lights-out management solutions. > > Screensaving is extremely useful as is power management, and power prices > are going up not down. We don't customise the upstream kernel just > because J Random User happens to want his defaults. > > There are a couple of things you can sensibly do > > 1. Just turn it off in software. It's run time configurable via setterm > > 2. If you have a reliable way of detecting the presence of a remote > console device and that device supports reporting when a connection is > made/broken you could submit a patch to make it unblank on connect.
3. unblank & disable blanking on any oops? (probably problematic) Anyway I dislike blanking here, too. > Alan -- Arkadiusz MiĆkiewicz, arekm / maven.pl -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/