Bug 876512 - VT font isn't set after boot
Summary: VT font isn't set after boot
Keywords:
Status: CLOSED DUPLICATE of bug 892340
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 17
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-14 10:21 UTC by Andrew
Modified: 2013-01-14 22:23 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-14 22:23:18 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Andrew 2012-11-14 10:21:35 UTC
I set Terminus font for VT but it isn't applied after boot.

systemd-vconsole-setup.service reports successful launch (log below) but it hasn't the desired effect.
However it really launch setfont with proper parameters and Terminus is applied if I restart this service manually after login.


$ systemctl status systemd-vconsole-setup.service
systemd-vconsole-setup.service - Setup Virtual Console
          Loaded: loaded (/usr/lib/systemd/system/systemd-vconsole-setup.service; static)
          Active: active (exited) since Wed, 14 Nov 2012 11:45:12 +0200; 36s ago
            Docs: man:vconsole.conf(5)
         Process: 282 ExecStart=/usr/lib/systemd/systemd-vconsole-setup (code=exited, status=0/SUCCESS)
          CGroup: name=systemd:/system/systemd-vconsole-setup.service


$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.6.6-1.fc17.x86_64 root=UUID=bd9b55f7-43f7-489d-86d8-8c0520323c79 ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=ter-v16n KEYTABLE=us rd.luks=0 LANG=en_US.UTF-8 plymouth.enable=0


$ cat /etc/sysconfig/i18n
LANG="en_US.UTF-8"
SYSFONT="ter-v16n"


/etc/vconsole.conf is absent

Looks similar: #670736. Plymouth is completely disabled for my case.


SW versions:
kbd-1.15.3-5.fc17.x86_64
systemd-44-21.fc17.x86_64

Comment 1 Kay Sievers 2012-11-14 11:52:46 UTC
It might be caused by the values from kernel command line, which overwrites
any setting from the config file.

Comment 2 Andrew 2012-11-14 15:05:01 UTC
(In reply to comment #1)

Ok, but what values exactly? SYSFONT has the same value at both places. There is nothing to override...

Besides that, results of several vconsole-setup launches should be consistent, as for me. Either change the font in both cases or not, but not a mix.

Comment 3 Andrew 2012-12-07 18:43:51 UTC
Still exists after upgrade to F18 Beta.

/etc/sysconfig/i18n now doesn't exist but vconsole.conf was appeared:

# cat /etc/vconsole.conf
FONT=ter-v16n
KEYMAP=ua-utf

It should be noted that in both Fedora versions font was really set to Terminus for some time at boot. So the case looks like default->ter-v16n->default.
The last switch happens somewhere around nouveau framebuffer init. I can be wrong though, it goes quite fast.

Comment 4 Andrew 2012-12-08 08:48:49 UTC
I filmed the boot process and the font switching points are following:

default->ter-v16n : starting systemd-vconsole-setup service

ter-v16n->default : screen blinks after this lines and new image is using default font:

Dec  8 10:20:56 localhost kernel: [drm] nouveau 0000:01:00.0: Detected an NV40 generation card (0x043100a4)
Dec  8 10:20:56 localhost kernel: fb: conflicting fb hw usage nouveaufb vs VESA VGA - removing generic driver
Dec  8 10:20:56 localhost kernel: Console: switching to colour dummy device 80x25

Comment 5 Lennart Poettering 2013-01-14 22:23:18 UTC
Hmm, sounds a lot like 892340, merging.

*** This bug has been marked as a duplicate of bug 892340 ***


Note You need to log in before you can comment on or make changes to this bug.