[sOLVED] Screen turns of while boot after update

Markus.N2 · 2026-04-10 17:40:42

Hi,
Since the latest upgrade, I can't get my system to boot anymore.
Edit:
The last message I see is:

Triggering uevents

and then the screen turns off.
/Edit:

I have a somewhat unusual hardware setup:

two NVME's, each with encryption and individual LVM on top
one md-raid, with encryption and individual LVM on top

So every hardware volume (md-raid counting as one) has their own encrypted partition and their own LVM because I wanted to keep the freedom to move them between PCs, and fortunately this is now making it easier to go with only one of them (see below).
In order to avoid a horribly long kernel command line, I've created a custom "encrypt" hook that reads the cryptdevices from a file instead of the kernel command line. The last update broke it.

In order to make things easier, I've reverted everything to the most default-ish setup I can work with:

only one NVME, but still encryption with LVM on top of it
Everything else unplugged and commented out of /etc/fstab
re-added "cryptdevice" parameter to kernel command line
using the package-provided mkinitcpio with just the hooks modified
switched back to the original "encrypt" hook

I've tried the systemd-based as well as the udev-based approach. However, I'm not sure if I did everything needed to do so. All I could find was that I need to have either "systemd" or "udev" in my "HOOKS" line.
For now, I would like to stick to the udev-based initramfs because of familiarity and maybe try the systemd approach on a virtual machine before converting my real machine.

When booting, I don't even get the password prompt for my disk encryption, so I think I missed something fundamental.

This is my kernel command line:

linux /vmlinuz-linux-lts root=/dev/mapper/SystemGroup-arch_prod rw amdgpu.dc=0 core.autosuspend=-1 pcie_aspm=off cryptdevice=/dev/disk/by-uuid/d966b99e-40df-4ee6-97c3-b32894b0d179:Samsung2TBlvm:allow-discards

And these are my hooks:

HOOKS=(base udev autodetect modconf kms keyboard keymap consolefont block encrypt lvm2 filesystems fsck)

Any ideas?
Thanks.

Last edited by Markus.N2 (2026-04-11 06:37:43)

seth · 2026-04-10 22:43:24

I've created a custom "encrypt" hook

The details on that sound rather relevant?
Also

I can't get my system to boot anymore.

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
What exactly fails how? Error messages?

systemd and busybox are not compatible here, you need the sd-encrypt hook for the former and the kernel commandline syntax differs.
https://bbs.archlinux.org/viewtopic.php?id=310004

Markus.N2 · 2026-04-10 22:59:23

Thanks for the reply. I've edited the original post to describe what I can see.
To make this thread easier to read, here is a copy:
The last message I see is:

Triggering uevents

and then the screen turns off.

The difference between my custom "encrypt" hook and the original is

that reads the cryptdevices from a file instead of the kernel command line

but as I wrote, I've reverted to the original for the purpose of troubleshooting this problem.

It looks a bit like the hooks are either not run or fail. Is there a way to create a "more verbose" initramfs that prints out something like "running ${hook}"?

Last edited by Markus.N2 (2026-04-10 23:01:08)

seth · 2026-04-11 00:13:31

The last message I see is:
Triggering uevents
and then the screen turns off.

amdgpu.dc=0 core.autosuspend=-1

Remove amdgpu.dc=0 and "core.autosuspend=-1" is likely supposed to be "usbcore.autosuspend=-1"
Does it help to add "nomodeset"? Resp. remove the "kms" hook to only load the GPU driver and kms after the initramfs

Markus.N2 · 2026-04-11 06:36:34

I removed the parameters you mentioned, and it worked. System starts again. I did not need to remove the "kms" hook.

Thank you very much.

The rest (multiple encrypted volumes, maybe systemd-based initramfs, ...) is now on me to figure out.

seth · 2026-04-11 06:44:33

You can keep the "usbcore.autosuspend=-1", I was just pointing out that the present version looks like you meant something else

Arch Linux

#1 2026-04-10 17:40:42

[sOLVED] Screen turns of while boot after update

#2 2026-04-10 22:43:24

Re: [sOLVED] Screen turns of while boot after update

#3 2026-04-10 22:59:23

Re: [sOLVED] Screen turns of while boot after update

#4 2026-04-11 00:13:31

Re: [sOLVED] Screen turns of while boot after update

#5 2026-04-11 06:36:34

Re: [sOLVED] Screen turns of while boot after update

#6 2026-04-11 06:44:33

Re: [sOLVED] Screen turns of while boot after update

Board footer