Possibly, since all three functions are exported as GPL-only. I’m pretty sure, yes, proprietary modules cannot use GPL-only symbols, and since 5.9 the “proprietary taint” is inherited by any module that uses symbols from proprietary modules. nvidia_uvm (Dual MIT/GPL license) uses symbols from nvidia (“NVIDIA” license), thus nvidia_uvm inherits “proprietary taint” from nvidia, thus it won’t be able to use GPL-only symbols, but it tries to, therefore it fails to load.
You can remove the taint inheritance part from the kernel. I’m interested in seeing what Manjaro developers do: patch the kernel or wait until Nvidia figures something out.
You can use that for sure on your private machine, however as distribution we can’t revert such things. We have to follow upstream decisions closely, not to break any laws.
If this is something that can’t/doesn’t get patched upstream could you create a tutorial thread? Would help a lot of people and stop the forums getting spammed with the same issue
Where is this point of view coming from? What you are saying is just contradicting the GPL2:
Let me quote it:
We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.
You may modify your copy or copies of the Program or any portion of it…
and so forth. The GPL2 is very clear. You have all rights to change the source and distribute it.
I am really concerned that the result of this FUD campaign is that you do not dare to patch the source code. The GPL2 is giving you all the rights to do so.
Who told you that you are not allowed to change certain parts of the source code? You are allowed to patch anything as long as the resulting source code is under GPL2 license
#Solved#
hi everybody,
I have just installed the 5.11 kernel version and still my opencl does not work in darktable
is this normal?
in advance, thank you for your help