Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #206359 > unrolled thread

blank time in console too short

Back to article view | Back to linux.debian.user

Contents

  blank time in console too short Hans <hans.ullrich@loop.de> - 2019-03-19 12:10 +0100
    Re: blank time in console too short Martin <keine-eile@online.de> - 2019-03-19 12:30 +0100
      Re: blank time in console too short Greg Wooledge <wooledg@eeg.ccf.org> - 2019-03-19 13:40 +0100
        Re: blank time in console too short Hans <hans.ullrich@loop.de> - 2019-03-19 13:50 +0100
          Re: blank time in console too short deloptes <deloptes@gmail.com> - 2019-03-20 05:30 +0100
    Re: blank time in console too short Felix Miata <mrmazda@earthlink.net> - 2019-03-20 05:40 +0100
      Re: blank time in console too short Hans <hans.ullrich@loop.de> - 2019-03-20 07:20 +0100
    Re: blank time in console too short Hans <hans.ullrich@loop.de> - 2019-03-22 08:10 +0100
      Re: blank time in console too short deloptes <deloptes@gmail.com> - 2019-03-22 20:50 +0100

#206359 — blank time in console too short

[Multipart message — attachments visible in raw view] — view raw

Hi folks, 

on my EEEPC, debian/testing, i386 since last update the blank time of the 
console (TTY1 - 5 ) is too short (1 Minute).

I checked with another system, but all configurations are the same.

How can I increase the time, until the console is blanking?

I know of setterm, and I checked /etc/console-*/* as well as /etc/laptop-mode/
*. 

Others, like /etc/kbd/* or /etc/init/tty/* are not existent on both systems.

I also know, that the blank time is hardcoded in the kernel (both got the same 
kernel version) and that it can be set either by a kernel parameter or using a 
setterm command in a login.def.

Question: 
Is there any configuration option I missed? 

If "NO": Why is the behaviour different between the systems?

If "YES": Where should I look, too?

Thanks for any hints.


Best regards

Hans

[toc] | [next] | [standalone]

#206361

May be, it is bash's TMOUT what you are looking for.

Am 19.03.19 um 12:08 schrieb Hans:
> Hi folks, 
> 
> on my EEEPC, debian/testing, i386 since last update the blank time of the 
> console (TTY1 - 5 ) is too short (1 Minute).
> 
> I checked with another system, but all configurations are the same.
> 
> How can I increase the time, until the console is blanking?
> 
> I know of setterm, and I checked /etc/console-*/* as well as /etc/laptop-mode/
> *. 
> 
> Others, like /etc/kbd/* or /etc/init/tty/* are not existent on both systems.
> 
> I also know, that the blank time is hardcoded in the kernel (both got the same 
> kernel version) and that it can be set either by a kernel parameter or using a 
> setterm command in a login.def.
> 
> Question: 
> Is there any configuration option I missed? 
> 
> If "NO": Why is the behaviour different between the systems?
> 
> If "YES": Where should I look, too?
> 
> Thanks for any hints.
> 
> 
> Best regards
> 
> Hans
> 

[toc] | [prev] | [next] | [standalone]

#206362

On Tue, Mar 19, 2019 at 12:28:43PM +0100, Martin wrote:
> May be, it is bash's TMOUT what you are looking for.

No, that makes the shell exit.  It doesn't do anything to the monitor.

Try looking at setterm(1), perhaps?

> Am 19.03.19 um 12:08 schrieb Hans:
> > I know of setterm, and I checked /etc/console-*/* as well as /etc/laptop-mode/
> > *. 

Oh.  Well, there goes my knowledge.

> > Others, like /etc/kbd/* or /etc/init/tty/* are not existent on both systems.
> > 
> > I also know, that the blank time is hardcoded in the kernel (both got the same 
> > kernel version) and that it can be set either by a kernel parameter or using a 
> > setterm command in a login.def.

Oh, it sounds like you already knew the answer before you asked us.
For the benefit of others who may be searching the archives looking
for the answer to this question, perhaps you could tell us which kernel
parameter this is.

(So, why did you ask us?)

[toc] | [prev] | [next] | [standalone]

#206368

[Multipart message — attachments visible in raw view] — view raw

> > > I also know, that the blank time is hardcoded in the kernel (both got
> > > the same kernel version) and that it can be set either by a kernel
> > > parameter or using a setterm command in a login.def.
> 
> Oh, it sounds like you already knew the answer before you asked us.
> For the benefit of others who may be searching the archives looking
> for the answer to this question, perhaps you could tell us which kernel
> parameter this is.
> 
> (So, why did you ask us?)

I had the hope, there might be someone pointing me to something else, I missed 
somewhere. :)

Best

Hans

[toc] | [prev] | [next] | [standalone]

#206382

Hans wrote:

> I had the hope, there might be someone pointing me to something else, I
> missed somewhere. :)

by blank you mean the screen goes dark or the time it waits for password?
For me blank is the screen goes dark and this is setting the blanking of the
screen - nothing to do with the console or terminal settings. It happens
when I use RS232 to connect to the firewall for example, but I don't know
how long it takes - if it is a minute or more.

[toc] | [prev] | [next] | [standalone]

#206383

Hans composed on 2019-03-19 12:08 (UTC+0100):

> on my EEEPC, debian/testing, i386 since last update the blank time of the 
> console (TTY1 - 5 ) is too short (1 Minute).

> I checked with another system, but all configurations are the same.

> How can I increase the time, until the console is blanking?

How about no blanking at all?
consoleblank=0
https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt
-- 
Evolution as taught in public schools is religion, not science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#206384

[Multipart message — attachments visible in raw view] — view raw

No, this is not want I want. However, i know ybout kernel params.

Best

Hans

> How about no blanking at all?
> consoleblank=0
> https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt

[toc] | [prev] | [next] | [standalone]

#206446

[Multipart message — attachments visible in raw view] — view raw

Am Donnerstag, 21. März 2019, 23:13:39 CET schrieb deloptes:




On Wed, Mar 20, 2019 at 7:15 AM Hans <hans.ullrich@loop.de[1]> wrote:


>> No, I mean not in windowmanager (or X), I mean in TTY1 - 5.



> So what about the monitor or precisely the DPMS setting 


As I said, not in X, but the console in the terminal you reach by ALT-F1, ALT-F2 and 
so on. And sa I also said: Both systems got an identical configuration but behave 
different.

Best

Hans


https://wiki.archlinux.org/index.php/
Display_Power_Management_Signaling#DPMS_interaction_in_a_Linux_console_with
_setterm[2]







--------
[1] mailto:hans.ullrich@loop.de
[2] https://wiki.archlinux.org/index.php/
Display_Power_Management_Signaling#DPMS_interaction_in_a_Linux_console_with
_setterm

[toc] | [prev] | [next] | [standalone]

#206477

Hans wrote:

> As I said, not in X, but the console in the terminal you reach by ALT-F1,
> ALT-F2 and so on. And sa I also said: Both systems got an identical
> configuration but behave different.
> 
> Best
> 
> Hans
> 
> 
> https://wiki.archlinux.org/index.php/
>
Display_Power_Management_Signaling#DPMS_interaction_in_a_Linux_console_with
> _setterm[2]

And the link I sent is about DPMS on the console and it is also not clear if
they use the same monitor, but even so - they might have different video
cards.

regards

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web