Skip to contentSkip to conversation

chars > 0xa0 not displayed in console since 2.6.24

DISCUSSION Gerardo Exequiel Pozzi 4 participants 5 messages Jan 28, 2008 – Jan 29, 2008

lore
Share & tools
lore
#0 lore raw

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.

#1 lore raw
Quoted 1 line · Gerardo Exequiel Pozzi

Hello,

Hello,

Quoted 6 lines

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.

Quoted 1 line

The dmesg and config are attached.

hmm no :)

#2 lore raw
Quoted 4 lines · Pascal Terjan
Quoted 1 line · Gerardo Exequiel Pozzi

Hello,

Hello,

Quoted 8 lines
Quoted 6 lines

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

Quoted 4 lines
Quoted 1 line

The dmesg and config are attached.

hmm no :)

#3 lore raw
In reply to Gerardo Exequiel Pozzi
Quoted 8 lines · Gerardo Exequiel Pozzi

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

Signature · 2 lines
Måns Rullgård
[email protected]
#4 lore raw
In reply to Gerardo Exequiel Pozzi
Quoted 7 lines · Gerardo Exequiel Pozzi

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.