Thiemo Seufer <[EMAIL PROTECTED]> wrote: >> The console in this case should be a standard Linux console on >> framebuffer, but I guess that it's not /that/ standard after >> all. Maybe Thiemo can tell us more about that ? > > It is not at all a standard framebuffer. The hardware allows no direct > memory access but provides userspace-driven DMA capability instead. > The X server uses the userland DMA for a while now, but the kernel > uses a special "newport" console which is rather inefficient.
It's the console which I qualified of "standard", in this case, as the framebuffer is indeed pretty exotic. >> The console groks at least latin1, btw. Could it be that the console >> lacks UTF8 support ? > > That's possible, I don't know the newport code by heart. Christian, can you confirm that the installer uses a UTF-8 console ? If yes, I should be able to reproduce the problem on a running system by calling unicode_start and echoing some UTF-8 text, I guess. JB. -- Julien BLACHE <[EMAIL PROTECTED]> | Debian, because code matters more Debian & GNU/Linux Developer | <http://www.debian.org> Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]