-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can not extract initramfs image properly (Ubuntu 18.04.1 LTS (Bionic Beaver)) #45
Comments
Are the other files like What yubikey-luks version do you use? The newest one need slight modifications of /etc/crypttab to work (however it may be not directly related to your issues. |
@Vincent43 The problem is about multi-segmented initramfs image. We need to use unmkinitramfs instead of cpio. Can you test it with your setup? |
This is ok. I have the same.
Did you changed initramfs compression method in /etc/initramfs-tools/update-initramfs.conf ? The default should be
I have similar output with that command so it shouldn't matter. I can't reproduce your problem. What files are extracted when you run In my testing it correctly deals with multi-segmented initramfs image, extracting all files under same directory including microcode. On the other hand So I think the problem is somewhere else. |
here is the outputs:
Cpio extracts only the early part of initramfs image, it can't extract "actual initramfs" in my setup. |
The only difference from my setup is that I use microcode for Intel. maybe AMD is screwing something. |
I have the same issue on intel. It happens on Ubuntu 18.04 with kernel 4.15 and 5.3. What is this line (https://github.com/cornelinux/yubikey-luks/blob/master/yubikey-luks-suspend#L92) actually supposed to do? |
I wanted to pick this up because I'm running into the same problem on 21.10. Ubuntu started using a strange process for their initrd, sometime around 18.04. The recommended initramfs decompression method is with the I'll work on this for a couple days and see if I can get a working suspend. If I get anywhere, I'll make a PR.
I'm not entirely clear on what that line is supposed to do, but the correct process for unpacking a traditional CPIO archive is to pipe the contents into cpio with the |
System startup usually works very well with Yubikey-luks, but when I try to suspend I get the following errors.
The first one is:
Because my initramfs not gunzip file.
Its OK. Then I changed the line with this
(cpio --quiet -id) < "${INITRAMFS}"
Then my laptop starts to suspend normally (it could wake up without yubikey) because of the line.
When I comment out the line and suspend proccess getting started with the following error:
chroot: failed to run command ‘/suspend’: No such file or directory
I figured out that my initramfs dont have suspend script (which is copied with initramfs hook)
Here is the update-initramfs log: https://gist.github.com/erolg/17d52e92195f8a3d251895ff54ab23b5
And here is my crypttab
cryptedlvm UUID=83feeca9-f770-4883-96fc-3d15d98190bd none luks,discard
update-initramfs seems to be OK. But there is no suspend script in the image.
I can't figure out why there is no suspend script in the image? Do you have any opinion?
Btw thank you for this great project!
The text was updated successfully, but these errors were encountered: