On Mon, 2015-07-13 at 18:38 +0800, Ed Greshko wrote: > On 07/13/15 17:27, Jean Jacques wrote: > > will not generated an module for kernel but works well under 4.0.6 > > > I see you got your answer on the rpmfusion list. > > When you have a problem with akmods you can check > /var/cache/akmods/akmods.log for information about what when wrong. Same thing happened to me. I fixed it by checking the log and rerunning the modulebuild script manually. This was discussed on several recent threads (search for nvidia in the Subject) and is fast becoming a FAQ. The basic issue is that the akmod install script compiles the source module against the new kernel, creating a new rpm. It then tries to install the rpm, but the rpm database is already locked by a different process (presumably the dnf run that called the script in the first place, though I haven't verified this). The rpm install fails but the user isn't told directly, and when he reboots there is no nvidia module available for the new kernel. I suspect that this happens to those of us who run dnf directly from the Shell. I understand that the GUI tool under Gnome reboots into a special image before actually doing the installation, which therefore avoids the problem, but I don't use Gnome or GUI installation tools so this is pure conjecture. poc -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
