main point is kbd (version 1.15.5-2) still doesn't set settings specified in
/etc/kbd/config.
settings what i refer to ...
# **** screen saver/DPMS settings: all VCs ****
# These settings are commented by default to avoid the chance of damage to
# very old monitors that don't support DPMS signalling.
# screen blanking timeout. monitor remains on, but the screen is cleared to
# range: 0-60 min (0==never) kernels I've looked at default to 10 minutes.
# (see linux/drivers/char/console.c)
BLANK_TIME=0
# blanking method (VESA DPMS mode to use after BLANK_TIME, before powerdown):
# on: the default, no DPMS signalling. near instant powerup, no power saving
# vsync: DPMS Standby mode. nearly instant recovery, uses 110/120W (17" screen)
# hsync: DPMS Suspend mode. typically 3s recovery, uses 15/120W (17" screen)
# powerdown,off: DPMS Off mode, typ. 10s recovery, uses 5/120W (17" screen)
# Those values are for my 17" Mag, but some monitors do suspend the same as
# standby. xset dpms force {off|standby|suspend|on} is useful for this, if X
# supports DPMS on your video card. Set X's DPMS screensaver with xset dpms
# or use option power_saver in XF86Config
#
# DPMS set by default to on, because hsync can cause problems on certain
# hardware, such as Armada E500 laptops
BLANK_DPMS=off
# Powerdown time. The console will go to DPMS Off mode POWERDOWN_TIME
# minutes _after_ blanking. (POWERDOWN_TIME + BLANK_TIME after the last input)
POWERDOWN_TIME=0
i made some tests and found out that setterm (when booting) gives following
error message
setterm: $TERM is not defined
i don't know should this bug be reopened or a new bug reported.
also i'm not fully sure did previous versions run /etc/init.d/kbd script fully
with setterm error message. but kbd settings was not set anyway.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
