On 02/13/17 05:14, Stephen Morris wrote: > To test out dkms compiling and installing my wifi driver I have > uninstalled the driver from the kernel with dkms, removed the driver > from dkms and re-added the driver to dkms. > > When I boot Fedora dkms compiles and installs the driver into the > kernel but it does not issue a modprobe to actually load the driver, > how do I force dkms to do so, or alternatively am I missing the > package that would provide that functionality? This sounds similar to the problem I'm seeing with the vboxvideo driver. When a new kernel is built the vboxvideo driver is built for the newly installed kernel. However, on reboot it does not get loaded. The system comes up with dkms.service running in the background again building the VBox modules. After that finishes I can reboot and the system will come up the modules loaded and the proper display configuration. I checked the sha256sum of the modules built by the kernel install and the dkms.service and they match. I also checked the selinux contexts of those and they matched. I have done some checking and have yet to determine why dkms feels the need to rebuild the modules. Does the module loading succeed on subsequent boots? -- Fedora Users List - The place to go to get others to do the work for you _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
