On Thu, Oct 22, 2009 at 07:11:37PM +0200, Mats Erik Andersson wrote: > Package: console-tools > Version: 1:0.2.3dbs-65.1 > Severity: important > > In the case an administrator installs Debian Lenny with a > character set that is __not__ of the utf-8 class, then the > virtual consoles tty2, tty3, and onwards, still yield > > # kbd_mode > The keyboard is in Unicode(UTF-8) mode > > whereas tty1 correctly responds with > > # kbd_mode > The keyboard is in the default(ASCII) mode
This seems to be caused by a change in the kernel: commit 77bf2bab91e4e7df361963451c7b9a803516438c Author: Jan Engelhardt <[email protected]> Date: Thu Oct 18 03:04:34 2007 -0700 Remove CONFIG_VT_UNICODE Since default_utf8 is already a sysfs attribute, having an extra CONFIG_VT_UNICODE compile-time option is redundant, since sysfs attributes c be set at boot and run time. Also let Linux VCs default to UTF-8 (as per the discussion at http://lkml.org/lkml/2007/9/6/99). Signed-off-by: Jan Engelhardt <[email protected]> Cc: Bill Nottingham <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Linus Torvalds <[email protected]> It can be worked around by adding "vt.default_utf8=0" to the kernel boot parameters. I've tried setting /sys/module/vt/parameters/default_utf8 in the console-screen.sh and keymap.sh script, but I think it gets run too late. In any case I expect console-tools to fix the default and set it correct. I think the problem is that unicode_start/unicode_stop only affects the VT it's being run on. Kurt -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
