https://devtalk.nvidia.com/default/topic/628864/num_physpages-and-support-for-3-11-and-later-kernels/?offset=1 This is workaround problem with alocating memory with >3.10 kernels and nvidia. This does not solve any problem but its temp fix from upstreem and have restrictions.
While I'd like to see the nvidia driver to catch up with the recent kernel development, the provided patch is not an official release by nvidia. Hence, this bug is a duplicate (don't have the bug ID at hand). I think, a dependency constraint on the kernel packages >=3.10 when nvidia-drivers are installed would be an appropriate temporary solution to this issue.
(In reply to Tolga Dalman from comment #1) > While I'd like to see the nvidia driver to catch up with the recent kernel > development, the provided patch is not an official release by nvidia. The patch is mentioned to be official in the post itself and the claim is made that (limited) support is provided; since Daniel Dadap is a Software Engineer at NVIDIA and not just a moderator, the statement can also be held as official. The patch is also mentioned to become part of future releases.
(In reply to Tom Wijsman (TomWij) from comment #2) > The patch is mentioned to be official in the post itself and the claim is > made that (limited) support is provided; since Daniel Dadap is a Software > Engineer at NVIDIA and not just a moderator, the statement can also be held > as official. I know. But since this patch is not even considered a beta, that circumstance should be reflected in the gentoo ebuild as well. For example, by adding an 'experimental' use flag, or a package mask. > The patch is also mentioned to become part of future releases. Yes, and I'm eagerly waiting for it. If an experimental nvidia-drivers package is provided in the portage tree beforehand, I will, of course, test and report :)
What are you still talking about? 304.116 and 331.20 came out today and have support for 3.12. And I checked 173.14.38 again (which already supported 3.11) and it's fine for 3.12, too. *** This bug has been marked as a duplicate of bug 447566 ***
