hello everyone , i have installed opensuse 13.1 three times repeatedly to make LVM. LUKS encryption work , i used guided partitioning , as opensuse is the only OS on my laptop , the installation setup runs and finished smoothly but after reboot it asks me for the encryption password , when i type it , it says password not found , is it a opensuse 13.1 specific problem or am i doing something wrong , i mean i used the guided partitioning so i dont know where i can go wrong , please clearify , what needs to be done to make LVM. LUKS encryption to work on OpenSUSE 13.1 cheers .
On 2014-01-24 11:56, linux new wrote:
>
> hello everyone , i have installed opensuse 13.1 three times repeatedly
> to make LVM. LUKS encryption work , i used guided partitioning , as
> opensuse is the only OS on my laptop , the installation setup runs and
> finished smoothly but after reboot it asks me for the encryption
> password , when i type it , it says password not found , is it a
> opensuse 13.1 specific problem or am i doing something wrong , i mean i
> used the guided partitioning so i dont know where i can go wrong ,
> please clearify , what needs to be done to make LVM. LUKS encryption to
> work on OpenSUSE 13.1 cheers .
Using a non US keyboard, perhaps? Only the US keyboard is allowed for
password at that point, I’m afraid.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
Well thanks mate . yes i m using a british keyboard , 
, just for information purpose , is this feature distribution specific or LINUX KERNEL specific ? because i used debian and LUKS encryption worked with it. debian is using 3.2.0.4 kernel at the moment whereas OpenSUSE is at 3.11.6.4.
Distribution specific. openSUSE mkinitrd lacks support for custom keyboard layouts. Next version will probably switch to dracut which does support it.
In any case - open bug report. Without bug report no patch can be issued for released versions (it does not mean it will be even if there is bug report, but still there is hope …)
On 2014-01-24 12:46, linux new wrote:
>
> robin_listas;2618947 Wrote:
>> Using a non US keyboard, perhaps? Only the US keyboard
>> is allowed for password at that point, I’m afraid.
> Well thanks mate . yes i m using a british keyboard , ,
Sigh. Mine is Spanish, so same problem. You have to limit yourself to
alphanumeric passphrases during boot. Manually mounted encrypted data
filesystems do not have this limitation, as they are activated with a
fully running system, so full keyboard support.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
On 2014-01-24 13:36, arvidjaar wrote:
>
> linux_new;2618950 Wrote:
>> is this feature distribution specific or LINUX KERNEL specific ?
>
> Distribution specific. openSUSE mkinitrd lacks support for custom
> keyboard layouts. Next version will probably switch to dracut which does
> support it.
I thought this was a limitation of grub :-? Huh, no, kernel is already
loaded…
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
Actually the same. grub2 itself does support custom keyboard layouts, the problem is a) to generate them and b) to use them. So it is entirely distro problem to produce correct grub configuration.
True, keyboard layout problems are common wrt passwords, particularly startup-passwords.
I don’t know Linux too well in this context, but my experience has always been that when things are US-keyboard specific, it is left to the BIOS to interprete the keyboard scancodes, or a simple “dummy” keyboard-driver-placeholder is in effect (I would expect that to continue with the new UEFI - unless country-specific keyboard layouts get direct support from UEFI as part of its Extensible part, which is not there today AFAIK).
If that holds true also in Linux (robin_listas/arvidjaar/anyone else?), you should be able to cope even with your UK keyboard, as the two layouts are pretty similar. Take a look here: http://www.uk-yankee.com/articles/us-vs-uk-keyboards-layouts-and-how-type-poundeuroother-symbols. There you will see the two layouts and its differences. The major difference in scancodes (the electrical codes sent by the keyboard and that are interpreted by BIOS and/or the keyboard driver) is complicated a little due to the fact that the UK keyboard has more keys than the US keyboard. If you did use a password mixed with punctuation/special characters (others than “+”, “-”, “_” and “=”), you may need to figure out which key send the correct scan-code, as that is moving around a little compared to the print on top of the keys. You do that by configuring US keyboard layout using your UK keyboard, and see which keys emit the characters you need.
So, if you didn’t use punctuation characters, #, $ or £ in your password, you should be fine. However, that would also indicate that your problem is elsewhere, and not keyboard layout related.
If you did use such characters in your password, try out what I described above.
dayfinger
EDIT: More info arrived when I wrote this, so some of it is already “old news”. What a great forum! 
The good news, is that you can probably fix your problem.
Boot from the install media, and open access to the encrypted LVM. Then you can use the “cryptsetup” command to add a second passphrase. Just be careful which keys you use with that. And use that new passphrase during future boots.
On 2014-01-24 14:56, arvidjaar wrote:
>
> robin_listas;2618984 Wrote:
>>
>> I thought this was a limitation of grub :-?
>
> Actually the same. grub2 itself does support custom keyboard layouts,
> the problem is a) to generate them and b) to use them. So it is entirely
> distro problem to produce correct grub configuration.
Uh. I guess it is not reusing the standard key maps the console or X
uses, they have to be generated for this task or something.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
No. They are far too complicated for a simple (simplistic) environment grub offers. It supports simple keyboard table with two different layouts and temporary switch (AltGr for the lack of better name) to the second one. It provides utility to generate keyboard layout tables from Xkb/linux ones.
On 2014-01-24 20:26, arvidjaar wrote:
>
> robin_listas;2619038 Wrote:
>>
>> Uh. I guess it [grub] is not reusing the standard key maps the console or X
>> uses, they have to be generated for this task or something.
>>
>
> No. They are far too complicated for a simple (simplistic) environment
> grub offers. It supports simple keyboard table with two different
> layouts and temporary switch (AltGr for the lack of better name) to the
> second one. It provides utility to generate keyboard layout tables from
> Xkb/linux ones.
Oh.
Perhaps sometime they will make keyboards that send utf-8 or similar
keycodes, not scancodes. Time to change that, after more than three
decades…
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)