Source: blender Followup-For: Bug #939145 On Tue, Jan 14, 2020 at 11:31:20PM +0100, Matteo F. Vescovi wrote: > On 2019-09-06 at 22:40 (-07), Leo L. Schwab wrote: > > Package: blender > > Version: 2.80+dfsg-3+b1 > > Followup-For: Bug #939145 > > > > Dear Maintainer, > > > > This may be related: When attempting to enable OpenCL in the > > preferences, a small panel appears claiming: "No compatible GPUs found > > for path tracing. Cycles will render on the CPU." > > > > I have an NVIDIA GTX-1070Ti with proprietary DKMS drivers > > installed, version 430.40. I also have Darktable installed; > > `darktable-cltest` runs successfully, and (in part) outputs the > > following info: > > > > ``` > > [opencl_init] device 0: GeForce GTX 1070 Ti > > GLOBAL_MEM_SIZE: 8116MB > > MAX_WORK_GROUP_SIZE: 1024 > > MAX_WORK_ITEM_DIMENSIONS: 3 > > MAX_WORK_ITEM_SIZES: [ 1024 1024 64 ] > > DRIVER_VERSION: 430.40 > > DEVICE_VERSION: OpenCL 1.2 CUDA > > ``` > > Ad exposed in #935810, there's no chance for Blender in Debian to use > CUDA support. Sorry. > > Closing. > We're not talking about CUDA; we're talking about OpenCL. I was merely illustrating that 'darktable' has no issue using the OpenCL support on my NVIDIA card. The presence of the word "CUDA" is an artifact of the device version reported by NVIDIA's OpenCL stack.
Schwab -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled