- This topic has 8 replies, 2 voices, and was last updated 6 years, 1 month ago by
.
-
Posts
-
Hi,
In December I have installed Argyll 1.8.3 + repack 2 and Dispcalgui 3.1.0.0-1 from the Software Center (Lubuntu 16.04) and I carried out the first calibration.
Perfect! But after a few weeks, I started to get the message “Calibration curves could not be loaded” and
the DisplayCal log gives the following error “Dispwin: Error – We don’t have access to the VideoLUT”
From the information I found on the web it seems this error is created by new drivers installed by one of the numerous Linux updates. Mainly Nvidia cards
have been affected but I also saw some messages about ATI Radeon cards (like mine) having the same problem.Furthermore, I am now having problems with Argyll because my Spider5 is not detected any longer.
I checked the syslog and I found the following errors:
failed to execute ‘/lib/udev/usb-db’ ‘usb-db /devices/pci0000:00/0000:00:10.2/usb4/4-2’: No such file or directory
failed to execute ‘/lib/udev/usb-db’ ‘usb-db /devices/pci0000:00/0000:00:10.2/usb4/4-2/4-2:1.0’: No such file or directoryIt seems that these errors refer to an old bug which is supposed to have been already solved a few years ago.
quote
This bug was fixed in the package argyll – 1.4.0-8ubuntu5
—————
argyll (1.4.0-8ubuntu5) saucy; urgency=low* Use hwdb builtin, instead of the obsolete usb-db in the udev
rules. (LP: #1200185)
— Dmitrijs Ledkovs <email address hidden> Thu, 29 Aug 2013 22:55:30 +0100Changed in argyll (Ubuntu):
status: Confirmed → Fix Releasedunquote
Until now I didn’t find a fix or a workaround for these problems, I am afraid I have to renounce to calibrate this PC since my knowledge of Linux is limited although I love it.
Any help is appreciated.
rgds Luigi
Hi,
In December I have installed Argyll 1.8.3 + repack 2
that’s a quite old version (released three years ago). Have you tried the latest version (2.0)?
Hi,
That version is the latest in the Software Center of Lubuntu 16.04, as I said my knowledge of Linux is limited.
The installation documentation of Argyll is quite difficult for me, i.e. I don’t know how to configure the $PATH environment variable to give access to the executables from the command line environment, nor if I really need to do it.
Anyway, I will try to install the latest version of both programs and I will tell you the results.rgds Luigi
I have installed DisplayCal V. 3.5.1 and untarred Argyll 2.0.0 into /usr/local as advised.
Unfortunately in the syslog I still have the same error :
Mar 23 18:16:39 IXTREME-MC-9600 kernel: [ 9897.283929] usb 4-2: new full-speed USB device number 2 using uhci_hcd
Mar 23 18:16:39 IXTREME-MC-9600 kernel: [ 9897.470961] usb 4-2: New USB device found, idVendor=085c, idProduct=0500
Mar 23 18:16:39 IXTREME-MC-9600 kernel: [ 9897.470967] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Mar 23 18:16:39 IXTREME-MC-9600 kernel: [ 9897.470969] usb 4-2: Product: Datacolor Spyder5
Mar 23 18:16:39 IXTREME-MC-9600 kernel: [ 9897.470972] usb 4-2: Manufacturer: Datacolor
Mar 23 18:16:40 IXTREME-MC-9600 systemd-udevd[9381]: failed to execute ‘/lib/udev/usb-db’ ‘usb-db /devices/pci0000:00/0000:00:10.2/usb4/4-2’: No such file or directory
Mar 23 18:16:40 IXTREME-MC-9600 systemd-udevd[9382]: failed to execute ‘/lib/udev/usb-db’ ‘usb-db /devices/pci0000:00/0000:00:10.2/usb4/4-2/4-2:1.0’: No such file or directoryChecking the /etc/udev/rules.d/55-Argyll.rules I found the following lines
# Set ID_VENDOR and ID_MODEL acording to VID and PID
#TEST==”/lib/udev/usb-db”, IMPORT{program}=”usb-db %p”
ENV{COLORD_SENSOR_KIND}==”*?”, ENV{ID_MODEL}==””, IMPORT{program}=”usb_id –export %p”
ENV{COLORD_SENSOR_KIND}==”*?”, ENV{ID_MODEL_FROM_DATABASE}==””, IMPORT{program}=”usb-db %p”is maybe this the problem? Wasn’t the old bug already solved in 2013?
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Displaycal gives me now other errors, here is the log file :
8:33:55,421 displaycal 3.5.1.0 2018-03-16T16:11:20.420275Z
18:33:55,440 Ubuntu 16.04 xenial x86_64
18:33:55,441 Python 2.7.12 (default, Dec 4 2017, 14:50:18)
18:33:55,441 [GCC 5.4.0 20160609]
18:33:55,442 ImportError: No module named faulthandler
18:33:55,660 wxPython 3.0.2.0 gtk2 (classic)
18:33:55,660 Encoding: UTF-8
18:33:55,660 File system encoding: UTF-8
18:33:55,908 Starting up…
18:33:56,111 SDL2: libSDL2-2.0.so.0
18:33:56,118 SDL2_mixer: libSDL2_mixer-2.0.so.0
18:33:56,125 Audio module: SDL 2.0
18:33:57,581 Enumerating display devices and communication ports…
18:33:57,583 /home/luigi/Downloads/Argyll_V2.0.0/bin
18:33:59,463 ArgyllCMS 2.0.0
18:33:59,466 …ok.
18:33:59,587 Checking video card gamma table access for display 1…
18:33:59,703 Dispwin: Warning – new_dispwin: Expected VideoLUT depth 8 doesn’t match actual
18:33:59,703 10
18:33:59,789 VideoLUT has 1024 entries, interpolating to 256
18:34:00,068 Dispwin: Warning – new_dispwin: Expected VideoLUT depth 8 doesn’t match actual
18:34:00,068 10
18:34:00,180 Dispwin: Warning – new_dispwin: Expected VideoLUT depth 8 doesn’t match actual
18:34:00,180 10
18:34:00,181 Verify: ‘test.cal’ IS loaded (discrepancy 0.0%)
18:34:00,293 Dispwin: Warning – new_dispwin: Expected VideoLUT depth 8 doesn’t match actual
18:34:00,293 10
18:34:00,294 …ok.
18:34:00,295 Initializing GUI…
18:34:00,531
18:34:05,280 …ok.
18:34:05,285 Ready.
18:34:05,521 Setting up scripting host at 127.0.0.1:15411
18:34:05,641 Check for application update…
18:34:05,725 DisplayCAL is up-to-date.
18:34:05,789 ArgyllCMS is up-to-date.I hope it makes sense to you.
rgds Luigi
Checking the /etc/udev/rules.d/55-Argyll.rules I found the following lines
# Set ID_VENDOR and ID_MODEL acording to VID and PID
#TEST==”/lib/udev/usb-db”, IMPORT{program}=”usb-db %p”
ENV{COLORD_SENSOR_KIND}==”*?”, ENV{ID_MODEL}==””, IMPORT{program}=”usb_id –export %p”
ENV{COLORD_SENSOR_KIND}==”*?”, ENV{ID_MODEL_FROM_DATABA SE}==””, IMPORT{program}=”usb-db %p”is maybe this the problem? Wasn’t the old bug already solved in 2013?
That’s a red herring.
Displaycal gives me now other errors, here is the log file
There are no errors in the log.
Have you actually tried using your Spyder5?
Of course.
In the Display & Instrument window, the instrument name is grey. The measurement area looks strange and if you start the calibration it freezes on the third color (grey) and you have to power off the computer to get out of it. I think the problem is the old Argyll bug using the obsolete usb-db instead of the hwdb. I posted the argyll error on the ubutu/lubuntu forum a few weeks ago and until now there are 0 views.
Thanks for your help. rgds Luigi
if you start the calibration it freezes on the third color (grey)
That indicates to me that the instrument is working fine though (instrument access would fail instantly).
I think the problem is the old Argyll bug using the obsolete usb-db instead of the hwdb.
No, as I said that error is unrelated and can be ignored (the usb-db fallback could probably be removed, but that is ArgyllCMS territory and it wouldn’t change anything other than getting rid of a misleadimg syslog entry).
