On Tue, 2015-03-03 at 13:47 -0500, Samuel Bronson wrote: [...] > > Is the TERM variable set correctly on the console (should be 'linux')? > > Yes, it's set correctly, and the terminfo is bold=\E[1m just like > console_codes(5) says it should be, and just like on my Wheezy laptop > where bold actually works on the console. > > Oh. I found somehing interesting; "setupcon -v" tells me it's loading > a "512-char" font on the box that isn't working; on the working one, > it says it's loading a "256-char" font; I know that VGA text mode is > fundamentally incapable of supporting both bold and 512 glyphs at the > same time, but console-setup(5) implies that this limitation does not > apply to the framebuffer console. > > Or not-so-interesting: manually selecting a smaller character set so > that it loads a "256-char" font doesn't help anyway :-(. Can I just clarify what you expect bold text to look like? The in-kernel terminal emulator treats bold as equivalent to a brighter foreground. When the foreground colour is already bright, turning on bold makes no difference. In a 1-bit-per-pixel mode, the fbcon driver implements bold by smearing each character to the right by one pixel. I think that's the only case where you can expect to see something like real bold text on the console. Ben. -- Ben Hutchings The world is coming to an end. Please log off.
Attachment:
signature.asc
Description: This is a digitally signed message part