1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
|
<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<meta name="GENERATOR" content="Mozilla/4.73 [en] (WinNT; I)
[Netscape]">
<title>Argyll Installation on Linux</title>
</head>
<body>
<h1> <u>Installing the software on Linux with X11<br>
</u></h1>
<br>
You will need to unpack the downloaded file in the location you have
chosen to hold the executable files. Typically this might be in <span
style="font-style: italic;">/usr/local/</span>, or perhaps <span
style="font-style: italic;">$HOME/bin/</span>. You would then
unpack the files using <span style="font-weight: bold;">tar -zxf</span>
<span style="font-weight: bold;">archivename.tgz</span>, which will
create a directory <span style="font-weight: bold;">Argyll_VX.X.X</span>,
where X.X.X is the version number, and the executables will be in <span
style="font-weight: bold;">Argyll_VX.X.X/bin</span> You will also
have to configure your $PATH environment variable to give access to
the executables from your command line environment. The .tgz file
also contains several useful reference files (such as scanner chart
recognition templates, sample illumination spectrum etc.) in the ref
sub-directory, as well as all the current HTML documentation in a
doc sub-directory. You may want to copy things to more standard
locations such as /usr/local/bin, /usr/local/argyll/bin etc.,
depending on the conventions used on your system.<br>
<br>
<big style="color: rgb(51, 102, 255);"><span style="font-weight:
bold;"><a name="bell"></a>Note on the system bell:</span></big><br>
<br>
When reading strips using the Eye-One Pro or ColorMunki instrument,
the system bell is used to indicate when the instrument the ready to
be used, and to provide feedback on any problems. On some Linux
installations the system bell may be disabled. As well as checking
the terminal and GUI sound preferences, you may have to enable the
used of the PC speaker driver, which can be done by adding the
command <span style="font-weight: bold;">/sbin/modprobe pcspkr </span>to
the <span style="font-weight: bold;">/etc/rc.local</span> startup
script. You may also have to run <span style="font-weight: bold;">xset
b 100 1000 100</span> in your local setup, if you are running in
an X11 environment. You can check that the system bell is operating
by doing an "echo ^G", where ^G is ctrl-G.<br>
<br>
<big style="color: rgb(51, 102, 255);"><span style="font-weight:
bold;"><a name="multimonitor"></a>Note on X11 multi-monitor
setups:</span></big><br>
<br>
When working with a multi-monitor X11 configuration, note that you
will only be able to individually calibrate monitors if the
multi-window extension you are using (if any), supports access to
the individual screen Video LUT tables that are used for
calibration. The native X11 multi-screen addressing supports this,
as does the Xinerama extension, and XRandR V1.2.<br>
<br>
The proprietary NVidia TwinView and ATI MergeFB extensions do not
currently support access to the individual screen Video LUTs, so
calibration of each screen independently is impossible if either of
these extensions are running. You can switch to using Xinerama to
solve this problem, or you can try doing a calibration for the
screens that do have accessible Video LUTs with these proprietary
extensions, or ignore calibration and rely purely on display
profiling. Use the dispwin tool to figure out what works on your
system. The NVidia ATI binary drivers do not seem to properly
support XRandR V1.2 either, even though they claim to do so. You may
have to set the <span style="font-weight: bold;"></span><span
style="font-weight: bold;">ARGYLL_IGNORE_XRANDR1_2</span>
environment variable if the XRandR V1.2 extension is faulty.<br>
<br>
If these limitations trouble you, then as a valuable customer of
NVidia or AMD/ATI, perhaps you should contact them and urge them to
fix the problems with Video LUT access in their proprietary
multi-monitor extensions and XRandR implementation, bringing their
support for multi-monitors on X11 up to the same standards as other
operating systems. Ask them to add full and correct support for the
XRandR V1.2 extension.<br>
<br>
<big style="color: rgb(51, 102, 255);"><span style="font-weight:
bold;"><a name="VideoLUTs"></a>Fixing access to Video LUTs:</span></big><br>
<br>
Some users have noted that their default X11 installation doesn't
properly enable access to the video card Video Lookup Tables
(RAMDAC). The Video LUTs are used for display calibration purposes,
and a warning will be issues by the <span style="font-weight:
bold;">dispcal</span> and <span style="font-weight: bold;">dispread</span>
tools if there is a problem with this. Without access to the
VideoLUTs, you won't be able to use display calibration.<br>
<br>
The problem may be because certain X11 extensions aren't being
loaded by default. You may want to check that you have<br>
<br>
<big style="color: rgb(51, 102, 255);"><span style="font-weight:
bold;"></span></big> Load "extmod" <br>
<br>
in the appropriate (or any) section of
your Xorg.conf file, to allow the XF86Video LUT
extensions to function correctly.<br>
<br>
Another source of problems is if the display isn't configured with a
suitable visual. Typically for high quality color you need to be
using at least <span style="font-weight: bold;">24 bits</span> per
pixel (8 Bits for each of Red, Green and Blue channels), but more
importantly the number of entries in the the VideoLUTs needs to
match the depth of the screen. So if the VideoLUTs have 256 entries
per channel, then the screen must be using 8 bits per channel to
match. Or 64 entries and 6 bits. Or 4096 entries and 12 bits, etc.
Running "dispwin -D" may give some clues as to what the nature of
the problem is. You might have to look into your xorg.conf or XRANDR
setup, or on some distributions there will be some configuration
program that will let you choose the display configuration (ie. YaST
or SaX2 on openSUSE, etc.).<br>
<br>
<big style="color: rgb(51, 102, 255);"><span style="font-weight:
bold;"><a name="InstAccess"></a>Setting up instrument access:<br>
<br>
</span></big>By default most Linux based systems make devices
inaccessible to user mode programs, so it is necessary to make some
modification to your permissions so that Argyll tools are able to
access the Color Measurement Instruments. In order from newest to
oldest, the following sub-systems may need to be configured to
permit this:<br>
<br>
<a style="font-weight: bold;" href="#None">No device
configuration needed when running from the console:</a><span
style="font-weight: bold; text-decoration: underline;"><br>
<br>
</span> <a href="#None">Mandriva 2008.0 default
installation</a><br>
<br>
<h5> <a href="Installing_Linux.html#udev1">USB instruments
access using udev:</a></h5>
<a href="#udev1"></a> <a
href="Installing_Linux.html#udev1">Ubuntu 10.04</a><br>
<a href="Installing_Linux.html#udev1">Fedora
Core 8</a><br>
<a href="#udev1">Mandriva 2008.1</a><br>
<a href="#udev1">OpenSuSE 10.3</a><br>
<a href="#udev1">Ubuntu 7.1</a><br>
<a href="#udev1">Kubuntu 7.1</a><br>
<a href="#udev1">Debian 4.0</a><br>
<h5> <a href="#hotplug">USB instruments access using hotplug:</a></h5>
<a href="#hotplug">Red Hat 4.0</a><br>
<a href="Installing_Linux.html#hotplug">Fedora Core 4</a><br>
<a href="Installing_Linux.html#hotplug">Fedora Core 3</a><br>
<a href="Installing_Linux.html#hotplug">Fedora Core 2</a><br>
<br>
<h5> <span style="text-decoration: underline;"></span><a
href="#serial">Serial instrument access:</a></h5>
<a href="#serial">All</a><br>
<br>
<span style="font-weight: bold;">NOTE:</span> That <b>mtp-probe</b>
/ <span style="font-weight: bold;">libmtp</span> been known
to interfere with device access, particularly the Spyder 3 and
DTP94. Recent versions of the libmtp should ignore any instrument
marked as COLOR_MEASUREMENT_DEVICE by the
/etc/udev/rules.d/55-Argyll.rules file, but for older systems you
probably need to disable libmtp (look in the udev configuration).<br>
<br>
The <b>JETI</b> specbos <span style="font-weight: bold;">1211</span><span
style="font-weight: bold;"> </span>and <b>1201</b> makes use of
the <a href="http://www.ftdichip.com/Drivers/VCP.htm">FTDI Virtual
COM Port Drivers</a> (VCP), that should come with any recent
version of Linux.<br>
<br>
<span style="font-weight: bold;"></span>
<hr style="width: 100%; height: 2px;">
<h5><span style="color: rgb(204, 51, 204);"><a name="None"></a>No
device configuration needed:</span></h5>
Some systems have in place a security configuration such that
anyone logging in at the console of a machine has access to all the
local devices.<span style="color: rgb(204, 51, 204);"><span
style="font-weight: bold;"><br>
</span></span>
<h5><span style="color: rgb(204, 51, 204);"><a name="udev1"></a>USB
instruments access using udev:<br>
</span></h5>
<span style="color: rgb(204, 51, 204);"> </span>Most recent systems
use udev to manage device names and permissions, but by default
color instruments may not be accessible to normal system users.<br>
To solve this a udev rule file needs to be added that modifies the
group and permission of any Color Measurement Instruments, and you
may then need to add yourself to that group.<br>
<br>
<span style="font-weight: bold;"></span>Copy the file <span
style="font-weight: bold;">usb/</span><span style="font-weight:
bold;">55-Argyll.rules</span> from the binary or source
distribution into <span style="font-weight: bold;">/etc/udev/rules.d/55-Argyll.rules</span>
with owner root, group root, permissions 644.<br>
(There may already be a file that handles some of the color
instruments as part of your installation. You need to check though
that it is up to date.)<br>
<br>
If you are on an <span style="font-weight: bold;">older system</span>
that uses a udev that doesn't recognize the syntax used in
55-Argyll.rules, or that doesn't have rules to create the libusb
/dev/bus/usb/00X/00Y device entries, you should install the <span
style="font-weight: bold;">usb/45-Argyll.rules</span> file
instead.<br>
<br>
On recent systems the new rules file will be notices as soon as you
plug the instrument in again.<br>
On older systems you may need to run <b>/sbin/udevtrigger</b>,
<b>/sbin/udevcontrol reload_rules</b> or <span
style="font-weight: bold;">/sbin/udevstart</span> or reboot to get
the new file noticed.<br>
<br>
----------------- cut here ---------------------<br>
# udev rule to recognize instruments and make them accessible to
user applications.<br>
# Copy this to /etc/udev/rules.d/55-Argyll.rules<br>
<br>
# Skip all this to speed things up if it'a not a usb add.<br>
ACTION!="add", GOTO="argyll_rules_end"<br>
SUBSYSTEM!="usb", GOTO="argyll_rules_end"<br>
<br>
# Recognize the color measurement devices<br>
<br>
# Colorimtre HCFR<br>
ATTRS{idVendor}=="04db", ATTRS{idProduct}=="005b",
ENV{COLOR_MEASUREMENT_DEVICE}="1"<br>
<br>
<br>
# MonacoOPTIX (Same as i1 Display 1)<br>
ATTRS{idVendor}=="0670", ATTRS{idProduct}=="0001",
ENV{COLOR_MEASUREMENT_DEVICE}="1"<br>
<br>
<br>
# HueyL (not tested)<br>
ATTRS{idVendor}=="0765", ATTRS{idProduct}=="5001",
ENV{COLOR_MEASUREMENT_DEVICE}="1"<br>
<br>
# HueyL (not tested)<br>
ATTRS{idVendor}=="0765", ATTRS{idProduct}=="5010",
ENV{COLOR_MEASUREMENT_DEVICE}="1"<br>
<br>
# i1Display 3<br>
ATTRS{idVendor}=="0765", ATTRS{idProduct}=="5020",
ENV{COLOR_MEASUREMENT_DEVICE}="1"<br>
<br>
# ColorMunki Smile<br>
ATTRS{idVendor}=="0765", ATTRS{idProduct}=="6003",
ENV{COLOR_MEASUREMENT_DEVICE}="1"<br>
<br>
# DTP20<br>
ATTRS{idVendor}=="0765", ATTRS{idProduct}=="d020",
ENV{COLOR_MEASUREMENT_DEVICE}="1"<br>
<br>
# DTP92Q (not tested)<br>
ATTRS{idVendor}=="0765", ATTRS{idProduct}=="d092",
ENV{COLOR_MEASUREMENT_DEVICE}="1"<br>
<br>
# DTP94<br>
ATTRS{idVendor}=="0765", ATTRS{idProduct}=="d094",
ENV{COLOR_MEASUREMENT_DEVICE}="1"<br>
<br>
<br>
# i1Pro<br>
ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2000",
ENV{COLOR_MEASUREMENT_DEVICE}="1"<br>
<br>
# i1Monitor<br>
ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2001",
ENV{COLOR_MEASUREMENT_DEVICE}="1"<br>
<br>
# i1Display<br>
ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2003",
ENV{COLOR_MEASUREMENT_DEVICE}="1"<br>
<br>
# i1 io table (not tested)<br>
ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2004",
ENV{COLOR_MEASUREMENT_DEVICE}="1"<br>
<br>
# Huey<br>
ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2005",
ENV{COLOR_MEASUREMENT_DEVICE}="1"<br>
<br>
# i1 iSis (not tested)<br>
ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2006",
ENV{COLOR_MEASUREMENT_DEVICE}="1"<br>
<br>
# ColorMunki<br>
ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2007",
ENV{COLOR_MEASUREMENT_DEVICE}="1"<br>
<br>
<br>
# Spyder 1<br>
ATTRS{idVendor}=="085c", ATTRS{idProduct}=="0100",
ENV{COLOR_MEASUREMENT_DEVICE}="1"<br>
<br>
# Spyder 2<br>
ATTRS{idVendor}=="085c", ATTRS{idProduct}=="0200",
ENV{COLOR_MEASUREMENT_DEVICE}="1"<br>
<br>
# Spyder 3<br>
ATTRS{idVendor}=="085c", ATTRS{idProduct}=="0300",
ENV{COLOR_MEASUREMENT_DEVICE}="1"<br>
<br>
# Spyder 4<br>
ATTRS{idVendor}=="085c", ATTRS{idProduct}=="0400",
ENV{COLOR_MEASUREMENT_DEVICE}="1"<br>
<br>
<br>
# ColorHug, old and new<br>
ATTRS{idVendor}=="04d8", ATTRS{idProduct}=="f8da",
ENV{COLOR_MEASUREMENT_DEVICE}="1"<br>
ATTRS{idVendor}=="273f", ATTRS{idProduct}=="1001",
ENV{COLOR_MEASUREMENT_DEVICE}="1"<br>
<br>
<br>
# Let udev-acl manage these devices, if it's available<br>
TEST=="/var/run/ConsoleKit/database",
ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1"<br>
<br>
# Otherwise, restrict access to members of the plugdev group,<br>
# which the user may have to add to the system.<br>
ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}!="*?",
MODE="660", GROUP="plugdev"<br>
<br>
# Set ID_VENDOR and ID_MODEL acording to VID and PID<br>
IMPORT{program}="usb-db %p"<br>
<br>
LABEL="argyll_rules_end"<br>
----------------- cut here ---------------------<br>
<br>
(You may want to refer to <a
href="http://reactivated.net/writing_udev_rules.html">this
document</a> for more guidance on modifying udev rules, as well as
<a
href="http://www.google.com/search?hl=en&q=man+udev&btnG=Search&meta=&aq=f&oq=">this</a>.)<br>
<br style="font-weight: bold;">
<span style="font-weight: bold;">YOU THEN MAY NEED TO:</span><br>
<br>
If your system is <span style="font-weight: bold;">not</span> using
the new ACL to manage device access for console users (the file <span
style="font-weight: bold;">/lib/udev/udev-acl</span> doesn't exist
on your system), then you will <span style="text-decoration:
underline;">need to add</span> yourself to the <span
style="font-weight: bold;">plugdev</span> group, if you are not
already a member of it. You can do this either by using a "Users and
Groups" system administration tool, or on the command line running
as root:<br>
<br>
sudo usermod -a -G plugdev yourusernamehere<br>
<br>
or<br>
su root<br>
usermod -a -G plugdev yourusernamehere<br>
<br>
(If the usermod program isn't found as root, it might be in
/usr/sbin, ie. use /usr/sbin/usermod .... etc.<br>
If usermod doesn't recognize the -a flag try "usermod -A
plugdev yourusernamehere".<br>
If this doesn't work you will have to run "id yourusername" to
list the current supplemental<br>
groups, and add them plus plugdev using just "usermod -G
group1,group2,... yourusername")<br>
<br>
You may find that the <span style="font-weight: bold;">plugdev</span>
group doesn't exist on your system, and if so you will need to
create it:<br>
<br>
sudo groupadd -r plugdev<br>
<br>
and then add yourself to the plugdev group.<br>
<br>
You may have to log out and then in again for the groups to become
effective.<br>
<br>
You can check whether the instrument is being recognized and set to
the plugdev group by comparing the output of <span
style="font-weight: bold;">ls -l -R /dev/bus/usb</span> without
and then with the instrument plugged in.<br>
<br>
You can test whether your instrument is accessible by plugging it in
and then running "spotread -?" and looking for it listed after the <span
style="font-weight: bold;">-c</span> option.<br>
<span style="font-weight: bold;"></span>
<h5><span style="color: rgb(204, 51, 204);"><a name="hotplug"></a>USB
instruments
access using hotplug:<br>
</span></h5>
Under <span style="font-weight: bold;">much older versions of Linux</span>,
you should look into the hotplug system configuration for USB
devices. You know you are running this because the <span
style="font-weight: bold;">/etc/hotplug</span> directory exists on
your system.<br>
<br>
Assuming we want to configure for all Argyll supported USB
instruments, copy the file <span style="font-weight: bold;">usb/</span><span
style="font-weight: bold;">Argyll.usermap</span> from the binary
or source distribution into <span style="font-weight: bold;">/etc/hotplug/usb/Argyll.usermap</span>
with owner root, group root, permissions 644.<span
style="font-weight: bold;"></span><br>
<br>
----------------- cut here ---------------------<br>
# hotplug device mapping to handling script.<br>
# Copy this to /etc/hotplug/usb/Argyll.usermap<br>
#<br>
# Detect instruments by their USB VID and PID<br>
#<br>
# DTP20<br>
Argyll 0x0003 0x0765 0xd020 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00
0x00 0x00000000<br>
#<br>
# DTP92Q - not tested<br>
Argyll 0x0003 0x0765 0xd092 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00
0x00 0x00000000<br>
#<br>
# DTP94<br>
Argyll 0x0003 0x0765 0xd094 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00
0x00 0x00000000<br>
#<br>
# MonacoOPTIX (Same as i1 Display 1)<br>
Argyll 0x0003 0x0670 0x0001 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00
0x00 0x00000000<br>
#<br>
# i1 Display<br>
Argyll 0x0003 0x0971 0x2003 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00
0x00 0x00000000<br>
#<br>
# i1 Display 3<br>
Argyll 0x0003 0x0765 0x5020 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00
0x00 0x00000000<br>
#<br>
# i1 Monitor<br>
Argyll 0x0003 0x0971 0x2001 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00
0x00 0x00000000<br>
#<br>
# i1 Pro<br>
Argyll 0x0003 0x0971 0x2000 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00
0x00 0x00000000<br>
#<br>
# ColorMunki<br>
Argyll 0x0003 0x0971 0x2007 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00
0x00 0x00000000<br>
#<br>
# ColorMunki Smile<br>
Argyll 0x0003 0x0765 0x6003 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00
0x00 0x00000000<br>
#<br>
# Colorimtre HCFR<br>
Argyll 0x0003 0x04DB 0x005B 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00
0x00 0x00000000<br>
#<br>
# Spyder 2<br>
Argyll 0x0003 0x085C 0x0200 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00
0x00 0x00000000<br>
#<br>
# Spyder 3<br>
Argyll 0x0003 0x085C 0x0300 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00
0x00 0x00000000<br>
#<br>
# Spyder 4<br>
Argyll 0x0003 0x085C 0x0400 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00
0x00 0x00000000<br>
#<br>
# Huey<br>
Argyll 0x0003 0x0971 0x2005 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00
0x00 0x00000000<br>
#<br>
# ColorHug<br>
Argyll 0x0003 0x04D8 0xF8DA 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00
0x00 0x00000000<br>
Argyll 0x0003 0x273F 0x1001 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00
0x00 0x00000000<br>
----------------- cut here ---------------------<br>
<br>
(For even older versions, append the lines above to <span
style="font-weight: bold;">/etc/hotplug/usb.usermap</span>, and
you may have to run <span style="font-weight: bold;">update-usb.usermap</span>)<br>
<br>
Then copy the file <span style="font-weight: bold;">usb/</span><span
style="font-weight: bold;">Argyll</span> from the binary or source
distribution into <span style="font-weight: bold;">/etc/hotplug/usb/Argyll</span>
with owner root, group root, permissions 744.<span
style="font-weight: bold;"></span><br>
<br>
----------------- cut here ---------------------<br>
#!/bin/sh<br>
# Copy to /etc/hotplug/usb/Argyll<br>
#<br>
# Argyll hotplug script. Adds the USB devices to the plugdev group.<br>
if [ "${ACTION}" = "add" ] && [ -f "${DEVICE}" ]<br>
then<br>
chgrp plugdev "${DEVICE}"<br>
chmod 660 "${DEVICE}"<br>
fi<br>
----------------- cut here ---------------------<br>
<br>
<span style="font-weight: bold;">YOU THEN NEED TO:</span><br>
<br>
You will then <span style="text-decoration: underline;">need to add</span>
yourself to the <span style="font-weight: bold;">plugdev</span>
group, if you are not already a member of it. You can do this either
by using a "Users and Groups" system administration tool, or on the
command line running as root:<br>
<br>
sudo usermod -a -G plugdev yourusernamehere<br>
<br>
or<br>
su root<br>
usermod -a -G plugdev yourusernamehere<br>
<br>
<br>
(If the usermod program isn't found as root, it might be in
/usr/sbin, ie. use /usr/sbin/usermod .... etc.<br>
If usermod doesn't recognize the -a flag try "usermod -A
plugdev yourusernamehere".<br>
If this doesn't work you will have to run "id yourusername" to
list the current suplemental<br>
groups, and add plugdev using just "usermod -G
group1,group2,... yourusername")<br>
<br>
You may find that the <span style="font-weight: bold;">plugdev</span>
group doesn't exist on your system, and if so you will need to
create it:<br>
<br>
sudo groupadd -r plugdev<br>
<br>
and then add youself to the plugdev group.<br>
<br>
You may have to log out and then in again for the groups to become
effecive.<br>
<br>
You can test whether your instrument is accessible by plugging it in
and then running "spotread -?" and looking for it listed after the <span
style="font-weight: bold;">-c</span> option.<br>
<span style="font-weight: bold;"></span> <br>
<h5><span style="color: rgb(204, 51, 204);"><a name="serial"></a>Serial
instruments
access:</span><br>
</h5>
If you have a serial instrument then you may find that by default
you don't have permission to access the serial ports or a Serial to
USB adapter. Most systems make the serial ports available to any
user in the <span style="font-weight: bold;">tty</span> and <span
style="font-weight: bold;">uucp </span>group, so the best way of
getting access to the serial ports is to add yourself to those
groups. You can do this either by using a "Users and Groups" system
administration tool, or on the command line using "usermod":<br>
<br>
su root<br>
usermod -a -G tty,uucp yourusernamehere<br>
<br>
or<br>
<br>
sudo usermod -a -G tty,uucp yourusernamehere<br>
<br>
(If the usermod program isn't found as root, it might be in
/usr/sbin, ie. use /usr/sbin/usermod .... etc.<br>
If usermod doesn't recognize the -a flag try "usermod -A
plugdev yourusernamehere".<br>
If this doesn't work you will have to run "id yourusername" to
list the current suplemental<br>
groups, and add a tty or uucp group using just "usermod -G
group1,group2,... yourusername")<br>
<br>
You may have to log out and then in again for the group to become
effecive.<span style="font-weight: bold;"><br>
</span>
<p> <br>
<br>
<br>
<br>
<br>
</p>
</body>
</html>
|
