NAME<\/a> sane\u2212scsi \u2212 SCSI adapter tips for scanners<\/p>\n This manual page contains various operating-system specific tips and tricks on how to get scanners with a SCSI interface working.<\/p>\n For scanners with a SCSI interface, it may be necessary to edit the appropriate backend configuration file before using SANE for the first time. For most systems, the configuration file should list the name of the generic SCSI device that the scanner is connected to (e.g., under Linux, \/dev\/sg4<\/i> or \/dev\/sge<\/i> is such a generic SCSI device). It is customary to create a symlink from \/dev\/scanner<\/i> to the generic SCSI device that the scanner is connected to. In this case, the configuration file simply lists the line \/dev\/scanner<\/i>. For a detailed description of each backend\u2019s configuration file, please refer to the relevant backend manual page (e.g., sane\u2212epson<\/b>(5) for Epson scanners, sane\u2212hp<\/b>(5) for HP scanners, etc.).<\/p>\n For some operating systems (e.g. Linux and OS\/2), there is an alternate way of specifying scanner devices. This alternate way allows one to identify scanners by the SCSI vendor and model string and\/or by the SCSI device address (consisting of bus number, channel number, id, and logical unit number). The syntax for specifying a scanner in this way is:<\/p>\n scsi VENDOR MODEL TYPE BUS CHANNEL ID LUN<\/i><\/p>\n where VENDOR<\/i> is the SCSI vendor string, MODEL<\/i> is the SCSI model string, TYPE<\/i> is type SCSI device type string, BUS<\/i> is the SCSI bus number (named “host” in \/proc\/scsi\/scsi<\/i>), CHANNEL<\/i> is the SCSI channel number, ID<\/i> is the SCSI id, and LUN<\/i> is the logical unit number of the scanner device. The first two fields are strings which must be enclosed in double-quotes if they contain any whitespace. The remaining four fields are non-negative integer numbers. The correct values for these fields can be found by using operating system specific tools, e.g. for Linux by looking at the output of the command cat \/proc\/scsi\/scsi<\/i>. To simplify configuration, a field\u2019s value can be replaced with an asterisk symbol (\u2018\u2018*\u2019\u2019). An asterisk has the effect that any value is allowed for that particular field. This can have the effect that a single scsi-line matches multiple devices. When this happens, each matching device will be probed by the backend one by one and registered if the backend thinks it is a compatible device. For example, the line<\/p>\n scsi MUSTEK MFS\u221206000CX Scanner 0 00 03 00<\/p>\n would attach the Mustek SCSI scanner with the following \/proc\/scsi\/scsi entry:<\/p>\n Host: scsi0 Channel: 00 Id: 03 Lun: 00 Usually it\u2019s sufficient to use vendor and model strings only or even only the vendor string. The following example<\/p>\n scsi MUSTEK bodies manpages.csv script_extrae_body.sh script.sh usr bodies manpages.csv script_extrae_body.sh script.sh usr bodies manpages.csv script_extrae_body.sh script.sh usr bodies manpages.csv script_extrae_body.sh script.sh usr bodies manpages.csv script_extrae_body.sh script.sh usr *<\/p>\n would have the effect that all SCSI devices in the system with a vendor string of MUSTEK would be probed and recognized by the backend.<\/p>\n If the remainder of a scsi-string consists of asterisks only, the asterisks can be omitted. For example, the following line is equivalent to the one specified previously:<\/p>\n scsi MUSTEK<\/p>\n On some platforms (e.g., OpenStep), SANE device names take a special form. This is explained below in the relevant platform-specific section.<\/p>\n When using a SCSI scanner, ensure that the access permission for the generic SCSI device is set appropriately. We recommend to add a group “scanner” to \/etc\/group<\/i> which contains all users that should have access to the scanner. The permission of the device should then be set to allow group read and write access. For example, if the scanner is at generic SCSI device \/dev\/sg0<\/i>, then the following two commands would set the permission correctly:<\/p>\n $ chgrp scanner \/dev\/sg0 When your system uses the device filesystem (devfs), you have to edit \/etc\/devfs\/perms.<\/i> There you should search the line<\/p>\n REGISTER ^sg[^\/]* PERMISSIONS root.root 0600<\/p>\n and add a new line (eg. for changing permissions of sg4):<\/p>\n REGISTER ^sg4 PERMISSIONS root.scanner 0660<\/p>\n Auto-configuration using the “scsi *” lines in the config files only works if the user running the frontend has read\/write access to \/dev\/xpt0<\/i>. Instead, you can also set a link \/dev\/scanner<\/i> to the appropriate \/dev\/uk<\/i> device.<\/p>\n Adaptec AHA1542CF<\/p>\n Reported to work fine under FreeBSD 2.2.2R with the aha<\/b> driver.<\/p>\n Adaptec 2940<\/p>\n Reported to work fine under FreeBSD 2.2.2.<\/p>\n Adaptec 1522<\/p>\n The scanner probes ok but any attempt to access it hangs<\/i> the entire system. It looks like something is disabling interrupts and then not re-enabling them, so it looks like a bug in the FreeBSD aic<\/b> driver.<\/p>\n Adaptec 1505<\/p>\n Works on FreeBSD 2.2.5R and 3.0 using the aic<\/b> driver, provided that Plug-and-Play support is disabled on the card. If there are no uk<\/i> devices, just do a sh MAKEDEV uk0<\/i> in the \/dev<\/i> directory. The scanner should then be accessible as \/dev\/uk0<\/i> if it was probed during boot.<\/p>\n Tekram DC390<\/p>\n Reported to work fine under FreeBSD 2.2.2R with the amd<\/b> driver.<\/p>\n First, make sure your kernel has SCSI generic support enabled. In make xconfig<\/i>, this shows up under \u2018\u2018SCSI support->SCSI generic support\u2019\u2019.<\/p>\n To keep scanning times to a minimum, it is strongly recommended to use a large buffer size for the generic SCSI driver. From SG driver version 2.0 on, the maximum buffer size can be changed at program run time, and there is no restriction in size. This driver version is part of the Linux kernels from version 2.2.7 on. If the new SG driver is available some backends (e.g. sane\u2212umax<\/b>(5), sane\u2212mustek<\/b>(5), sane\u2212sharp<\/b>(5)) automatically request larger SCSI buffers. If a backend does not automatically request a larger SCSI buffer, set the environment variable SANE_SG_BUFFERSIZE<\/b> to the desired buffer size in bytes. It is not recommended to use more than 1 MB, because for large values the probability increases that the SG driver cannot allocate the necessary buffer(s). For ISA cards, even 1 MB might be a too large value. For a detailed discussion of memory issues of the SG driver, see http:\/\/www.torque.net\/sg.<\/i><\/p>\n For Linux kernels before version 2.2.7 the size of the buffer is only 32KB. This works, but for many cheaper scanners this causes scanning to be slower by about a factor of four than when using a size of 127KB. Linux defines the size of this buffer by macro SG_BIG_BUFF<\/b> in header file \/usr\/include\/scsi\/sg.h<\/i>. Unless a system is seriously short on memory, it is recommended to increase this value to the maximum legal value of 128*1024-512=130560 bytes. After changing this value, it is necessary to recompile both the kernel (or the SCSI generic module) and the SCSI backends. Keep in mind that this is only necessary with older Linux kernels.<\/p>\n A common issue with SCSI scanners is what to do when you booted the system while the scanner was turned off. In such a case, the scanner won\u2019t be recognized by the kernel and SANE won\u2019t be able to access it. Fortunately, Linux provides a simple mechanism to probe a SCSI device on demand. Suppose you have a scanner connected to SCSI bus 2 and the scanner has a SCSI id of 5. When the system is up and running and the scanner is turned on, you can issue the command:<\/p>\n echo “scsi add\u2212single\u2212device 2 0 5 0” > \/proc\/scsi\/scsi<\/p>\n and the kernel will probe and recognize your scanner (this needs to be done as root). It\u2019s also possible to dynamically remove a SCSI device by using the \u2018\u2018remove\u2212single\u2212device\u2019\u2019 command. For details, please refer to to the SCSI-2.4-HOWTO.<\/p>\n Scanners are known to work with the following SCSI adapters under Linux. This list isn\u2019t complete, usually any SCSI adapter supported by Linux should work.<\/p>\n Acard\/Advance SCSI adapters<\/p>\n Some old versions of the kernel driver (atp870u.c<\/i>) cut the inquiry information. Therefore the scanner couldn\u2019t be detected correctly. Use a current kernel.<\/p>\n Adaptec AHA-1505\/AHA-1542\/AHA-2940<\/p>\n Reported to work fine with Linux since v2.0. If you encounter kernel freezes or other unexpected behaviour get the latest Linux kernel (2.2.17 seems to work) or reduce SCSI buffer size to 32 kB.<\/p>\n ASUS SC200<\/p>\n Reported to work fine with Linux v2.0.<\/p>\n BusLogic BT958<\/p>\n To configure the BusLogic card, you may need to follow these instructions (contributed by Jeremy NCR\/Symbios 53c400\/53c400a or Domex DTC3181E\/L\/LE (DTCT436\/436P) This card is supplied by Mustek (and other vendors). It\u2019s supported since Linux 2.2. The SCSI cards are supported by the module g_NCR5380. It\u2019s necessary to tell the kernel the io port and type of card. Example for a 53c400a: modprobe g_NCR5380 ncr_addr=0x280 ncr_53c400a=1 .<\/i> Once the kernel detects the card, it should work all right. However, while it should work, do not expect good performance out of this card—it has no interrupt line and therefore while a scan is in progress, the system becomes almost unusable. You may change the values of the USLEEP macros in drivers\/scsi\/g_NCR5380.c<\/i>. Some documentation is in this file and NCR5380.c<\/i>.<\/p>\n NCR\/Symbios 810<\/p>\n For some scanners it may be necessary to disable disconnect\/reconnect. To achieve this use the option ncr53c8xx=”disc:n”. Some people reported that their scanner only worked with the 53c7,8xx driver, not the ncr53c8xx. Try both if you have trouble. Tekram DC315<\/p>\n The driver can be downloaded from http:\/\/www.garloff.de\/kurt\/linux\/dc395\/<\/i>. For some older scanners it may be necessary to disable all the more advanced features by using e.g. modprobe dc395x_trm dc395x_trm=7,5,1,32<\/i>.<\/p>\n Tekram DC390<\/p>\n Version 1.11 of the Tekram driver seems to work fine mostly, except that the scan does not terminate properly (it causes a SCSI timeout after 10 minutes). The generic AM53C974 also seems to work fine and does not suffer from the timeout problems.<\/p>\n Under Solaris, OpenStep and NeXTStep, the generic SCSI device name refers to a SCSI bus, not to an individual device. For example, \/dev\/sg0<\/i> refers to the first SCSI bus. To tell SANE which device to use, append the character \u2019a\u2019+target-id to the special device name. For example, the SCSI device connected to the first SCSI controller and with target-id 0 would be called \/dev\/sg0a<\/i>, and the device with target-id 1 on that same bus would be called \/dev\/sg0b,<\/i> and so on.<\/p>\n SANE_DEBUG_SANEI_SCSI<\/b><\/p>\n If the library was compiled with debug support enabled, this environment variable controls the debug level for the generic SCSI I\/O subsystem. E.g., a value of 128 requests all debug output to be printed by the backend. A value of 255 also prints kernel messages from the SCSI subsystem (where available). Smaller levels reduce verbosity.<\/p>\n SANE_SCSICMD_TIMEOUT<\/b><\/p>\n sets the timeout value for SCSI commands in seconds. Overriding the default value of 120 seconds should only be necessary for very slow scanners.<\/p>\n
DESCRIPTION<\/a>
GENERAL INFO<\/a>
FREEBSD INFO<\/a>
LINUX INFO<\/a>
SOLARIS, OPENSTEP AND NEXTSTEP INFO<\/a>
ENVIRONMENT<\/a>
SEE ALSO<\/a>
AUTHOR<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
GENERAL INFO <\/a> <\/h2>\n
Vendor: MUSTEK Model: MFS\u221206000CX Rev: 4.04
Type: Scanner ANSI SCSI revision: 0<\/p>\n
$ chmod 660 \/dev\/sg0<\/p>\nFREEBSD INFO <\/a> <\/h2>\n
LINUX INFO <\/a> <\/h2>\n
ISA SCSI card<\/p>\n
For Linux kernels before 2.0.33 it may be necessary to increase the SCSI timeout. The default timeout for the Linux kernels before 2.0.33 is 10 seconds, which is way too low when scanning large area. If you get messages of the form \u2018\u2018restart (ncr dead ?)\u2019\u2019 in your \/var\/log\/messages<\/i> file or on the system console, it\u2019s an indication that the timeout is too short. In this case, find the line \u2018\u2018if (np->latetime>10)\u2019\u2019 in file ncr53c8xx.<\/i> (normally in directory \/usr\/src\/linux\/drivers\/scsi<\/i>) and change the constant 10 to, say, 60 (one minute). Then rebuild the kernel\/module and try again.<\/p>\nSOLARIS, OPENSTEP AND NEXTSTEP INFO <\/a> <\/h2>\n
ENVIRONMENT <\/a> <\/h2>\n
SEE ALSO <\/a> <\/h2>\n