From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LdkjW-0001Xg-2G for garchives@archives.gentoo.org; Sun, 01 Mar 2009 12:25:26 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C9909E02A8; Sun, 1 Mar 2009 12:25:18 +0000 (UTC) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by pigeon.gentoo.org (Postfix) with ESMTP id 8C9EDE02A8 for ; Sun, 1 Mar 2009 12:25:18 +0000 (UTC) Received: from bertrandrussell.teuto37.teuto.37.de (dslb-088-078-031-216.pools.arcor-ip.net [88.78.31.216]) by mrelayeu.kundenserver.de (node=mrelayeu7) with ESMTP (Nemesis) id 0ML2xA-1LdkjN38jj-0006GL; Sun, 01 Mar 2009 13:25:17 +0100 From: "Florian v. Savigny" To: gentoo-user@lists.gentoo.org In-reply-to: (message from Nikos Chantziaras on Sun, 01 Mar 2009 12:30:02 +0200) Subject: Re: [gentoo-user] Re: Kernel update messed up console encoding References: <0MKv1o-1Ld6WW1EfT-000DMF@mrelayeu.kundenserver.de> <20090227210537.GA10044@marvin.heimnetz.local> <0ML21M-1LdMWh49My-00067l@mrelayeu.kundenserver.de> <20090228142648.GB20212@marvin.heimnetz.local> <0ML2xA-1LdT9M2LrY-0006L9@mrelayeu.kundenserver.de> <20090228184805.GA7841@marvin.heimnetz.local> <0ML21M-1Ldi5r2mAw-00066S@mrelayeu.kundenserver.de> Message-Id: <0ML2xA-1LdkjN38jj-0006GL@mrelayeu.kundenserver.de> Date: Sun, 01 Mar 2009 13:25:17 +0100 X-Provags-ID: V01U2FsdGVkX1+cdxOSug/QOhXoD0p28abGp03YL29QzK2F/C6 Fm9aXWcZo+58BWqIFCUtEnwOrlqg43jMSZIoqMGWiRRQZtsUYd PYQp3ElxTMT7up450Gc5g== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Archives-Salt: c6963e5e-c8e5-4cd4-8142-bdef18be4d45 X-Archives-Hash: 09ba9287d0288eeae61e3c8a8a0acad1 Hi Nikos, > > $LANG and $LC_ALL are not set (i.e. locale simply shows > > "LANG=" and "LC_ALL=" with no values). All other LC_... variables are > > set to "POSIX". > > I don't think that will work. Interestingly, I just discovered the locales are different for one user (who has "de_DE.iso-8859-1" for all variables (including LANG) except LC_ALL, which is empty). For the other users, the locales are as above, and it is this way no matter which kernel is running. But the console does not behave differently for the two users, but differently for the two kernels (i.e. identically for both users). So, the bottom line is: that is apparently not the heart of the problem either, as the setting cited above DOES work under my kernel 2.6.17. But thanks for having me discover the user-specific locale settings! I wasn't aware of that. A user who said he was too lazy to subscribe to the list (which is a loss for the list, I think) gave me the tip that passing the kernel the parameter "default_utf8=0" should reverse that behaviour. While the kernel does know the parameter, it did not change the behaviour. But he also said that the command kbd_mode can change the behaviour of the keyboard, and indeed it can: kbd_mode -a sets the behaviour to single bytes, i.e. the keys send single bytes, while kbd_mode -u sets it to sending one, two, or three bytes, depending on what UTF-8 requires. kbd_mode without a parameter outputs the current status, and this is indeed different after booting the two kernels: as expected, for the old kernel, it is "The keyboard is in ASCII mode", for the new one "The keyboard is in Unicode (UTF-8) mode" (the documentation explains that "ASCII" is misleading; it is indeed "single-byte", and fine for all iso-8859- encodings). After saying "kbd_mode -a" under the new kernel, I can now produce ISO-8859-1-encoded files with Emacs or the shell. I haven't worked out how to get the screen to display them correctly, however (as it does under the old kernel). The unsubscribed user told me two magic escape sequences, but I have yet to see how to type them correctly. ('ECS ( K' to switch to single-byte mode, 'ESC % G' to switch to utf-8 mode). "console" covers both keyboard and screen, he explained. (Sounds familiar, but I thought it would not hurt to repeat it here.) But still, I am wondering how to get the new kernel to behave as I want out of the box. My best guess is now that this console behaviour has become the default at some point between kernels 2.6.17 and 2.6.27, and that you now have to switch it off explicitely. But how? Regards, Florian