[SOLVED] No polish characters during boot with DAEMON_LOCALE=YES

Question

Hello, it didn't bother me much before cause I always had DAEMON_LOCALE=NO, but with recent upgrade new rc.conf was introduced with DAEMON_LOCALE set by default to YES. Now my messages are like this:
Checking Filesystems    [BUSY] /dev/sda2: czysty, 183465/647168 plików, 2083335/2588473 bloków
Questions are: is it supposed to be half message in english half in polish? and how to repair those missing characters? (loading console font is done after those messages)
BTW this is on virtualbox guest with all testing + kde-unstable repos enabled
Last edited by masteryod (2012-06-06 10:46:45)

Answer 1

DSpider wrote:
Whenever you edit the "/etc/mkinitcpio.conf" file (ie. add "consolefont" to the HOOKS line), don't forget to regenerate your initramfs image!
# mkinitcpio -p linux
Yes, I know and I do execute it every time I touch the "/etc/mkinitcpio.conf"
DSpider wrote:It still wasn't fixed? Then try adding keymap (which says there that it "Adds keymap and consolefonts from rc.conf."), and don't forget to regenerate your initramfs image!
I have tried that and still no luck:
1. Edit CONSOLE* settings in /etc/rc.conf
[root@dog etc]# grep ^CONSOLE rc.conf
CONSOLEFONT="lat2-16"
CONSOLEMAP="8859-2"
2. Add consolefont and keymap to HOOKS in /etc/mkinitcpio.conf
[root@dog etc]# grep ^HOOKS mkinitcpio.conf
HOOKS="base udev autodetect sata filesystems fsck consolefont keymap"
3. Run mkinitcpio
[root@dog etc]# mkinitcpio -p linux
==> Building image from preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.3.7-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [sata]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
-> Running build hook: [consolefont]
-> Running build hook: [keymap]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.3.7-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [sata]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
-> Running build hook: [consolefont]
-> Running build hook: [keymap]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
I have dug the problem deeper and checked what is going on in the /etc/rc.* scripts. Everything seems to be in order, but the loading of consolefont/keymap on boot is not having any effect in my case:
1. System boots, then
2. Loging in as root
3. Typing in some Polish pangram as test: zażółć gęślą jaźń
4. Observing lack of Polish diacritics printed
5. Re-executing the rc.sysinit steps releated to consolefont/keymap settings:
# source /etc/rc.conf
# source /etc/rc.d/functions
# set_consolefont
:: Loading Console Font: lat2-16
6. Trying the Polish pangram test again.
7. Success, all Polish characters are rendered correctly.
Here is screenshot which presents the simple test explained above:
Now, this test suggests to me that the rc.sysinit procedure of configuring consolefont/keymap seems correct.
However, something seems to get messed during rc.sysinit, so the configuration is later overriden and doesn't persist afterwards.
Does anyone have an idea what may be wrong? Does it qualify to be reported as a bug?
Last edited by mloskot (2012-06-06 00:34:10)