You are not logged in.
This is not my first time installing arch linux, but this time I'm out of luck to fix some starting issues. I've installed arch linux on lvm with full disk encryption using luks. I followed this guide: https://gist.github.com/kylemanna/cde14 … ac16b85458
However after the first boot I recognized a weird behavior regarding the internal keyboard of the fujitsu lifebook e 549. Whenever I try to enter the decryption password with the internal keyboard I don't get any reaction (not even on enter). When I connect a external keyboard it works flawless. After the system started the internal keyboard starts working again. Also when I tap numlock on the external keyboard when I have to enter the decryption password the internal keyboard starts working again but as soon as the system is started the internal keyboard stops working.
Here is what I tried to far:
enabling/disabling usb legacy support
mkinitcpio.conf with or without atkbd in modules
mkinitcpio.conf with different combinations of hook including keyboard, keymap, lvm2, encrypt, consolefont, autodetect
None of which resulted in any changes.
As of this post all updates are installed.
uname -r: 5.15.7-arch1-1
I know for a fact that these Laptops work great with linux (also without keyboard issues) when a different Distro is installed. However I like Arch better. Hopefully some of you can point me in any direction.
Offline
I followed this guide:
The official installation guide contains a more verbose description.
So follow the only guide that is supported on these boards and post again if the problem still persists.
Jin, Jîyan, Azadî
Offline
The link mentioned in the github tutorial didn't provide a verbose discription on how to setup archlinux with lvm and luks. However I found this site https://wiki.archlinux.org/title/Dm-cry … ire_system which was a little more helpful. Although I tried it with the instruction on the arch linux wiki page it didn't work.
However I found a workaround following another tutorial on github https://gist.github.com/huntrar/e42aee6 … d098c81268. The solution is unlocking the encrypted partition with a file (therefor avoiding the keyboard issue) during initramfs but unlocking the encrypted partition during grub with a password. This is not a solution!
Are there any other suggestions on how to properly solve this issue?
Last edited by iehfned (2021-12-14 15:32:15)
Offline