This is a discussion topic for the following Common Issue:
You can discuss the problem and its solutions here, but please note that debugging and technical feedback should primarily go to the issue trackers (e.g. Bugzilla) linked in the Common Issue, because that’s the place that developers watch, not here.
If there are any updates/changes/amendments for the Common Issue description, which you believe should be performed, please post it here.
Please see the Common Issue for solution/workarounds:
Is this necessary? We don’t have it included in the Common Issue description.
If akmods run the compile processes in background, is there a better way to ensure the processes have finished, rather than waiting some time and hoping it was enough? Grep the process list perhaps?
The script doesn’t seem to offer the functionality.
Possibly not. Once the akmods command ends (while running in the foreground) the kmod package has already been installed. I suggested that for additional insurance.
Note that on the initial install of akmod-nvidia the fact that akmods is still performing the background compile after the install is complete and a prompt reboot without waiting does interfere with the compile and install of the kmod-nvidia-$(uname -r) package.
The current understanding of the problem is that some (system upgrade) process kills the akmod task before it ends. The usual workaround is to run sudo depmod -a
(then modinfo nvidia will works).
See also 2011120
Note that this issue never occurs with dnf distro-sync --releasever=39 (some insight are explained on the bug).