[darktable-user] Re: [darktable-dev] OpenCL does not work after Nvidia driver upgrade to 384.90
* 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 user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
[darktable-user] Re: [darktable-dev] OpenCL does not work after Nvidia driver upgrade to 384.90
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 user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
[darktable-user] date/time sorting behavior
Dear all, I am confused by the date/time sorting behavior: (1) If I change the filter e.g. from * to ***, the sorting will not applied directly. I must push the sorting forward/backward button to do so. This could be fixed easily, I guess. (2) Even if I push the sorting forward/backward button, some pictures are not in the right order. It seems the first oder priority are the film rolls of the collection, and the second order is the date/time. I am using the linux version of darktable 2.4.0 (source: ppa) Greetings Sebastian signature.asc Description: OpenPGP digital signature