Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues when both kernel and kernel module are updated within the same boot #9

Open
JonnyHaystack opened this issue Apr 7, 2020 · 1 comment

Comments

@JonnyHaystack
Copy link

This hook does stop kernel updates from breaking everything, but if the kernel and a module e.g. nvidia are both updated in the same boot, the nvidia driver seems to stop working (can't start any new processes that use GPU acceleration, e.g. Alacritty). I'm not 100% sure of the exact circumstances that cause this to happen.

This also happens if you updated the kernel then you try to install a new kernel module. The other week I had a kernel update, then later I installed the wireguard module, but I could not load it with modprobe. This seems to be because it installs the module only in the new kernel, but not for the currently running kernel. When I installed wireguard-dkms instead, it installed it for both the running kernel and the new kernel, so I was able to load it.

Is there anything that can be done about this problem?

@Optiligence
Copy link

afaik this already breaks if only the nvidia package is upgraded (more than only pkgrel)
some files (haven’t bothered to find out which yet) from that seem to be required for the module to continue to function properly

so, basically, this is a rather separate issue (although i’d like to have a nice solution for that as well)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants