[opensuse] leap15 - how do I enable display power saving ?
I realised this a while back - in Leap15 on real iron, the display is not being switched into power saving after a while. What do I need to do to enable that? Minimum server install, so no GUI. -- Per Jessen, Zürich (18.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Per Jessen <per@computer.org> [05-23-18 08:09]:
I realised this a while back - in Leap15 on real iron, the display is not being switched into power saving after a while. What do I need to do to enable that? Minimum server install, so no GUI.
xset +dpms xset dpms <value> <value> <value> sleep 1; xset s on to see settings: xset q -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-23 14:36, Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [05-23-18 08:09]:
I realised this a while back - in Leap15 on real iron, the display is not being switched into power saving after a while. What do I need to do to enable that? Minimum server install, so no GUI.
xset +dpms xset dpms <value> <value> <value> sleep 1; xset s on
to see settings: xset q
No X, remember. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [05-23-18 08:09]:
I realised this a while back - in Leap15 on real iron, the display is not being switched into power saving after a while. What do I need to do to enable that? Minimum server install, so no GUI.
xset +dpms xset dpms <value> <value> <value> sleep 1; xset s on
to see settings: xset q
That seems to intended for X ? # xset q xset: unable to open display "" -- Per Jessen, Zürich (19.7°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Per Jessen <per@computer.org> [05-23-18 08:44]:
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [05-23-18 08:09]:
I realised this a while back - in Leap15 on real iron, the display is not being switched into power saving after a while. What do I need to do to enable that? Minimum server install, so no GUI.
xset +dpms xset dpms <value> <value> <value> sleep 1; xset s on
to see settings: xset q
That seems to intended for X ?
# xset q xset: unable to open display ""
then try your bios, many if not most provide a green mode or a display blanking -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [05-23-18 08:44]:
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [05-23-18 08:09]:
I realised this a while back - in Leap15 on real iron, the display is not being switched into power saving after a while. What do I need to do to enable that? Minimum server install, so no GUI.
xset +dpms xset dpms <value> <value> <value> sleep 1; xset s on
to see settings: xset q
That seems to intended for X ?
# xset q xset: unable to open display ""
then try your bios, many if not most provide a green mode or a display blanking
It's not a BIOS setting, other machines do this by default. (pre- Leap15). -- Per Jessen, Zürich (20.7°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-23 14:08, Per Jessen wrote:
I realised this a while back - in Leap15 on real iron, the display is not being switched into power saving after a while. What do I need to do to enable that? Minimum server install, so no GUI.
I saw posts recently about this, I think. Some systemd tool or setting somewhere, I think. now, how to find the post...? The person asking the question I think found a desktop method, but in the conversation a generic one arouse. I said to myself I was going to take a note, but I don't remember where :-( I grepped for a few strings, no luck. I remember that on my previous home server I resorted to start X and terminals there for the only purpose of having the screen power off. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
On 2018-05-23 14:08, Per Jessen wrote:
I realised this a while back - in Leap15 on real iron, the display is not being switched into power saving after a while. What do I need to do to enable that? Minimum server install, so no GUI.
I saw posts recently about this, I think. Some systemd tool or setting somewhere, I think. now, how to find the post...?
The person asking the question I think found a desktop method, but in the conversation a generic one arouse. I said to myself I was going to take a note, but I don't remember where :-( I grepped for a few strings, no luck.
I remember that on my previous home server I resorted to start X and terminals there for the only purpose of having the screen power off.
It works fine on older distros - e.g. 12.3 and 42.3. I just don't know _how_ it works, so I might work out what's missing on my Leap15 installs. -- Per Jessen, Zürich (21.1°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
I realised this a while back - in Leap15 on real iron, the display is not being switched into power saving after a while. What do I need to do to enable that? Minimum server install, so no GUI.
Should be done via setterm IIRC. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Peter Suetterlin wrote:
Per Jessen wrote:
I realised this a while back - in Leap15 on real iron, the display is not being switched into power saving after a while. What do I need to do to enable that? Minimum server install, so no GUI.
Should be done via setterm IIRC.
Thanks for the hint! I tried 'setterm --blank 1' - which did blank the scren after a minute. That's a good start, now I'm waiting to see if it'll also put it in suspend. This must be (have been) part of the virtual console start-up. -- Per Jessen, Zürich (22.6°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Peter Suetterlin wrote:
Per Jessen wrote:
I realised this a while back - in Leap15 on real iron, the display is not being switched into power saving after a while. What do I need to do to enable that? Minimum server install, so no GUI.
Should be done via setterm IIRC.
Thanks for the hint!
I tried 'setterm --blank 1' - which did blank the scren after a minute. That's a good start, now I'm waiting to see if it'll also put it in suspend.
This must be (have been) part of the virtual console start-up.
I've found out that 'setterm --blank' sets /sys/module/kernel/parameters/consoleblank This may also be set at boot-up using kernel argument: consoleblank=xx I guess the default was changed in 15.0. Looking at my 42.3 systems, they have /sys/module/kernel/parameters/consoleblank = 600. -- Per Jessen, Zürich (23.1°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
I've found out that 'setterm --blank' sets
/sys/module/kernel/parameters/consoleblank
This may also be set at boot-up using kernel argument:
consoleblank=xx
Ah, more info/options are always good :)
I guess the default was changed in 15.0. Looking at my 42.3 systems, they have
/sys/module/kernel/parameters/consoleblank = 600.
My TW has it set to zero, too. But this is only screenblank - DPMS might need setterm --powersave on -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Peter Suetterlin wrote:
Per Jessen wrote:
I've found out that 'setterm --blank' sets
/sys/module/kernel/parameters/consoleblank
This may also be set at boot-up using kernel argument:
consoleblank=xx
Ah, more info/options are always good :)
I would just prefer not supplying this kind of "unimportant" information as a kernel argument. I guess I'll have to add a 'setterm' somewhere in the agetty scripts.
I guess the default was changed in 15.0. Looking at my 42.3 systems, they have
/sys/module/kernel/parameters/consoleblank = 600.
My TW has it set to zero, too.
But this is only screenblank - DPMS might need setterm --powersave on
Yes, I'm just testing that. I'm waiting to see if my older systems will do a monitor suspend. (which I believe they did/should do). -- Per Jessen, Zürich (21.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Peter Suetterlin wrote:
But this is only screenblank - DPMS might need setterm --powersave on
Yes, I'm just testing that. I'm waiting to see if my older systems will do a monitor suspend. (which I believe they did/should do).
Hmm, on the first attempt, I don't see any monitor suspend. Nor on the 2nd with a Leap15 system (setterm --blank 60 --powersave on). TBH, it's not a major problem, we only have a few monitors in the datacentre, we're just not use to seeing them on all the time. Still, now that I've looked into it, having them suspend would be nice. (they can on for weeks and months). -- Per Jessen, Zürich (21.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-23 19:23, Per Jessen wrote:
Per Jessen wrote:
Peter Suetterlin wrote:
But this is only screenblank - DPMS might need setterm --powersave on
Yes, I'm just testing that. I'm waiting to see if my older systems will do a monitor suspend. (which I believe they did/should do).
Hmm, on the first attempt, I don't see any monitor suspend. Nor on the 2nd with a Leap15 system (setterm --blank 60 --powersave on).
TBH, it's not a major problem, we only have a few monitors in the datacentre, we're just not use to seeing them on all the time. Still, now that I've looked into it, having them suspend would be nice. (they can on for weeks and months).
It saves some electricity. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 05/23/2018 12:23 PM, Per Jessen wrote:
Per Jessen wrote:
Peter Suetterlin wrote:
But this is only screenblank - DPMS might need setterm --powersave on
Yes, I'm just testing that. I'm waiting to see if my older systems will do a monitor suspend. (which I believe they did/should do).
Hmm, on the first attempt, I don't see any monitor suspend. Nor on the 2nd with a Leap15 system (setterm --blank 60 --powersave on).
TBH, it's not a major problem, we only have a few monitors in the datacentre, we're just not use to seeing them on all the time. Still, now that I've looked into it, having them suspend would be nice. (they can on for weeks and months).
This is frustrating has hell, and I think it is kernel related more than anything else. This problem showed up on Arch several months ago. The default console just stopped blanking itself. I don't recall if it was with 4.16 or one of the .1, .2 --- releases since. I just got to the point I leave the monitors turned off. If you find a solution, I'm interested. I can't believe crap just breaks that has been working fine for 15 years and isn't fixed before it gets released. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
David C. Rankin wrote:
On 05/23/2018 12:23 PM, Per Jessen wrote:
Per Jessen wrote:
Peter Suetterlin wrote:
But this is only screenblank - DPMS might need setterm --powersave on
Yes, I'm just testing that. I'm waiting to see if my older systems will do a monitor suspend. (which I believe they did/should do).
Hmm, on the first attempt, I don't see any monitor suspend. Nor on the 2nd with a Leap15 system (setterm --blank 60 --powersave on).
TBH, it's not a major problem, we only have a few monitors in the datacentre, we're just not use to seeing them on all the time. Still, now that I've looked into it, having them suspend would be nice. (they can on for weeks and months).
This is frustrating has hell, and I think it is kernel related more than anything else. This problem showed up on Arch several months ago.
Ah, that's interesting.
The default console just stopped blanking itself. I don't recall if it was with 4.16 or one of the .1, .2 --- releases since. I just got to the point I leave the monitors turned off.
I know, the easiest solution. Except you have to reemember to do it :-(
If you find a solution, I'm interested. I can't believe crap just breaks that has been working fine for 15 years and isn't fixed before it gets released.
I have to agree, it's a bit annoying. Testing it is not so easy though. We've had Leap15 running for maybe 2 months, yet it was only yesterday I noticed this. It's one of these "exotic" things that many people have no reason to use. Well, as for a solution - I'll keep digging to see if I can have a monitor put into suspend, but the consoleblank default setting has to be in the kernel somewhere. -- Per Jessen, Zürich (15.2°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/24/2018 12:48 AM, Per Jessen wrote:
I have to agree, it's a bit annoying. Testing it is not so easy though. We've had Leap15 running for maybe 2 months, yet it was only yesterday I noticed this. It's one of these "exotic" things that many people have no reason to use.
Well, as for a solution - I'll keep digging to see if I can have a monitor put into suspend, but the consoleblank default setting has to be in the kernel somewhere.
And note, this wasn't a slight on openSuSE testing, I don't think openSuSE had anything to do with it as I have seen this behavior on multiple distros starting sometime in the 4.16.x time frame (it could have been with the 0 release). The only reason I notice is I have 2 servers that have no need for X, so they only have the console up. For literally 15 years, with all AMD, NVidia and Intel video the consoles have always blanked. From the time of CRT's and using xvidtune to setup X it has always worked. I'm not sure it is such an exotic feature. Surely you and I are not the only people that use Linux as a server that don't have X installed ;-) The other possibility is that the kernel code was removed and the blanking responsibility is not another undocumented (or poorly documented) systemd feature. I haven't had the time to run this issue to the ground. I suspect, like others, a simple Monitor->Off has had to do in the interim. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
David C. Rankin wrote:
On 05/24/2018 12:48 AM, Per Jessen wrote:
I have to agree, it's a bit annoying. Testing it is not so easy though. We've had Leap15 running for maybe 2 months, yet it was only yesterday I noticed this. It's one of these "exotic" things that many people have no reason to use.
Well, as for a solution - I'll keep digging to see if I can have a monitor put into suspend, but the consoleblank default setting has to be in the kernel somewhere.
And note, this wasn't a slight on openSuSE testing, I don't think openSuSE had anything to do with it as I have seen this behavior on multiple distros starting sometime in the 4.16.x time frame (it could have been with the 0 release).
Right, I think so too.
The only reason I notice is I have 2 servers that have no need for X, so they only have the console up. For literally 15 years, with all AMD, NVidia and Intel video the consoles have always blanked. From the time of CRT's and using xvidtune to setup X it has always worked.
Do you also get them into suspend mode? I could swear I have seen monitors (without X) with the orange LED lit/flashing instead of the green, but I'm having trouble getting it to work now. (or finding an old system where it does work).
I'm not sure it is such an exotic feature. Surely you and I are not the only people that use Linux as a server that don't have X installed ;-)
You know what I meant :-) -- Per Jessen, Zürich (16.6°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
David C. Rankin wrote:
And note, this wasn't a slight on openSuSE testing, I don't think openSuSE had anything to do with it as I have seen this behavior on multiple distros starting sometime in the 4.16.x time frame (it could have been with the 0 release).
Right, I think so too.
Add me in, I was also thinking of some change in the kernel being the reason behind this...
Do you also get them into suspend mode? I could swear I have seen monitors (without X) with the orange LED lit/flashing instead of the green, but I'm having trouble getting it to work now. (or finding an old system where it does work).
I'm absolutely sure the Pi I installed a month ago (Leap 42.3, also console only) does go to suspend after a while. It's however no longer connected to a monitor, and at a location where doing that isn't too easy. /sys/module/kernel/parameters/consoleblank is set to 600 there. But no idea how DPMI is handled :o -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/24/2018 02:04 AM, Per Jessen wrote:
Do you also get them into suspend mode? I could swear I have seen monitors (without X) with the orange LED lit/flashing instead of the green, but I'm having trouble getting it to work now. (or finding an old system where it does work). Yes - they would always 'blank' (monitor still powered, dim faint backlight) and then 'powerdown' (monitor power off - no dim faint backlight - just solid black).
When this quit working, it quit working for both blank and suspend. When it first occurred, I could enable DPMS with setterm, e.g. # setterm --blank 4 # setterm --powerdown 5 But I haven't tested lately. The other thought I had was the virtual console renumbering that went on could have broken the default behavior. openSuSE preserved the traditional /dev/tty1-6 and X on /dev/tty7, so that doesn't seem likely. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
David C. Rankin wrote:
On 05/24/2018 02:04 AM, Per Jessen wrote:
Do you also get them into suspend mode? I could swear I have seen monitors (without X) with the orange LED lit/flashing instead of the green, but I'm having trouble getting it to work now. (or finding an old system where it does work). Yes - they would always 'blank' (monitor still powered, dim faint backlight) and then 'powerdown' (monitor power off - no dim faint backlight - just solid black).
When this quit working, it quit working for both blank and suspend. When it first occurred, I could enable DPMS with setterm, e.g.
# setterm --blank 4 # setterm --powerdown 5
But I haven't tested lately.
From my tests yesterday, blanking works, it is just disabled by default, but --powerdown does nothing, not on Leap15 nor on older systems.
-- Per Jessen, Zürich (22.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 24 May 2018 01:31:55 -0500 "David C. Rankin" <drankinatty@suddenlinkmail.com> wrote:
The other possibility is that the kernel code was removed and the blanking responsibility is not another undocumented (or poorly documented) systemd feature. I haven't had the time to run this issue to the ground. I suspect, like others, a simple Monitor->Off has had to do in the interim.
I wouldn't be at all surprised. One of the mentions about RHEL 7 makes me suspect this: https://superuser.com/questions/152347/change-linux-console-screen-blanking-... -- Liam Proven - Technical Writer, SUSE Linux s.r.o. Corso II, Křižíkova 148/34, 186-00 Praha 8 - Karlín, Czechia Email: lproven@suse.com - Office telephone: +420 284 241 084 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
David C. Rankin wrote:
This is frustrating has hell, and I think it is kernel related more than anything else. This problem showed up on Arch several months ago. The default console just stopped blanking itself. I don't recall if it was with 4.16 or one of the .1, .2 --- releases since. I just got to the point I leave the monitors turned off.
If you find a solution, I'm interested. I can't believe crap just breaks that has been working fine for 15 years and isn't fixed before it gets released.
FYI, I have opened a ticket - https://bugzilla.opensuse.org/show_bug.cgi?id=1094452 -- Per Jessen, Zürich (16.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/24/2018 01:34 AM, Per Jessen wrote:
FYI, I have opened a ticket - https://bugzilla.opensuse.org/show_bug.cgi?id=1094452
Good deal, in the mean time, I've found a way to set consoleblank from a remote session, e.g. # TERM=linux setterm -blank 10 -powerdown 12 >/dev/tty0 </dev/tty0 That will restore /sys/module/kernel/parameters/consoleblank 600 The TERM=linux is required so that setterm will communicate with the correct terminal. When accessing remotely via xterm, the environment variable TERM=xterm which doesn't have an interface. The apparent kernel default changed from 600 to 0 at some point which I believe is what broke this. (I suspect it was a cludge to fix a problem with vt blanking effecting X, but instead of fixing the new X to work correctly with consoleblank, somebody got the bright idea to just set consoleblank to 0) God I hope we haven't slipped to that level of "fixing" things. The biggest PITA is /sys/module/kernel/parameters/consoleblank is read-only (0444), so the only way to set it is either by passing the kernel parameter "consoleblank=600" (which doesn't set the powerdown), or with setterm. Thank you for filing the bug, I added to it... (what utter BS -- "this is intended behavior" -- intended behavior my a55... I guess it was just broken for the past 20 years (while it actually worked) and then got fixed when it stopped working???? What planet are we living on? Planet Stupidity? -- where things NOT working are the "intended behavior", and we are all supposed to be just dumb enough to take "this is intended behavior" as a valid reason for it not working?? Good lord...) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
David C. Rankin wrote:
On 05/24/2018 01:34 AM, Per Jessen wrote:
FYI, I have opened a ticket - https://bugzilla.opensuse.org/show_bug.cgi?id=1094452
Good deal, in the mean time, I've found a way to set consoleblank from a remote session, e.g.
# TERM=linux setterm -blank 10 -powerdown 12 >/dev/tty0 </dev/tty0
That will restore /sys/module/kernel/parameters/consoleblank 600
The TERM=linux is required so that setterm will communicate with the correct terminal. When accessing remotely via xterm, the environment variable TERM=xterm which doesn't have an interface.
The apparent kernel default changed from 600 to 0 at some point which I believe is what broke this. (I suspect it was a cludge to fix a problem with vt blanking effecting X, but instead of fixing the new X to work correctly with consoleblank, somebody got the bright idea to just set consoleblank to 0) God I hope we haven't slipped to that level of "fixing" things.
The biggest PITA is /sys/module/kernel/parameters/consoleblank is read-only (0444), so the only way to set it is either by passing the kernel parameter "consoleblank=600" (which doesn't set the powerdown), or with setterm.
I was thinking of putting a setterm somewhere in the start-up of a virtual console, getty@.service. With a system drop-in, that would do it for me. If only setterm could also get the powerdown to work ... -- Per Jessen, Zürich (22.0°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/24/2018 01:17 PM, Per Jessen wrote:
I was thinking of putting a setterm somewhere in the start-up of a virtual console, getty@.service. With a system drop-in, that would do it for me. If only setterm could also get the powerdown to work ...
# setterm --powerdown <minutes> should do it. I don't know what kernel param that sets, but according to the man page -- that is what the option is for. # setterm --blank 10 # setterm --powerdown 12 is working fine with 4.16.10 -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
David C. Rankin wrote:
On 05/24/2018 01:17 PM, Per Jessen wrote:
I was thinking of putting a setterm somewhere in the start-up of a virtual console, getty@.service. With a system drop-in, that would do it for me. If only setterm could also get the powerdown to work ...
# setterm --powerdown <minutes>
should do it. I don't know what kernel param that sets, but according to the man page -- that is what the option is for.
# setterm --blank 10 # setterm --powerdown 12
is working fine with 4.16.10
Aha. I tried it with both arguments on one line, and that didn't work for me. Does your monitor actually suspend or power down? -- Per Jessen, Zürich (16.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
David C. Rankin wrote:
On 05/24/2018 01:17 PM, Per Jessen wrote:
I was thinking of putting a setterm somewhere in the start-up of a virtual console, getty@.service. With a system drop-in, that would do it for me. If only setterm could also get the powerdown to work ...
# setterm --powerdown <minutes>
should do it. I don't know what kernel param that sets, but according to the man page -- that is what the option is for.
# setterm --blank 10 # setterm --powerdown 12
is working fine with 4.16.10
Aha. I tried it with both arguments on one line, and that didn't work for me. Does your monitor actually suspend or power down?
From a highly scientific experiment this morning, three different monitors, 5 different openSUSE releases, 5 different video cards.
Conclusion - blanking works on all, sometimes powerdown/powersave works too! On two machines with ATI Rage XL, I had to use '-powersave on' to get it to work. On one with ATI ES1000, it worked without '-powersave on'. I'm not sure about whether the timeouts work. On Leap15.0 (HP L1950, xgi z7/z9, via kvm) I'm trying out the following: /etc/systemd/system/getty@.service.d/powersave.conf : [Service] ExecStartPost=/usr/bin/setterm -powersave on -blank 2 -powerdown 5 -- Per Jessen, Zürich (17.4°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Per Jessen wrote:
On Leap15.0 (HP L1950, xgi z7/z9, via kvm) I'm trying out the following:
/etc/systemd/system/getty@.service.d/powersave.conf :
[Service] ExecStartPost=/usr/bin/setterm -powersave on -blank 2 -powerdown 5
When a new console is started (ctrl-fx), I got this: setterm[1510]: setterm: cannot (un)set powersave mode: Inappropriate ioctl for device I changed to this: # /etc/systemd/system/getty@.service.d/powersave.conf [Service] Environment=TERM=linux ExecStartPost=/usr/bin/setterm -powersave on -blank 2 -powerdown 5
/dev/%I
but I still get that message. I'm going to go see what Google says about it. -- Per Jessen, Zürich (18.5°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/25/2018 03:29 AM, Per Jessen wrote:
Per Jessen wrote:
Per Jessen wrote:
On Leap15.0 (HP L1950, xgi z7/z9, via kvm) I'm trying out the following:
/etc/systemd/system/getty@.service.d/powersave.conf :
[Service] ExecStartPost=/usr/bin/setterm -powersave on -blank 2 -powerdown 5
When a new console is started (ctrl-fx), I got this:
setterm[1510]: setterm: cannot (un)set powersave mode: Inappropriate ioctl for device
I changed to this:
# /etc/systemd/system/getty@.service.d/powersave.conf [Service] Environment=TERM=linux ExecStartPost=/usr/bin/setterm -powersave on -blank 2 -powerdown 5
/dev/%I
but I still get that message. I'm going to go see what Google says about it.
The problem is the default was stripped and this is yet another "feature" that was apparently turned over to systemd -- the only problem is nobody ever implemented a service for consoleblank so all monitors not under X just remain on forever (so much for energy conservation...) To fix it we need a service file for console blanking. (we need a package, but..), you can create a custom service, e.g. /usr/lib/systemd/system/console-blanking.service Just create/edit the file (adjust as desired) and add: [Unit] Description=Enable virtual console blanking and poweroff [Service] Type=oneshot Environment=TERM=linux StandardOutput=tty TTYPath=/dev/console ExecStart=/usr/bin/setterm -blank 5 -powerdown 6 [Install] WantedBy=multi-user.target Then reload the systemd daemon # systemctl daemon-reload and enable/start the service # systemctl enable console-blanking # systemctl start console-blanking Things are good again: $ cat /sys/module/kernel/parameters/consoleblank 300 (thanks to Celti on the Arch list for the service file...) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
David C. Rankin wrote:
On 05/25/2018 03:29 AM, Per Jessen wrote:
Per Jessen wrote:
Per Jessen wrote:
On Leap15.0 (HP L1950, xgi z7/z9, via kvm) I'm trying out the following:
/etc/systemd/system/getty@.service.d/powersave.conf :
[Service] ExecStartPost=/usr/bin/setterm -powersave on -blank 2 -powerdown 5
When a new console is started (ctrl-fx), I got this:
setterm[1510]: setterm: cannot (un)set powersave mode: Inappropriate ioctl for device
I changed to this:
# /etc/systemd/system/getty@.service.d/powersave.conf [Service] Environment=TERM=linux ExecStartPost=/usr/bin/setterm -powersave on -blank 2 -powerdown 5
/dev/%I
but I still get that message. I'm going to go see what Google says about it.
I never found out much about it. Apart from the 'powersave' on, the above works fine.
The problem is the default was stripped and this is yet another "feature" that was apparently turned over to systemd -- the only problem is nobody ever implemented a service for consoleblank so all monitors not under X just remain on forever (so much for energy conservation...)
To fix it we need a service file for console blanking. (we need a package, but..), you can create a custom service, e.g.
That's a little over-engineered, I think. My 3-line drop-in achieves the same: # /etc/systemd/system/getty@.service.d/powersave.conf [Service] Environment=TERM=linux ExecStartPost=/usr/bin/setterm -blank 2 -powerdown 5 /dev/%I I'll have to see if any of those other parameters make any difference wrt "setterm: cannot (un)set powersave mode: Inappropriate ioctl for device". -- Per Jessen, Zürich (22.0°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-03 09:37, David C. Rankin wrote:
On 05/25/2018 03:29 AM, Per Jessen wrote:
Per Jessen wrote:
...
and enable/start the service
# systemctl enable console-blanking # systemctl start console-blanking
Things are good again:
$ cat /sys/module/kernel/parameters/consoleblank 300
(thanks to Celti on the Arch list for the service file...)
Oneshot... what about returning from hibernation? -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 05/25/2018 01:04 AM, Per Jessen wrote:
# setterm --powerdown <minutes>
should do it. I don't know what kernel param that sets, but according to the man page -- that is what the option is for.
# setterm --blank 10 # setterm --powerdown 12
is working fine with 4.16.10 Aha. I tried it with both arguments on one line, and that didn't work for me. Does your monitor actually suspend or power down?
Yes, both blanking and powerdown are working (this is Arch), I'll have to load my 15 drive (I have W10 and 42.3 loaded right now) I have 15 as a VM too running on a Arch server that I access via rdesktop, but I'm a bit unsure whether the vt interface on a vm would be testable in the same way. Logically if /sys/module/kernel/parameters/consoleblank is still set, it should show the same behavior, but with 15 autostart of X (on that vm), I doubt I could tell whether DPMS or setterm was in play. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Carlos E. R. -
David C. Rankin -
Liam Proven -
Patrick Shanahan -
Per Jessen -
Peter Suetterlin