stuck at boot initialization

[ltsdw]

booster.yaml:

universal: true
strip: false
vconsole: false
timeout: 20s
append_all_modaliases: true
extra_files: busybox,fsck,fsck.btrfs,fsck.xfs
modules: xe,btrfs,dm_crypt,xfs
compression: ""

grub config:

GRUB_CMDLINE_LINUX_DEFAULT="rd.luks.name=(uuid)=root root=/dev/mapper/root booster.log=debug,console"

I'd love to provide a log, but as the log never gets written to disk because I unable to unlock my disks, journalctl doesn't log anything (also I can't use shift pgup/pgdown, so I can't read the initial log either).

It never times out, because I can't even type the password, read #113 but I don't think it's my case, because typing the password and waiting does nothing either.

[anatol]

It never times out

For the configuration you have booster will timeout after 20 seconds. And then drop into the busybox console. The console will help to examine kernel/booster logs.

because I can't even type the password

Do you mean that booster waits for the password but keyboard key pressing does nothing? Then it sounds like module for the keyboard/hid is missing in booster image. Run lsmod at a functional system and then compare it to booster ls $image to see what modules were not included to the image.

What booster version and what Linux kernel/distro do you use?

[ltsdw]

For the configuration you have booster will timeout after 20 seconds. And then drop into the busybox console. The console will help to examine kernel/booster logs.

I think it would only timeout if it happened to fail to mount the root partition, right? But I think as it never gets to the point of unlocking the root partition to mount, it cannot timeout.

Do you mean that booster waits for the password but keyboard key pressing does nothing?

Almost that, it shows a little message:

"Loading Arch Linux ...
Loading initial ramdisk ..."

Some initialization kernel log and also some log from the booster (but only about 8 lines which doesn't seem show anything useful, but I can't scroll up with "page up" to see more), the screen will blink (this is the part where the intel xe drm module gets loaded), and then... nothing, I can type, but nothing happens.

I can hear the fans spinning like crazy, like something is using all the cpu.

Run lsmod at a functional system and then compare it to booster ls $image to see what modules were not included to the image.

lsmod.txt
booster-ls.txt

Comparing the output of the lsmod and booster ls above, I tried adding vfat, fat, dm_integrity, usbhid and hid_multitouch, but no difference.

What booster version and what Linux kernel/distro do you use?

Arch Linux (as for kernel I tried with the arch's vanilla and a custom kernel, same result for both)
booster: 0.11-2