Re: [darktable-dev] OpenCL does not work after Nvidia driver upgrade to 384.90

[Patrick Shanahan]

* KOVÁCS István  [01-08-18 15:24]:
> Hello,
> 
> In case anyone is interested, upgrading to nvidia-384.98 from PPA
> solved my problem.
> kofa@eagle:~$ dpkg -l|egrep -i "opencl|nvidia|cuda"
> ii  bbswitch-dkms   0.8-3ubuntu1
>   amd64Interface for
> toggling the power on NVIDIA Optimus video cards
> ii  libcuda1-384
> 384.98-0ubuntu0~gpu16.04.1   amd64
> NVIDIA CUDA runtime library
> ii  nvidia-384
> 384.98-0ubuntu0~gpu16.04.1   amd64
> NVIDIA binary driver - version 384.98
> ii  nvidia-libopencl1-384
> 384.98-0ubuntu0~gpu16.04.1   amd64
> NVIDIA OpenCL Driver and ICD Loader library
> ii  nvidia-opencl-icd-384
> 384.98-0ubuntu0~gpu16.04.1   amd64
> NVIDIA OpenCL ICD
> ii  nvidia-prime0.8.2
>   amd64Tools to enable
> NVIDIA's Prime
> ii  nvidia-settings
> 387.22-0ubuntu0~gpu16.04.1   amd64
> Tool for configuring the NVIDIA graphics driver
> ii  opencl-headers  2.0~svn32091-2
>   all  OpenCL (Open
> Computing Language) header files
> 
> Kofa
> 
> 
> On 19 December 2017 at 09:07, Bob Tregilus  wrote:
> >
> >
> >
> >
> > On Mon, Dec 18, 2017 at 11:30 PM, KOVÁCS István 
> > wrote:
> >>
> >> Update: I've gone through all the modules, moving the .cl source files
> >> for failing modules so darktable would get through the startup
> >> process. The following needed to be moved (these are the ones that
> >> fail to compile):
> >> atrous.cl  basic.cl  blendop.cl  bloom.cl  colorreconstruction.cl
> >> demosaic_markesteijn.cl  demosaic_other.cl  demosaic_vng.cl
> >> denoiseprofile.cl  extended.cl  liquify.cl  nlmeans.cl  sharpen.cl
> >> soften.cl
> >>
> >>
> >>
> >> >> K.
> >> >
> >> >
> >>
> >
> > I mention this because it is an odd behavior when I start Darktable
> > (versions 2.2.5 and now 2.4.0~rc2, but not older versions).
> >
> > Under KDE there's a function called "KDE Wallet Subsystem". I guess it's
> > intended to store passwords.
> >
> > It's very annoying and it's the first thing I turn off when installing a new
> > upgrade.
> >
> > In the past, if I turn the Wallet off, when I launched various software that
> > would attempt to call the wallet up, of course nothing would happen because
> > it was turned off.
> >
> > However, beginning with Darktable 2.2.5, when I start it up, the wallet
> > dialog box opens. I just click 'cancel' which closes the dialog, but it
> > immediately reopens again. It takes three 'cancels' before a forth dialog
> > opens telling me something about the wallet misbehaving, which I close as
> > well. Meanwhile, Darktable loads in the background of all of that going on
> > and runs fine thereafter.
> >
> > I haven't paid it much attention to it because that's the way the KDE Wallet
> > behaved in the past when it first appeared about 10-12 years ago. After a
> > couple of years, it finally stayed off completely after being initially
> > being disabled upon installation of the distro.
> >
> > Just thought I'd mention it. Haven't a clue if it's related at all to your
> > problem or NVIDIA cards and their software, which I've run for the past two
> > decades. Use to have to compile the NVIDIA drivers into the kernel, years
> > ago.
> >
> > Bob
> >
> > PS: If Roman & Adam are reading this, support for the ILCE-7RM3 in 2.4.0~rc2
> > seems to be working fine. Thanks!
> >
> >
> > ___
> > darktable developer mailing list to unsubscribe send a mail to
> > darktable-dev+unsubscr...@lists.darktable.org
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

NVIDIA-Linux-x86_64-387.12.run
NVIDIA-Linux-x86_64-387.22.run
NVIDIA-Linux-x86_64-387.34.run
NVIDIA-Linux-x86_64-390.12.run


-- 
(paka)Patrick Shanahan   Plainfield, Indiana, USA  @ptilopteri
http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri
Registered Linux User #207535@ http://linuxcounter.net
Photos: http://wahoo.no-ip.org/piwigo   paka @ IRCnet freenode
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] OpenCL does not work after Nvidia driver upgrade to 384.90

[KOVÁCS István]

Hello,

In case anyone is interested, upgrading to nvidia-384.98 from PPA
solved my problem.
kofa@eagle:~$ dpkg -l|egrep -i "opencl|nvidia|cuda"
ii  bbswitch-dkms   0.8-3ubuntu1
  amd64Interface for
toggling the power on NVIDIA Optimus video cards
ii  libcuda1-384
384.98-0ubuntu0~gpu16.04.1   amd64
NVIDIA CUDA runtime library
ii  nvidia-384
384.98-0ubuntu0~gpu16.04.1   amd64
NVIDIA binary driver - version 384.98
ii  nvidia-libopencl1-384
384.98-0ubuntu0~gpu16.04.1   amd64
NVIDIA OpenCL Driver and ICD Loader library
ii  nvidia-opencl-icd-384
384.98-0ubuntu0~gpu16.04.1   amd64
NVIDIA OpenCL ICD
ii  nvidia-prime0.8.2
  amd64Tools to enable
NVIDIA's Prime
ii  nvidia-settings
387.22-0ubuntu0~gpu16.04.1   amd64
Tool for configuring the NVIDIA graphics driver
ii  opencl-headers  2.0~svn32091-2
  all  OpenCL (Open
Computing Language) header files

Kofa


On 19 December 2017 at 09:07, Bob Tregilus  wrote:
>
>
>
>
> On Mon, Dec 18, 2017 at 11:30 PM, KOVÁCS István 
> wrote:
>>
>> Update: I've gone through all the modules, moving the .cl source files
>> for failing modules so darktable would get through the startup
>> process. The following needed to be moved (these are the ones that
>> fail to compile):
>> atrous.cl  basic.cl  blendop.cl  bloom.cl  colorreconstruction.cl
>> demosaic_markesteijn.cl  demosaic_other.cl  demosaic_vng.cl
>> denoiseprofile.cl  extended.cl  liquify.cl  nlmeans.cl  sharpen.cl
>> soften.cl
>>
>>
>>
>> >> K.
>> >
>> >
>>
>
> I mention this because it is an odd behavior when I start Darktable
> (versions 2.2.5 and now 2.4.0~rc2, but not older versions).
>
> Under KDE there's a function called "KDE Wallet Subsystem". I guess it's
> intended to store passwords.
>
> It's very annoying and it's the first thing I turn off when installing a new
> upgrade.
>
> In the past, if I turn the Wallet off, when I launched various software that
> would attempt to call the wallet up, of course nothing would happen because
> it was turned off.
>
> However, beginning with Darktable 2.2.5, when I start it up, the wallet
> dialog box opens. I just click 'cancel' which closes the dialog, but it
> immediately reopens again. It takes three 'cancels' before a forth dialog
> opens telling me something about the wallet misbehaving, which I close as
> well. Meanwhile, Darktable loads in the background of all of that going on
> and runs fine thereafter.
>
> I haven't paid it much attention to it because that's the way the KDE Wallet
> behaved in the past when it first appeared about 10-12 years ago. After a
> couple of years, it finally stayed off completely after being initially
> being disabled upon installation of the distro.
>
> Just thought I'd mention it. Haven't a clue if it's related at all to your
> problem or NVIDIA cards and their software, which I've run for the past two
> decades. Use to have to compile the NVIDIA drivers into the kernel, years
> ago.
>
> Bob
>
> PS: If Roman & Adam are reading this, support for the ILCE-7RM3 in 2.4.0~rc2
> seems to be working fine. Thanks!
>
>
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] OpenCL does not work after Nvidia driver upgrade to 384.90

[Bob Tregilus]

On Mon, Dec 18, 2017 at 11:30 PM, KOVÁCS István 
wrote:

> Update: I've gone through all the modules, moving the .cl source files
> for failing modules so darktable would get through the startup
> process. The following needed to be moved (these are the ones that
> fail to compile):
> atrous.cl  basic.cl  blendop.cl  bloom.cl  colorreconstruction.cl
> demosaic_markesteijn.cl  demosaic_other.cl  demosaic_vng.cl
> denoiseprofile.cl  extended.cl  liquify.cl  nlmeans.cl  sharpen.cl
> soften.cl
>
>
>
> >> K.
> >
> >
>
>
I mention this because it is an odd behavior when I start Darktable
(versions 2.2.5 and now 2.4.0~rc2, but not older versions).

Under KDE there's a function called "KDE Wallet Subsystem". I guess it's
intended to store passwords.

It's very annoying and it's the first thing I turn off when installing a
new upgrade.

In the past, if I turn the Wallet off, when I launched various software
that would attempt to call the wallet up, of course nothing would happen
because it was turned off.

However, beginning with Darktable 2.2.5, when I start it up, the wallet
dialog box opens. I just click 'cancel' which closes the dialog, but it
immediately reopens again. It takes three 'cancels' before a forth dialog
opens telling me something about the wallet misbehaving, which I close as
well. Meanwhile, Darktable loads in the background of all of that going on
and runs fine thereafter.

I haven't paid it much attention to it because that's the way the KDE
Wallet behaved in the past when it first appeared about 10-12 years ago.
After a couple of years, it finally stayed off completely after being
initially being disabled upon installation of the distro.

Just thought I'd mention it. Haven't a clue if it's related at all to your
problem or NVIDIA cards and their software, which I've run for the past two
decades. Use to have to compile the NVIDIA drivers into the kernel, years
ago.

Bob

PS: If Roman & Adam are reading this, support for the ILCE-7RM3 in
2.4.0~rc2 seems to be working fine. Thanks!

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] OpenCL does not work after Nvidia driver upgrade to 384.90

[KOVÁCS István]

Update: I've gone through all the modules, moving the .cl source files
for failing modules so darktable would get through the startup
process. The following needed to be moved (these are the ones that
fail to compile):
atrous.cl  basic.cl  blendop.cl  bloom.cl  colorreconstruction.cl
demosaic_markesteijn.cl  demosaic_other.cl  demosaic_vng.cl
denoiseprofile.cl  extended.cl  liquify.cl  nlmeans.cl  sharpen.cl
soften.cl


@Bob: Thanks for the quick check!
The idea of needing
/usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.1 comes from the
workaround mentioned by Pascal.

That's very interesting. Without
/usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.1, darktable is
complaining:
(This is after issuing rm -rf
.cache/darktable/cached_kernels_for_GeForceGTX650/ - a command that
removes compiled versions of the GPU-accelerated modules.)

[opencl_init] compiling program `demosaic_ppg.cl' ..
[opencl_fopen_stat] could not open file
`/home/kofa/.cache/darktable/cached_kernels_for_GeForceGTX650/demosaic_ppg.cl.bin'!
[opencl_load_program] could not load cached binary program, trying to
compile source
[opencl_load_program] successfully loaded program from
`/usr/share/darktable/kernels/demosaic_ppg.cl'
[opencl_build_program] successfully built program
[opencl_build_program] BUILD STATUS: 0
BUILD LOG:


[opencl_build_program] saving binary
[opencl_init] compiling program `atrous.cl' ..
[opencl_fopen_stat] could not open file
`/home/kofa/.cache/darktable/cached_kernels_for_GeForceGTX650/atrous.cl.bin'!
[opencl_load_program] could not load cached binary program, trying to
compile source
[opencl_load_program] successfully loaded program from
`/usr/share/darktable/kernels/atrous.cl'
[opencl_build_program] could not build program: -
[opencl_build_program] BUILD STATUS: -2
BUILD LOG:
error   : Unable to load library 'libnvidia-ptxjitcompiler.so.1'

[opencl_init] failed to compile program `atrous.cl'!
[opencl_init] FINALLY: opencl is NOT AVAILABLE on this system.
[opencl_init] initial status of opencl enabled flag is OFF.

If I run ldconfig after removing the symlink, I get no such error,
just the usual compilation problem for atrous.cl:
[opencl_init] compiling program `atrous.cl' ..
[opencl_fopen_stat] could not open file
`/home/kofa/.cache/darktable/cached_kernels_for_GeForceGTX650/atrous.cl.bin'!
[opencl_load_program] could not load cached binary program, trying to
compile source
[opencl_load_program] successfully loaded program from
`/usr/share/darktable/kernels/atrous.cl'
[opencl_build_program] could not build program: -5
[opencl_build_program] BUILD STATUS: -2
BUILD LOG:

[opencl_init] failed to compile program `atrous.cl'!

Kofa

On 19 December 2017 at 07:09, Bob Tregilus  wrote:
>
>
> On Mon, Dec 18, 2017 at 10:06 PM, KOVÁCS István 
> wrote:
>>
>> On 19 December 2017 at 07:05, KOVÁCS István 
>> wrote:
>> > Could you please try one more thing for me? Run the command
>> > ls -l /usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.1
>> > and paste its output here.
>> >
>> > (I did not have that file; I needed to link it from
>> > /usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.1, as suggested
>> > by Pascal.)
>>
>> Again, too early. I had to link the file *from*
>> /usr/lib/nvidia-384/libnvidia-ptxjitcompiler.so.1 *to*
>> /usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.1
>>
>> K.
>
>
> Whatever the case:
>
> ~ $ ls -l /usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.1
> ls: cannot access '/usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.1':
> No such file or directory
>
> Bob
>
>
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] OpenCL does not work after Nvidia driver upgrade to 384.90

[KOVÁCS István]

On 19 December 2017 at 07:05, KOVÁCS István  wrote:
> Could you please try one more thing for me? Run the command
> ls -l /usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.1
> and paste its output here.
>
> (I did not have that file; I needed to link it from
> /usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.1, as suggested
> by Pascal.)

Again, too early. I had to link the file *from*
/usr/lib/nvidia-384/libnvidia-ptxjitcompiler.so.1 *to*
/usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.1

K.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] OpenCL does not work after Nvidia driver upgrade to 384.90

[KOVÁCS István]

Thanks, Bob.

I have now removed all extra packages and reconfigured the remaining
ones; the result is more free disk space, but no improvement in
darktable.
One thing I see is that your nvidia packages are of version
384.90-0ubuntu0.16.04.1, while mine are 384.90-0ubuntu0.16.04.2.
I'll try a downgrade later.

Could you please try one more thing for me? Run the command
ls -l /usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.1
and paste its output here.

(I did not have that file; I needed to link it from
/usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.1, as suggested
by Pascal.)

Thanks,
Kofa
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] OpenCL does not work after Nvidia driver upgrade to 384.90

[Bob Tregilus]

---

On Mon, Dec 18, 2017 at 11:34 AM, KOVÁCS István 
wrote:

>
> Bob,
> Please try this:
> dpkg -l|egrep -i "opencl|nvidia|cuda"
> This is how I generated my package list.
>

---

~ # dpkg -l|egrep -i "opencl|nvidia|cuda"
ii  bbswitch-dkms   0.8-3ubuntu1
 amd64Interface for toggling the
power on NVIDIA Optimus video cards
ii  libcuda1-375
384.90-0ubuntu0.16.04.1  amd64
Transitional package for libcuda1-384
ii  libcuda1-384
384.90-0ubuntu0.16.04.1  amd64
NVIDIA CUDA runtime library
ii  nvidia-375
384.90-0ubuntu0.16.04.1  amd64
Transitional package for nvidia-384
ii  nvidia-384
384.90-0ubuntu0.16.04.1  amd64
NVIDIA binary driver - version 384.90
ii  nvidia-opencl-icd-375
 384.90-0ubuntu0.16.04.1  amd64
Transitional package for nvidia-opencl-icd-384
ii  nvidia-opencl-icd-384
 384.90-0ubuntu0.16.04.1  amd64
NVIDIA OpenCL ICD
ii  nvidia-prime0.8.2linuxmint1
  amd64Tools to enable NVIDIA's
Prime
ii  nvidia-prime-applet 1.0.6
  all  An applet for NVIDIA Prime
ii  nvidia-settings 361.42-0ubuntu1
  amd64Tool for configuring the
NVIDIA graphics driver
ii  ocl-icd-libopencl1:amd642.2.8-1
  amd64Generic OpenCL ICD Loader

Bob

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] OpenCL does not work after Nvidia driver upgrade to 384.90

[KOVÁCS István]

Hello All,

I seems I posted the wrong logs - I guess it was too early in the
morning for me.
Here are the correct ones:
clinfo output: 
http://tech.kovacs-telekes.org/files/darktable-opencl-nvidia384.90/clinfo.log
darktable -d opencl output:
http://tech.kovacs-telekes.org/files/darktable-opencl-nvidia384.90/darktable_-d_opencl.log
(shows that demosaic_ppg.cl gets compiled OK, but atrous.cl does not)
dpkg -l filtered output:
http://tech.kovacs-telekes.org/files/darktable-opencl-nvidia384.90/dpkg.log
(NVidia, OpenCL, CUDA related stuff)
nvidia-smi output:
http://tech.kovacs-telekes.org/files/darktable-opencl-nvidia384.90/nvidia-smi.log

Bob,
Please try this:
dpkg -l|egrep -i "opencl|nvidia|cuda"
This is how I generated my package list.

Thanks,
Kofa
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] OpenCL does not work after Nvidia driver upgrade to 384.90

[Bob Tregilus]

On Mon, Dec 18, 2017 at 1:54 AM, KOVÁCS István 
wrote:

> Hi Bob,
>
> It gives me hope :)
> Could you please check the link to my logs, and send me the output of the
> commands on your system? E.g. dpkg.
>
> I installed the driver using the driver manager app; is that all you did,
> too, or did you need to add any package manually?
>
> Thanks,
> István
>
>
The NVIDIA update came through and was installed via the Update Manager.

Is the following what you are after? Otherwise, you'll need to give me
precise instructions (commands) for what you are looking for. (I'm just a
user.)

/var/log/apt/term.log

Log started: 2017-12-05  13:59:04
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 217070 files and directories currently installed.)
Preparing to unpack .../libxml2_2.9.3+dfsg1-1ubuntu0.4_amd64.deb ...
Unpacking libxml2:amd64 (2.9.3+dfsg1-1ubuntu0.4) over
(2.9.3+dfsg1-1ubuntu0.3) ...
Processing triggers for libc-bin (2.23-0ubuntu9) ...
/sbin/ldconfig.real: /usr/lib/nvidia-384/libEGL.so.1 is not a symbolic link

/sbin/ldconfig.real: /usr/lib32/nvidia-384/libEGL.so.1 is not a symbolic
link

Setting up libxml2:amd64 (2.9.3+dfsg1-1ubuntu0.4) ...
Processing triggers for libc-bin (2.23-0ubuntu9) ...
/sbin/ldconfig.real: /usr/lib/nvidia-384/libEGL.so.1 is not a symbolic link

/sbin/ldconfig.real: /usr/lib32/nvidia-384/libEGL.so.1 is not a symbolic
link

(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 217070 files and directories currently installed.)
Preparing to unpack .../libxml2-utils_2.9.3+dfsg1-1ubuntu0.4_amd64.deb ...
Unpacking libxml2-utils (2.9.3+dfsg1-1ubuntu0.4) over
(2.9.3+dfsg1-1ubuntu0.3) ...
Preparing to unpack .../linux-firmware_1.157.14_all.deb ...
Unpacking linux-firmware (1.157.14) over (1.157.13) ...
Preparing to unpack .../python-libxml2_2.9.3+dfsg1-1ubuntu0.4_amd64.deb ...
Unpacking python-libxml2 (2.9.3+dfsg1-1ubuntu0.4) over
(2.9.3+dfsg1-1ubuntu0.3) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up libxml2-utils (2.9.3+dfsg1-1ubuntu0.4) ...
Setting up linux-firmware (1.157.14) ...
update-initramfs: Generating /boot/initrd.img-4.8.0-53-generic
Warning: No support for locale: en_US.utf8
Setting up python-libxml2 (2.9.3+dfsg1-1ubuntu0.4) ...
Log ended: 2017-12-05  13:59:33

Bob
---

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] OpenCL does not work after Nvidia driver upgrade to 384.90

[KOVÁCS István]

Hi Bob,

It gives me hope :)
Could you please check the link to my logs, and send me the output of the
commands on your system? E.g. dpkg.

I installed the driver using the driver manager app; is that all you did,
too, or did you need to add any package manually?

Thanks,
István

On 18 Dec 2017 08:00, "Bob Tregilus"  wrote:


I'm running Linux Mint 18.2 KDE with the NVIDIA driver 384.90 and
Darktable 2.2.5 from Pascal's PPA has been running without any problems.

Hope that helps.

Bob

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] OpenCL does not work after Nvidia driver upgrade to 384.90

[Bob Tregilus]

On Sun, Dec 17, 2017 at 10:33 PM, Pascal Obry  wrote:

>
> István,
>
> > I'm using darktable 2.2.5 from Pascal's PPA on Mint 18.2. I upgraded
> > from Nvidia 340 to 384, now opencl fails. It does compile the first
> > module at least, so I'm not sure if I really have a missing package.
>
> Looks like a known issue fixed in 384.98-3. See
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883303
>
> There is a workaround:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883303#10
>
> Or upgrade to a new version if possible.
>
> ---
>

I'm running Linux Mint 18.2 KDE with the NVIDIA driver 384.90 and
Darktable 2.2.5 from Pascal's PPA has been running without any problems.

Hope that helps.

Bob

___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscribe@
> lists.darktable.org
>
>

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] OpenCL does not work after Nvidia driver upgrade to 384.90

[Ulrich Pegelow]

Unfortunately the OpenCL compiler fails to give a reasonable build log. 
What you could do is try to isolate the offending part of atrous.cl that 
leads to the issues. Start by commenting out the whole code section of 
atrous.cl with "#if 0 ... #endif" and narrow it down from there.


Ulrich

Am 18.12.2017 um 07:43 schrieb KOVÁCS István:

[opencl_init] compiling program `atrous.cl' ..
[opencl_fopen_stat] could not open file
`/home/kofa/.cache/darktable/cached_kernels_for_GeForceGTX650/atrous.cl.bin'!
[opencl_load_program] could not load cached binary program, trying to
compile source
[opencl_load_program] successfully loaded program from
`/usr/share/darktable/kernels/atrous.cl'
[opencl_build_program] could not build program: -5
[opencl_build_program] BUILD STATUS: -2
BUILD LOG:


[opencl_init] failed to compile program `atrous.cl'!
[opencl_init] FINALLY: opencl is NOT AVAILABLE on this system.
[opencl_init] initial status of opencl enabled flag is OFF.
===

Thanks,
Kofa

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] OpenCL does not work after Nvidia driver upgrade to 384.90

[KOVÁCS István]

Thanks for the quick reply. My issue seems to be different: the first
module gets compiled.
I've tried the workaround, anyway, but it failed:
==
eagle ~ # cd /usr/lib/x86_64-linux-gnu
eagle x86_64-linux-gnu # ls
nvidia/current/libnvidia-ptxjitcompiler.so.1<-- this was the
original file linked in the workaround description
ls: cannot access 'nvidia/current/libnvidia-ptxjitcompiler.so.1': No
such file or directory
eagle x86_64-linux-gnu # locate libnvidia-ptxjitcompiler.so.1
/usr/lib/nvidia-384/libnvidia-ptxjitcompiler.so.1
/usr/lib32/nvidia-384/libnvidia-ptxjitcompiler.so.1
eagle x86_64-linux-gnu # ln -s
/usr/lib/nvidia-384/libnvidia-ptxjitcompiler.so.1 .
==

darktable output is the same as earlier:
===
[opencl_init] compiling program `demosaic_ppg.cl' ..
[opencl_load_program] loaded cached binary program from file
`/home/kofa/.cache/darktable/cached_kernels_for_GeForceGTX650/demosaic_ppg.cl.bin'
[opencl_load_program] successfully loaded program from
`/usr/share/darktable/kernels/demosaic_ppg.cl'
[opencl_build_program] successfully built program
[opencl_build_program] BUILD STATUS: 0
BUILD LOG:


[opencl_init] compiling program `atrous.cl' ..
[opencl_fopen_stat] could not open file
`/home/kofa/.cache/darktable/cached_kernels_for_GeForceGTX650/atrous.cl.bin'!
[opencl_load_program] could not load cached binary program, trying to
compile source
[opencl_load_program] successfully loaded program from
`/usr/share/darktable/kernels/atrous.cl'
[opencl_build_program] could not build program: -5
[opencl_build_program] BUILD STATUS: -2
BUILD LOG:


[opencl_init] failed to compile program `atrous.cl'!
[opencl_init] FINALLY: opencl is NOT AVAILABLE on this system.
[opencl_init] initial status of opencl enabled flag is OFF.
===

Thanks,
Kofa

On 18 December 2017 at 07:33, Pascal Obry  wrote:
>
> István,
>
>> I'm using darktable 2.2.5 from Pascal's PPA on Mint 18.2. I upgraded
>> from Nvidia 340 to 384, now opencl fails. It does compile the first
>> module at least, so I'm not sure if I really have a missing package.
>
> Looks like a known issue fixed in 384.98-3. See
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883303
>
> There is a workaround:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883303#10
>
> Or upgrade to a new version if possible.
>
> --
>   Pascal Obry /  Magny Les Hameaux (78)
>
>   The best way to travel is by means of imagination
>
>   http://www.obry.net
>
>   gpg --keyserver keys.gnupg.net --recv-key F949BD3B
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] OpenCL does not work after Nvidia driver upgrade to 384.90

[Pascal Obry]

István,

> I'm using darktable 2.2.5 from Pascal's PPA on Mint 18.2. I upgraded
> from Nvidia 340 to 384, now opencl fails. It does compile the first
> module at least, so I'm not sure if I really have a missing package.

Looks like a known issue fixed in 384.98-3. See

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883303

There is a workaround:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883303#10

Or upgrade to a new version if possible.

-- 
  Pascal Obry /  Magny Les Hameaux (78)

  The best way to travel is by means of imagination

  http://www.obry.net

  gpg --keyserver keys.gnupg.net --recv-key F949BD3B
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org