On Sun, Jun 7, 2020 at 1:26 PM Luya Tshimbalanga
<luya(a)fedoraproject.org> wrote:
zram-generator has no service unit file at all. The zram.service unit
file is part of Anaconda.
Good to know. I proceed to remove on my desktop which has 32 GB RAM.
I'm not sure whose service this is but I don't have it.
After removing both anaconda and zram package, the result is
systemctl status zram-setup(a)zram0.service
● zram-setup(a)zram0.service - Setup zram based device zram0
Loaded: loaded (/usr/lib/systemd/system/zram-setup@.service; static; vendor preset:
disabled)
Active: active (exited) since Sun 2020-06-07 22:08:36 PDT; 4min 57s ago
Process: 856 ExecStart=/bin/sh -c echo $ZRAM_NUM_STR >
/sys/class/block/zram0/max_comp_streams (code=exited, s>
Process: 879 ExecStart=/bin/sh -c echo $ZRAM_DEV_SIZE >
/sys/class/block/zram0/disksize (code=exited, status=1>
Process: 882 ExecStart=/bin/sh -c [ "$SWAP" = "y" ] &&
mkswap /dev/zram0 && swapon /dev/zram0 (code=exited, st>
Main PID: 882 (code=exited, status=1/FAILURE)
CPU: 4ms
It seems the script failed to properly read the last two variables.
This service is not permanent it's created by the generator, and
is
the only service unit I see.
Jun 03 00:47:53 flap.local systemd[1]: swap-create(a)zram0.service: Succeeded.
I got the same result from the journalctl:
systemd[1]: swap-create(a)zram0.service: Succeeded.
Conflicting implementations. I recommend removing both anaconda and
zram packages. Keep zram-generator package.
Done but these minor conflicts still remained. Maybe filing a bug related to that issue?
It's no longer needed. This is a hibernation hint. If you have no need
for hibernation, you can remove it. If you have disabled/removed the
disk based swap partition/LV then you can also remove this resume
hint, because you can't hibernate anyway.
Done. Hibernation was never used as the system has secure-boot enabled by default
--
Luya Tshimbalanga
Fedora Design Suite maintainer