search

Frogging-Family / linux-tkg

linux-tkg custom kernels
GNU General Public License v2.0
1.33k stars 166 forks source link

debian testing: no keyboard for booting with luks #891

Open mabod opened 7 months ago

mabod commented 7 months ago

I did my first try with linux-tkg on debian testing. The resulting packages are linux-image-6.6.18-tkg-eevdf_6.6.18-1_amd64.deb and linux-headers-6.6.18-tkg-eevdf_6.6.18-1_amd64.deb

But I can not boot with them because I can not enter the LUKS password for the encrypted root partition. I see the luks prompt, but the cursor is not blinking and I can not enter the password. The keyboard seems to be dead. Nothing works. Not even Cntrl-Alt-Delete.

This is the customization.cfg I have used: customization.cfg.txt

What am I missing?

EDIT: I need to add that this is on my laptop: Lenovo X1 carbon with the integrated keyboard.

Tk-Glitch commented 7 months ago

Hi mabod,

You should try to build a full kernel first (by disabling modprobed-db in your .cfg). That will take more time (and disk space) to build but you should have everything working.

After using your machine for a while and populating your modprobed-db with the full kernel, you should then be able to build with it enabled again, now with the modules needed for your machine. You could also decide not to use modprobed-db if your CPU is strong enough, and always build full kernels to have the freedom of adding new devices or depending software down the line - at the price of longer compilations and a bit larger kernel packages.

mabod commented 7 months ago

You should try to build a full kernel first (by disabling modprobed-db in your .cfg).

my customization.cfg has _modprobeddb="false" That should do it.

But it is solved now. Looks like a module was missing in the initramfs. When I changed initramfs.conf from

MODULES=dep

to

MODULES=most

it started to work. But I still do not know which module was missing. I would like to identify that module and include it in the kernel. Any idea how to identify that module?

AdelKS commented 7 months ago

it started to work. But I still do not know which module was missing. I would like to identify that module and include it in the kernel. Any idea how to identify that module?

Is it dracut that debian uses ?

mabod commented 7 months ago

debian testing is using mkinitramfs , no dracut. I would assume that this missing module is not an isolated problem for my laptop. I am using a standard debian testing install with grub and luks. I assume that this non functional keyboard during luks prompt affects many more debian users with luks+grub.