Bug 3722 - USB keyboard not working during boot = Can not unlock encrypted system
Summary: USB keyboard not working during boot = Can not unlock encrypted system
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL: https://forums.mageia.org/en/viewtopi...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-12 17:31 CET by Morgan Leijström
Modified: 2012-12-02 14:31 CET (History)
0 users

See Also:
Source RPM: kernel
CVE:
Status comment:


Attachments
Output of lsinitrd /boot/initrd-$(uname -r).img (29.03 KB, text/plain)
2011-12-12 17:33 CET, Morgan Leijström
Details

Description Morgan Leijström 2011-12-12 17:31:34 CET
Description of problem:
USB keyboard does not work during boot.
It works in BIOS, GRUB, and after boot, but i can not enter passphrase.
Tried different ports, and with the keyboard as only USB device, and no other keyboard.

Steps to Reproduce:
1. Install mga 1 with encrupted root
More specifically i use / in an encrypted LVM
-All set up during install using mga1 installer only.

2. Now with only an USB keyboard, try to enter the passphrase during boot...

3. Plug in a PS/2 keyboard, and you can enter it OK.

To be more specific i installed having only a PS/2 keyboard.
Maybe it is so intelligent that it know it did not need USB keyboard support before.

This being a production system and i have never touched initrd etc before i refrain from experimenting...
Comment 1 Morgan Leijström 2011-12-12 17:33:07 CET
Created attachment 1227 [details]
Output of lsinitrd /boot/initrd-$(uname -r).img
Comment 2 Morgan Leijström 2011-12-12 17:45:23 CET
I see three entries for "USB keyboard" in MCC "browse hardware":
The first use usbhid, and the second sysrq, and i can not find neither in the lsinitrd output.
The third use kbd, which i have there.
Comment 3 Manuel Hiebel 2011-12-12 22:23:15 CET
thomas, something related to the kernel ?

Assignee: bugsquad => tmb
Source RPM: (none) => kernel

Comment 4 Morgan Leijström 2012-01-04 20:17:38 CET
After todays updates (including kernel) i can enter the key using USB keyboard :D

-> FIXED (how, i do not know but it works ;) )

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 5 Morgan Leijström 2012-07-18 01:51:25 CEST
It is baaack :/ 
Today i could not unlock my mga1 systems during boot, (fileserver and workstation) without using a PS/2 keyboard retried from the basement...
They have been running for at least two weeks without update so i am not certain when it broke.

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Comment 6 Morgan Leijström 2012-07-18 01:54:37 CEST
OOPS,i meant they have been running for at least two weeks without *reboot*
I run update on them about each week manually.
Comment 7 Manuel Hiebel 2012-11-05 16:51:18 CET
This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

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 Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad
Comment 8 Manuel Hiebel 2012-12-02 14:31:20 CET
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no 
longer maintained, which means that it will not receive any further security or 
bug fix updates. As a result we are closing this bug. 

If you can reproduce this bug against a currently maintained version of Mageia 
please feel free to click on "Version" change it against that version of Mageia and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
Mageia Bugsquad

Status: REOPENED => RESOLVED
Resolution: (none) => WONTFIX


Note You need to log in before you can comment on or make changes to this bug.