kbd.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Alexey Gladkov <gladkov.alexey@gmail.com>
To: kbd@lists.altlinux.org
Subject: Re: [kbd] mapscrn: cannot open map file _8859-15_
Date: Sun, 25 Nov 2012 14:32:06 +0400	[thread overview]
Message-ID: <50B1F3A6.2090102@gmail.com> (raw)
In-Reply-To: <CAE8zHmRJ574XPEngF_gbprDiVFwDVYRR9A5Me6iCPr6Pk050JA@mail.gmail.com>

25.11.2012 04:53, Raphael Yoshimura wrote:
> Hello all,
> I'm having an annoying issue with kbd that I can't seem to resolve:
> When I boot, during the boot screen after GRUB I see an error saying:
> "mapscrn: cannot open map file _8859-15_"
> 
> I'm using Mageia 2 Linux and my secondary language is Bulgarian.
> 
> This is how my /etc/sysconfig/i18n looked like;
> 
> SYSFONTACM=8859-15
>> LANGUAGE=en_US:en
>> LC_ADDRESS=bg_BG
>> LC_COLLATE=en_US
>> LC_NAME=bg_BG
>> LC_NUMERIC=bg_BG
>> LC_MEASUREMENT=bg_BG
>> LC_TIME=en_US
>> LANG=en_US
>> LC_IDENTIFICATION=bg_BG
>> LC_MESSAGES=en_US
>> LC_CTYPE=en_US
>> LC_TELEPHONE=bg_BG
> 
> 
> I was having unicode issues aside, so when I enabled UTF-8 from Mageia
> Control Center, the first line disappeared. Now it looks like this.
> 
> LANGUAGE=en_US:en
>> LC_ADDRESS=bg_BG
>> LC_COLLATE=en_US
>> LC_NAME=bg_BG
>> LC_NUMERIC=bg_BG
>> LC_MEASUREMENT=bg_BG
>> LC_TIME=en_US
>> LANG=en_US
>> LC_IDENTIFICATION=bg_BG
>> LC_MESSAGES=en_US
>> LC_CTYPE=en_US
>> LC_TELEPHONE=bg_BG
> 
> 
> However the error still exists.
> 
> One person running Archlinux on initramfs solved his issue this way:
> 
> removed the keymap HOOK in the configuration file / etc / mkinitcpio.conf
>> and regenerated the initramfs
> 
> 
> However I'm not running Archlinux, I don't have a /etc/mkinitcpio.conf and
> I'm on a ext4 not an initramfs.
> 
> Any ideas will be greatly appreciated.

https://wiki.mageia.org/en/Mageia_2_beta2#initrd

"Mageia 2 will default to dracut as tool for creating initrds (initial
ramdisk, used during boot). We still provide mkinitrd for those that
need that, but will only support it when used with initscripts. Users
of systemd must use dracut."

So for initrd you can use either the mkinitrd or dracut. It depends on
the configuration. So, do you have a systemd ?

You are using dracut if you have a systemd. Here's how to set up the
console in dracut:

http://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#_i18n

Check out your /etc/vconsole.conf.

-- 
Rgrds, legion



       reply	other threads:[~2012-11-25 10:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAE8zHmRJ574XPEngF_gbprDiVFwDVYRR9A5Me6iCPr6Pk050JA@mail.gmail.com>
2012-11-25 10:32 ` Alexey Gladkov [this message]
     [not found]   ` <CAE8zHmTxoKBHZOA26nmAo2W12qedJGNM_W+4N+_GQu84+Wu7OQ@mail.gmail.com>
     [not found]     ` <CAE8zHmQQJu90VyLXv905AU=mLODsQiaXddEJa7sBmFXoDj9vcQ@mail.gmail.com>
2012-11-30 23:02       ` [kbd] mapscrn: cannot open map file _8859-15_ Ken Moffat
     [not found]         ` <CAE8zHmQJ5r3Uw5P9qTe4Ka1rdaiDjjn=u1zHx+j0zn9YHBGLzg@mail.gmail.com>
2012-12-01 14:51           ` Ken Moffat

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50B1F3A6.2090102@gmail.com \
    --to=gladkov.alexey@gmail.com \
    --cc=kbd@lists.altlinux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).