NVIDIA on slackware 14.1...need help

55020 · 02-08-2014, 06:14 AM

Code:

-MODULE_LICENSE("NVIDIA");
+MODULE_LICENSE("GPL");

Wow. I don't know who would be more angry about this blatant act of copyright infringement - nVidia, or the thousands of kernel contributors.

And at the end of the day, all that patch does is prevent the kernel's taint flag from being set. It won't fix any build problems at all.

LightStar · 02-08-2014, 06:35 AM

Quote:

Originally Posted by 55020

Code:

-MODULE_LICENSE("NVIDIA");
+MODULE_LICENSE("GPL");

Wow. I don't know who would be more angry about this blatant act of copyright infringement - nVidia, or the thousands of kernel contributors.

And at the end of the day, all that patch does is prevent the kernel's taint flag from being set. It won't fix any build problems at all.

But it fixed. No more "FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 'mutex_lock_nested'" error for me

55020 · 02-08-2014, 06:47 AM

Quote:

Originally Posted by LightStar

But it fixed. No more "FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 'mutex_lock_nested'" error for me

That's not a build problem. That's working as designed.

If nVidia wants to put its hand in the GPL cookie-jar...

ReaperX7 · 02-08-2014, 04:53 PM

It's a dirty fix regardless. That's a fix better suited for developers only, testers, and such crowds, not end users.

It is nothing more than a kernel license lockout avoidance, not a fix. That feature that is disabled is only a kernel feature used by debugging and developments. You gain no benefit from applying that except extra debugging.

LightStar · 02-09-2014, 12:02 AM

You are right indeed. But can't find any other solution yet. Nvidia kernel driver 331.20 won't build for 3.12 kernel otherwise.

guanx · 02-09-2014, 03:27 AM

Quote:

Originally Posted by LightStar

...
Nvidia kernel driver 331.20 won't build for 3.12 kernel otherwise.

How did you come to this conclusion? No one else have this problem. Besides, is there any reason to not use v331.38 or later drivers?

LightStar · 02-09-2014, 03:48 AM

Well, topic starter had this problem (and by the way he tried to build newer version 331.38). I had it too and just posted my solution because didn't seen any other solution in this thread which is working (other then using stock 3.10.17 kernel, which is in fact no solution at all). If you have any other idea how to solve it - just post it please.

LightStar · 02-09-2014, 04:15 AM

But sorry, didn't tried "disable lock debugging" thing yet. Will do it when have time.