Closed kallisti5 closed 6 months ago
Please use the latest version to test, it is possible that this has been fixed in the meantime.
FWIW: I ran into this issue on Arch Linux as well.
In my case the reason was, that I had upgraded the kernel but didn't reboot yet (we nuke the modules of the previous kernel, so netavark was not able to load the required kernel modules on demand).
FWIW: I ran into this issue on Arch Linux as well.
In my case the reason was, that I had upgraded the kernel but didn't reboot yet (we nuke the modules of the previous kernel, so netavark was not able to load the required kernel modules on demand).
Huh? This sounds like big arch linux issue, doesn't it keep older kernels on updates like other distros?
Regardless this is not something netavark can fix so I close this one.
Huh? This sounds like big arch linux issue, doesn't it keep older kernels on updates like other distros?
You can keep the modules of the previous kernel around with a script but generally we do not have that type of versioned package. The linux package is always tracking the latest version, the linux-lts always the LTS releases, etc.