Tiny Console Fonts - Almost Fixed
in [Debian]
|
Prev: What to put on SSD
Next: repair partition: wrong size
From: Roger Leigh on 7 Aug 2010 10:40 On Fri, Aug 06, 2010 at 09:29:30AM -0400, Thomas H. George wrote: > I gave up and installed kbd. On boot up the initial font was large. > About half way through the boot up the scripts changed to tiny fonts and > then after a half dozen lines switched back to large fonts. The console > is now very readable but when mutt displays the threaded list of > postings the lines and arrows are replaces by strange characters. This is most likely due to a mismatch between your locale character set (charmap) and the encoding of the console font. I'd advise using UTF-8 for both. You can check the locale codeset with % locale -k charmap ==> charmap="UTF-8" Because the Linux console has a limited number of characters (512 IIRC), you need to choose a subset of Unicodei, which is why there are separate Uni1, Uni2 and Uni3 fonts. I use Uni2 myself. All have the basic Latin characters, but different Greek/Cyrillic/Arabic/Symbol characters. IIRC Uni2 has more symbols, but try them all out to see which works best for you. If you're not using UTF-8, then you'll need to choose the exact same encoding as your locale charmap. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
From: Roger Leigh on 7 Aug 2010 10:50
On Thu, Aug 05, 2010 at 09:12:20AM -0500, Jordon Bedwell wrote: > Edit: > kernel /boot/blah-blah-kernel root=/my/device ro quiet splash > > Add: > vga=HEX > > > Size 640x400 640x480 800x600 1024x768 1152x864 1280x1024 1600x1200 > --------+-------------------------------------------------------------- > 8 bits | 0x300 0x301 0x303 0x305 0x161 0x307 0x31C > 15 bits | ? 0x310 0x313 0x316 0x162 0x319 0x31D > 16 bits | ? 0x311 0x314 0x317 0x163 0x31A 0x31E > > In otherwords, changing the console resolution should solve your > problem. You just have to be careful because you could end up with > squishy text but it will be bigger. But, isn't this the wrong solution to the problem? Changing to a lower resolution and keeping the same font size is not as good as using the native or maximal resolution of the monitor together with a larger, clearer font. While it's still possible to use the VGA=<hex> option, I've not seen a graphics card where the resolution couldn't be specified directly with video= for some time. For example: video=radeonfb:1680x1050-32(a)60 which allows the x and y resolution, bit depth and refresh rate to all be specified. I'm not sure if this still works with KMS since it gets the correct values using DPMS, but I'm sure there's an equivalent. Overall, KMS seems to be a very good thing albeit with a few rough edges for some users. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `- GPG Public Key: 0x25BFB848 Please GPG sign your mail. |