From 094535c010320967639e8e86f974d878e80baa72 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=B6rg=20Frings-F=C3=BCrst?= Date: Fri, 1 May 2015 16:13:57 +0200 Subject: Imported Upstream version 1.7.0 --- doc/Installing_Linux.html | 362 +++++++++++++++------------------------------- 1 file changed, 113 insertions(+), 249 deletions(-) (limited to 'doc/Installing_Linux.html') diff --git a/doc/Installing_Linux.html b/doc/Installing_Linux.html index 608ff7d..a26d64c 100644 --- a/doc/Installing_Linux.html +++ b/doc/Installing_Linux.html @@ -2,9 +2,9 @@ + charset=windows-1252"> + charset=windows-1252"> Argyll Installation on Linux @@ -46,6 +46,11 @@ + + + + + the /etc/rc.local startup script. You may also have to run xset @@ -53,6 +58,11 @@ + + + + + b 100 1000 100 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.
@@ -172,45 +182,88 @@ probably need to disable libmtp (look in the udev configuration).

The JETI specbos 1211 and 1201 makes use of - the FTDI Virtual - COM Port Drivers (VCP), that should come with any recent - version of Linux.
+ style="font-weight: bold;"> and 1201, and the Klien + + + + + K10A makes use of the FTDI Virtual COM + Port Drivers (VCP), that should come with any recent version + of Linux. You may have to add yourself to the dialout group + to be able to open the instrument.

No device configuration needed:
- Some systems have in place  a security configuration such that + A few 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.
USB - instruments access using udev:
+ instruments access using udev with existing /etc/udev/rules.d or + /usr/lib/udev/rules.d/69-cd-sensors.rules + file.
- Most recent systems - use udev to manage device names and permissions, but by default - color instruments may not be accessible to normal system users.
+ Recent Fedora based + systems include Gnome Color Manager, which comes with a udev rule + for color instruments. You can check this by looking for the /etc/udev/rules.d or in /usr/lib/udev/rules.d/69-cd-sensors.rules + file. If this exists and is up to date enough to include the + instrument you want to use, then all you have to do is add yourself + to the colord group, ie:
+
+    sudo usermod -a -G colord $USER
+
+ If the 69-cd-sensors.rules file is out of date and does not + include the latest instruments supported by Argyll, then the + simplest thing to do is to replace the 69-cd-sensors.rules + file with the usb/55-Argyll.rules. You will need + to do this as root, and set the owner as root, group root, + permissions 644. You may need to re-plug in your instrument to get + changes to the udev rules recognised.
+
USB + instruments access using udev, with no existing /etc/udev/rules.d or /usr/lib/udev/rules.d/69-cd-sensors.rules + file.
+
+ Most recent systems use udev to manage device names and permissions, + but by default color instruments may not be accessible to normal + system users.
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.

+ First check whether other rules are in /etc/udev/rules.d or in /usr/lib/udev/rules.d, + and use the appropriate directory.
+ (You may also want to check in that directory whether + 55-Argyll.rules or some other .rules file that is setup to enable + color instruments already exists in that directory.)
+
Copy the file usb/55-Argyll.rules from the binary or source distribution into /etc/udev/rules.d/55-Argyll.rules - with owner root, group root, permissions 644.
- (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.)
+ or /usr/lib/udev/rules.d/55-Argyll.rules + + + + (as appropriate) with owner root, group root, + permissions 644.

If you are on an older system 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 usb/45-Argyll.rules file - instead.
+ style="font-weight: bold;">usb/45-Argyll.rules file instead + - See below.

On recent systems the new rules file will be notices as soon as you plug the instrument in again.
@@ -221,128 +274,15 @@ + + + + + /sbin/udevcontrol reload_rules or  /sbin/udevstart or reboot to get the new file noticed.

- ----------------- cut here ---------------------
- # udev rule to recognize instruments and make them accessible to - user applications.
- # Copy this to /etc/udev/rules.d/55-Argyll.rules
-
- # Skip all this to speed things up if it'a not a usb add.
- ACTION!="add", GOTO="argyll_rules_end"
- SUBSYSTEM!="usb", GOTO="argyll_rules_end"
-
- # Recognize the color measurement devices
-
- # Colorimtre HCFR
- ATTRS{idVendor}=="04db", ATTRS{idProduct}=="005b", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
-
- # MonacoOPTIX (Same as i1 Display 1)
- ATTRS{idVendor}=="0670", ATTRS{idProduct}=="0001", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
-
- # HueyL (not tested)
- ATTRS{idVendor}=="0765", ATTRS{idProduct}=="5001", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # HueyL (not tested)
- ATTRS{idVendor}=="0765", ATTRS{idProduct}=="5010", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # i1Display 3
- ATTRS{idVendor}=="0765", ATTRS{idProduct}=="5020", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # ColorMunki Smile
- ATTRS{idVendor}=="0765", ATTRS{idProduct}=="6003", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # DTP20
- ATTRS{idVendor}=="0765", ATTRS{idProduct}=="d020", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # DTP92Q (not tested)
- ATTRS{idVendor}=="0765", ATTRS{idProduct}=="d092", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # DTP94
- ATTRS{idVendor}=="0765", ATTRS{idProduct}=="d094", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
-
- # i1Pro
- ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2000", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # i1Monitor
- ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2001", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # i1Display
- ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2003", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # i1 io table (not tested)
- ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2004", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # Huey
- ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2005", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # i1 iSis (not tested)
- ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2006", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # ColorMunki
- ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2007", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
-
- # Spyder 1
- ATTRS{idVendor}=="085c", ATTRS{idProduct}=="0100", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # Spyder 2
- ATTRS{idVendor}=="085c", ATTRS{idProduct}=="0200", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # Spyder 3
- ATTRS{idVendor}=="085c", ATTRS{idProduct}=="0300", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # Spyder 4
- ATTRS{idVendor}=="085c", ATTRS{idProduct}=="0400", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
-
- # ColorHug, old and new
- ATTRS{idVendor}=="04d8", ATTRS{idProduct}=="f8da", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
- ATTRS{idVendor}=="273f", ATTRS{idProduct}=="1001", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
-
- # Let udev-acl manage these devices, if it's available
- TEST=="/var/run/ConsoleKit/database", - ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1"
-
- # Otherwise, restrict access to members of the plugdev group,
- # which the user may have to add to the system.
- ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}!="*?", - MODE="660", GROUP="plugdev"
-
- # Set ID_VENDOR and ID_MODEL acording to VID and PID
- IMPORT{program}="usb-db %p"
-
- LABEL="argyll_rules_end"
- ----------------- cut here ---------------------
-
(You may want to refer to this document for more guidance on modifying udev rules, as well as @@ -352,50 +292,48 @@ href="http://www.google.com/search?hl=en&q=man+udev&btnG=Search&meta YOU THEN MAY NEED TO:

If your system is not using - the new ACL to manage device access for console users (the file /lib/udev/udev-acl doesn't exist - on your system), then you will need to add yourself to the plugdev 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:
+ the ACL to manage device access for console users (the file /var/run/ConsoleKit/database + doesn't exist on your system), then you will need to add yourself to + the colord 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:

-    sudo usermod -a -G plugdev yourusernamehere
+    sudo usermod -a -G colord $USER

or
    su root
-     usermod -a -G plugdev yourusernamehere
+     usermod -a -G colord $USER

(If the usermod program isn't found as root, it might be in /usr/sbin, ie. use /usr/sbin/usermod .... etc.
 If usermod doesn't recognize the -a flag try "usermod -A - plugdev yourusernamehere".
+ colord $USER".
 If this doesn't work you will have to run "id yourusername" to list the current supplemental
-  groups, and add them plus plugdev using just "usermod -G +  groups, and add them plus colord using just "usermod -G group1,group2,... yourusername")

- You may find that the plugdev - group doesn't exist on your system, and if so you will need to - create it:
+ You may find that the colord group doesn't exist on + your system, and if so you will need to create it:

-   sudo groupadd -r plugdev
+   sudo groupadd -r colord

- and then add yourself to the plugdev group.
+ and then add yourself to the colord group.

You may have to log out and then in again for the groups to become effective.

You can check whether the instrument is being recognized and set to - the plugdev group by comparing the output of ls -l -R /dev/bus/usb without and then with the instrument plugged in.

You can test whether your instrument is accessible by plugging it in and then running "spotread -?" and looking for it listed after the -c option.
-  
USB instruments @@ -404,6 +342,11 @@ instruments + + + + + access using hotplug:
Under much older versions of Linux, @@ -419,78 +362,6 @@ instruments with owner root, group root, permissions 644.

-     ----------------- cut here ---------------------
- # hotplug device mapping to handling script.
- # Copy this to /etc/hotplug/usb/Argyll.usermap
- #
- # Detect instruments by their USB VID and PID
- #
- # DTP20
- Argyll 0x0003 0x0765 0xd020 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # DTP92Q - not tested
- Argyll 0x0003 0x0765 0xd092 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # DTP94
- Argyll 0x0003 0x0765 0xd094 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # MonacoOPTIX (Same as i1 Display 1)
- Argyll 0x0003 0x0670 0x0001 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # i1 Display
- Argyll 0x0003 0x0971 0x2003 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # i1 Display 3
- Argyll 0x0003 0x0765 0x5020 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # i1 Monitor
- Argyll 0x0003 0x0971 0x2001 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # i1 Pro
- Argyll 0x0003 0x0971 0x2000 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # ColorMunki
- Argyll 0x0003 0x0971 0x2007 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # ColorMunki Smile
- Argyll 0x0003 0x0765 0x6003 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # Colorimtre HCFR
- Argyll 0x0003 0x04DB 0x005B 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # Spyder 2
- Argyll 0x0003 0x085C 0x0200 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # Spyder 3
- Argyll 0x0003 0x085C 0x0300 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # Spyder 4
- Argyll 0x0003 0x085C 0x0400 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # Huey
- Argyll 0x0003 0x0971 0x2005 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # ColorHug
- Argyll 0x0003 0x04D8 0xF8DA 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- Argyll 0x0003 0x273F 0x1001 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
-     ----------------- cut here ---------------------

 (For even older versions, append the lines above to /etc/hotplug/usb.usermap, and @@ -502,49 +373,37 @@ instruments with owner root, group root, permissions 744.

-     ----------------- cut here ---------------------
- #!/bin/sh
- # Copy to /etc/hotplug/usb/Argyll
- #
- # Argyll hotplug script. Adds the USB devices to the plugdev group.
- if [ "${ACTION}" = "add" ] && [ -f "${DEVICE}" ]
- then
-     chgrp plugdev "${DEVICE}"
-     chmod 660 "${DEVICE}"
- fi
-     ----------------- cut here ---------------------
-
YOU THEN NEED TO:

You will then need to add - yourself to the plugdev + yourself to the colord 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:

-    sudo usermod -a -G plugdev yourusernamehere
+    sudo usermod -a -G colord $USER

or
    su root
-     usermod -a -G plugdev yourusernamehere
+     usermod -a -G colord $USER


(If the usermod program isn't found as root, it might be in /usr/sbin, ie. use /usr/sbin/usermod .... etc.
 If usermod doesn't recognize the -a flag try "usermod -A - plugdev yourusernamehere".
+ colord $USER".
 If this doesn't work you will have to run "id yourusername" to list the current suplemental
-  groups, and add plugdev using just "usermod -G +  groups, and add colord using just "usermod -G group1,group2,... yourusername")

- You may find that the plugdev + You may find that the colord group doesn't exist on your system, and if so you will need to create it:

-   sudo groupadd -r plugdev
+   sudo groupadd -r colord

- and then add youself to the plugdev group.
+ and then add youself to the colord group.

You may have to log out and then in again for the groups to become effecive.
@@ -561,6 +420,11 @@ instruments + + + + + access:
If you have a serial instrument then you may find that by default @@ -573,16 +437,16 @@ instruments administration tool, or on the command line using "usermod":

    su root
-     usermod -a -G tty,uucp yourusernamehere
+     usermod -a -G tty,uucp $USER

or

-    sudo usermod -a -G tty,uucp yourusernamehere
+    sudo usermod -a -G tty,uucp $USER

(If the usermod program isn't found as root, it might be in /usr/sbin, ie. use /usr/sbin/usermod .... etc.
 If usermod doesn't recognize the -a flag try "usermod -A - plugdev yourusernamehere".
+ colord $USER".
 If this doesn't work you will have to run "id yourusername" to list the current suplemental
 groups, and add a tty or uucp group using just "usermod -G -- cgit v1.2.3