Home › Forums › Help and Support › once more Error – new_disprd() failed with ‘Instrument Access Failed
- This topic has 9 replies, 3 voices, and was last updated 7 years, 3 months ago by Florian Höch.
-
AuthorPosts
-
2017-01-08 at 15:14 #5428
Hi Mr Höch,
i use Manjaro Linux and an Colorhug 2 .
In the past i’ve all things runns well. Now with DC 3.3.2 and Argyl 1.9.2 this error came.
i’ve checked ” /etc/udev/rules.d/55-Argyll.rules or /etc/udev/rules.d/69-cd-sensors.rules exist?”
no there are no such files.
what to do?
The firmware of CH2 is newest controled with fwupdmgr get-devices and it is known by the system > usb is o.k.
Sorry for my english. I’m an 55 years old German not realy often use my old schol english.
schorschi
2017-01-08 at 17:31 #5432Hello Mr Höch,
a few more informations:
— If i use the tools>report> verify calibration it runns all 100 sample points witout any error.
— “You may also have to check /lib/udev/rules.d/55-Argyll.rules or /lib/udev/rules.d/69-cd-sensors.rules2
they are there owned by root.
— now i run an new calibration it goes well for ~ 20′ and then the error commes again.
very myterious.
schorschi
- This reply was modified 7 years, 3 months ago by schorschi2.
2017-01-08 at 19:35 #5443Hi,
— now i run an new calibration it goes well for ~ 20′ and then the error commes again.
Hmm. This looks like an intermittent USB problem of some sort, or probably the ColorHug2 isn’t behaving as expected. Enable advanced options in the “Options” menu, and then enable Argyll debug output under “Options” -> “Advanced”. Run a new calibration. When it fails again, please attach the logfiles (menu “Tools” -> “Show log”). Thanks.
2017-01-09 at 20:05 #5462Hi Mr Höch
here is the File. It abortet after long time runing.
Attachments:
You must be logged in to view attached files.2017-01-09 at 23:22 #5469Thanks, I see you got a response from Graeme Gill on the colorhug-users mailinglist, and it is probably better to wait for Richard Hughes (ColorHug2 developer) to weigh in as well, as I will not be able to provide help directly if it’s (assumedly) a firmware problem of the CH2.
2017-01-15 at 6:09 #5532I am having the same problem with DisplayCAL 3.1.4 or 3.2.3 and dispcal(Argyll) 1.6.3 on open SUSE leap 42.2.
I see 55-Argyll.rules in /lib/udev/rules.d.
A couple of years ago i didn’t have any issue to use this software on SuSE linux 11 or 12.
Below is the log after error.
Any help would be appreciated.
21:46:59,106 Measure
21:46:59,124 ——————————————————————————–
21:46:59,124 Session log: DTP94 & HP LP2475w 2017-01-14 21-46-55.log
21:46:59,124
21:46:59,124 Working directory:
21:46:59,125 /
21:46:59,125 tmp/
21:46:59,125 DisplayCAL-BwYpLH/
21:46:59,126
21:46:59,126 Command line:
21:46:59,126 dispread
21:46:59,127 -v
21:46:59,127 -d1
21:46:59,127 -c1
21:46:59,128 -yl
21:46:59,128 -P0.499644633973,0.499272197962,1.49562682216
21:46:59,128 -Ib
21:46:59,128 -k
21:46:59,129 ‘DTP94 & HP LP2475w 2017-01-14 21-46-55.cal’
21:46:59,129 ‘DTP94 & HP LP2475w 2017-01-14 21-46-55’
21:46:59,129
21:46:59,140 DisplayCAL: Starting interaction with subprocess
21:46:59,329
21:46:59,366 Number of patches = 4
21:46:59,367 Setting up the instrument
21:47:00,397 dispread: Error – new_disprd failed with ‘Instrument Access Failed’
21:47:00,397
21:47:00,399 DisplayCAL: Reached EOF (OK)
21:47:00,500 …aborted.
21:57:28,264 Check for application update…
21:57:29,681 An update is available: DisplayCAL 3.2.3.0
21:57:34,921 An update is available: Argyll CMS 1.9.2- This reply was modified 7 years, 3 months ago by frozenpenguin.
2017-01-15 at 10:02 #5534dispcal(Argyll) 1.6.3
Argyll CMS 1.6.3 is over three years out of date. Please update to the latest version.
2017-01-15 at 22:33 #5537no differenace with Argll 1.9 either, the
same error.2017-01-16 at 5:56 #5538One more update.
It is kind of strange but it now works. I don’t know what fixed it.
Here is what I did.
- Installed Argyll 1.9.2 in /usr/local/bin
- Copied 55-Argyll.rules file to /etc/udev/rules.d. The same file was in /usr/lib/udev/rules.d before i copied and it is still there.
- Created a group ID ‘colord’ and added my user ID to it.
- Restarted my computer.
Still not clear what has fixed the issue.
2017-01-16 at 21:24 #5547Still not clear what has fixed the issue.
Possibly a combination of
Copied 55-Argyll.rules file to /etc/udev/rules.d. The same file was in /usr/lib/udev/rules.d before i copied and it is still there.
Created a group ID ‘colord’ and added my user ID to it. -
AuthorPosts