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

[darktable-dev] correcoes ...

[Jefferson Ferreira]

- criar um jfocus (focus stacking)

https://www.youtube.com/watch?v=4sIgiJqiZYU


-- 
Jefferson Ferreira

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

[darktable-dev] darktable 2.4.0rc2 released

[Tobias Ellinghaus]

we're proud to announce the third release candidate for the upcoming 2.4 
series of darktable, 2.4.0rc2!

the github release is here: https://github.com/darktable-org/darktable/
releases/tag/release-2.4.0rc2.

as always, please don't use the autogenerated tarball provided by github, but 
only our tar.xz. the checksum is:

```
$ sha256sum darktable-2.4.0rc2.tar.xz
dcb56e1eb2c10aa9fe64ea9ba3e806e3da3a3a0ebb47646a07e1838b88f15949 
darktable-2.4.0rc1.tar.xz
$ sha256sum darktable-2.4.0rc2.dmg
5ad1c355c04d8a42bab7c2879cba92891dbdd0a89b8fe0ff2ea18f1f8b592f15 
darktable-2.4.0rc1.dmg
$ sha256sum darktable-2.4.0rc2.dirty-win64.exe
a4cd63e9e44f029d4a85b430c5fdaf49e110c1ebe0a9cfc51ac2bf86ebac41cf 
darktable-2.4.0rc1.exe
```

 Important note: to make sure that darktable can keep on supporting the 
raw file format for your camera, *please* read [this post](https://
discuss.pixls.us/t/raw-samples-wanted/5420?u=lebedevri) on how/what raw 
samples you can contribute to ensure that we have the *full* raw sample set 
for your camera under CC0 license!

## changes since rc1

- Fix a bug in haze removal that resulted in black areas in the exported image
- Support Sony ILCE-7RM3
- Make calls to exiv2's readMetadata thread safe to not crash randomly
- Don't hide the mode combobox in the exposure module, just disable it
- Change the styling of insensitive bauhaus widgets
- Fix spurious segfault in local contrast
- Don't show an error popup on Windows when the CD drive is empty

and the changelog as compared to 2.2.0 can be found below. Some of the fixes 
might have been backported to the stable 2.2.x series already.

- The maintainership of the RawSpeed library was transferred to the darktable 
project. The work on code cleanup, hardening, modernization, simplification 
and testing is ongoing.
- Well over 2 thousand commits to darktable+rawspeed since 2.2.0
- 244 pull requests handled
- 320+ issues closed
- Updated user manual is coming soon™

## Hell Froze Over

- As you might have read on our [news post](https://www.darktable.org/2017/08/
darktable-for-windows/) we finally ported darktable to Windows and intend to 
support it in the future. At the moment it's still lacking a few features (for 
example there is not printing support), has a few limitations (tethering 
requires special drivers to be installed) and comes with its own set of bugs. 
But overall we are confident that it's quite usable already and hope you will 
enjoy it. A very special thanks goes to Peter Budai who finally convinced us 
to agree to the port and who did most of the work.

## The Big Ones

- A new module for haze removal
- The local contrast module can now be pushed much further, it also got a new 
local laplacian mode
- Add undo support for masks and more intelligent grouping of undo steps
- Blending now allows to display individual channels using false colors
- darktable now supports loading Fujifilm compressed RAFs
- darktable now supports loading floating point HDR DNGs as written by 
HDRMERGE
- We also added channel specific blend modes for Lab and RGB color spaces
- The base curve module allows for more control of the exposure fusion feature 
using the newly added bias slider
- The tonecurve module now supports auto colour adjustment in RGB
- Add absolute color input as an option to the color look up table module
- A new X-Trans demosaicing algorithm, Frequency Domain Chroma, was 
implemented.
- You can now choose from pre-defined scheduling profiles for OpenCL
- Speaking of OpenCL, darktable now allows to force-use OpenCL for a specific 
pixelpipe
- Xmp sidecar files are no longer written to disk when the content didn't 
actually change. That mostly helps with network storage and backup systems 
that use files' time stamps

## New Features And Changes

- Show a dialog window that tells when locking the database/library failed
- Don't shade the whole region on the map when searching for a location. 
Instead just draw a border around it.
- Also in map mode: Clear the search list and map indicators when resetting 
the search module.
- With OsmGPSMap newer than version 1.1.0 (i.e., anything released after that 
OsmGPSMap version) the map will show copyright info.
- Running jobs with a progressbar (mostly import and export) will show that 
progress bar ontop the window entry in your task bar – if the system supports 
it. It should work on GNOME, KDE and Windows at least.
- Add bash like string replacement for variables (export, watermark, session 
settings).
- Add a preferences option to ask before removing empty dirs
- The "colorbalance" module got a lot faster, thanks to SSE optimized code
- Make gradient sliders a little more colorful
- Make PNG compression level used for exporting configurable
- On OSX, load single images from command line or via drag in darkroom 
mode
- Add an option to omit the intermediate tag hierarchy in exported files and 
only add the last level
- In the watermark module, sort the list of SVG files and omit the file 

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