+++ This bug was initially created as a clone of Bug #699282 +++ Description of problem: After system boot up, I've switched to console (Ctrl-Alt-F2), login and run mc (Midnight Commander) or another application with Russian symbols. Russian symbols not displayed, again. Like this was in Fedora 12. Version-Release number of selected component (if applicable): initscripts-9.29 How reproducible: always Steps to Reproduce: 1. Boot system 2. switch to console 3. run application with Russian symbols, as example LANG=ru_RU.UTF-8 mc Actual results: White squares instead Russian symbols. Expected results: Russian symbols displayed correctly. Additional info: I've find workaround or patch. If I change this line in /lib/udev/rules.d/10-console.rules: KERNEL=="tty0",><------>RUN+="/lib/udev/console_init %k" like this: KERNEL=="tty*",><------>RUN+="/lib/udev/console_init %k" then Russian symbols displayed correctly. --- Additional comment from atigro on 2011-04-24 23:34:08 CEST --- In earlier dracut (in F14) initramfs image contained system binary /lib/udev/console_init from initscripts. Maybe it is the second way to fix this problem: https://github.com/RussianFedora/dracut/blob/f15%2Ffixes/dracut-009-console_init.patch --- Additional comment from lpoetter on 2011-04-27 02:30:00 CEST --- systemd-vconsole should be responsible for setting that up. Does invoking /lib/systemd/systemd-vconsole-setup manually make things work for you? What is the content of /etc/sysconfig/i18n? --- Additional comment from elemc on 2011-04-27 19:59:39 CEST --- Yes, after run /lib/systemd/systemd-vconsole-setup in console Russian symbols displayed correctly. cat /etc/sysconfig/i18n LANG="ru_RU.UTF-8" --- Additional comment from lpoetter on 2011-04-28 00:39:26 CEST --- Which systemd version is this? Normally /lib/systemd/systemd-vconsole-setup should run at boot. Can you do "systemctl --full | grep vconsole" after boot when the problem happened and paste the output here? --- Additional comment from elemc on 2011-04-28 08:31:27 CEST --- # yum list installed systemd* systemd.x86_64 25-1.fc15 @updates-testing systemd-units.x86_64 25-1.fc15 @updates-testing I've booted and checked what problem still persist. # systemctl --full | grep vconsole systemd-vconsole-setup.service loaded active exited Setup Virtual Console --- Additional comment from mschmidt on 2011-04-28 10:52:30 CEST --- Can you boot with "rd.plymouth=0"? Do the fonts appear correctly then? --- Additional comment from elemc on 2011-04-28 11:05:39 CEST --- Yes, with rd.plymouth=0 kernel parameter the fonts appear correctly. --- Additional comment from lpoetter on 2011-04-28 16:54:36 CEST --- Hmm, Ray, have you heard of such a problem with font loading and Plymouth colliding? --- Additional comment from lpoetter on 2011-04-28 16:59:20 CEST --- OK, my guess is that this might be related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/554172/comments/245 i.e. setfont should probably retry opening /dev/tty0 a couple of times. --- Additional comment from lpoetter on 2011-04-28 17:06:38 CEST --- Tentatively reassigning this to kbd. The EIO loop is definitely necessary in kbd. It might fix this problem. If it doesn't feel free to reassign back. kbd maintainers, can you please beef up open_a_console() in src/getf_fd.c to loop a couple of times if you get EIO when opening the device? Since the BKL was dropped in the kernel this is unfortunately necessary in userspace to make things work race-freely, see the linked ubuntu bug. We do a similar loop in systemd: http://cgit.freedesktop.org/systemd/tree/src/util.c#n2326 --- Additional comment from notting on 2011-04-28 18:38:23 CEST --- (In reply to comment #8) > Hmm, Ray, have you heard of such a problem with font loading and Plymouth > colliding? vconsole setup needs done before plymouth sets the terminal to graphics mode/the framebuffer driver is loaded, IIRC. (font/unicode state is per-VT, but inherited from the prior existing console) --- Additional comment from lpoetter on 2011-04-30 03:45:44 CEST --- OK, will duplicate against dracut then, which apparently dropped the font loading. Harald, please add an invocation of systemd-vconsole-setup to dracut, before you run plymouth, as discussed on IRC the other day.
dracut-009-7.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/dracut-009-7.fc15
dracut-009-8.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/dracut-009-8.fc15
Package dracut-009-8.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing dracut-009-8.fc15' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/dracut-009-8.fc15 then log in and leave karma (feedback).
I have installed new dracut-009-8.fc15 and update initramfs (/usr/libexec/plymouth/plymouth-update-initrd). New dracut does not fix this problem. Only squares were replaced by "Western" symbols, but no cyrillic (see bad.jpg in attachment). After running setsysfont, cyrillic symbols will appear again (see good-aftersetsysfont.jpg).
Created attachment 496991 [details] Bad fonts in console
Created attachment 496992 [details] Good fonts in console
well, dracut only sets tty0, so you cannot blame dracut for tty2 in dracut-009-8.fc15 systemd-vconsole-setup is used. what is the kernel command line? what does # cat /sys/module/vt/parameters/default_utf8 output?
kernel command line.. a-a-a-a in grub.conf? --- kernel /vmlinuz-2.6.38.5-22.fc15.x86_64 ro root=UUID=a41ac62e-5e4b-4d68-989c-66ee0c73f2bc rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=ru_RU.UTF-8 KEYTABLE=ru rhgb quiet --- --- # cat /sys/module/vt/parameters/default_utf8 0 --- So, if I try run systemd-vconsole-setup: -- loadkeys: warning: loading Unicode keymap on non-Unicode console (perhaps you want to do `kbd_mode -u'?) -- If I run kbd_mode -u; /lib/systemd/systemd-vconsole-setup nothing changed. No cyrillic symbols.
Hmm, I see no "SYSFONT=" in your kernel command line. Does it help, if you add your kernel command line the SYSFONT set like in /etc/sysconfig/i18n. Lennart, is $LANG set for the "systemd-vconsole-setup" call? Arkady, if you add "rd.break" to the kernel command line, you will be dropped to a dracut shell. What is "/sys/module/vt/parameters/default_utf8" in there?
dracut-009-9.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/dracut-009-9.fc15
(In reply to comment #11) > dracut-009-9.fc15 has been submitted as an update for Fedora 15. > https://admin.fedoraproject.org/updates/dracut-009-9.fc15 This is not true... I removed the patch from dracut-009-8 for this update. So dracut-009-9 does not use systemd-vconsole-setup. Please do not update to this release, if you want to help debug this further.
I added rd.break, but can't drop to shell. But I saw that systemd-vconsole-setup said -- loadkeys: warning: loading Unicode keymap on non-Unicode console (perhaps you want to do `kbd_mode -u'?) -- If I add SYSFONT=latarcyrheb-sun16, nothing changed. In Russian SYSFONT does not use in /etc/sysconfig/i18n. Font dropped from anaconda lang-table many releases ago.
Created attachment 499218 [details] Picture of bad fonts I am coming from bug 486042. I have dracut-009-10.fc15.noarch installed and the fonts in the vt2 look as in the picture. The text should say zażółć gęślą jaźń ZAŻÓŁĆ GĘŚLĄ JAŹŃ. My kernel boot line is as follows: kernel /vmlinuz-2.6.38.6-26.rc1.fc15.x86_64 ro root=/dev/mapper/vg_snowball2-lv_root rd_LVM_LV=vg_snowball2/lv_root rd_LVM_LV=vg_snowball2/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=pl_PL.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=pl2 rhgb quiet nouveau.modeset=0 rdblacklist=nouveau
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping