See Pascal's email (23 January):
===
Just in case you have the same problem it can same you some time.
On Debian/sid the Nvidia version 346.96 and now 349.16 are broken as
the uvm module cannot be loaded. This breaks darktable OpenCL support.
I have filed an issue here:
https://bugs.debian.org/c
Am 28.01.2016 um 22:12 schrieb David Vincent-Jones:
> Kofa; thanks for that reference: from your material it looks like I am
> missing 'nvidia-331' and 'nvidia-331-uvm' but everything else on your list
> looks to be in place.
>
> Debian offers kernel 340.96 now can I assume that does not
Kofa; thanks for that reference: from your material it looks like I am
missing 'nvidia-331' and 'nvidia-331-uvm' but everything else on your
list looks to be in place.
Debian offers kernel 340.96 now can I assume that does not create
problems?
David
On 28/01/16 07:57 PM, KOVÁCS Istvá
Hi David,
darktable only needs to find one of those. As naming conventions varied
a bit between distributions we check this list of options. The first one
that is found will be used. If darktable still is not able to use OpenCL
there must be another reason.
Ulrich
Am 28.01.2016 um 10:29 schri
In case you haven't read it, check out
http://tech.kovacs-telekes.org/2014-07-29-darktable-opencl-nvidia-ubuntu-1404-mint-17
Kofa
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM +
Yes. From libOpenCl.so to libOpenCl.so.1
Thanks
On Thu, 28 Jan 2016 20:42 Oliver Bedford wrote:
> Hi!
>
> > Dave proposed a symlink from libOpenCL.so.1 to libOpenCL.so but I
> have
> > no idea where to place the link . my darktable is located in a
> > ~/darktable directory.
>
> Shouldn't it
Hi!
> Dave proposed a symlink from libOpenCL.so.1 to libOpenCL.so but I
have
> no idea where to place the link . my darktable is located in a
> ~/darktable directory.
Shouldn't it be the other way around?
ojo@apollo:~$ ll /usr/lib/x86_64-linux-gnu/libOpenCL*
lrwxrwxrwx 1 root root14 Ap
Hi Paul; yes nvidia-modprobe is showing as installed.
Dave proposed a symlink from libOpenCL.so.1 to libOpenCL.so but I have
no idea where to place the link . my darktable is located in a
~/darktable directory.
David
On 28/01/16 01:35 PM, J. Paul Bissonnette wrote:
> On Thu, 28 Jan 2016 10
On Thu, 28 Jan 2016 10:29:55 +0100
David Vincent-Jones wrote:
> I am trying to install OpenCL on Debian Jessie with a Nvidia chipset.
>
> I have installed: nvidia-libopencl1, nvidia-opencl-icd and
> opencl-headers based on a web instruction.
>
> When I run dt it finds libOpenCL.so.1 but does N
A suggestion only :
Create a symlink from libOpenCl.so.1 to libOpenCl.so.
This has worked for me many times before with other libraries. It's also
easy to reverse.
On my phone so I cannot easily provide an example.
Regards
Dave
On Thu, 28 Jan 2016 11:31 David Vincent-Jones wrote:
> I am trying
I am trying to install OpenCL on Debian Jessie with a Nvidia chipset.
I have installed: nvidia-libopencl1, nvidia-opencl-icd and
opencl-headers based on a web instruction.
When I run dt it finds libOpenCL.so.1 but does NOT FIND libOpenCL nor
libOpenCL.so
I would appreciate if somebody with sim
Hi,
I just merged my OpenCL implementation of the Markesteijn demosaicing
algorithm into master. Markesteijn with one or three passes ("-1" and
"-3", respectively) is darktable's preferred method for demosaicing
images of cameras with Fuji's X-Trans sensor.
The algorithm is rather complex and
I think there's a bug with AMD Catalyst over Ubuntu 15.10.
When I turn OpenCL on, even the exported image shows errors.
Here's the exported image:
https://www.flickr.com/photos/andrefelipecarvalho/23015821693/in/dateposted-public/
--
André Felipe
https://www.flickr.com/photos/andrefelipeca
Thanks for sharing your experience Phil. The "dnf install mesa-libOpenCL
clinfo" was also what got things working for me as well.
I'll be doing a fresh Fedora install soon. Now we just have to wait and
see if it survives a kernel update ;)
On 01/12/15 01:58 PM, Phil Evans wrote:
Hi, thanks
Il 01/12/2015 21:29, Brandt, Riley ha scritto:
>
> So for a new Fedora install, assuming the driver install worked
> properly, a user would really only need to:
>
> Enable the RPMFusion repos
> # dnf install akmod-nvidia "kernel-devel-uname-r == $(uname -r)"
> # dnf update -y
> reboot
> # dnf insta
Hi, thanks again for your work on this Germano and Riley. I have just
completed a clean install of fedora 23 on to a test hard drive. Updated
fedora. I then followed your steps of adding rpm fusion free and non free.
Updated. Installed the akmod nvidia and kernel devel packages. Updated.
Rebooted.
So for a new Fedora install, assuming the driver install worked
properly, a user would really only need to:
Enable the RPMFusion repos
# dnf install akmod-nvidia "kernel-devel-uname-r == $(uname -r)"
# dnf update -y
reboot
# dnf install xorg-x11-drv-nvidia-cuda
Correct? With the possible add
Il 01/12/2015 20:12, Phil Evans ha scritto:
> Hi, I have been following the thread with interest and would like to
> thank everyone for the testing and work that has gone into the
> positive result.
> I will do a clean install on a test drive and hope this works with my
> rigg. I agree it is much b
Il 01/12/2015 19:43, Brandt, Riley ha scritto:
>
> It works! Thank you so much:)
>
> I am going to install Fedora as my main OS now that I have finished
> testing it on an old hard drive.
>
You see? We managed to solve the problem :-)
I would like to thank also Nicolas Chauvet from #rpmfusion that
Hi, I have been following the thread with interest and would like to
thank everyone for the testing and work that has gone into the positive
result.
I will do a clean install on a test drive and hope this works with my
rigg. I agree it is much better to use the nvidia driver from rpmfusion
than the
My response with all the output is being held because it is too long.
The good news is, it works!! I really appreciate all the help :)
I wanted to confirm the correct steps for when I do a fresh install of
Fedora. Would it be like this?
Enable the RPMFusion repos
# dnf install akmod-nvidia "
Ok now
# updatedb
and show output of
# locate libOpenCL
$ darktable-cltest
--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in t
OK, the output of clinfo is:
Number of platforms 2
Platform Name NVIDIA CUDA
Platform Vendor NVIDIA Corporation
Platform VersionOpenCL 1.2 CUDA 7.5.0
Platform
# dnf install mesa-libOpenCL clinfo
reboot and show the output of
# clinfo
--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in th
Thanks for all your help so far!
/usr/lib64/nvidia
├── alternate-install-present
├── libcuda.so -> libcuda.so.358.16
├── libcuda.so.1 -> libcuda.so.358.16
├── libcuda.so.358.16
├── libEGL_nvidia.so.0
├── libEGL.so.1
├── libGLdispatch.so.0
├── libGLESv1_CM.so.1 -> libGLESv1_CM.so.358.16
├── lib
We are going to fix... We need only a few steps. Show the output of
# tree /usr/lib64/nvidia*
--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use
After running # updatedb, I ran #locate libOpenCL but nothing comes up.
No libOpenCL :(
On 2015-12-01 08:19, Germano Massullo wrote:
> # updatedb # locate libOpenCL
--
Go from Idea to Many App Stores Faster with Int
# updatedb
# locate libOpenCL
--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Everything is fine. Show us the complete output of
$ darktable-cltest
--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this al
[opencl_init] opencl related configuration options:
[opencl_init]
[opencl_init] opencl: 1
[opencl_init] opencl_library: ''
[opencl_init] opencl_memory_requirement: 768
[opencl_init] opencl_memory_headroom: 300
[opencl_init] opencl_device_priority: '*/!0,*/*/*'
[opencl_init] opencl_size_roundup:
LSMOD | GREP NVIDIA
nvidia_uvm 90112 0
nvidia_modeset716800 4
nvidia 8749056 79 nvidia_modeset,nvidia_uvm
drm 335872 4 nvidia
RPM -QA *NVIDIA* | SORT
akmod-nvidia-358.16-1.fc23.x86_64
kmod-nvidia-4.2.6-301.fc23.x86_64-358.16-1.fc23.x8
2015-12-01 15:45 GMT+01:00 Brandt, Riley :
>
> That would be great. One user mentioned they had success after installing:
>
> mesa-libOpenCL opencl-filesystem.noarch opencl-utils.x86_64
> opencl-headers.noarch mesa-libOpenCL.i686 opencl-utils.i686
> gromacs-opencl.x86_64
>
> Maybe this is what is
That would be great. One user mentioned they had success after
installing:
mesa-libOpenCL opencl-filesystem.noarch opencl-utils.x86_64
opencl-headers.noarch mesa-libOpenCL.i686 opencl-utils.i686
gromacs-opencl.x86_64
Maybe this is what is missing.
On 2015-12-01 04:26, Germano Massullo wrot
Hi, so after # dnf install xorg-x11-drv-nvidia-cuda, there was no
nvidia-uvm, so I ran # modprobe nvidia-uvm. Still no opencl. Here is the
output from darktable-cltest:
[opencl_init] opencl related configuration options:
[opencl_init]
[opencl_init] opencl: 1
[opencl_init] opencl_library: ''
[
Next days you should see an updated version of the guide [1] with all
instructions for OpenCL (nVidia) on Fedora systems
[1]: https://www.darktable.org/usermanual/ch09s02s04.html.php
--
Go from Idea to Many App Stores Fast
# dnf install xorg-x11-drv-nvidia-cuda
# lsmod | grep nvidia
if there is *not* nvidia-uvm, do: (it's a SELinux problem that we will fix
later, don't worry)
# modprobe nvidia-uvm
then show us
$ darktable-cltest
--
Go from Id
On Mon, 30 Nov 2015 16:32:33 -0700
"Brandt, Riley" wrote:
>
>
>I ran all the commands and rebooted. Still no OpenCL in darktable.
>Here is the updated output:
>
>LSMOD | GREP NVIDIA
>
I am no Fedora expert, but both in Ubuntu and Archlinux, I have to
also install the CUDAs packages to make op
?
*From:* "Brandt, Riley"
*To:* Germano Massullo
*Cc:* Darktable-users
*Sent:* Monday, November 30, 2015 3:32 PM
*Subject:* Re: [Darktable-users] OpenCL in Fedora with Nvidia?
I ran all the commands and rebooted. Still no
rpmfusion-free-updates-testing RPM Fusion for Fedor enabled:
230Do you want this enabled?
From: "Brandt, Riley"
To: Germano Massullo
Cc: Darktable-users
Sent: Monday, November 30, 2015 3:32 PM
Subject: Re: [Darktable-users] OpenCL in Fedora with Nvidia?
I tried running #modprobe nvidia-uvm but still no luck. My output from #
darktable -d opencl:
[opencl_init] opencl related configuration options:
[opencl_init]
[opencl_init] opencl: 1
[opencl_init] opencl_library: ''
[opencl_init] opencl_memory_requirement: 768
[opencl_init] opencl_memory_hea
I ran all the commands and rebooted. Still no OpenCL in darktable. Here
is the updated output:
LSMOD | GREP NVIDIA
nvidia_modeset716800 3
nvidia 8749056 61 nvidia_modeset
drm 335872 4 nvidia
DNF REPOLIST ALL
repo id
Il 01/12/2015 00:24, Brandt, Riley ha scritto:
>
> Thanks. I will disable the 3rd party repos and try again..
>
> I originally installed the drivers from RPMFusion following the
> instructions here: http://rpmfusion.org/Howto/nVidia
>
> But OpenCL didn't work. I'll try your method now.
>
If my meth
Thanks. I will disable the 3rd party repos and try again..
I originally installed the drivers from RPMFusion following the
instructions here: http://rpmfusion.org/Howto/nVidia
But OpenCL didn't work. I'll try your method now.
On 2015-11-30 15:56, Germano Massullo wrote:
> Il 30/11/2015 2
okay you messed up with third party (crap) repositories. When you have
Fedora and RPMFusion enabled, you usually never need other repos.
# dnf config-manager --set-disabled negativo17 - Nvidia
# dnf config-manager --set-disabled fedora-nvidia
# dnf config-manager --set-disabled fedora-nvidia-source
Il 30/11/2015 23:55, Germano Massullo ha scritto:
> okay you messed up with third party (crap) repositories. When you have
> Fedora and RPMFusion enabled, you usually never need other repos.
> # dnf config-manager --set-disabled negativo17 - Nvidia
> # dnf config-manager --set-disabled fedora-nvidi
The nvidia-modprobe package comes from the Negativo17 repo I believe. If
I run "dnf install nvidia-modprobe", I get: Package
nvidia-modprobe-2:358.16-1.fc23.x86_64 is already installed. Anyway, all
my output:
LSMOD | GREP NVIDIA
nvidia_modeset716800 3
nvidia 8749056 6
Hi Phil,
Thanks so much for the detailed response! I'll give this a try.
I see you enabled the rawhide repo, does this install a different driver
than from regular RPM Fusion?
What are the last two commands doing? Adding some needed OpenCL support?
On 2015-11-30 14:55, Phil Evans wrote:
Il 30/11/2015 22:28, Brandt, Riley ha scritto:
> I've installed the nvidia-modprobe package
Such package does not exist.
Please show the output of:
# lsmod | grep nvidia
# dnf repolist all
# rpm -qa *nvidia*
# rpm -qa kernel*
# lspci -k | grep -iA 3 vga
# rpm -q darktable
-
Hi all
Having used arch linux and opensuse for several years and having no
problem installing the nvidia proprietry drivers and enabling opencl
for darktable, I allways found it difficult to get opencl working on
fedora and not having it break after a kernel update. However I was
determined to crac
Proper link to the blog post this time:
http://www.dzhang.com/blog/2014/03/20/darktable-and-nvidia-opencl-on-fedora
On 2015-11-30 14:28, Brandt, Riley wrote:
> I've installed the nvidia-modprobe package, but this didin't fix it. There is
> no nvidia-uvm package to install. There is a nvid
I've installed the nvidia-modprobe package, but this didin't fix it.
There is no nvidia-uvm package to install. There is a nvidia-uvm.ko file
in: /usr/lib/modules/4.2.6-301.fc23.x86_64/extra/nvidia
There is an old blog post from Fedora user,
https://kolabnow.com/apps/e365dd77e0ddda88/?_task=ma
Hi, I am the Darktable co maintainer. Does
# modprobe nvidia-uvm
help you?
--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in th
Has anyone managed to get OpenCL working with Nvidia drivers in Fedora 23?
I've tried the proprietary drivers from both RPM Fusion and the
Negativo17 repos, without success. I've also installed the
nvidia-modprobe package that I needed back when I was on Ubuntu, but
that also didn't help.
Go
Thanks. I'm using an ati card. I have had this card working previously. I
installed the fglrx packages as well as opencl, but obviously missing
something. Deborah unstable is particularly unstable at the moment. Thanks
for the pointer.
On Sun, Sep 6, 2015, 4:54 AM Ulrich Pegelow
wrote:
> Hi,
>
>
Hi,
what kind of graphics card and driver are you using? The error message
talks about an internal problem finding some libraries. Maybe your
driver installation is not complete.
Ulrich
Am 05.09.2015 um 23:13 schrieb Derek Kite:
> I'm getting an error running darktable-cltest.
>
> BUILD LOG:
>
I'm getting an error running darktable-cltest.
BUILD LOG:
In file included from /tmp/OCL12595T5.cl:19:
/opt/darktable/share/darktable/kernels/common.h:19:20: warning: 'extern'
variable has an initializer
constant sampler_t sampleri = CLK_NORMALIZED_COORDS_FALSE |
CLK_ADDRESS_CLAMP_TO_EDGE | CLK_F
So, I have a brandnew installation of Linux Mint made.
Add PPAs:
ppa:pmjdebruijn/darktable-release
ppa:graphics-drivers/ppa
Installation of darktable 1.6.8, nvidia-355, nvidia-opencl-icd-355,
nvidia-libopencl1-355, libcuda1-355, nvidia-settings and reboot
1. Problem: could not find runtime libra
Am 18.08.2015 um 10:14 schrieb Roman Lebedev:
> On Tue, Aug 18, 2015 at 11:05 AM, Jörn
> Eisenkrätzer mailto:a...@aed-dresden.de>> wrote:
>
> Hi Roman,
>
> Please ALWAYS keep the mailing list as CC. DO NOT remove it.
>
> thanks for this tip.Removing of beignet made possible launch of DT
>
Hi,
also I removed beignet and I can start DT as user without error messages
dri2 and witout openCL support, start as root I have openCL support.
Then I changed the permission:
chgrp video /usr/bin/darktable
and I have openCL support by DT. I'm member of the video group.
But the desktop will fr
On Tue, Aug 18, 2015 at 11:05 AM, Jörn Eisenkrätzer
wrote:
> Hi Roman,
>
Please ALWAYS keep the mailing list as CC. DO NOT remove it.
thanks for this tip.Removing of beignet made possible launch of DT as user
> without error message of dri2.
>
How exactly did beignet got installed on your machi
On Mon, Aug 17, 2015 at 10:33 PM, Jörn Eisenkrätzer
wrote:
> Hi,
>
Hi.
> I have this same problem, a Notebook with Intel i915 GA and nVidia 940M GA.
> But I can't disable the i915 in BIOS.
>
> I use LinuxMint 17 with mamarley/nvidia-ppa, the normal ubuntu-nvidia lets
> frozen the desktop if I u
Hi,
I have this same problem, a Notebook with Intel i915 GA and nVidia 940M GA.
But I can't disable the i915 in BIOS.
I use LinuxMint 17 with mamarley/nvidia-ppa, the normal ubuntu-nvidia lets
frozen the desktop if I use the touchpad
Unfortunately am I not an expert in in affairs like graphic
Hi,
thanks to all. Removing beignet did the trick.
Am 09.07.2015 um 21:48 schrieb Andrea Angeloni:
> is your system composed by two graphics card?
not really. I've deactivated the on board graphics in the BIOS.
> Good luck, and enjoy this fabolous piece of software we're speaking about.
Yes it
Ciao,
is your system composed by two graphics card?
I spent several hours struggling against a NVIDIA + Intel setup, in the
end I won via bumblebee (browse the net for it). Idea is that Intel asks
to Nvidia to process data, and then displays the result.
Let's suppose that your Intel card doe
On Thu, Jul 9, 2015 at 8:41 AM, Ulrich Pegelow
wrote:
> Hi,
>
> google indicates that the error message "X server found. dri2 connection
> failed!" meight be linked to beignet, the OpenCL implementation for
> Intel graphics cards.
+1, it most definitely is.
There was a person with "X server fou
Hi,
google indicates that the error message "X server found. dri2 connection
failed!" meight be linked to beignet, the OpenCL implementation for
Intel graphics cards. As you said you have just bought a new Nvidida
card. Maybe there are stale libraries and/or config files of your
previous hardw
On Thu, 09 Jul 2015 02:12:31 +0200
Jan Niklas Fingerle wrote:
>Hi,
>
>Am 09.07.2015 um 01:45 schrieb Patrick Shanahan:
>> Yes, but that would indicate a problem between dt and opencl...
>
>yes, of course. That's what I suspected as well, hence the debugging
>output for opencl in my first mail.
Hi,
Am 09.07.2015 um 01:45 schrieb Patrick Shanahan:
> Yes, but that would indicate a problem between dt and opencl...
yes, of course. That's what I suspected as well, hence the debugging
output for opencl in my first mail. I should have stated my suspicion
more directly. Anyway, yes, there is
* Jan Niklas Fingerle [07-08-15 19:33]:
> Hi,
>
> Am 09.07.2015 um 01:11 schrieb Patrick Shanahan:
> > * Jan Niklas Fingerle [07-08-15 19:09]:
> >> Hi,
> >>
> >> I've just bought and installed a Gigabyte Nvida Geforce GTX 960 and
> >> installed the drivers downloaded from Nvidia to my Linux Mint
Hi,
Am 09.07.2015 um 01:11 schrieb Patrick Shanahan:
> * Jan Niklas Fingerle [07-08-15 19:09]:
>> Hi,
>>
>> I've just bought and installed a Gigabyte Nvida Geforce GTX 960 and
>> installed the drivers downloaded from Nvidia to my Linux Mint 17.1
>> Cinnamon (64 bit) (essentially an Ubuntu Linux).
* Jan Niklas Fingerle [07-08-15 19:09]:
> Hi,
>
> I've just bought and installed a Gigabyte Nvida Geforce GTX 960 and
> installed the drivers downloaded from Nvidia to my Linux Mint 17.1
> Cinnamon (64 bit) (essentially an Ubuntu Linux).
>
> When trying to run darktable, I get the following:
[.
Hi,
I've just bought and installed a Gigabyte Nvida Geforce GTX 960 and
installed the drivers downloaded from Nvidia to my Linux Mint 17.1
Cinnamon (64 bit) (essentially an Ubuntu Linux).
When trying to run darktable, I get the following:
jnf@agricola ~ $ darktable -d opencl
[opencl_init] opencl
Am Sonntag, den 21.06.2015, 12:42 -0700 schrieb
darkta...@911networks.com:
> Hi,
>
> I'm trying to configure OpenCL:
>
> * xUbuntu 14.04.2 up to date
> * Nvidia 650Ti
> * nvidia331-update
>
> Chapter 9 of the manual:
>
> lsmod|grep nvidia: only shows
> nvidia 10744943 30
>
> an
On Sun, 21 Jun 2015 12:42:20 -0700
darkta...@911networks.com wrote:
> Hi,
>
> I'm trying to configure OpenCL:
>
> * xUbuntu 14.04.2 up to date
> * Nvidia 650Ti
> * nvidia331-update
>
> Chapter 9 of the manual:
>
> lsmod|grep nvidia: only shows
> nvidia 10744943 30
>
> and
>
>
Hi,
I'm trying to configure OpenCL:
* xUbuntu 14.04.2 up to date
* Nvidia 650Ti
* nvidia331-update
Chapter 9 of the manual:
lsmod|grep nvidia: only shows
nvidia 10744943 30
and
ls -l /dev/nvidia* only gives
crw-rw-rw- 1 root root 195, 0 Jun 21 09:40 /dev/nvidia0
crw-rw-rw- 1
I've just got myself a second-hand 2012 model MacBook Pro retina 15"
which has an nVidia GeForce GT 650M with 1GB RAM. I've managed to get
everything installed to the point where darktable seems pretty happy to
use it, compiling all the opencl kernels and showing me the opencl
option in the co
Thanks Robert!
Btw, any plans for another video tutorial soon? Miss them. :)
Gonçalo Marrafa
On 20 May 2015 at 02:16, Robert William Hutton wrote:
> On 19/05/15 00:03, Gonçalo Marrafa wrote:
> > Has anyone run DT with OpenCL support using Beignet? How is your
> experience? Does it work OK? I
On 19/05/15 00:03, Gonçalo Marrafa wrote:
> Has anyone run DT with OpenCL support using Beignet? How is your experience?
> Does it work OK? Is the
> performance noticeable?
It doesn't currently work, and the current thinking is that there wouldn't be
much of an improvement
in performance anyway
Hi.
Has anyone run DT with OpenCL support using Beignet? How is your
experience? Does it work OK? Is the performance noticeable?
Thanks in advance.
Gonçalo Marrafa
--
One dashboard for servers and applications across Ph
Thanks Ulrich - I have tried again with a fresh build after merging the changes
and I can confirm I no longer see the error message.
David
On 02/05/15 11:42, Ulrich Pegelow wrote:
> This has been fixed now in master. Was a stupid bug introduced by my
> commit 7c7040b87b7bb8662f6510dcdddab84262b
This has been fixed now in master. Was a stupid bug introduced by my
commit 7c7040b87b7bb8662f6510dcdddab84262b3a815.
Ulrich
Am 27.04.2015 um 21:00 schrieb David Smith:
> I suspect this may be a driver issue, but wondered if anyone had any
> suggestions about an error I see running with OpenCL.
That error number (-30) means "CL_INVALID_VALUE". It's on the one hand a
very generic error that can theoretically occur at almost any OpenCL
command. On the other hand I have not seen this error being reported in
the past with darktable.
Best guess is a driver issue as you both seem to use the
You don't need to uncheck the box. If the setting is greyed out then
darktable does not use OpenCL because darktable has not found a running
OpenCL environment on your system. Anyhow the Intel-GPU OpenCL system is
still very shaky. AFAIK there has been no success report on using it
with darktab
I am running Darktable on a notebook that has an Intel GPU. How can I
uncheck the "activate OpenCL support" option?
>From the DT manual: "darktable can use your GPU to speed up processing
significantly. Interface OpenCL requires suitable hardware and matching
OpenCL drivers on your system. If one
Am 28.04.2015, 07:01 Uhr, schrieb Robert William Hutton
:
> How much video RAM?
>
[opencl_init] found 1 device
[opencl_init] device 0 `GeForce GTX 750 Ti' has sm_20 support.
[opencl_init] device 0 `GeForce GTX 750 Ti' supports image sizes of 32768
x 32768
[opencl_init] device 0 `GeForce GTX 75
> How much video RAM?
I believe it is 4GB.
[ 5.411] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 860M (GM107-A) at
PCI:1:0:0 (GPU-0)
[ 5.411] (--) NVIDIA(0): Memory: 4194304 kBytes
David
On 28/04/15 05:00, David Smith wrote:
>> I suspect this may be a driver issue, but wondered if anyone
How much video RAM?
On 28/04/15 05:00, David Smith wrote:
> I suspect this may be a driver issue, but wondered if anyone had any
> suggestions about an error I
> see running with OpenCL.
>
> The problem is I consistently see this:
>
> [opencl copy_image] could not copy image: -30
> [opencl_resam
Same here.
Ubuntu 15.04
Geforce GTX 750Ti with NVIDIA 340.76
thanks
Am 27.04.2015, 21:00 Uhr, schrieb David Smith :
> I suspect this may be a driver issue, but wondered if anyone had any
> suggestions about an error I see running with OpenCL.
>
> The problem is I consistently see this:
>
> [op
I suspect this may be a driver issue, but wondered if anyone had any
suggestions about an error I see running with OpenCL.
The problem is I consistently see this:
[opencl copy_image] could not copy image: -30
[opencl_resampling] couldn't enqueue kernel! -30
[opencl_demosaic] couldn't enqueue ke
Hi,
it's fixed now in git master.
BTW your Nvidia OpenCL driver is really old (304.117). You might
consider to upgrade to a newer one.
Ulrich
Am 09.10.2014 um 16:58 schrieb Komzar:
> Hi. I have a problem tu run OpneCL on my computer. I'm using stable
> version of DT
>ASUS K70I with Nvidia
Hi,
thanks for reporting. There are different stepping modes of Nvidia GPUs
around. Some of them support atomic float32 operations, others not. We
have a list in our code which darktable consults. Your GPU is obviously
not in that list. I'll add it today, then it should work.
Ulrich
Am 09.10
Hi. I have a problem tu run OpneCL on my computer. I'm using stable
version of DT
ASUS K70I with Nvidia 320M
The part of debug logs on startup looks like that:
"
[opencl_init] trying to load opencl library: ''
[opencl_init] opencl library 'libOpenCL' found on your system and loaded
[opencl_in
Hi Federico,
Am Mo 06 Okt 2014 13:49:59 CEST
schrieb Federico Bruni :
> Thanks Micheal, I never came so close to get OpenCL working, after
> months (I didn't put much effort though). Purging and reinstalling
...
> Now I get this:
...
> [opencl_init] compiling program `demosaic_ppg.cl' ..
> [ope
Il giorno lun 6 ott 2014 alle 12:26, Michael Below ha
scritto:
Hi Tomas,
Thanks for your input. For me, OpenCL is now working, (nearly)
without workarounds, using the packages from Debian testing (nvidia
driver v. 340).
My steps:
- Debian testing, ocl-icd-libopencl1 is providing
l
On Mon, 6 Oct 2014 12:26:05 +0200
"Michael Below" wrote:
> 2. And darktable doesn’t use the correct SONAME when it tries to load
> libOpenCL.so instead of libOpenCL.so.1. This works only if
> nvidia-cuda-toolkit (or, probably, any other OpenCL development package) is
> installed, which p
...@seznam.cz]
Gesendet: Montag, 6. Oktober 2014 10:54
An: Michael Below
Cc: darktable-users
Betreff: Re: [Darktable-users] OpenCL detected by clinfo, not detected by dt,
ideas?
Hi,
>From what I've read so far this may be slightly different situation. However I
>thought sharing it
Hi,
>From what I've read so far this may be slightly different situation. However
I thought sharing it may help in some way? I am running Mint 17 (based on
Ubuntu 14.04). I just bought a new GeForce GTX 980 graphics card and
installed drivers 343 following these notes - http://www.binarytides.com
Here's a (previous) explanation for the naming of dynamic libraries by
the same Debian developer:
"Usually a library (lets take libfoobar as an example) comes with three
files:
libfoobar.so.1.234 (the actual file)
libfoobar.so.1 -> libfoobar.so.1.234 (symbolic link)
libfoobar.so -> libfoobar
Am So 05 Okt 2014 21:27:49 CEST
schrieb Michael Below :
> Update: Thanks to
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1311362/comments/7
> I installed nvidia-cuda-toolkit, now it works...
Second update: I filed this as Debian bug #764146. Now Debian
developer Andreas Beckmann points o
Hi,
Try this (info gathered mostly from this forum):
http://tech.kovacs-telekes.org/2014-07-29-darktable-opencl-nvidia-ubuntu-1404-mint-17
Kofa
On 5 October 2014 20:39, Michael Below wrote:
> Hi,
>
> I am trying to use darktable with OpenCL with my NVidia GTX750, using
> Debian testing, kernel
1 - 100 of 138 matches
Mail list logo
