public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: Kernel update messed up console encoding
Date: Mon, 02 Mar 2009 13:29:02 +0200	[thread overview]
Message-ID: <gogftn$lj7$1@ger.gmane.org> (raw)
In-Reply-To: <0ML25U-1LdwWu02kc-0006UX@mrelayeu.kundenserver.de>

Florian v. Savigny wrote:
> [...]
> I think I'll continue on a kernel list to figure out what kernel
> 2.6.27 does differently from 2.6.17, and why (and whether that
> behaviour cannot be changed with a compile-time option). I think that
> part is really not a gentoo-specific question. But I'll report here
> when I get the result!

On my /etc/rc.conf, there's this:

   # Set unicode to YES to turn on unicode support for keyboards
   # and screens.
   unicode="YES"

So I suppose maybe simpley changing this to "NO" will do the job.  I'm 
on OpenRC now though so maybe it looks different on older baselayout.

Try "grep -ri unicode /etc" and see what you find.




  reply	other threads:[~2009-03-02 11:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-27 17:29 [gentoo-user] Kernel update messed up console encoding Florian v. Savigny
2009-02-27 21:05 ` Sebastian Günther
2009-02-28 10:34   ` Florian v. Savigny
2009-02-28 11:34     ` Eray Aslan
2009-02-28 14:26     ` Sebastian Günther
2009-02-28 17:38       ` Florian v. Savigny
2009-02-28 18:48         ` Sebastian Günther
2009-03-01  9:36           ` Florian v. Savigny
2009-03-01 10:30             ` [gentoo-user] " Nikos Chantziaras
2009-03-01 12:25               ` Florian v. Savigny
2009-03-01 12:48                 ` Nikos Chantziaras
2009-03-02  1:01                   ` Florian v. Savigny
2009-03-02 11:29                     ` Nikos Chantziaras [this message]
2009-03-02 12:51                       ` Florian v. Savigny

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='gogftn$lj7$1@ger.gmane.org' \
    --to=realnc@arcor.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox