Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#45849 - [linux] [dm-crypt] booting kernel 4.1.3-1 does not prompt for LUKS passphrase

Attached to Project: Arch Linux
Opened by Moviuro (Moviuro) - Thursday, 30 July 2015, 19:44 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 29 August 2015, 11:58 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After the last kernel upgrade and reboot, system fails to boot and doesn't ask me to enter a LUKS passphrase: mounting times out and I don't get into a recovery shell.
My root is a BTRFS partition, but the little info I get when booting doesn't point to it at all.

Works flawlessly on 4.1.2-2

Additional info:
* linux 4.1.3-1 x86_64
* systemd 223-1

/etc/mkinitcpio.conf
HOOKS="systemd autodetect modconf block sd-vconsole keyboard sd-encrypt filesystems"

/boot/loader/entries/arch.conf
title ArchLinux - signed
linux /vmlinuz-linux.signed
initrd /intel-ucode.img
initrd /initramfs-linux.img
options cryptdevice=UUID=c3c2fcfa-9265-4da7-a927-0a18d83d8d77:luks-c3c2fcfa-9265-4da7-a927-0a18d83d8d77:allow-discards root=UUID=73b5d405-ed79-474c-bb6a-e6c137eb9dcd rootflags=subvol=__active/root rw acpi_osi=Linux acpi_backlight=legacy quiet elevator=deadline


Steps to reproduce:
This task depends upon

Closed by  Dave Reisner (falconindy)
Saturday, 29 August 2015, 11:58 GMT
Reason for closing:  Not a bug
Comment by Moviuro (Moviuro) - Sunday, 09 August 2015, 21:40 GMT
Still broken on 4.1.4, please someone have a look at this and fix it.
Comment by Dave Reisner (falconindy) - Sunday, 09 August 2015, 23:23 GMT
Have you verified that downgrading to 4.1.2 produces a working configuration?
Comment by Moviuro (Moviuro) - Monday, 10 August 2015, 19:19 GMT
Yes, as stated above:

Works flawlessly on 4.1.2-2

(I wouldn't have been able to post if it didn't, BTW)
Comment by Dave Reisner (falconindy) - Monday, 10 August 2015, 19:58 GMT
No that isn't as stated above. I explicitly asked about a downgrade, which you don't call out in the original report.

> (I wouldn't have been able to post if it didn't, BTW)
Many people own multiple devices capable of loading a browser. I can't possibly assume anything about your setup.
Comment by Moviuro (Moviuro) - Tuesday, 18 August 2015, 19:48 GMT
4.1.5 is also broken.

Downgrading to 4.1.2 fixes the issue
Comment by Moviuro (Moviuro) - Saturday, 29 August 2015, 11:53 GMT
It actually was an issue with my not correctly secureboot-signing the kernel and using an outdated kernel with an uptodate initramfs.

Loading...