foundObjects / zram-swap

A simple zram swap service for modern systemd Linux

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

FATAL: Module zram not found in kernel 5.15

archisman-panigrahi opened this issue · comments

I installed the zram-swap-git package from the AUR in EndeavourOS. I get the following error when I try to start the service.

$ sudo systemctl start zram-swap.service
Job for zram-swap.service failed because the control process exited with error code.
See "systemctl status zram-swap.service" and "journalctl -xeu zram-swap.service" for details.

Here is the status

$ systemctl status zram-swap.service
× zram-swap.service - zram swap service
     Loaded: loaded (/usr/lib/systemd/system/zram-swap.service; disabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Mon 2022-02-07 10:18:09 IST; 8s ago
    Process: 35823 ExecStart=/usr/bin/zram-swap.sh start (code=exited, status=1/FAILURE)
   Main PID: 35823 (code=exited, status=1/FAILURE)
        CPU: 13ms

Feb 07 10:18:09 eOS-KDE systemd[1]: Starting zram swap service...
Feb 07 10:18:09 eOS-KDE zram-swap.sh[35826]: modprobe: FATAL: Module zram not found in directory /lib/modules/5.15.19-1-lts
Feb 07 10:18:09 eOS-KDE zram-swap.sh[35823]: Err main: Failed to load zram module, exiting
Feb 07 10:18:09 eOS-KDE systemd[1]: zram-swap.service: Main process exited, code=exited, status=1/FAILURE
Feb 07 10:18:09 eOS-KDE systemd[1]: zram-swap.service: Failed with result 'exit-code'.
Feb 07 10:18:09 eOS-KDE systemd[1]: Failed to start zram swap service.

I ended up with same error today. Most probable scenario explained here:

[rpdom] wrote:
Have you recently done and apt full-upgrade and not rebooted yet? It could be that you now have a 5.4.51 kernel and associated modules installed, but because you haven't rebooted you are are still running the old 4.19.118 kernel.

Please @apandada1 confirm if this was your case to close this issue.
PS: I'm adding this information here for future reference. Kudos to rpdom

Yes, this was the issue. I had to start/enable the service after reboot.