vt: disable console blanking by default
Subsystems (2)
PATCH 1/1 vt: disable console blanking by default
Quoted 2 lines
From
ea7cf47e3230eda63aa6c46092719437f9bbae8eMon Sep 17 00:00:00 2001
From: Tomasz Torcz <[email protected]>
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.
--- Documentation/kernel-parameters.txt | 4 ++-- drivers/tty/vt/vt.c | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-)
Documentation/kernel-parameters.txt +2 -2
@@ -710,8 +710,8 @@ bytes respectively. Such letter suffixes can also be entirely omitted. For now, only VisioBraille is supported. consoleblank= [KNL] The console blank (screen saver) timeout in - seconds. Defaults to 10*60 = 10mins. A value of 0 - disables the blank timer. + seconds. A value of 0 disables the blank timer. + Defaults to never blank. coredump_filter= [KNL] Change the default value for
drivers/tty/vt/vt.c +1 -1
@@ -176,7 +176,7 @@ int console_blanked;static int vesa_blank_mode;/* 0:none 1:suspendV 2:suspendH 3:powerdown */ static int vesa_off_interval; -static int blankinterval =10 *60 ; +static int blankinterval;core_param (consoleblank, blankinterval, int,0444 ); static DECLARE_WORK(console_work, console_callback);
Signature · 5 lines
1.9.3 -- Tomasz Torcz Only gods can safely risk perfection, xmpp: [email protected] it's a dangerous thing for a man. -- Alia
Quoted 6 lines · Tomasz Torcz
Quoted 2 lines
From
ea7cf47e3230eda63aa6c46092719437f9bbae8eMon Sep 17 00:00:00 2001From: Tomasz Torcz <[email protected]>
Date: Wed, 18 Jun 2014 11:18:06 +0200
Subject: [PATCH] vt: disable console blanking by default
Quoted 7 lines
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.Signed-off-by Tomasz Torcz <[email protected]>
Dunno. You'll kill an LCD if you let same image there for too long. Make it 10hours?
Pavel
Quoted 32 lines
Documentation/kernel-parameters.txt | 4 ++-- drivers/tty/vt/vt.c | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-)Documentation/kernel-parameters.txt +2
-2@@ -710,8 +710,8 @@ bytes respectively. Such letter suffixes can also be entirely omitted. For now, only VisioBraille is supported. consoleblank= [KNL] The console blank (screen saver) timeout in - seconds. Defaults to 10*60 = 10mins. A value of 0 - disables the blank timer. + seconds. A value of 0 disables the blank timer. + Defaults to never blank. coredump_filter= [KNL] Change the default value fordrivers/tty/vt/vt.c +1
-1@@ -176,7 +176,7 @@ int console_blanked;static int vesa_blank_mode;/* 0:none 1:suspendV 2:suspendH 3:powerdown */ static int vesa_off_interval; -static int blankinterval =10 *60 ; +static int blankinterval;core_param (consoleblank, blankinterval, int,0444 ); static DECLARE_WORK(console_work, console_callback);
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Quoted 13 lines · Pavel Machek
Quoted 12 lines · Tomasz Torcz
Quoted 2 lines
From
ea7cf47e3230eda63aa6c46092719437f9bbae8eMon Sep 17 00:00:00 2001From: Tomasz Torcz <[email protected]>
Date: Wed, 18 Jun 2014 11:18:06 +0200
Subject: [PATCH] vt: disable console blanking by defaultRemove 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.
Quoted 4 lines
Quoted 1 line
Signed-off-by Tomasz Torcz <[email protected]>Dunno. You'll kill an LCD if you let same image there for too long. Make it 10hours?
There is no practical difference between 10 minutes and 10 hours. Both
are more than none. This means that If I need to access console, it will probably be blanked. For some servers, console access is needed less than once per year, if ever. But IF the console need to be accessed, there's a strong reason to it (some kind of fault), and having to press anything to unblank may be invasive.
I would prefer to fix the issue at the source, instead of sticking "consoleblank=0"
in grub2.cfg on houndreds of boxes. BTW, kernel already contains "consoleblank=0" in arch/arc/boot/dts/nsimosci.dts and arch/arm/boot/dts/omap3-lilly-a83x.dtsi
Is LCD damage for currently produced LCDs real issue, still?
Signature · 2 lines
Tomasz Torcz To co nierealne -- tutaj jest normalne. xmpp: [email protected] Ziomale na życie mają tu patenty specjalne.
Quoted 26 lines · Tomasz Torcz
Quoted 13 lines · Pavel Machek
Quoted 12 lines · Tomasz Torcz
Quoted 2 lines
From
ea7cf47e3230eda63aa6c46092719437f9bbae8eMon Sep 17 00:00:00 2001From: Tomasz Torcz <[email protected]>
Date: Wed, 18 Jun 2014 11:18:06 +0200
Subject: [PATCH] vt: disable console blanking by defaultRemove 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.Quoted 4 lines
Quoted 1 line
Signed-off-by Tomasz Torcz <[email protected]>Dunno. You'll kill an LCD if you let same image there for too long. Make it 10hours?
There is no practical difference between 10 minutes and 10 hours. Both
are more than none. This means that If I need to access console, it will probably be blanked. For some servers, console access is needed less than once per year, if ever. But IF the console need to be accessed, there's a strong reason to it (some kind of fault), and having to press anything to unblank may be invasive.
Quoted 5 lines
I would prefer to fix the issue at the source, instead of sticking "consoleblank=0"
in grub2.cfg on houndreds of boxes. BTW, kernel already contains "consoleblank=0" inarch/arc/boot/dts/nsimosci.dtsandarch/arm/boot/dts/omap3-lilly-a83x.dtsiIs LCD damage for currently produced LCDs real issue, still?
Probably yes. Plus, people are still running CRTs and blanked screen still eats significantly less power. So "consoleblank=0" seems right solution for you, and current default still sounds right.
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Quoted 11 lines · On Wed, 18 Jun 2014 11:27:31 +0200 Tomasz Torcz <[email protected]> wrote:
Quoted 2 lines
From
ea7cf47e3230eda63aa6c46092719437f9bbae8eMon Sep 17 00:00:00 2001From: Tomasz Torcz <[email protected]>
Date: Wed, 18 Jun 2014 11:18:06 +0200
Subject: [PATCH] vt: disable console blanking by defaultRemove 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.
Alan
Quoted 19 lines · One Thousand Gnomes
On Wed, 18 Jun 2014 11:27:31 +0200
Quoted 11 lines · Tomasz Torcz
Quoted 1 line
From
ea7cf47e3230eda63aa6c46092719437f9bbae8eMon Sep 17 00:00:00 2001From: Tomasz Torcz <[email protected]>
Date: Wed, 18 Jun 2014 11:18:06 +0200
Subject: [PATCH] vt: disable console blanking by defaultRemove 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.
Quoted 7 lines
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.
Quoted 1 line
Alan
Signature · 1 line
Arkadiusz Miśkiewicz, arekm / maven.pl
Quoted 1 line
3. unblank & disable blanking on any oops? (probably problematic)
We already try to do that.
Alan