Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934190AbYA2UHo (ORCPT ); Tue, 29 Jan 2008 15:07:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754518AbYA2UG7 (ORCPT ); Tue, 29 Jan 2008 15:06:59 -0500 Received: from sovereign.computergmbh.de ([85.214.69.204]:35126 "EHLO sovereign.computergmbh.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752383AbYA2UG5 (ORCPT ); Tue, 29 Jan 2008 15:06:57 -0500 Date: Tue, 29 Jan 2008 21:06:56 +0100 (CET) From: Jan Engelhardt To: Gerardo Exequiel Pozzi cc: linux-kernel@vger.kernel.org Subject: Re: chars > 0xa0 not displayed in console since 2.6.24 In-Reply-To: <479E5082.50208@gmail.com> Message-ID: References: <479E5082.50208@gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 691 Lines: 18 On Jan 28 2008 20:00, Gerardo Exequiel Pozzi wrote: > > Chars are displayed OK in kernels < 2.6.24 (2.6.22.16, 2.6.23.14) with the same > config. > I booted clean with init=/bin/bash to discard distro (slackware-current) > problem/incompat, but the problem persist. > > This is a know problem? Yes, it is a "known" (at least in kernel land, not sure about slack) "problem" with slackware which does not explicitly set 8-bit mode during bootup. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/