Tested with sys-kernel/gentoo-sources-4.10.0 during QA prior to starting on the sys-kernel/ck-sources-4.10.0 version bump. I'm assuming any 4.10.x kernel is affected by this issue, though can't be certain. Reproducible: Always Steps to Reproduce: 1. install a 4.10.x kernel 2. set the symlink for the new kernel 3. emerge @module-rebuild Actual Results: emerge failure on the package: x11-drivers/nvidia-drivers-375.39 Expected Results: x11-drivers/nvidia-drivers-375.39 video driver should be installed over in #ck the ck-patches author managed to come up with a fix for building the driver in question. I did the following to get it working: 1. install 4.10.0 kernel source tree as per usual (and set symlink, etc.) 2. ebuild `equery which =x11-drivers/nvidia-drivers-375.39::gentoo` unpack 3. apply the patch manually 4. ebuild `equery which =x11-drivers/nvidia-drivers-375.39::gentoo` merge 5. file a bug about it, and include a link for the patch http://ck.kolivas.org/patches/4.0/4.10/nvidia-375.39-linux-4.10.patch
Created attachment 464394 [details] emerge -pqv && emerge --info (and build log) Already included a patch which fixes the issue, but went ahead and provided some logs and info.
Just confirming - and thank you for the link to the patch.
thank you! the patch also applies fine with x11-drivers/nvidia-drivers-378.13 (epatch_user).
Obviously we have to do this with every new kernel branch release. The answer is always the same.
*** Bug 610110 has been marked as a duplicate of this bug. ***
*** Bug 610776 has been marked as a duplicate of this bug. ***
*** Bug 610812 has been marked as a duplicate of this bug. ***
*** Bug 610832 has been marked as a duplicate of this bug. ***
*** Bug 611474 has been marked as a duplicate of this bug. ***
*** Bug 610614 has been marked as a duplicate of this bug. ***
For anyone who doesn't know: /etc/portage/patches/x11-drivers/nvidia-drivers-375.39 ^ you can just drop the patch in there instead of manually applying the patch. (Like until upstream releases a new version of the driver to support 4.10)
*** Bug 614014 has been marked as a duplicate of this bug. ***
*** Bug 613884 has been marked as a duplicate of this bug. ***
*** Bug 614406 has been marked as a duplicate of this bug. ***