Bug 501584

Summary:	Initial initramfs created during installation has no keymap support
Product:	[Fedora] Fedora	Reporter:	Andreas Thienemann <andreas>
Component:	mkinitrd	Assignee:	Peter Jones <pjones>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	11	CC:	dcantrell, hdegoede, jlaska, pjones, rmaximo, vanmeeuwen+fedora, wtogami
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-01-12 15:32:30 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	446452

Description Andreas Thienemann 2009-05-19 20:43:41 UTC

Description of problem:
The initramfs created during anaconda installation has no support for the local keymap.
This is problematic when using cryptoroot as the password has to be entered with the keymap not matching the keyboard.

Rerunning mkinitrd after installation fixes this. Subsequent boots have the correct keymaps installed and the password entry works as expected.

Extracting the initial and the remade initramfs images and comparing the file lists gives the following: (a == orig, b == remade)

[root@dyn112 tmp]# diff -uNr a.lst b.lst 
--- a.lst       2009-05-20 00:21:04.955586740 +0200
+++ b.lst       2009-05-20 00:21:12.130592458 +0200
@@ -7,6 +7,8 @@
 ./bin/rmmod
 ./bin/cryptsetup
 ./bin/lvm
+./bin/loadkeys
+./bin/setfont
 ./bin/nash
 ./bin/modprobe
 ./bin/plymouth
@@ -16,6 +18,9 @@
 ./etc/lvm
 ./etc/lvm/lvm.conf
 ./etc/ld.so.cache
+./etc/sysconfig
+./etc/sysconfig/keyboard
+./etc/sysconfig/i18n
 ./etc/system-release
 ./etc/ld.so.conf.d
 ./etc/ld.so.conf.d/kernel-2.6.29.3-140.fc11.i686.PAE.conf
@@ -94,6 +99,28 @@
 ./lib/libreadline.so.5.2
 ./lib/libz.so.1.2.3
 ./lib/libpthread-2.10.1.so
+./lib/kbd
+./lib/kbd/consolefonts
+./lib/kbd/consolefonts/latarcyrheb-sun16.psfu
+./lib/kbd/keymaps
+./lib/kbd/keymaps/i386
+./lib/kbd/keymaps/i386/include
+./lib/kbd/keymaps/i386/include/linux-keys-bare.inc
+./lib/kbd/keymaps/i386/include/linux-with-alt-and-altgr.inc
+./lib/kbd/keymaps/i386/include/qwertz-layout.inc
+./lib/kbd/keymaps/i386/include/euro2.map
+./lib/kbd/keymaps/i386/include/compose.inc
+./lib/kbd/keymaps/i386/qwertz
+./lib/kbd/keymaps/i386/qwertz/de-latin1-nodeadkeys.map
+./lib/kbd/keymaps/i386/qwertz/de-latin1.map
+./lib/kbd/keymaps/include
+./lib/kbd/keymaps/include/compose.latin
+./lib/kbd/keymaps/include/compose.latin2
+./lib/kbd/keymaps/include/compose.8859_8
+./lib/kbd/keymaps/include/compose.latin4
+./lib/kbd/keymaps/include/compose.latin1
+./lib/kbd/keymaps/include/compose.8859_7
+./lib/kbd/keymaps/include/compose.latin3
 ./lib/libgcc_s-4.4.0-20090506.so.1
 ./lib/libsepol.so.1
 ./lib/libm.so.6
[root@dyn112 tmp]# 



Version-Release number of selected component (if applicable):
anaconda 11.5.0.53

How reproducible:
Always

Comment 1 Andreas Thienemann 2009-05-19 21:18:03 UTC

For details the initrd images are uploaded:

The initially generated initrd from anaconda:
http://home.bawue.de/~ixs/initrd-2.6.29.3-140.fc11.i686.PAE.orig.img

The regnerated one after installation:
http://home.bawue.de/~ixs/initrd-2.6.29.3-140.fc11.i686.PAE.img

Comment 2 Peter Jones 2009-05-29 21:06:34 UTC

Adding "kbd" to mkinitrd's deps seems to fix this issue.

* Fri May 29 2009 Peter Jones <pjones> - 6.0.86-2
- Require "kbd" package so keyboard settings will work right after initial
  installation. (#501584)

Comment 3 Jesse Keating 2009-06-01 17:57:28 UTC

Proposing for the blocker list, to get it in the next RC.

Comment 4 James Laska 2009-06-03 12:35:25 UTC

andreas: this issue has been fixed in Rawhide (as of 2009-06-02).  Are you able to confirm that rawhide behaves as expected with regards to local keymaps?

Comment 5 James Laska 2009-06-05 19:20:18 UTC

Andreas:  Peter Jones suggested the following steps to reproduce.  Using these steps, are you able to confirm the issue has been resolved?  

1) install with a foreign keyboard that has a known keymap (i.e. "keyboard cz-us-qwertz" in kickstart)
2) select encryption
3) set the encryption password to something that uses your keyboard's "y" key.  I recommend what would be "qwertyqwerty", except since you're in a weird keymap that's "qwertzqwertz"
4) reboot, and type qwertyqwerty in the box.  If it works, it worked.  If not, try "qwertzqwertz".  If that works, then it didn't.

If we are unable to verify this fix prior to release, it is possible this issue will remain in F-11 final.  Any help you can lend is appreciated!

Comment 6 Bug Zapper 2009-06-09 16:07:56 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Hans de Goede 2010-01-12 15:32:30 UTC

This is a mass edit of all mkinitrd bugs.

Thanks for taking the time to file this bug report (and/or commenting on it).

As you may have heard in Fedora 12 mkinitrd has been replaced by dracut. In Fedora 12 the mkinitrd package is still around as some programs depend on
certain libraries it provides, but mkinitrd itself is no longer used.

In Fedora 13 mkinitrd will be removed completely. This means that all work
on initrd has stopped.

Rather then keeping mkinitrd bugs open and giving false hope they might get fixed we are mass closing them, so as to clearly communicate that no more work will be done on mkinitrd. We apologize for any inconvenience this may cause. 

If you are using Fedora 11 and are experiencing a mkinitrd bug you cannot work around, please upgrade to Fedora 12. If you experience problems with the initrd in Fedora 12, please file a bug against dracut.