After installing OpenSUSE 13.2 x64 in English with chosen Greek Keyboard layout
I can’t seem to get the keyboard working when it comes to LUKS login, to decrypt the hard-drive.
It works well in BIOS and in Grub.
I have had that happen in the past, but managed to work around it.
Are you using some special keyboard that requires a driver that isn’t loaded until after the LUKS password is given?
If the keyboard worked during install, and if the keyboard works when booting live media, then it very likely is a module that needs to be forced into the “initrd” so that it is available before you provide the encryption key.
I went at a friend’s house and picked up a PS/2 keyboard…
GUESS WHAT??! It Almost worked… the pS/2 worked but, some keys were broken… Everything worked (except 3 keys that I needed for the password)
then “dracut” showed up and I was like “let’s connect my keyboard” and this happened http://imgur.com/a/SYrD7
The mouse shouldn’t matter, since it isn’t used during the LUKS key prompt. I had to look up “Sharkoon Skiller” – it seems to be a fancy gaming keyboard.
My suggestion: use a standard generic keyboard, and see if that gets you past the LUKS password prompt.
If that works, then use the command “lsmod” to list loaded modules. Redirect that to a file.
Then plug in your fancy keyboard. Do the “lsmod” again, to a different file. Then try to find which additional module was loaded that might be relevant.
I think you can then force that into the “initrd” using “dracut.conf” (in “/etc”).
During the installation I chose English Language and Greek keyboard layout.
As far as I know, plain ASCII is used at that stage in booting.
eh, it’s not that fancy just a usual multimedia with nice design (15€)
Still have no way to get in… the ps/2 worked but, as i mentioned some keys aren’t working (that i need for the password)
but I’ll find another one try again and leave a reply…
By the way, the same thing has happened with Ubuntu, Mint and another distro… when I used LUKS instead of normal installation.
You should make your LUKS password one that uses only standard characters available on a plain ASCII keyboard. Or add a second LUKS password for standard characters only.
If you are encrypting root, as is often done with an encrypted LVM, then the LUKS password prompting is done before any special keyboard setup.
From my readings on Google that particular keyboard is a problem for Linux in general and requires special instruction to work. Maybe if you don’t encrypt the root just the data you want to protect it might work better. Or just use a standard keyboard. Gaming keyboards in general are bad news and this one seems worse then many. Can it be made to work. I have no doubt. How many hours do you want to invest in the project???
Time isn’t a problem - (If that’s what you mean. Sorry english is not my native :))
I just wanna make it work… http://imgur.com/a/SYrD7 in these photos, I connect my keyboard and it shows up as “echi-pci”… Maybe I should somehow load “echi-pci”… Someone else also suggested to load “hid-generic”.
Is this possible from the ‘boot’ partition or Grub? If not, i’ll just find a ps/2 keyboard and make the way arround.
On 2015-05-18 00:16, igotproblemsyeah wrote:
>
> I forgot to add, the keyboard works Perfectly in all recent linux
> unencrypted distros!
>
> It’s only an issue when it comes to LUKS Login Promt.
Probably because the needed module is loaded later.
The place to load it is by placing it in initrd, which is an archive in
/boot, so it is accessible before entering the password. I don’t know
how to do it in 13.2, but it is done via dracut configs. Have a look at
this thread:
On 2015-05-18 07:06, igotproblemsyeah wrote:
>
> robin_listas;2710417 Wrote:
>> On 2015-05-18 00:16, igotproblemsyeah wrote:
>>
>> The place to load it is by placing it in initrd, which is an archive in
>> /boot, so it is accessible before entering the password. I don’t know
>> how to do it in 13.2, but it is done via dracut configs. Have a look at
>> this thread:
>>
>> http://lists.opensuse.org/opensuse/2015-03/msg00780.html
>>
>>
>
> Thanks for your reply, I appreciate it a ton!
>
> Do you mean in here? http://prntscr.com/76hcux
> (initrd-3.16.7-21-desktop) http://prntscr.com/76hdbo
Please read the entire mail list thread I linked above.
What you do ends up in initrd, but don’t even dream of touching the
archive directly. You have to change dracut configs /somehow/, and you
have to find out that somehow from that thread. And after finding the
somehow, you have to find the /what/ to change, probably a module to be
loaded at boot. Which? No idea.
On 2015-05-18 10:26, igotproblemsyeah wrote:
>
> Maybe I could set up a USB Key, log in… and then update the Boot-load
> packages? (if yes, how could i do that?)
>
>
You have to mount your system root, say on /mnt. If you have /boot and
/boot/efi, mount them as well. Home is not needed (unless you need read
some thing)
Then you have to mount bind all the virtual filesystems from the live to
the system under maintenance:
mount --bind /proc /mnt/proc
same for sys and dev.
Finally, you do “chroot /mnt” and run whatever commands you need for
maintenance.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)