Jack Carroll wrote:
> On Sun, Aug 13, 2006 at 09:59:19AM +0100, Alastair McKinstry wrote:
>
>>> Aha! Removing the symlink in /etc/rcS.d to
>>> /etc/init.d/console-screen does indeed make the bug go away. If that
>>> caused any side effects, I didn't detect them.
>>>
>>>
>> This is confusing; console-tools has not changed in many weeks.
>>
>
> That makes me wonder whether this has been going on for quite a
> while, and I just wasn't watching.
>
>
>
>> While console-screen can change the video mode, it does not by default,
>> for the
>> reasons described: no safe defaults on all the old hardware out there.
>>
>> Can you please send a copy of:
>> /etc/console-tools/*
>>
>
> $ cat /etc/console-tools/config
> #
> # This files tells the console-tools package:
> #
> # - whether to load a specific font and boot (and maybe a screen-font map,
> # but you should avoid that if possible).
> # - whether to setup an Application-Charset Map other than the default CP437.
> # - whether to start "vcstime" to have time on all text VC'S.
> #
> # You can also specify per-VC settings by suffixing variable names as in
> # the examples below. This only works on framebuffer devices.
> #
> # CAVEATS:
> #
> # - When using the new framebuffer devices, the "global setting" for a font
> # only affects the current console (ie., at boot-time, the first one)
> # - ACM setting involves 2 steps (maybe loading a user ACM, and activating
> # it on a given charset slot - see charset(1) for details), the 1st of which
> # affects the entire system, but the 2nd of which only affects the current
> # VC (ie., at boot-time, the first one). So that if you want to use the same
> # ACM on all VCs, you have to specify "APP_CHARSET_MAP_vc<N>=user" for all
> # relevant values of <N>.
> #
> # Example:
> #
> #SCREEN_FONT=iso01.f16
> #SCREEN_FONT_vc2=LatArCyrHeb-16
> #
> #APP_CHARSET_MAP=iso05
> #APP_CHARSET_MAP_vc2=user
> #
> # Set the following - more euro-friendly default than kernel font.
> # SCREEN_FONT=latcyrheb-sun16.psf
>
> #DO_VCSTIME=yes
> #
> # Forget this one unless you _know_ it is necessary for your font:
> #SCREEN_FONT_MAP=iso01
>
> # **** 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=30
>
> # 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=30
>
> # rate and delay can get only specific values, consult kbdrate(1) for help
> #KEYBOARD_RATE="30"
> #KEYBOARD_DELAY="250"
>
> # Turn on numlock by default
> #LEDS=+num
> SCREEN_FONT=lat0-sun16
> SCREEN_FONT_vc2=lat0-sun16
> SCREEN_FONT_vc3=lat0-sun16
> SCREEN_FONT_vc4=lat0-sun16
> SCREEN_FONT_vc5=lat0-sun16
> SCREEN_FONT_vc6=lat0-sun16
>
>
> $ cat /etc/console-tools/remap
> # This sed script is run across the dumpkeys output to remap keys on the
> console
>
> # This turns caps lock into control
> #s/keycode 58 = Caps_Lock/keycode 58 = Control/;
>
>
>
>> dpkg -l | grep splash
>>
>
> No output.
>
>
>> dpkg -l | grep console
>>
>
> $ dpkg -l | grep console
> ii console-common 0.7.60 Basic
> infrastructure for text console configuration
> ii console-data 1.0-2 Keymaps,
> fonts, charset maps, fallback tables for console-tools
> ii console-tools 0.2.3dbs-64 Linux
> console and font utilities
> ii libconsole 0.2.3dbs-64 Shared
> libraries for Linux console and font manipulation
> ii libjline-java 0.9.5-2 Java library
> for handling console input
> ii libsvga1 1.4.3-23 console SVGA
> display libraries
> ii usbutils 0.72-4 USB console
> utilities
>
>
>
>> kernel version?
>>
>
> $ uname -a
> Linux edgar 2.6.16-2-k7-smp #1 SMP Sat Jul 15 23:38:43 UTC 2006 i686
> GNU/Linux
>
>
> I turned the symlink back on to make sure recent Etch updates
> haven't eliminated the bug. They haven't.
> What tests would you like next?
>
>
Hi,
Could you please test with the symlink in /etc.rcS.d in place, but with
all the
options in /etc/console-tools/config commented out?
Thanks
Alastair
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
