1sane-find-scanner(1) SANE Scanner Access Now Easy sane-find-scanner(1)
2
6 sane-find-scanner - find SCSI and USB scanners and their device files
7
9 sane-find-scanner [-h|-?] [-v] [-q] [-p] [-f] [-F filename] [devname]
10
13 sane-find-scanner is a command-line tool to find SCSI and USB scanners
14 and determine their Unix device files. Its primary aim is to make sure
15 that scanners can be detected by SANE backends.
16 For SCSI scanners, it checks the default generic SCSI device files
18 (e.g., /dev/sg0) and /dev/scanner. The test is done by sending a SCSI
19 inquiry command and looking for a device type of "scanner" or "proces‐
20 sor" (some old HP scanners seem to send "processor"). So sane-find-
21 scanner will find any SCSI scanner connected to those default device
22 files even if it isn't supported by any SANE backend.
23 For USB scanners, first the USB kernel scanner device files (e.g.
25 /dev/usb/scanner0), /dev/usb/scanner, and /dev/usbscanner) are tested.
26 The files are opened and the vendor and device ids are determined, if
27 the operating system supports this feature. Currently USB scanners are
28 only found this way if they are supported by the Linux scanner module
29 or the FreeBSD or OpenBSD uscanner driver. After that test, sane-find-
30 scanner tries to scan for USB devices found by the USB library libusb
31 (if available). There is no special USB class for scanners, so the
32 heuristics used to distinguish scanners from other USB devices is not
33 perfect. sane-find-scanner also tries to find out the type of USB chip
34 used in the scanner. If detected, it will be printed after the vendor
35 and product ids. sane-find-scanner will even find USB scanners, that
36 are not supported by any SANE backend.
37 sane-find-scanner won't find most parallel port scanners, or scanners
39 connected to proprietary ports. Some parallel port scanners may be
40 detected by sane-find-scanner -p. At the time of writing this will
41 only detect Mustek parallel port scanners.
42
45 -h, -? Prints a short usage message.
46 -v Verbose output. If used once, sane-find-scanner shows every
48 device name and the test result. If used twice, SCSI inquiry
49 information and the USB device descriptors are also printed.
50 -q Be quiet. Print only the devices, no comments.
52 -p Probe parallel port scanners.
54 -f Force opening all explicitly given devices as SCSI and USB
56 devices. That's useful if sane-find-scanner is wrong in deter‐
57 mining the device type.
58 -F filename
60 filename is a file that contains USB descriptors in the format
61 of /proc/bus/usb/devices as used by Linux. sane-find-scanner
62 tries to identify the chipset(s) of all USB scanners found in
63 such a file. This option is useful for developers when the out‐
64 put of "cat /proc/bus/usb/devices" is available but the scanner
65 itself isn't.
66 devname Test device file "devname". No other devices are checked if
68 devname is given.
69
71 sane-find-scanner -v
72 Check all SCSI and USB devices for available scanners and print a line
73 for every device file.
74 sane-find-scanner /dev/scanner
76 Look for a (SCSI) scanner only at /dev/scanner and print the result.
77 sane-find-scanner -p
79 Probe for parallel port scanners.
80
82 sane(7), sane-scsi(5), sane-usb(5), scanimage(1), xscanimage(1),
83 xsane(1), sane-"backendname"[22m(5)
84
87 Oliver Rauch, Henning Meier-Geinitz and others
88
90 USB support is limited to Linux (kernel, libusb), FreeBSD (kernel,
91 libusb), NetBSD (libusb), OpenBSD (kernel, libusb). Detecting the ven‐
92 dor and device ids only works with Linux or libusb.
93 SCSI support is available on Irix, EMX, Linux, Next, AIX, Solaris,
95 FreeBSD, NetBSD, OpenBSD, and HP-UX.
96
99 No support for most parallel port scanners yet.
100 Detection of USB chipsets is limited to a few chipsets.
101sane-backends 1.0.18 4 Oct 2004 sane-find-scanner(1)