Bug 4491

Summary: insmod /path/to/nvidia.ko works, but modprobe nvidia does not works
Product: Fedora Reporter: sHaggY_caT <xusha.msk>
Component: nvidia-kmodAssignee: Nicolas Chauvet <kwizart>
Status: RESOLVED EXPIRED    
Severity: minor CC: leigh123linux, leigh123linux
Priority: P1    
Version: 25   
Hardware: x86_64   
OS: GNU/Linux   
namespace:
Attachments: result of the nvidia-bug-report.sh (nvidia does not loaded) and start log of the xorg with nvidia module

Description sHaggY_caT 2017-03-26 01:46:09 CET
Created attachment 1756 [details]
result of the nvidia-bug-report.sh (nvidia does not loaded) and start log of the xorg with nvidia module

I installed nvidia from rpmfusion-nonfree-updates-testing.

So, the insmod of the nvidia works, but modprobe nvidia does not works:

insmod /lib/modules/4.9.14-200.fc25.x86_64/extra/nvidia/nvidia.ko ; echo $?

returns 0, and lsmod | grep nvidia -here is module 

Also, it can run Xorg.

modprobe nvidia
modprobe: FATAL: Module nvidia not found in directory /lib/modules/4.9.14-200.fc25.x86_64


I've just attacted result of the nvidia-bug-report.sh (nvidia does not loaded) and log of the starting xorg with nvidia module
Comment 1 Nicolas Chauvet 2017-03-26 11:40:45 CEST
It could be because you have rebooted to early and the package installation didn't make a depmod command.
Another reason is that you have secureboot enabled ?
If you remove every kmod-nvidia and run akmods --force you should be able to modprobe nvidia appropriately.
Comment 2 sHaggY_caT 2017-03-26 12:29:36 CEST
after deleting all nvdia rpms and installing they again, and command akmods --force, modprobe works.
But without akmods --force it doesn't.

Probably you have to change a spec of the src.rpm, and add this command in the post-install scenario.
Comment 3 leigh scott 2017-03-27 08:28:20 CEST
I'm not seeing this issue on F25 or F26
Comment 4 Nicolas Chauvet 2017-06-27 13:52:09 CEST
It seems like there are a mix of issues here.

First akmods doesn't use modprobe nvidia anymore, we reload udev (in short) so the normal kmod loading mechanism occurs, so we don't need to hardcode anything in the module we have built and want to have loaded.

Then on post install, you might need to wait a little in order of the kmod to be built. It is still possible that if on a older kernel, the kmod is only built if you boot on the latter kernel. (uname  -r) and latter kernel-devel aren't found.

Now I don't think there is an issue on insmod/modprobe (which the bug summary describes). At least I don't reproduce that and I would need more information.
For example, are you able to use modinfo nvidia.
So to me this seems like a race condition where the module was built and your test occured in-between.

Feel free to re-open if you can provide more informations.
Thx