lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 23 Mar 2017 08:42:03 -0400
From:   "Austin S. Hemmelgarn" <ahferroin7@...il.com>
To:     Scot Doyle <lkml14@...tdoyle.com>,
        Tim Gardner <tim.gardner@...onical.com>
Cc:     linux-kernel@...r.kernel.org,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Jiri Slaby <jslaby@...e.com>,
        Adam Borowski <kilobyte@...band.pl>
Subject: Re: [PATCH linux-next V2] tty: Disable default console blanking
 interval

On 2017-03-22 21:32, Scot Doyle wrote:
> On Wed, 22 Mar 2017, Tim Gardner wrote:
>> BugLink: http://bugs.launchpad.net/bugs/869017
>>
>> Console blanking is not enabling DPMS power saving (thereby negating any
>> power-saving benefit), and is simply turning the screen content blank. This
>> means that any crash output is invisible which is unhelpful on a server
>> (virtual or otherwise).
>>
>> Furthermore, CRT burn in concerns should no longer govern the default case.
>> Affected users could always set consoleblank on the kernel command line.
>
> Does screen blanking save some power by disabling the cursor blink?
>
Unless you're dealing with ancient hardware, the difference in power 
usage is probably on the order of single digit micro-watts, which is not 
worth worrying about on almost anything you would expect to have a 
console display connected to.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ