Hello,
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?
The dmesg and config are attached.
On Jan 28, 2008 11:00 PM, Gerardo Exequiel Pozzi <[email protected]> wrote:
> Hello,
Hello,
> 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?
I think this is because the console is now by default in UTF-8 mode.
> The dmesg and config are attached.
hmm no :)
On Jan 28, 2008 11:12 PM, Pascal Terjan <[email protected]> wrote:
> On Jan 28, 2008 11:00 PM, Gerardo Exequiel Pozzi <[email protected]> wrote:
> > Hello,
> Hello,
>
> > 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?
>
> I think this is because the console is now by default in UTF-8 mode.
You can try with vt.default_utf8=0
> > The dmesg and config are attached.
>
> hmm no :)
>
Gerardo Exequiel Pozzi <[email protected]> writes:
> Hello,
>
> 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?
Probably something to do with this commit:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ecb77fa96ceda9cae88015bfe3293ffe19006159
--
M?ns Rullg?rd
[email protected]
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.