linux-kernel - Re: [PATCH linux-next V2] tty: Disable default console blanking interval

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:   Wed, 22 Mar 2017 20:32:30 -0500 (CDT)
From:   Scot Doyle <lkml14@...tdoyle.com>
To:     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 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?