Can't use keyboard to type in LVM crypt password

English Install/Boot/Login
1

Hello I have installed leap 42.1 and using LVM container to encrypt my partitions.
However when I boot my machine I’m not able to type in the password in the password prompt.
I have an USB keyboard from Logitech (k800). I found out when I’m using an old keyboard with ps2 connector it works.
The K800 keyboard works in bios, in grub2 and afterwards when the system is booted.
But when the password dialog is shown it does not work.
What can I try to fix this? I don’t want to use 2 Keyboards all the time.

Thanks in advance for your help.
hihu

2

report the problem on bugzilla (same password as here)

workaround maybe get a USB to PS2 connector

3

Check https://bugzilla.opensuse.org/show_bug.cgi?id=953035 if it applies to your case.

4

Thank you guys for your replies. It looks like it is the same bug. I added a comment there. Hope it will be resolved soon.

I have another question concerning my partitioning. Maybe someone can answer me.

I have a Intel SSD 80GB and a 640 GB hardisk. Finally I managed to create the efi-boot, boot partition and / on my SSD. On the harddisk I have my home directory.

hihu@linux-f0te:~> lsblk --fs
NAME                                                     FSTYPE LABEL UUID MOUNTPOINT
sda                                                                        
├─sda1                                                                     /boot/efi
├─sda2                                                                     /boot
└─sda3                                                                     
  └─cr_ata-INTEL_SSDSA2M080G2GC_CVPO018601E8080JGN-part3                   
    ├─system-swap                                                          [SWAP]
    └─system-root                                                          /opt
sdb                                                                        
└─sdb1                                                                     
  └─cr_ata-WDC_WD6400AAKS-65A7B2_WD-WCASYA566723-part1                     
    └─xs-home

So partition sda3 and sdb1 are separate LVM volume groups which I encrypted.
Afterward I divided sda3 into swap and root.

Do I also have to encrypt the sub directories swap and root or is it enough when the “main container” is encrypted?

Graphically it looks like this.

http://i64.tinypic.com/amfrf6.jpg

http://i64.tinypic.com/qxw7l3.jpg

http://i68.tinypic.com/4g42u8.jpg

The last screenshot says unencrypted. Is it correctly encrypted?
When the SSD gets defective can I mount the home LVM container on another OS and read the data there?

Thank you very much

5

You encrypt the LVM anything in it is encrypted. Volumes in the LVM are not encrypted the container where they live is encrypted, thus the info in them is encrypted.

If I need a key to get into my offices I may opt to not use a key to get into my file cabinet because the office locks protects the files. Does the help??

6

Thanks gogalthorp. Yes that helps a lot. When I lock the front door I don’t need to lock the office door inside the building. Makes sense.

And I can also put my harddisk with lvm home into another linux computer and read it from there (of course only if I know the correct password)?
Just in case my root gets somehow corrupted, deleted, destroyed, what else (of course I make backups too).

greetings

7

Well remember that once you unlock the door any one can come in. Encryption only protects against someone stealing the machine not against some when setting down to a logged in session. So use cloning to back up if you want your backups also protected. Simply backing files and you backups are in the clear.

8

That’s true. That’s the reason why encrypting a notebook makes more sense than an desktop computer because the notebook is at higher risk to be stolen at public places.
To steal a desktop you would have to unlock the “front door” first :slight_smile:

Thank you very much

9

Thank you everybody. Got a reply from the developer and it will be fixed with an update.

So when you don’t have an PS2 Keyboard you need to follow the steps mentioned at the bugtracker. Otherwise you can wait until the update is released.

Solved