I just stumbled about an issue with the blender build provided in the repo-oss on Tumbleweed and cycles.
The cycles render engine can not run on the GPU while the portable version from blender.org can and I wonder if I just missing some additional packages.
Thanks in advance
PS.: I added some images to show the actual issue.
Hi
I would surmise that the portable version has the nvidia blob present, whereas your system does not have the proprietary driver installed, or it is and out of date/not functional…
I do have everything properly installed (I think), the NV dirver is the one from the repos as well.
Without the proprietary NVDirver the portable version would also not being be able to render on the GPUs.
Below you’ll find the nvidia packages I have installed.
That’s why my initial thought was that there is some packages just missing I’m just not aware of being necessary.
Can you show me a list of nv packages you have installed? Maybe that would help me here
Hi
I use the run file(s) to install the nvidia drivers, cuda and cudnn (just libs), if your system is up to date with the 5.2.11 kernel, then the nvidia blobs are out of date…
Whats the different between “updates” and your “kernel/drivers/video”?
So I guess that is the problem and to fix it I would need to install the driver “the hard way” right?
And thank you very much for the time to take a look on this
I’m not sure what this should look like
But it’s the default settings I did not bother with the boot options at all.
I once only upgraded Leap 15.1 to Tumbleweed (and had zero issues and not a single application broken so I assumed everything worked quite well could this be related?)
what exactly do you mean with a test user and how should it look like because if I log in with my normal user which is not very special (afaik I did not set any additional groups) and I wonder how a test user should work in this case?
And do you speaking of CUDA showing up as enabled in Blender or somewhere else?
When people here suggest a test user, they mean a fresh created user that can then be used to check if certain things that are going wrong with an already existing user (who may have a long histoty of creating and changing configuration files in his home directory) are going wrong in the same way with that fresh (without the long hostory of configuration files over maybe several levels of the operating system, the desktop in use and/or the application going wrong) user.
Thus you only have to use YaST > Security and users > Users and Groups and create a new user there wthout much whistles and bells. Then use that user to test what happens when you try to recreate your problem. After the test, you can again remove that test user from the system.
I created a new user and experienced the same issue
Furthermore I tested the whole thing on my 2nd Tumbleweed machine and also there I am not able to use the GPUs to render with the repo build but with the portable version from the website it works.
Hi,
The blender in the opensuse repos will only use the gpu in rendering
if you compile cuda. You can download the cuda from nvidia.
just read the instructions and all will be fine. If you encounter problem
please post and I’m guessing malcolmlewis will surely help. He helped me
a lot in the past
Is there no way to get it work without compiling CUDA on my own? SInce on any GPU driver or Kernel update I’ll need to recompile it right? Which could be a bit annoying on Tumbleweed