RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1111405 - Anaconda does not set keymap for console / luks
Summary: Anaconda does not set keymap for console / luks
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On: 1170579
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-20 00:55 UTC by William Brown
Modified: 2020-12-15 07:30 UTC (History)
3 users (show)

Fixed In Version: anaconda-19.31.83-1
Doc Type: Bug Fix
Doc Text:
Cause: Anaconda wrote boot options trying to set the console keymap on boot which no longer works with the way how dracut handles the host-only mode. Consequence: Problems with console keymap. Fix: Anaconda no longer writes boot options trying to set the console keymap on boot which no longer works with the way how dracut handles the host-only mode. Result: Less problems with console keymap on boot.
Clone Of:
: 1170579 (view as bug list)
Environment:
Last Closed: 2020-12-15 07:30:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description William Brown 2014-06-20 00:55:41 UTC 
Description of problem:
Identical to https://bugzilla.redhat.com/show_bug.cgi?id=875567

Anaconda does not set the vconsole parameter correctly, meaning a system's tty or plymoth prompts don't match the installed keyboard layout.
Comment 3 Alexander Todorov 2014-11-24 15:06:51 UTC 
I've selected Bulgarian language at the welcome screen and in keyboard selection removed US layout and left only BG layout. Then proceeded to install using the default disk layout + encryption. 

The system reboots but doesn't display any LUKS prompt. In fact the screen stays black all the time shortly after grub menu dissapears. I'm going to dig deeper into this tomorrow.
Comment 4 Alexander Todorov 2014-12-02 13:04:48 UTC 
See comment #3. 

After install the graphical plymouth scrfeen doesn't show a prompt to enter the password. Removing rhgb from the boot command line shows a text prompt but I'm unable to enter the password. Moving back to ASSIGNED.
Comment 5 Vratislav Podzimek 2014-12-03 09:04:33 UTC 
(In reply to Alexander Todorov from comment #4)
> See comment #3. 
> 
> After install the graphical plymouth scrfeen doesn't show a prompt to enter
> the password. Removing rhgb from the boot command line shows a text prompt
> but I'm unable to enter the password. Moving back to ASSIGNED.
I don't think any of these two issues you describe are caused by anaconda. Can you please check that on such system the /etc/vconsole.conf file contains the right value(s)? And that the grub configuration doesn't contain the specification of a vconsole.keymap? If these two things are as expected, there's nothing more anaconda could do about it. Everything else is dracut's task.
Comment 6 Alexander Todorov 2014-12-03 23:09:23 UTC 
* grub.conf doesn't define vconsole.keymap
* /etc/vconsole.conf has:
KEYMAP="us"
FONT="latarcyrheb-sun16"


Changing the KEYMAP to "bg" before reboot doesn't change anything. I forgot to check is initrd.img contains a copy of /etc/vconsole.conf but maybe it does.
Comment 7 Vratislav Podzimek 2014-12-04 10:44:30 UTC 
(In reply to Alexander Todorov from comment #6)
> * grub.conf doesn't define vconsole.keymap
That's correct.

> * /etc/vconsole.conf has:
> KEYMAP="us"
This is a bug in systemd which (via systemd-localed) suggests 'us' or nothing as a matching VConsole keymap for the 'bg' layout when queried by anaconda.

> FONT="latarcyrheb-sun16"
> 
> 
> Changing the KEYMAP to "bg" before reboot doesn't change anything. I forgot
> to check is initrd.img contains a copy of /etc/vconsole.conf but maybe it
> does.
This is a feature of dracut which requires intrd.img to be regenerated if /etc/vconsole.conf changed.
Comment 8 David Cantrell 2014-12-17 15:43:51 UTC 
Moving to 7.2 as this is dependent on bug #1170579.
Comment 16 RHEL Program Management 2020-12-15 07:30:41 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.