You are not logged in.
Moderator comment. Changed the thread title from "[SOLVED] Cannot boot encrypted root filesystem after kernel upgrade" after making this a sticky topic
After the recent kernel update to 3.13, I can no longer boot my system.
When prompting for the luks password, my computer doesn’t react to any keyboard input (not even C-A-Del) and I have to power it down manually.
This is my mkinitcpio.conf:
MODULES="ahci asus_laptop libahci ehci-hcd uhci-hcd ext4 btrfs crc32c"
BINARIES=""
FILES=""
HOOKS="base udev autodetect modconf block encrypt lvm2 btrfs"
COMPRESSION="xz"
and from my syslinux.cfg:
LABEL arch
LINUX /vmlinuz-linux
APPEND cryptdevice=/dev/sda3:root:allow-discards root=/dev/mapper/vgroup-root rootflags=subvol=@,compress=lzo,ssd rootfstype=btrfs ro
INITRD /initramfs-linux.img
The LTS kernel works fine.
Last edited by ewaller (2014-02-21 17:01:41)
Offline
Hey, I think you're the first!
Read the news on the front page.
Offline
pacman prints the info too.
Offline
Hey, I think you're the first!
Read the news on the front page.
Could have thought of that … thanks.
Offline
Moderator Comment: I think this topic needs to be made sticky for a while.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Moderator Comment: I think this topic needs to be made sticky for a while.
Sure, but the thread's title is pretty specific to OP's problem and other users might still overlook it.
Offline
ewaller wrote:Moderator Comment: I think this topic needs to be made sticky for a while.
Sure, but the thread's title is pretty specific to OP's problem and other users might still overlook it.
Good Point. I think I'll (slightly) abuse my privileges and change the title.
Related thread: https://bbs.archlinux.org/viewtopic.php?id=177453
Last edited by ewaller (2014-02-22 01:00:59)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
The default line in mkinitcpio.conf (I think that this is the default line)
HOOKS="base udev autodetect modconf block keyboard fsck"
does not work when using cryptsetup such that systemd prompts the user for a password, and must then be changed to
HOOKS="base udev autodetect modconf keyboard block fsck"
At least this is true when using
MODULES="atkbd ..."
I am an evil patriARCH, peach!
Offline
Any chance that this might mess with USB keyboards as well, or is it strictly a P/S2 concern?
Offline
Any chance that this might mess with USB keyboards as well, or is it strictly a P/S2 concern?
Strictly a P/S2 problem.
Feel free to start a new thread if you are having a similar problem with a USB keyboard. If you are only having trouble in X, be sure to read up on some of the issues some members have been encountering with rootless Xorg.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline