[opensuse] how to enable display power saving on virtual consoles
Per Jessen wrote:
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
Correction, this is what we ended up with: /etc/systemd/system/getty\@.service.d/powersave.conf [Service] Environment=TERM=linux ExecStartPost=-/usr/bin/setterm -powersave on >/dev/%I ExecStartPost=/usr/bin/setterm -blank 2 -powerdown 5 >/dev/%I Remarkably, "/usr/bin/setterm -powersave on" works fine when issued from a console. -- Per Jessen, Zürich (22.6°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 wrote:
Per Jessen wrote:
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
Correction, this is what we ended up with:
/etc/systemd/system/getty\@.service.d/powersave.conf
[Service] Environment=TERM=linux ExecStartPost=-/usr/bin/setterm -powersave on >/dev/%I ExecStartPost=/usr/bin/setterm -blank 2 -powerdown 5 >/dev/%I
Remarkably, "/usr/bin/setterm -powersave on" works fine when issued from a console.
Uh, it works on some machines, not all. I wonder if it might be dependent on the graphics driver. -- Per Jessen, Zürich (23.7°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 06/03/2018 07:15 AM, Per Jessen wrote:
Uh, it works on some machines, not all. I wonder if it might be dependent on the graphics driver.
It shouldn't be, IIRC we are talking vesafb by default. Even when using one of the extended resolutions for the console. I know the X side will depend on the graphics card and EDID monitor info, but as long as the card does vesa, then the console frame-buffer shouldn't care. I'll have to think on how to confirm that. -- 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 06/03/2018 07:15 AM, Per Jessen wrote:
Uh, it works on some machines, not all. I wonder if it might be dependent on the graphics driver.
It shouldn't be, IIRC we are talking vesafb by default. Even when using one of the extended resolutions for the console. I know the X side will depend on the graphics card and EDID monitor info, but as long as the card does vesa, then the console frame-buffer shouldn't care.
I see it working on HP Proliants with ATI Rage XL, but not on Supermicro boards with XGI Z7/Z9. -- Per Jessen, Zürich (26.5°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 06/03/2018 09:37 AM, Per Jessen wrote:
On 06/03/2018 07:15 AM, Per Jessen wrote:
Uh, it works on some machines, not all. I wonder if it might be dependent on the graphics driver. It shouldn't be, IIRC we are talking vesafb by default. Even when using one of the extended resolutions for the console. I know the X side will depend on the graphics card and EDID monitor info, but as long as the card does vesa, then the console frame-buffer shouldn't care. I see it working on HP Proliants with ATI Rage XL, but not on Supermicro boards with XGI Z7/Z9.
Strange, I have 2 older SuperMicro boards (one dual-quad-core Opteron, one quad-quad-core Opetron). Both successfully blank and powerdown. They do have the radeon graphics, e.g. fb: switching to radeondrmfb from VESA VGA Supports vblank timestamp caching Rev 2 (21.10.2013). Driver supports precise vblank timestamp query. radeon: irq initialized. Loading R100 Microcode Check toward the end of dmesg and see what the non-blank/poweroff hardware is reporting. -- 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 06/03/2018 09:37 AM, Per Jessen wrote:
On 06/03/2018 07:15 AM, Per Jessen wrote:
Uh, it works on some machines, not all. I wonder if it might be dependent on the graphics driver. It shouldn't be, IIRC we are talking vesafb by default. Even when using one of the extended resolutions for the console. I know the X side will depend on the graphics card and EDID monitor info, but as long as the card does vesa, then the console frame-buffer shouldn't care. I see it working on HP Proliants with ATI Rage XL, but not on Supermicro boards with XGI Z7/Z9.
Strange, I have 2 older SuperMicro boards (one dual-quad-core Opteron, one quad-quad-core Opetron). Both successfully blank and powerdown.
They do have the radeon graphics, e.g.
fb: switching to radeondrmfb from VESA VGA Supports vblank timestamp caching Rev 2 (21.10.2013). Driver supports precise vblank timestamp query. radeon: irq initialized. Loading R100 Microcode
Check toward the end of dmesg and see what the non-blank/poweroff hardware is reporting.
[ 30.313212] xgifb: module is from the staging directory, the quality is unknown, you have been warned. [ 30.320733] xgifb 0000:0f:00.0: Relocate IO address: 6000 [00006030] [ 30.320892] xgifb 0000:0f:00.0: chipid = 30 [ 30.321035] xgifb: SR14=41 DramSzie 1000000 ChannelNum 1 [ 30.321204] xgifb 0000:0f:00.0: Framebuffer at 0xef000000, mapped to 0xffffc90002000000, size 16384k [ 30.321423] xgifb 0000:0f:00.0: MMIO at 0xee300000, mapped to 0xffffc90000600000, size 256k [ 30.357534] xgifb 0000:0f:00.0: No or unknown bridge type detected [ 30.357669] xgifb: Default mode is 800x600x16 (60Hz) [ 30.357897] fbcon: XGI (fb0) is primary device [ 30.369814] Console: switching to colour frame buffer device 100x37 I don't know how much support 'setterm' needs from the driver. -- Per Jessen, Zürich (18.1°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
David C. Rankin wrote:
On 06/03/2018 07:15 AM, Per Jessen wrote:
Uh, it works on some machines, not all. I wonder if it might be dependent on the graphics driver.
It shouldn't be, IIRC we are talking vesafb by default. Even when using one of the extended resolutions for the console. I know the X side will depend on the graphics card and EDID monitor info, but as long as the card does vesa, then the console frame-buffer shouldn't care.
I have a Dell Poweredge T610 that uses an onboard VGA card. It doesn't talk VESA nor does it activate power-saving on the monitor it came with (a 16:9 LCD with HDMI inputs only -- they had to include an HDMI->VGA adapter with the system -- also the graphics card is only capable of 4:3 (and one 5:4) ratios. If you want full color you are limited to 1024x768. The 1280x1024 mode only is capable of 16-bit color. It doesn't perform well as a frame-buffer device, so it stays in its native VGA mode where it gets assist from HW scrolling. Trying to boot a standard suse system make the monitor go blank as soon as it hits the video driver in the booting kernel. First output I can see, *if* it boots is the login prompt. It was very hard to debug, as I kept adding debug code to the disk boot process -- found out later that it had been booting from a premade ramdisk, so any fixes or debugging I tried was moot. To further complicate matters, I think the boot loader had been changed away from lilo at the same time. Lovely coinciding of perplexing issues that I knew nothing about. Anyway -- I thought VGA supported power-saving (?) but maybe not? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
L A Walsh wrote:
Anyway -- I thought VGA supported power-saving (?) but maybe not?
It does. The 3 monitors we have in the datacentre are all VGA. -- Per Jessen, Zürich (21.1°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 wrote:
L A Walsh wrote:
Anyway -- I thought VGA supported power-saving (?) but maybe not?
It does. The 3 monitors we have in the datacentre are all VGA.
And they all go into power-saving mode when @ the linux console? (i.e not in a graphics or GUI mode)? Cuz never have seen my console turnoff. The linux console has code: ESC [ 14 ; n ] Set the VESA powerdown interval in minutes. They don't specify any equivalent for VGA. :-( If it works for you, how do you specify the timeout? Maybe the driver dos something to turn it off in VGA mode? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
L A Walsh wrote:
Per Jessen wrote:
L A Walsh wrote:
Anyway -- I thought VGA supported power-saving (?) but maybe not?
It does. The 3 monitors we have in the datacentre are all VGA.
And they all go into power-saving mode when @ the linux console? (i.e not in a graphics or GUI mode)?
Yep, when I am able to enable it. Two are LCDs, one an ancient Dell CRT :-)
Cuz never have seen my console turnoff.
With recent openSUSE versions, it is off by default.
The linux console has code: ESC [ 14 ; n ] Set the VESA powerdown interval in minutes.
They don't specify any equivalent for VGA. :-(
The above is also for VGA, surely? It's the ansi escape sequence spewed out by setterm.
If it works for you, how do you specify the timeout?
with setterm - e.g. setterm -powersave on -blank 5 -powerdown 5 (which doesn't work everywhere). -- Per Jessen, Zürich (17.7°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
participants (3)
-
David C. Rankin -
L A Walsh -
Per Jessen