Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 681304 - sys-block/zram-init-8.1 - zram_swap.service fails to initialize in systemd due to misconfigured algorithm(?)
Summary: sys-block/zram-init-8.1 - zram_swap.service fails to initialize in systemd du...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal
Assignee: Jason Zaman
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-22 16:06 UTC by contactopublico57
Modified: 2024-08-05 17:45 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description contactopublico57 2019-03-22 16:06:59 UTC 
Source package referenced by zram-init 8.1 ebuild contains misconfigured execstart in zram_swap.service.

source:
ExecStart=/sbin/zram-init -s2 -azstd -Lzram_swap 2048  
fails systemd load and reports algorithm issue

modified:
ExecStart=/sbin/zram-init -s2 -a lz4 -Lzram_swap 2048  
syntax has been modified to specify lz4 algorithm and zram.swap.service loads without error.

Note that lz4 should be installed in the system for this to work.
Comment 1 Matt Turner gentoo-dev 2019-07-15 00:49:01 UTC 
Presumably it just requires that you have CONFIG_CRYPTO_ZSTD enabled in your kernel (or CONFIG_CRYPTO_LZ4 for lz4, etc).
Comment 2 Michael 'veremitz' Everitt 2020-07-10 05:39:39 UTC 
Adding mvaeth to CC for upstream verification, and potential resolutions. Tia Martin! :)
Comment 3 Martin Väth 2020-07-10 18:13:22 UTC 
Which algorithms are supported depends on your kernel and your kernel configuration. I have not rechecked, but CONFIG_CRYPTO_ZSTD is probably indeed the correct option which is needed.
Comment 4 Mattéo Rossillol‑‑Laruelle 2024-03-02 14:28:34 UTC 
This bug is probably outdated as `=sys-block/zram-init-8.1` was dropped a long time ago and, therefore, should be marked as resolved ?
Comment 5 Martin Väth 2024-03-02 14:39:54 UTC 
See comment#3. I would close the bug as INVALID, but I do not have permissions to change the status.