lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Mon, 30 Jun 2014 21:48:38 +0200
From:	poma <>
To:	Linux Kernel list <>
CC:	For testing and quality assurance of Fedora releases 
	systemd Mailing List <>,
	Mailing-List fedora-kernel <>
Subject: console font

On 25.06.2014 20:49, poma wrote:
> On 25.06.2014 20:10, Felix Miata wrote:
>> On 2014-06-25 10:05 (GMT-0700) Adam Williamson composed:
>>> So...these are three different machines?
>> 3 out of 14 on which Rawhide is currently installed (test machines total 20+)
>> here, among which are represented various flavors of MGA (400 & 550), SiS
>> (Z7/Z9 XG20 core), Intel (810, 815, 845, 865, 915, 945, 965, 3100, 4100), ATI
>> (rv200, rv250, rv370, rv380, rv516) & NVidia for video.
>>> I'm curious: why are you passing video= parameters on each one? Do
>>> any/all of them work if you don't pass that parameter?
>> Most of my test machines get used most of the time with a '21"' CRT with
>> preferred mode 1600x1200 reported as preferred mode 1280x1024 used at
>> approximately 175% of normal viewing distance. Avoiding eyestrain requires
>> 1152x864 or lower on the vttys unless I want to monkey with terminal font
>> reconfiguration from default.
>> My second most used test machine display is a 19" LCD TV with native mode
>> 1440x900 that reports preferred 1280x1024 but supports 4:3 modes up to
>> 1792x1344. It is used at similar distance, so also needs 1024x768 on the
>> vttys for the same reason as the CRT.
>> I also have 2 15" 1024x768, 17" & 19" 1280x1024 and 20" 1600x1200 LCD puter
>> displays, 2 31.5" TVs, and an abundance of other CRTs to use as test
>> conditions require, in addition to the LCDs used for my 24/7 systems that can
>> be briefly pressed into test service when necessary.
> # yum install terminus-fonts-console
> - permanent system wide
> /etc/vconsole.conf
> FONT=<Big mama font>
> e.g. 'latarcyrheb-sun32' or 'ter-v32b'
> - runtime local
> $ setfont latarcyrheb-sun32
> $ setfont ter-v32b


It seems this kernel? bug is still present[2].

"rd.vconsole.font=ter-v32b" also fails to subsist due to
"fb: switching to nouveaufb from VESA VGA".

- journal systemd-vconsole-setup
systemd[1]: Starting Setup Virtual Console...
systemd-vconsole-setup[347]: putfont: KDFONTOP: Invalid argument
systemd-vconsole-setup[347]: /usr/bin/setfont failed with error code 71.
systemd[1]: Started Setup Virtual Console.

I've found so far that this can only be overcome with these two almost identical solutions;
When I thought of 'actual-vconsole-setup-start' I did not know that Yegor already done it.

Yegor's solution[1]:
  # cp /usr/lib/systemd/system/systemd-vconsole-setup.service /etc/systemd/system/
  # diff /etc/systemd/system/systemd-vconsole-setup.service \
  > /usr/lib/systemd/system/systemd-vconsole-setup.service
  > After=systemd-readahead-collect.service systemd-readahead-replay.service

or even simpler - leave 'systemd-vconsole-setup.service' as is,
and make this one
# Actual Virtual Console Setup Start

Description=Actual Virtual Console Setup Start



# systemctl enable actual-vconsole-setup-start.service

and now you have appropriate font size for 1920x1080,
no need to lower resolution via "video=<xres>x<yres>".
Perhaps '32' is too large, so choose <= '28', e.g. ter-v28b or ter-v24b.


[1] systemd-vconsole-setup: /usr/bin/setfont failed with error code 71

[2] Can not change console font via /etc/vconsole.conf

     The keyboard layout for the virtual console cannot be changed using
     “localectl set-keymap <map>; dracut -f; reboot;”

     font settings are lost when kernel fb drivers are changed

     Kernel drivers lose console font settings

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists