@magnus, the invocation seems wrong to me try with something like:
(sudo) sedutil-sleep --prepareForS3Sleep 0 $pass /dev/nvme0n1
the important part is that the device includes the "n1" (special for nvme)
Git Clone URL: | https://aur.archlinux.org/sedutil-sleep-git.git (read-only, click to copy) |
---|---|
Package Base: | sedutil-sleep-git |
Description: | TCG OPAL 2.00 SED Management Program - including S3 sleep support |
Upstream URL: | https://github.com/fabiogermann/sedutil |
Keywords: | opal s3 sedutil sleep tcg |
Licenses: | GPL3 |
Submitter: | germafab |
Maintainer: | germafab |
Last Packager: | germafab |
Votes: | 1 |
Popularity: | 0.000000 |
First Submitted: | 2020-05-10 12:25 (UTC) |
Last Updated: | 2021-04-03 12:13 (UTC) |
@magnus, the invocation seems wrong to me try with something like:
(sudo) sedutil-sleep --prepareForS3Sleep 0 $pass /dev/nvme0n1
the important part is that the device includes the "n1" (special for nvme)
I'm getting errno 25 when running the --prepareForS3Sleep
:
# sedutil-sleep --prepareForS3Sleep 0 my-pwd /dev/nvme0
Error saving the password to the kernel errno = 25
AFAIU that means the device doesn't like the ioctl code sent, but why would that be?
@IncredibleLaser I have added the build dependency "git" - thanks for the hint
Please add git to the build dependencies, otherwise it will fail in a clean chroot.
Seems to be resolved recently.
@germafab. I don't use any BIOS supported encryption, so on my end that won't be the case. However, in the linked issue, there's also a link to https://github.com/Drive-Trust-Alliance/sedutil/issues/354 which in turn points to an apparent kernel regression at https://bugzilla.kernel.org/show_bug.cgi?id=211227. I'm awaiting progress on that kernel ticket so far.
@khenderick thanks for pointing out the issue. Having followed up on comments in the github issue the most likely reason for this is mixing BIOS managed encryption and sedutil/OPAL (pba image etc.) - which is not supported. Should this not be the case, please reach out to me by email and I'll try to help.
It seems resume after sleep is broken at this moment as the system seems to freeze. See also: https://github.com/Drive-Trust-Alliance/sedutil/issues/90#issuecomment-763079486
This installs as new binary 'sedutil-sleep'. (sudo may be required)
usage (with password directly):
(sudo) sedutil-sleep --prepareForS3Sleep 0 <password> <device>
or (with hashed password - for i.e. Systemd service):
(sudo) sedutil-sleep --printPasswordHash <password> <device>
(sudo) sedutil-sleep -n -x --prepareForS3Sleep 0 <HASHED_PASSWORD> <device>
Based on work in: https://github.com/Drive-Trust-Alliance/sedutil/issues/90
Pinned Comments
germafab commented on 2020-05-10 12:49 (UTC) (edited on 2020-05-10 12:52 (UTC) by germafab)
README
This installs as new binary 'sedutil-sleep'. (sudo may be required)
usage (with password directly):
or (with hashed password - for i.e. Systemd service):
Based on work in: https://github.com/Drive-Trust-Alliance/sedutil/issues/90