Repositoreis: Blender and Cycles

Hello everybody,

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 :slight_smile:

PS.: I added some images to show the actual issue.

Installed blender packages:
https://i.imgur.com/eMCV7kp.png

System preferences window of the portable blender version:
https://i.imgur.com/pVUNoE0.png

And the same window from the repo build:
https://i.imgur.com/5zyAoV0.png

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…

Here is mine at present;

Screenshot from 2019-09-05 16-46-12.png

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.

https://i.imgur.com/YKsa5Wg.png

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 :slight_smile:

Thanks in advance :slight_smile:

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… :wink:


pinxi -GxxSaz

System:    Host: grover Kernel: 5.2.11-1-default x86_64 bits: 64 compiler: gcc v: 9.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.2.11-1-default root=UUID=01c3dc8a-0bae-468a-8acf-08bf697ce6df splash=silent 
           scsi_mod.use_blk_mq=1 intel_iommu=on ipv6.disable=1 quiet loglevel=4 systemd.show_status=auto 
           Desktop: Gnome 3.32.2 wm: gnome-shell dm: GDM Distro: openSUSE Tumbleweed 20190904 
Graphics:  Device-1: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:016a 
           Device-2: NVIDIA GK208B [GeForce GT 710] vendor: ZOTAC driver: nvidia v: 435.21 bus ID: 01:00.0 chip ID: 10de:128b 
           Device-3: NVIDIA GK208B [GeForce GT 710] vendor: ZOTAC driver: nvidia v: 435.21 bus ID: 02:00.0 chip ID: 10de:128b 
           Device-4: NVIDIA GK208B [GeForce GT 710] vendor: ZOTAC driver: nvidia v: 435.21 bus ID: 03:00.0 chip ID: 10de:128b 
           Display: x11 server: X.Org 1.20.5 driver: fbdev,modesetting,nvidia,vesa alternate: nouveau,nv 
           compositor: gnome-shell resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce GT 710/PCIe/SSE2 v: 4.6.0 NVIDIA 435.21 direct render: Yes 

If you run;


/sbin/modinfo nvidia | grep filename

filename:       /lib/modules/5.2.11-1-default/kernel/drivers/video/nvidia.ko

Does it show up in weak-updates?

Hey ho :slight_smile:

Okay, here is my the output of inxi -GxxSaz:

System:    Host: Z004 Kernel: 5.2.11-1-default x86_64 bits: 64 compiler: gcc v: 9.2.1 Desktop: KDE Plasma 5.16.4 tk: Qt 5.13.0 
           wm: kwin_x11 dm: GDM, SDDM Distro: openSUSE Tumbleweed 20190904 
Graphics:  Device-1: NVIDIA GP104 [GeForce GTX 1080] driver: nvidia v: 435.21 bus ID: 23:00.0 chip ID: 10de:1b80 
           Device-2: NVIDIA GP104 [GeForce GTX 1080] driver: nvidia v: 435.21 bus ID: 24:00.0 chip ID: 10de:1b80 
           Display: x11 server: X.Org 1.20.5 driver: none unloaded: fbdev,modesetting,nouveau,nv,nvidia,vesa 
           compositor: kwin_x11 resolution: 1920x1080~60Hz, 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 1080/PCIe/SSE2 v: 4.6.0 NVIDIA 435.21 direct render: Yes 


And the nvidia module

/sbin/modinfo nvidia | grep filename
filename:       /lib/modules/5.2.11-1-default/updates/nvidia.ko

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? :smiley:

And thank you very much for the time to take a look on this :slight_smile:

Hi
Well your driver looks ok, I’m guessing dracut did it’s thing in the background…

I think this is the possible issue;


My System:
Display: x11 server: X.Org 1.20.5 driver: fbdev,modesetting,nvidia,vesa alternate: nouveau,nv

Your System:
Display: x11 server: X.Org 1.20.5 driver: none unloaded: fbdev,modesetting,nouveau,nv,nvidia,vesa

You didn’t boot with nomodeset? or is it in the kernel boot options?


cat /etc/default/grub | grep GRUB_CMDLINE_LINUX_DEFAULT

Hey there,

yes I was wondering about the “driver” part too.

Here is the output from the GRUB_CMDLINE_LINUX_DEFAULT

cat /etc/default/grub | grep GRUB_CMDLINE_LINUX_DEFAULT
GRUB_CMDLINE_LINUX_DEFAULT="splash=silent resume=/dev/disk/by-id/ata-WDC_WDS100T1B0A-00H9H0_164710803211-part2 quiet mitigations=auto"

I’m not sure what this should look like :smiley:
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?) :slight_smile:

Kind regards,
Vortex

Hi
Well that looks fine, can you post the output from;


/sbin/lspci -nnk | egrep -A3 "VGA|Display|3D"

Heye there,

of course I can :smiley:

/sbin/lspci -nnk | egrep -A3 "VGA|Display|3D"
23:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1)
        Subsystem: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80]
        Kernel driver in use: nvidia
        Kernel modules: nouveau, nvidia_drm, nvidia
--
24:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1)
        Subsystem: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80]
        Kernel driver in use: nvidia
        Kernel modules: nouveau, nvidia_drm, nvidia


Thank you :slight_smile:

Hi
All very strange, ok so if you create a test user and login, does cuda show as enabled for this user?

Hey there,

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? :slight_smile:
And do you speaking of CUDA showing up as enabled in Blender or somewhere else?

Thank you in advance :slight_smile:

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.

Hey everybody,

thanks for all your help :slight_smile:

I created a new user and experienced the same issue :frowning:

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.

Here’s what the 2nd machine looks like:


inxi -GxxSaz
System:    Host: Z003 Kernel: 5.2.11-1-default x86_64 bits: 64 compiler: gcc v: 9.2.1 Desktop: KDE Plasma 5.16.5 tk: Qt 5.13.1 
           wm: kwin_x11 dm: GDM, SDDM Distro: openSUSE Tumbleweed 20190909 
Graphics:  Device-1: NVIDIA GM204 [GeForce GTX 970] vendor: ZOTAC driver: nvidia v: 435.21 bus ID: 01:00.0 chip ID: 10de:13c2 
           Device-2: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: ZOTAC driver: nvidia v: 435.21 bus ID: 02:00.0 
           chip ID: 10de:1c03 
           Display: x11 server: X.Org 1.20.5 driver: none unloaded: nvidia compositor: kwin_x11 resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 435.21 direct render: Yes


/sbin/modinfo nvidia | grep filename
filename:       /lib/modules/5.2.11-1-default/updates/nvidia.ko


cat /etc/default/grub | grep GRUB_CMDLINE_LINUX_DEFAULT
GRUB_CMDLINE_LINUX_DEFAULT="resume=/dev/disk/by-uuid/4a5e7d4e-1807-4056-899c-5a35bdf7f57e splash=silent quiet showopts"


/sbin/lspci -nnk | egrep -A3 "VGA|Display|3D"
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1)
        Subsystem: ZOTAC International (MCO) Ltd. Device [19da:1366]
        Kernel driver in use: nvidia
        Kernel modules: nouveau, nvidia_drm, nvidia
--
02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1)
        Subsystem: ZOTAC International (MCO) Ltd. Device [19da:1438]
        Kernel driver in use: nvidia
        Kernel modules: nouveau, nvidia_drm, nvidia

Also on that machine a new user wasn’t able to do so. :confused:

Thank you all for your help :slight_smile:

Any further suggestions?

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 :slight_smile:

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 :smiley:

Hi
No, that’s not necessary, install without the driver (or gcc check) and use the openSUSE version, or the hardway (my preferred way :wink: )

For example;


./cuda_10.1.243_418.87.00_linux.run --override