Arch Linux

Simaryp

Member

Registered: 2018-04-28

Posts: 153

No keyboard on boot to unlock encrypted system

Hi,

I recently updated a machine thats running arch with gnome and plymouth and gdm-plymouth.

After the update I've stuck now with the problem that I get no keyboard to enter anything so I am stuck on the input for decryption.

During boot I got the message:
Warning: /lib/modules/5.6.5-arch3-1/modules.devname not found - ignoring

So I thought maybe I messed up, because I didn't upgrade plymouth and gdm-plymouth. So I chrooted into the system updated the two packages and did a pacman -Syu again.

During boot I get now the message:
Warning: /lib/modules/5.6.6-arch1-1/modules.devname not found - ignoring

And when prompted for the decryption password I still have no keyboard.

Now I am a bit stuck . Can anyone help me, get it running again?

loqs

Member

Registered: 2014-03-06

Posts: 19,077

Re: No keyboard on boot to unlock encrypted system

Warning: /lib/modules/5.6.6-arch1-1/modules.devname not found - ignoring

Means the kernel and modules do not match.  Was /boot mounted when the kernel package was updated?

Simaryp

Member

Registered: 2018-04-28

Posts: 153

Re: No keyboard on boot to unlock encrypted system

I guess so.

And definitely it was when I updated again in chroot environment.

Can it be related to having both linux and linux-lts installed?

My boot parameters in my refind_linux.conf are:
cryptdevice=/dev/sdb2:lvm:allow-discards quiet splash vt.global_cursor_default=0 loglevel=3 rd.udev.log-priority=3 root=/dev/volgroup0/lv_root rw initrd=/arch/intel-ucode.img initrd=/arch/initramfs-linux-lts.img

But so far that worked fine.

Edit:
To make a simple check I changed the refind_linux.conf to boot initramfs-linux.img and that worked.
So for whatever reasons on that systemthe correct modules for linux kernel are there, but not for the lts kernel.
Thats somehow ironical, because I installed lts there, to get a bit more stable system^^.

If there is a simple fix or if it helps to debug something I would stay with lts. Otherwise I am also fine with uninstalling lts and keep the system now as it is.

Last edited by Simaryp (2020-04-25 05:57:13)

loqs

Member

Registered: 2014-03-06

Posts: 19,077

Re: No keyboard on boot to unlock encrypted system

REFInd#For_kernels_automatically_detected_by_rEFInd?

Simaryp

Member

Registered: 2018-04-28

Posts: 153

Re: No keyboard on boot to unlock encrypted system

If you were refering on extra_kernel_version_strings that didn't help.

loqs

Member

Registered: 2014-03-06

Posts: 19,077

Re: No keyboard on boot to unlock encrypted system

I was referring to extra_kernel_version_strings.  Have you tried an entry using %v?

cryptdevice=/dev/sdb2:lvm:allow-discards quiet splash vt.global_cursor_default=0 loglevel=3 rd.udev.log-priority=3 root=/dev/volgroup0/lv_root rw initrd=/arch/intel-ucode.img initrd=/arch/initramfs-%v.img

Simaryp

Member

Registered: 2018-04-28

Posts: 153

Re: No keyboard on boot to unlock encrypted system

I tried it out now and it boots correctly, but the normal linux. And not lts.
The very same effect I got when I didn't enable the extra_kernel_version_strings and just remove -lts from my parameters.

I also wonder if this is really the problem, because the configuration as posted before worked just fine for several months. Maybe something went wrong on the installation of linux-lts on the recent update?

But it's also ok for me to just go without lts.

loqs

Member

Registered: 2014-03-06

Posts: 19,077

Re: No keyboard on boot to unlock encrypted system

From the refind menu are there two entries one for linux and one for linux-lts?
If you edit the entry for linux-lts with F2 is the initrd listed as initrd=/arch/initramfs-linux.img or as initrd=/arch/initramfs-linux-lts.img?

Simaryp

Member

Registered: 2018-04-28

Posts: 153

Re: No keyboard on boot to unlock encrypted system

I only created one entry and that was configured to be linux-lts specified by the refind_linux.conf line i posted above.

When I edited it to be initramfs-linux.img to boot the normal kernel everything was working now. I just removed the linux-lts and linux-lts-headers on that machine. I think it's not really a solution, more a workaround but it's ok for me.

loqs

Member

Registered: 2014-03-06

Posts: 19,077

Re: No keyboard on boot to unlock encrypted system

The entries in refind_linux.conf are intended to apply to every kernel in that directory as the wiki explains.
If refind was not providing menu entries for both linux and linux-lts with the correct extra_kernel_version_strings then something was going wrong.
How is the ESP mounted on the installation?  You could create full entries in refind.conf for both linux and linux-lts.

Simaryp

Member

Registered: 2018-04-28

Posts: 153

Re: No keyboard on boot to unlock encrypted system

As i said, I will just go with non-lts.

But for completeness. I mounted  esp to /efi created a folder /efi/arch and mount --bind /efi/arch to /boot. Therefor in my refind_linux.conf the paths start with /arch.

Thanks anyway for the effort. I guess that you are right in terms that I could enhance my refind by editing proper settings to have both normal and lts to select from boot etc. But I don't think that this is the core of the problem. Because that worked now for a long time with both non-lts and lts installed and untouched configs. If that would be the problem it should have been a problem way before, wouldn't it?