#6167 (Bug) dispcal: Error – new_disprd() failed with ‘Instrument Access Failed’ on LMDE2

+1 0

New
Component:
Created by

Last modified


Displaycal fails the calibration because of failure to access instrument. I'm running Linux Mint Debian Edition 2. I'm using Datcolor Spyder 5.

/etc/udev/rules.d $ ls
55-Argyll.rules 61-debian-system-adjustments-polling.rules
60-vboxdrv.rules 70-persistent-net.rules

55-Argyll.rules is empty

Please please please.. help me resolve this issue. I've had it running fine on regular mint flavor, but ubuntu -16.4 is too unstable for me and does not do what I need it to do. I've had to change to a debian-base. Regular debian is too old for some of my other software needs. 31st of march I'm bicycle touring around the world and can't wait for Debian Stretch to become stable. Stretch-testing has crashed. I really want and need it to work with LMDE2.


DisplayCAL (text/plain | 2017-03-10 13:27:16)
DisplayCAL (text/plain | 2017-03-13 11:05:53)


19 thoughts on “dispcal: Error – new_disprd() failed with ‘Instrument Access Failed’ on LMDE2”

  1. I used gdebi to install displaycal_3.2.4.0-1_amd64.deb .. I should be running Argyll_V1.9.2  .. I’ve tried to install the Argyll CMS instrument configuration file via the menues i.e. Tools > instrument .. The tab is greyed out and unresponsive.

    How do I proceed? Is it a kernel-matter? I had the same issue with Mint 17.2 .. I didn’t with 18.1, but the Ubuntu 16.04-base is a nightmare on my hardware and crashes software.

    I’ve considered installing 16.04 in a VM to make a profile that I’ll export to my main OS.. Would that be doable and a viable alternative to configuration-troubleshooting?

    Was the error-logs succesfully uploaded?

    If not, here goes:

    12:59:10,054 Calibrate & profile
    12:59:10,200
    12:59:10,212 ——————————————————————————–
    12:59:10,213 Session log: LTN140KT03401 #1 2017-03-10 12-59 2.2 F-S XYZLUT+MTX
    12:59:10,213
    12:59:10,213 Working directory:
    12:59:10,214 /
    12:59:10,214 tmp/
    12:59:10,214 DisplayCAL-qx3xfJ/
    12:59:10,215
    12:59:10,216 Command line:
    12:59:10,216 dispcal
    12:59:10,217 -v2
    12:59:10,217 -d1
    12:59:10,217 -c1
    12:59:10,218 -yn
    12:59:10,219 -P0.500484027106,0.501501501502,1.5
    12:59:10,219 -ql
    12:59:10,219 -t
    12:59:10,220 -g2.2
    12:59:10,220 -f1.0
    12:59:10,221 -k0.0
    12:59:10,221 -A4.0
    12:59:10,221 -b
    12:59:10,222 ‘LTN140KT03401 #1 2017-03-10 12-59 2.2 F-S XYZLUT+MTX’
    12:59:10,222
    12:59:10,232 DisplayCAL: Starting interaction with subprocess
    12:59:10,720 Setting up the instrument
    12:59:10,723 usb_open_port: open ‘/dev/bus/usb/001/006’ config 1 failed (-1) (Permissions ?)
    12:59:10,724 usb_open_port: open ‘/dev/bus/usb/001/006’ config 1 failed (-1) (Permissions ?)
    12:59:10,725 dispcal: Error – new_disprd() failed with ‘Instrument Access Failed’
    12:59:10,725
    12:59:10,729 DisplayCAL: Reached EOF (OK)
    12:59:10,831 …aborted.

  2. 55-Argyll.rules is empty

    That should not be the case.

    I’ve tried to install the Argyll CMS instrument configuration file via the menues i.e. Tools > instrument .. The tab is greyed out and unresponsive.

    This’ll only be available if using the “official” binaries from argyllcms.com, and there are no installed 55-Argyll.rules files in /etc/udev/rules.d and /lib/udev/rules.d

    In case there’s already 55-Argyll.rules in any of the above mentioned locations, they need to be uninstalled first (uninstallation again only is available when using the binaries from argyllcms.com)

    I’ve considered installing 16.04 in a VM to make a profile that I’ll export to my main OS.. Would that be doable and a viable alternative to configuration-troubleshooting?

    No access to the videoLUT when running in a VM means calibration can’t be used. I’d recommend fixing the underlying (permissions) issue instead by uninstalling/re-installing the instrument configuration (udev rules) in the way described above.

  3. Hi Florian,

    thank you for answering.

    I installed Displaycal from a .deb file from your website. I used gdebi for this. Displaycal installed ArgyllCMS automatically the first time it ran. Please link me to instructions how to install Argyll-binaries. I would think that’s what displaycal would do? There’s a 55-Argyll.rules file in /etc/udev/rules.d directory, but when I ‘sudo nano’ it, it is empty. There is no 55-Argyll.rules at /lib/udev/rules.d .. I tried using displaycal to uninstall the instrument configuration file. The file is still around, yet empty. Should I use CLI and purge it? Do I need to uninstall ArgyllCMS and install it a different way? If so, please guide me in doing so.

    I’m despairing over this issue. I had displaycal going in 16.04, but else it was rubbish. Now I have everything else working as needed, but not display calibration. Which I really need for video and photo editing on my laptop.

    My CLI-chops are not up to the task of fixing this issue with the suggestions you’ve given me alone. But. I’m willing to spend the time and make this work if at all possible, but please point me in the right direction. What precisely do I need to do first.

    Best

    Ronald

     

  4. Displaycal installed ArgyllCMS automatically the first time it ran.

    Good, that means you should be set.

    I tried using displaycal to uninstall the instrument configuration file. The file is still around, yet empty

    Is something holding the file in use (possibly the sudo instance of nano that you started)?

    Should I use CLI and purge it?

    Yes, try that. At the very least you’ll get an error detailing why the file couldn’t be removed if it’s still locked.

    After the file is removed, restart DisplayCAL. The “Install Argyll instrument configuration” menu item should become available.

    1. when both files are deleted, the “install Argyll instrument …” button is available. After a Displaycal restart I tried it, but it fails with a empty pop-up with a ‘no entry’ traffic sign and no text. That’s after I typed my password.

    1. 17:03:15,952 displaycal 3.2.4.0 2017-02-19T17:02:17.634864Z
      17:03:15,955 LinuxMint 2 betsy x86_64
      17:03:15,955 Python 2.7.9 (default, Jun 29 2016, 13:08:31)
      17:03:15,955 [GCC 4.9.2]
      17:03:15,955 wxPython 3.0.1.1 gtk2 (classic)
      17:03:15,956 Encoding: UTF-8
      17:03:15,956 File system encoding: UTF-8
      17:03:15,956 Connection to 127.0.0.1:15411 failed: [Errno 111] Connection refused
      17:03:16,237 Starting up…
      17:03:16,421 Audio module: pygame 1.9.1release
      17:03:17,966 Enumerating display devices and communication ports…
      17:03:17,967 /home/ronald/Downloads/Argyll_V1.9.2/bin
      17:03:19,662 Argyll CMS 1.9.2
      17:03:19,667 …ok.
      17:03:19,730 Checking video card gamma table access for display 1…
      17:03:19,896 Verify: ‘test.cal’ IS loaded (discrepancy 0.0%)
      17:03:19,940 …ok.
      17:03:19,941 Initializing GUI…
      17:03:20,054
      17:03:21,550 …ok.
      17:03:21,552 Ready.
      17:03:21,900 Setting up scripting host at 127.0.0.1:15411
      17:03:21,958 Check for application update…
      17:03:22,103 DisplayCAL is up-to-date.
      17:03:22,305 Argyll CMS is up-to-date.
      17:03:32,841 Authentification
      17:03:35,847 ——————————————————————————–
      17:03:35,848 Working directory:
      17:03:35,850 /
      17:03:35,850 etc/
      17:03:35,851 udev/
      17:03:35,851 rules.d/
      17:03:35,851
      17:03:35,851 Command line:
      17:03:35,853 cp
      17:03:35,853 -f
      17:03:35,854 /usr/share/DisplayCAL/usb/55-Argyll.rules
      17:03:35,854 55-Argyll.rules
      17:03:35,854
      17:03:35,866 DisplayCAL: Waiting for EOF
      17:03:35,929 Password:
      17:03:35,936 cp: not writing through dangling symlink ‘55-Argyll.rules’
      17:03:35,936 DisplayCAL: Reached EOF (OK)
      17:03:36,024
      17:03:36,037 …aborted.
      17:03:36,037 2017-03-12 17:03:36,066

  5. I ran ‘sudo rm -rf /etc/udev/rules.d/55-Argyll.rules’

    .. then I ran sudo unlink /etc/udev/rules.d/55-Argyll.rules

    Maybe that was a mistake to improvise.. Now, Tools > Instrument shows a black ‘uninstall *” which does nothing when pressed.. The ‘Install *’ button is greyed out.

    I really appreciate your help. I’m somewhat stressed out because of time-pressure on this bike-expeditions-thing and I’m trying stuff while I avait your answers. I hope I didn’t set this whole thing back because of it. If so, then sorry. I don’t want to be disrespectful of your time and help.

    Latest log:

    17:13:05,056 DisplayCAL: Starting interaction with subprocess
    17:13:05,646 Setting up the instrument
    17:13:05,671 icoms_set_ser_port: tcgetattr on ‘/dev/ttyS0’ failed with 3 (Input/output error)
    17:13:05,673 icoms_set_ser_port: tcgetattr on ‘/dev/ttyS0’ failed with 3 (Input/output error)
    17:13:05,748 dispcal: Error – new_disprd() failed with ‘Instrument Access Failed’
    17:13:05,749
    17:13:05,750 DisplayCAL: Reached EOF (OK)
    17:13:05,851 …aborted.

    1. Later still:

      17:27:14,065 DisplayCAL: Starting interaction with subprocess
      17:27:14,568 Setting up the instrument
      17:27:14,571 usb_open_port: open ‘/dev/bus/usb/004/003’ config 1 failed (-1) (Permissions ?)
      17:27:14,571 usb_open_port: open ‘/dev/bus/usb/004/003’ config 1 failed (-1) (Permissions ?)
      17:27:14,572 dispcal: Error – new_disprd() failed with ‘Instrument Access Failed’
      17:27:14,573
      17:27:14,577 DisplayCAL: Reached EOF (OK)
      17:27:14,679 …aborted.

  6. Maybe that was a mistake to improvise.. Now, Tools > Instrument shows a black ‘uninstall *” which does nothing when pressed.. The ‘Install *’ button is greyed out.

    When you do changes on the udev rule files outside of DisplayCAL, you have to restart it again to detect the changes.

  7. Hi,

    so.. I reinstalled, rebooted, and ran on the same errors. Made the ‘unlink’ command, which took care of one error message. It let me install Argyll CMS instrument configuration files. I should be back to a default installation. It faults out just like before. Tried reinstalling Argyll-conf.. no changes.

    Attachment:
  8. Hi Florian..

    I’m still stuck on this issue. I’m biking around Germany with a useless piece of electronics in my pannier. Please can you guide me in the right direction to how to resolve this issue?

    I had a similar problem with Mint 17.2 which was resolved out of the box with 18.1. Unfortunately ubuntu 16.04 as a base is not an option. Is there reason to believe that this is a linux kernel issue and would resolve itself when Debian Stretch becomes stable and the base for LMDE?

    1. Please can you guide me in the right direction to how to resolve this issue?

      Sorry, I do not know what to suggest. I don’t think the problem is related to permissions anymore.

      I had a similar problem with Mint 17.2 which was resolved out of the box with 18.1.

      A bug in the USB stack probably. You could report it to the LMDE maintainers and see if something can be done.

      Is there reason to believe that this is a linux kernel issue and would resolve itself when Debian Stretch becomes stable and the base for LMDE?

      Impossible to tell without trying and seeing if it works.

Leave a Reply