On Sun, Jun 7, 2020 at 11:25 PM Luya Tshimbalanga
<luya(a)fedoraproject.org> wrote:
> 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
This suggests the mkswap failed which might happen if this device is
already active, and somehow this service is from something else. Maybe
do:
dnf provides /usr/lib/systemd/system/zram-setup@.service
If that doesn't reveal anything, maybe this will reveal something:
journalctl -b | grep 'swap\|zram'
Done but these minor conflicts still remained. Maybe filing a bug
related to that issue?
Might give a shot on here first. Someone else may run into it, and
look in thread for a fix.
--
Chris Murphy