Bonjour,
I am wondering why fedora packagers limit the capabilities of softwares:
I installed blender from fedora repo (f34) version 2.93.5. It is impossible to enable the graphical acceleration of my graphic card (nvidia GeForce GTX 1050 Ti).
I went to blender official site and got the same version of blender and.... graphical acceleration is set without any problem.
Why this difference?
Thank you.
On Wed, 2021-10-20 at 10:26 +0200, François Patte wrote:
Bonjour,
I am wondering why fedora packagers limit the capabilities of softwares:
I installed blender from fedora repo (f34) version 2.93.5. It is impossible to enable the graphical acceleration of my graphic card (nvidia GeForce GTX 1050 Ti).
I went to blender official site and got the same version of blender and.... graphical acceleration is set without any problem.
Why this difference?
Which Nvidia driver are you using? The Nouveau driver almost certainly doesn't support this feature. The non-free binary Nvidia one might do so (I haven't checked) but that's not an official Fedora package. You need to get it from RPMfusion.
poc
Le 2021-10-20 11:37, Patrick O'Callaghan a écrit :
On Wed, 2021-10-20 at 10:26 +0200, François Patte wrote:
Bonjour,
I am wondering why fedora packagers limit the capabilities of softwares:
I installed blender from fedora repo (f34) version 2.93.5. It is impossible to enable the graphical acceleration of my graphic card (nvidia GeForce GTX 1050 Ti).
I went to blender official site and got the same version of blender and.... graphical acceleration is set without any problem.
Why this difference?
Which Nvidia driver are you using? The Nouveau driver almost certainly doesn't support this feature. The non-free binary Nvidia one might do so (I haven't checked) but that's not an official Fedora package. You need to get it from RPMfusion.
I use nvidia driver from rpmfusion and this feature is enabled when I use blender from blender site but not from /pub/linux/fedora/linux/updates/34/Everything/x86_64/Packages/
on fedora mirrors.
On 20/10/2021 11:12, François Patte wrote:
Le 2021-10-20 11:37, Patrick O'Callaghan a écrit :
On Wed, 2021-10-20 at 10:26 +0200, François Patte wrote:
Bonjour,
I am wondering why fedora packagers limit the capabilities of softwares:
I installed blender from fedora repo (f34) version 2.93.5. It is impossible to enable the graphical acceleration of my graphic card (nvidia GeForce GTX 1050 Ti).
I went to blender official site and got the same version of blender and.... graphical acceleration is set without any problem.
Why this difference?
Which Nvidia driver are you using? The Nouveau driver almost certainly doesn't support this feature. The non-free binary Nvidia one might do so (I haven't checked) but that's not an official Fedora package. You need to get it from RPMfusion.
I use nvidia driver from rpmfusion and this feature is enabled when I use blender from blender site but not from /pub/linux/fedora/linux/updates/34/Everything/x86_64/Packages/
on fedora mirrors.
I posted recently on the rpmfusion list about using nvidia-settings in KDE plasma under Wayland and X11. X11 seems largely ok; Wayland says it can't find the display, but then still uses it.
I later found a thread on a similar topic on this list. Doesn't explain the difference you see between the two builds of blender but might be related.
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/...
John P
On Wed, 2021-10-20 at 11:38 +0100, John Pilkington wrote:
On 20/10/2021 11:12, François Patte wrote:
Le 2021-10-20 11:37, Patrick O'Callaghan a écrit :
On Wed, 2021-10-20 at 10:26 +0200, François Patte wrote:
Bonjour,
I am wondering why fedora packagers limit the capabilities of softwares:
I installed blender from fedora repo (f34) version 2.93.5. It is impossible to enable the graphical acceleration of my graphic card (nvidia GeForce GTX 1050 Ti).
I went to blender official site and got the same version of blender and.... graphical acceleration is set without any problem.
Why this difference?
Which Nvidia driver are you using? The Nouveau driver almost certainly doesn't support this feature. The non-free binary Nvidia one might do so (I haven't checked) but that's not an official Fedora package. You need to get it from RPMfusion.
I use nvidia driver from rpmfusion and this feature is enabled when I use blender from blender site but not from /pub/linux/fedora/linux/updates/34/Everything/x86_64/Packages/
on fedora mirrors.
I posted recently on the rpmfusion list about using nvidia-settings in KDE plasma under Wayland and X11. X11 seems largely ok; Wayland says it can't find the display, but then still uses it.
I later found a thread on a similar topic on this list. Doesn't explain the difference you see between the two builds of blender but might be related.
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/...
That was me, with feedback from Ed. I now have no issues running Nvidia under KDE/X11 (not using Wayland until other stuff is fixed, such as session saving), but as I said I don't use Blender.
poc
On 20/10/2021 17:37, Patrick O'Callaghan wrote:
On Wed, 2021-10-20 at 10:26 +0200, François Patte wrote:
Bonjour,
I am wondering why fedora packagers limit the capabilities of softwares:
I installed blender from fedora repo (f34) version 2.93.5. It is impossible to enable the graphical acceleration of my graphic card (nvidia GeForce GTX 1050 Ti).
I went to blender official site and got the same version of blender and.... graphical acceleration is set without any problem.
Why this difference?
Which Nvidia driver are you using? The Nouveau driver almost certainly doesn't support this feature. The non-free binary Nvidia one might do so (I haven't checked) but that's not an official Fedora package. You need to get it from RPMfusion.
I can confirm the experience of the OP.
I'm using the rpmfusion nvidia packages which includes
xorg-x11-drv-nvidia-cuda-470.74-1.fc34.x86_64
The blender from the fedora repos doesn't detect a capable GPU. But blender downloaded from the blender site does.
It shows:
CUDA - NVIDIA Geforce GTX 660(Display)
-- On Facebook it is called Vaguebooking.
On Wed, 2021-10-20 at 18:17 +0800, Ed Greshko wrote:
On 20/10/2021 17:37, Patrick O'Callaghan wrote:
On Wed, 2021-10-20 at 10:26 +0200, François Patte wrote:
Bonjour,
I am wondering why fedora packagers limit the capabilities of softwares:
I installed blender from fedora repo (f34) version 2.93.5. It is impossible to enable the graphical acceleration of my graphic card (nvidia GeForce GTX 1050 Ti).
I went to blender official site and got the same version of blender and.... graphical acceleration is set without any problem.
Why this difference?
Which Nvidia driver are you using? The Nouveau driver almost certainly doesn't support this feature. The non-free binary Nvidia one might do so (I haven't checked) but that's not an official Fedora package. You need to get it from RPMfusion.
I can confirm the experience of the OP.
I'm using the rpmfusion nvidia packages which includes
xorg-x11-drv-nvidia-cuda-470.74-1.fc34.x86_64
The blender from the fedora repos doesn't detect a capable GPU. But blender downloaded from the blender site does.
It shows:
CUDA - NVIDIA Geforce GTX 660(Display)
Yes, my nvidia-settings does show CUDA cores so it looks like a packaging issue for blender.
poc
On Wed, 20 Oct 2021 at 05:26, François Patte < francois.patte@mi.parisdescartes.fr> wrote:
Bonjour,
I am wondering why fedora packagers limit the capabilities of softwares:
I installed blender from fedora repo (f34) version 2.93.5. It is impossible to enable the graphical acceleration of my graphic card (nvidia GeForce GTX 1050 Ti).
I went to blender official site and got the same version of blender and.... graphical acceleration is set without any problem.
Why this difference?
Distribution packages for complex software often use a basic configuration that lacks some of the features needed for some use cases. I use remote sensing software from NASA and ESA. These include versions of 3rd party software configured to the requirements of the applications because they can't assume the distro packages will work. In some cases, features involve licenses or export restrictions that prevent including in a distro package, but enabling fewer features also minimizes bloat with features many users don't need.
On 10/20/21 01:26, François Patte wrote:
Why this difference?
As Ed and Patrick point out, the difference is probably CUDA. The CUDA client libraries are not licensed appropriately for redistribution, therefore they are not packaged in Fedora. And since they aren't packaged, they aren't available in the build root, and it isn't possible to build software that uses CUDA.
You could ask NVidia to re-license the CUDA libraries, or you could ask Blender developers if they'd consider an OpenCL implementation, since OpenCL does appear to be supported in Fedora. Or, as you've done, you can use the not-entirely-Free release that Blender publishes. I'd imagine you could get it from Flathub, too.
On Wed, Oct 20, 2021 at 10:13 AM Gordon Messmer gordon.messmer@gmail.com wrote:
On 10/20/21 01:26, François Patte wrote:
Why this difference?
As Ed and Patrick point out, the difference is probably CUDA. The CUDA client libraries are not licensed appropriately for redistribution, therefore they are not packaged in Fedora. And since they aren't packaged, they aren't available in the build root, and it isn't possible to build software that uses CUDA.
This is not technically true but may be practically true, my google search was not conclusive.
It looks like Blender has a build time option to dynamically load (i.e., dlopen) the cuda library but the first link was from 2018 and said that it crashed blender. I would hope this has been fixed by now but I didn't look any further.
Searching the blender spec file[1] I don't see any reference to the dynaload option but I'm not sure if it's on or off by default.
Thanks, Richard
[1] https://src.fedoraproject.org/rpms/blender/blob/rawhide/f/blender.spec
On 10/20/21 08:32, Richard Shaw wrote:
As Ed and Patrick point out, the difference is probably CUDA. The CUDA client libraries are not licensed appropriately for redistribution, therefore they are not packaged in Fedora. And since they aren't packaged, they aren't available in the build root, and it isn't possible to build software that uses CUDA.
This is not technically true but may be practically true, my google search was not conclusive.
It looks like Blender has a build time option to dynamically load (i.e., dlopen) the cuda library
As far as I can tell, the CUDA libraries must be present in the build environment in order to build that support:
On 10/20/21 19:08, Gordon Messmer wrote:
It looks like Blender has a build time option to dynamically load (i.e., dlopen) the cuda library
As far as I can tell, the CUDA libraries must be present in the build environment in order to build that support:
Though I could be wrong... there are some hints in the build log that CUDA support is being built (including -DWITH_CUDA -DWITH_CUDA_DYNLOAD in some build arguments):
https://kojipkgs.fedoraproject.org//packages/blender/2.93.5/1.fc36/data/logs...