1sane(7)                  SANE Scanner Access Now Easy                  sane(7)
2
3
4

NAME

6       sane - Scanner Access Now Easy: API for accessing scanners
7
8

DESCRIPTION

10       SANE  is an application programming interface (API) that provides stan‐
11       dardized access to any raster image scanner hardware. The  standardized
12       interface  makes  it possible to write just one driver for each scanner
13       device instead of one driver for each scanner and application.
14
15       While SANE is primarily targeted at a UNIX  environment,  the  standard
16       has been carefully designed to make it possible to implement the API on
17       virtually any hardware or operating system.
18
19       This manual page provides a summary of the information available  about
20       SANE.
21
22       If  you  have  trouble getting your scanner detected, read the PROBLEMS
23       section.
24
25

TERMINOLOGY

27       An application that uses the SANE interface is called a SANE  frontend.
28       A  driver  that implements the SANE interface is called a SANE backend.
29       A meta backend provides some means to manage one or  more  other  back‐
30       ends.
31
32
33

SOFTWARE PACKAGES

35       The  package  `sane-backends' contains a lot of backends, documentation
36       (including the SANE standard), networking support, and the command line
37       frontend   `scanimage'.    The   frontends  `xscanimage',  `xcam',  and
38       `scanadf' are included in the package `sane-frontends'.  Both  packages
39       can       be      downloaded      from      the      SANE      homepage
40       (http://www.sane-project.org/).  Information about other frontends  and
41       backends can also be found on the SANE homepage.
42
43

GENERAL INFORMATION

45       The  following  sections  provide  short descriptions and links to more
46       information about several aspects of SANE.  A name  with  a  number  in
47       parenthesis (e.g.  `sane-dll(5)') points to a manual page. In this case
48       `man   5   sane-dll'   will   display   the    page.    Entries    like
49       `/usr/share/doc/sane-backends/sane.tex'  are  references  to text files
50       that   were   copied    to    the    SANE    documentation    directory
51       (/usr/share/doc/sane-backends/) during installation. Everything else is
52       a URL to a resource on the web.
53
54
55       SANE homepage
56         Information on all aspects of SANE including a tutorial and a link to
57         the    SANE    FAQ    can    be   found   on   the   SANE   homepage:
58         http://www.sane-project.org/.
59
60       SANE device lists
61         The SANE device lists contain information about the  status  of  SANE
62         support  for  a  specific device. If your scanner is not listed there
63         (either supported or unsupported), please contact us. See section HOW
64         CAN  YOU HELP SANE for details. There are lists for specific releases
65         of SANE, for the current development version  and  a  search  engine:
66         http://www.sane-project.org/sane-supported-devices.html.   The  lists
67         are also installed on your system at /usr/share/doc/sane-backends/.
68
69       SANE mailing list
70         There is a mailing list for the purpose of discussing the SANE  stan‐
71         dard and its implementations: sane-devel.  Despite its name, the list
72         is not only intended for developers, but also for  users.  There  are
73         also  some  more  lists  for  special  topics,  however,  for  users,
74         sane-devel is the right  list.  How  to  subscribe  and  unsubscribe:
75         http://www.sane-project.org/mailing-lists.html.
76
77       SANE IRC channel
78         The  IRC  (Internet  Relay  Chat)  channel  #sane can be found on the
79         Freenode network (irc.freenode.net). It's for discussing  SANE  prob‐
80         lems,  talking  about  development and general SANE related chatting.
81         Before asking for help, please read the other documentation mentioned
82         in  this  manual page. The channel's topic is also used for announce‐
83         ments of  problems  with  SANE  infrastructure  (mailing  lists,  web
84         server, etc.).
85
86       Compiling and installing SANE
87         Look  at  /usr/share/doc/sane-backends/README  and  the  os-dependent
88         README files for information about compiling and installing SANE.
89
90       SCSI configuration
91         For information  about  various  systems  and  SCSI  controllers  see
92         sane-scsi(5).
93
94       USB configuration
95         For information about USB configuration see sane-usb(5).
96
97

FRONTENDS AND MISCELLANEOUS PROGRAMS

99       scanimage
100         Command-line frontend. See scanimage(1).
101
102       saned
103         SANE network daemon that allows remote clients to access image acqui‐
104         sition devices available on the local host. See saned(8).
105
106       sane-find-scanner
107         Command-line tool to find SCSI and USB scanners and  determine  their
108         Unix device files. See sane-find-scanner(1).
109
110       Also,  have a look at the sane-frontends package (including xscanimage,
111       xcam,   and   scanadf)   and   the   frontend   information   page   at
112       http://www.sane-project.org/sane-frontends.html.
113
114

BACKENDS FOR SCANNERS

116       abaton
117         The SANE backend for Abaton flatbed scanners supports the Scan 300/GS
118         (8bit, 256 levels of gray) and  the  Scan  300/S  (black  and  white,
119         untested). See sane-abaton(5) for details.
120
121       agfafocus
122         This  backend  supports  AGFA  Focus  scanners  and the Siemens S9036
123         (untested).  See sane-agfafocus(5) for details.
124
125       apple
126         The SANE backend for Apple flatbed scanners  supports  the  following
127         scanners:   AppleScanner,   OneScanner   and   ColorOneScanner.   See
128         sane-apple(5) for details.
129
130       artec
131         The SANE Artec backend supports  several  Artec/Ultima  SCSI  flatbed
132         scanners  as  well as the BlackWidow BW4800SP and the Plustek 19200S.
133         See sane-artec(5) for details.
134
135       artec_eplus48u
136         The SANE artec_eplus48u backend supports the scanner Artec E+ 48U and
137         re-badged  models like Tevion MD 9693, Medion MD 9693, Medion MD 9705
138         and Trust Easy Webscan 19200. See sane-artec_eplus48u(5) for details.
139
140       as6e
141         This is a SANE backend for using the Artec AS6E parallel port  inter‐
142         face scanner. See sane-as6e(5) for details.
143
144       avision
145         This  backend  supports several Avision based scanners. This includes
146         the original Avision scanners (like AV 630, AV 620, ...) as  well  as
147         the  HP  ScanJet 53xx and 74xx series, Fujitsu ScanPartner, some Mit‐
148         subishi and Minolta film-scanners.  See sane-avision(5) for details.
149
150       bh
151         The bh backend provides access to Bell+Howell Copiscan II series doc‐
152         ument scanners. See sane-bh(5) for details.
153
154       canon
155         The  canon  backend  supports  the  CanoScan  300,  CanoScan 600, and
156         CanoScan 2700F SCSI flatbed scanners. See sane-canon(5) for details.
157
158       canon630u
159         The canon630u backend supports the CanoScan 630u and 636u  USB  scan‐
160         ners.  See sane-canon630u(5) for details.
161
162       canon_dr
163         The  canon_dr  backend  supports the Canon DR-Series ADF SCSI and USB
164         scanners. See sane-canon_dr(5) for details.
165
166       canon_pp
167         The canon_pp backend supports the CanoScan FB330P, FB630P, N340P  and
168         N640P parallel port scanners.  See sane-canon_pp(5) for details.
169
170       cardscan
171         This  backend  provides  support for Corex Cardscan USB scanners. See
172         sane-cardscan(5) for details.
173
174       coolscan
175         This  is  a  SANE  backend  for  Nikon  Coolscan  film-scanners.  See
176         sane-coolscan(5) for details.
177
178       coolscan2
179         This  is  a  SANE  backend  for  Nikon  Coolscan  film-scanners.  See
180         sane-coolscan2(5) for details.
181
182       epjitsu
183         The epjitsu backend provides  support  for  Epson-based  Fujitsu  USB
184         scanners. See sane-epjitsu(5) for details.
185
186       epson
187         The SANE epson backend provides support for Epson SCSI, parallel port
188         and USB flatbed scanners. See sane-epson(5) for details.
189
190       fujitsu
191         The fujitsu backend provides support for most Fujitsu SCSI  and  USB,
192         flatbed and adf scanners. See sane-fujitsu(5) for details.
193
194       genesys
195         The  genesys  backend  provides support for several scanners based on
196         the Genesys Logic GL646, GL841, GL843, GL847 and GL124 chips like the
197         Medion 6471 and Hewlett-Packard 2300c.
198          See sane-genesys(5) for details.
199
200       gt68xx
201         The  gt68xx  backend  provides  support  for  scanners  based  on the
202         Grandtech GT-6801 and GT-6816 chips like the Artec  Ultima  2000  and
203         several  Mustek  BearPaw  CU  and  TA  models.  Some Genius, Lexmark,
204         Medion, Packard Bell, Plustek, and Trust scanners are also supported.
205         See sane-gt68xx(5) for details.
206
207       hp
208         The  SANE hp backend provides access to Hewlett-Packard ScanJet scan‐
209         ners  which  support  SCL  (Scanner  Control  Language  by  HP).  See
210         sane-hp(5) for details.
211
212       hpsj5s
213         The  SANE  backend  for  the  Hewlett-Packard ScanJet 5S scanner. See
214         sane-hpsj5s(5) for details.
215
216       hp3500
217         The SANE backend for the Hewlett-Packard  ScanJet  3500  series.  See
218         sane-hp3500(5) for details.
219
220       hp3900
221         The  SANE  backend  for  the Hewlett-Packard ScanJet 3900 series. See
222         sane-hp3900(5) for details.
223
224       hp4200
225         The SANE backend for the Hewlett-Packard  ScanJet  4200  series.  See
226         sane-hp4200(5) for details.
227
228       hp5400
229         The  SANE  backend  for the Hewlett-Packard ScanJet 54XXC series. See
230         sane-hp5400(5) for details.
231
232       hpljm1005
233         The SANE backend for the Hewlett-Packard LaserJet M1005 scanner.  See
234         sane-hpljm1005(5) for details.
235
236       hs2p
237         The  SANE  backend  for  the Ricoh IS450 family of SCSI scanners. See
238         sane-hs2p(5) for details.
239
240       ibm
241         The  SANE  backend  for  some  IBM  and  Ricoh  SCSI  scanners.   See
242         sane-ibm(5) for details.
243
244       kodak
245         The SANE backend for some large Kodak scanners. See sane-kodak(5) for
246         details.
247
248       kodakaio
249         The SANE backend for Kodak AiO printer/scanners. See sane-kodakaio(5)
250         for details.
251
252       kvs1025
253         The    SANE   backend   for   Panasonic   KV-S102xC   scanners.   See
254         sane-kvs1025(5) for details.
255
256       leo
257         This backend supports the Leo S3 and the Across FS-1130, which  is  a
258         re-badged LEO FS-1130 scanner. See sane-leo(5) for details.
259
260       lexmark
261         This  backend  supports the Lexmark X1100 series of USB scanners. See
262         sane-lexmark(5) for details.
263
264       ma1509
265         The ma1509 backend supports the  Mustek  BearPaw  1200F  USB  flatbed
266         scanner. See sane-ma1509(5) for details.
267
268       magicolor
269         The  magicolor  backend  supports the KONICA MINOLTA magicolor 1690MF
270         multi-function   printer/scanner/fax.   See   sane-magicolor(5)   for
271         details.
272
273       matsushita
274         This  backend  supports  some Panasonic KVSS high speed scanners. See
275         sane-matsushita(5) for details.
276
277       microtek
278         The microtek backend  provides  access  to  the  "second  generation"
279         Microtek  scanners  with SCSI-1 command set. See sane-microtek(5) for
280         details.
281
282       microtek2
283         The microtek2 backend provides access to some Microtek scanners  with
284         a SCSI-2 command set. See sane-microtek2(5) for details.
285
286       mustek
287         The  SANE  mustek  backend supports most Mustek SCSI flatbed scanners
288         including the Paragon and ScanExpress series and the 600 II N and 600
289         II  EP  (non-SCSI).  Some  Trust  scanners  are  also  supported. See
290         sane-mustek(5) for details.
291
292       mustek_pp
293         The mustek_pp backend provides access to Mustek parallel port flatbed
294         scanners. See sane-mustek_pp(5) for details.
295
296       mustek_usb
297         The mustek_usb backend provides access to some Mustek ScanExpress USB
298         flatbed scanners. See sane-mustek_usb(5) for details.
299
300       mustek_usb2
301         The mustek_usb2 backend provides access to scanners using  the  SQ113
302         chipset  like the Mustek BearPaw 2448 TA Pro USB flatbed scanner. See
303         sane-mustek_usb2(5) for details.
304
305       nec
306         The SANE nec backend supports the NEC PC-IN500/4C SCSI  scanner.  See
307         sane-nec(5) for details.
308
309       niash
310         The niash backend supports the Agfa Snapscan Touch and the HP ScanJet
311         3300c, 3400c, and 4300c USB flatbed scanners. See  sane-niash(5)  for
312         details.
313
314       p5
315         The SANE backend for Primax PagePartner. See sane-p5(5) for details.
316
317       pie
318         The  pie  backend  provides access to Pacific Image Electronics (PIE)
319         and Devcom SCSI flatbed scanners. See sane-pie(5) for details.
320
321       pixma
322         The pixma backend supports  Canon  PIXMA  MP  series  (multi-function
323         devices),  Canon  imageCLASS  series  (laser  devices),  Canon MAXIFY
324         series and some Canon CanoScan series. See sane-pixma(5) for details.
325
326       plustek
327         The SANE plustek backend supports USB flatbed scanners that  use  the
328         National  Semiconductor  LM983[1/2/3]  chipset  aka  Merlin. Scanners
329         using this LM983x chips include some models from Plustek, KYE/Genius,
330         Hewlett-Packard,  Mustek, Umax, Epson, and Canon. See sane-plustek(5)
331         for details.
332
333       plustek_pp
334         The SANE plustek_pp backend supports Plustek  parallel  port  flatbed
335         scanners.  Scanners using the Plustek ASIC P96001, P96003, P98001 and
336         P98003 include some models  from  Plustek,  KYE/Genius,  Primax.  See
337         sane-plustek_pp(5) for details.
338
339       ricoh
340         The  ricoh  backend  provides  access  to the following Ricoh flatbed
341         scanners: IS50 and IS60. See sane-ricoh(5) for details.
342
343       ricoh2
344         The ricoh2 backend provides access to  the  following  Ricoh  flatbed
345         scanners:  SG-3100SNw, SP-100SU, and SP-111SU. See sane-ricoh2(5) for
346         details.
347
348       s9036
349         The s9036 backend provides access to Siemens 9036  flatbed  scanners.
350         See sane-s9036(5) for details.
351
352       sceptre
353         The  sceptre  backend  provides  access  to the Sceptre S1200 flatbed
354         scanner. See sane-sceptre(5) for details.
355
356       sharp
357         The  SANE  sharp  backend   supports   Sharp   SCSI   scanners.   See
358         sane-sharp(5) for details.
359
360       sm3600
361         The  SANE  sm3600  backend  supports  the Microtek ScanMaker 3600 USB
362         scanner. See sane-sm3600(5) for details.
363
364       sm3840
365         The SANE sm3840 backend supports  the  Microtek  ScanMaker  3840  USB
366         scanner.  See sane-sm3840(5) for details.
367
368       snapscan
369         The  snapscan  backend  supports  AGFA SnapScan flatbed scanners. See
370         sane-snapscan(5) for details.
371
372       sp15c
373         This backend supports the Fujitsu FCPA ScanPartner 15C flatbed  scan‐
374         ner. See sane-sp15c(5) for details.
375
376       st400
377         The  sane-st400  backend  provides access to Siemens ST400 and ST800.
378         See sane-st400(5) for details.
379
380       tamarack
381         The SANE tamarack backend supports Tamarack  Artiscan  flatbed  scan‐
382         ners. See sane-tamarack(5) for details.
383
384       teco1 teco2 teco3
385         The  SANE teco1, teco2 and teco3 backends support some TECO scanners,
386         usually sold under the Relisys, Trust, Primax, Piotech, Dextra names.
387         See sane-teco1(5), sane-teco2(5) and sane-teco3(5) for details.
388
389       u12
390         The sane-u12 backend provides USB flatbed scanners based on Plustek's
391         ASIC 98003 (parallel-port ASIC) and  a  GeneSys  Logics'  USB-parport
392         bridge  chip  like  the  Plustek OpticPro U(T)12. See sane-u12(5) for
393         details.
394
395       umax
396         The sane-umax backend provides access to  several  UMAX-SCSI-scanners
397         and some Linotype Hell SCSI-scanners. See sane-umax(5) for details.
398
399       umax_pp
400         The  sane-umax_pp  backend  provides  access  to  Umax  parallel port
401         flatbed scanners and the HP 3200C. See sane-umax_pp(5) for details.
402
403       umax1200u
404         The sane-umax1220u  backend  supports  the  UMAX  Astra  1220U  (USB)
405         flatbed  scanner  (and  also  the  UMAX  Astra  2000U,  sort of). See
406         sane-umax1220u(5) for details.
407
408       xerox_mfp
409         The sane-xerox_mfp backend supports multiple  Samsung-based  Samsung,
410         Xerox, and Dell scanners. See sane-xerox_mfp(5) for details.
411
412       Also,    have   a   look   at   the   backend   information   page   at
413       http://www.sane-project.org/sane-supported-devices.html and the list of
414       projects in /usr/share/doc/sane-backends/PROJECTS.
415
416

BACKENDS FOR DIGITAL CAMERAS

418       dc210
419         Backend for Kodak DC210 Digital Camera. See sane-dc210(5).
420
421       dc240
422         Backend for Kodak DC240 Digital Camera. See sane-dc240(5).
423
424       dc25
425         Backend for Kodak DC20/DC25 Digital Cameras. See sane-dc25(5).
426
427       dmc
428         Backend for the Polaroid Digital Microscope Camera. See sane-dmc(5).
429
430       gphoto2
431         Backend for digital cameras supported by the gphoto2 library package.
432         (See http://www.gphoto.org for more information and a  list  of  sup‐
433         ported  cameras.)  Gphoto2 supports over 140 different camera models.
434         However, please note that more  development  and  testing  is  needed
435         before  all  of these cameras will be supported by SANE backend.  See
436         sane-gphoto2(5).
437
438       qcam
439         Backend for Connectix QuickCam cameras. See sane-qcam(5).
440
441       stv680
442         The sane-stv680 backend provides access  to  webcams  with  a  stv680
443         chip. See sane-stv680(5) for details.
444
445       Also,    have   a   look   at   the   backend   information   page   at
446       http://www.sane-project.org/sane-supported-devices.html and the list of
447       projects in /usr/share/doc/sane-backends/PROJECTS.
448
449

MISCELLANEOUS BACKENDS

451       dll
452         The  sane-dll  library implements a SANE backend that provides access
453         to an arbitrary number of other SANE backends by dynamic loading. See
454         sane-dll(5).
455
456       net
457         The  SANE network daemon saned provides access to scanners located on
458         different  computers  in  connection  with  the  net   backend.   See
459         sane-net(5) and saned(8).
460
461       pnm
462         PNM  image reader pseudo-backend. The purpose of this backend is pri‐
463         marily to aid in debugging of SANE frontends. See sane-pnm(5).
464
465       pint
466         Backend for scanners that use the PINT (Pint  Is  Not  Twain)  device
467         driver.   The  PINT driver is being actively developed on the OpenBSD
468         platform, and has been ported to a few other *nix-like operating sys‐
469         tems. See sane-pint(5).
470
471       test
472         The SANE test backend is for testing frontends and the SANE installa‐
473         tion.  It provides  test  pictures  and  various  test  options.  See
474         sane-test(5).
475
476       v4l
477         The  sane-v4l library implements a SANE backend that provides generic
478         access to video cameras and similar equipment using  the  V4L  (Video
479         for Linux) API. See sane-v4l(5).
480
481       Also,    have   a   look   at   the   backend   information   page   at
482       http://www.sane-project.org/sane-supported-devices.html and the list of
483       projects in /usr/share/doc/sane-backends/PROJECTS.
484
485

CHANGING THE TOP-LEVEL BACKEND

487       By  default,  all SANE backends (drivers) are loaded dynamically by the
488       sane-dll meta backend. If you have  any  questions  about  the  dynamic
489       loading,  read  sane-dll(5).  SANE frontend can also be linked to other
490       backends directly by copying or linking  a  backend  to  libsane.so  in
491       /usr/lib64/sane.
492

DEVELOPER'S DOCUMENTATION

494       It's  not hard to write a SANE backend. It can take some time, however.
495       You should have basic knowledge  of  C  and  enough  patience  to  work
496       through the documentation and find out how your scanner works. Appended
497       is a list of some documents that help to write backends and frontends.
498
499       The SANE standard defines the application programming  interface  (API)
500       that  is  used to communicate between frontends and backends. It can be
501       found at /usr/share/doc/sane-backends/sane.ps (if latex is installed on
502       your system) and on the SANE website: http://www.sane-project.org/html/
503       (HTML), or http://www.sane-project.org/sane.ps (Postscript).
504
505       There is some more information for programmers in  /usr/share/doc/sane-
506       backends/backend-writing.txt.   Most  of  the  internal  SANE  routines
507       (sanei)         are         documented          using          doxygen:
508       http://www.sane-project.org/sanei/.   Before  a new backend or frontend
509       project  is  started,  have   a   look   at   /usr/share/doc/sane-back‐
510       ends/PROJECTS  for  projects  that are planned or not yet included into
511       the   SANE   distribution   and    at    our    bug-tracking    system:
512       http://www.http://www.sane-project.org/bugs.html.
513
514       There  are  some links on how to find out about the protocol of a scan‐
515       ner: http://www.meier-geinitz.de/sane/misc/develop.html.
516
517
518       If you start writing a backend or frontend or any other part  of  SANE,
519       please contact the sane-devel mailing list for coordination so the same
520       work isn't done twice.
521
522

FILES

524       /etc/sane.d/*.conf
525              The backend configuration files.
526
527       /usr/lib64/sane/libsane-*.a
528              The static libraries implementing the backends.
529
530       /usr/lib64/sane/libsane-*.so
531              The shared libraries implementing the backends (present on  sys‐
532              tems that support dynamic loading).
533
534       /usr/share/doc/sane-backends/*
535              SANE  documentation: The standard, READMEs, text files for back‐
536              ends etc.
537
538

PROBLEMS

540       If your device isn't found but you know that it is supported, make sure
541       that  it  is  detected by your operating system. For SCSI and USB scan‐
542       ners, use the  sane-find-scanner  tool  (see  sane-find-scanner(1)  for
543       details).  It prints one line for each scanner it has detected and some
544       comments (#). If sane-find-scanner finds your scanner only as root  but
545       not  as  normal  user,  the  permissions  for  the device files are not
546       adjusted correctly. If the scanner isn't found at  all,  the  operating
547       system hasn't detected it and may need some help. Depending on the type
548       of your scanner, read sane-usb(5) or sane-scsi(5).  If your scanner (or
549       other device) is not connected over the SCSI bus or USB, read the back‐
550       end's manual page for details on how to set it up.
551
552       Now your scanner is detected by the operating system but not  by  SANE?
553       Try  scanimage  -L.   If the scanner is not found, check that the back‐
554       end's name is mentioned in  /etc/sane.d/dll.conf.   Some  backends  are
555       commented  out  by default. Remove the comment sign for your backend in
556       this case. Also some backends aren't compiled at all if  one  of  their
557       prerequisites  are  missing.  Examples  include dc210, dc240, canon_pp,
558       hpsj5s, gphoto2, pint, qcam, v4l, net, sm3600, snapscan,  pnm.  If  you
559       need  one  of  these backends and they aren't available, read the build
560       instructions in the README file and the individual manual pages of  the
561       backends.
562
563       Another  reason for not being detected by scanimage -L may be a missing
564       or wrong configuration in the backend's configuration file. While  SANE
565       tries  to  automatically  find  most scanners, some can't be setup cor‐
566       rectly without the intervention of  the  administrator.  Also  on  some
567       operating systems auto-detection may not work. Check the backend's man‐
568       ual page for details.
569
570       If your scanner is still not found, try setting the various environment
571       variables  that  are available to assist in debugging.  The environment
572       variables are documented in the relevant manual pages.  For example, to
573       get  the maximum amount of debug information when testing a Mustek SCSI
574       scanner, set environment variables  SANE_DEBUG_DLL,  SANE_DEBUG_MUSTEK,
575       and  SANE_DEBUG_SANEI_SCSI  to  128 and then invoke scanimage -L .  The
576       debug messages for the dll backend tell if the mustek backend was found
577       and  loaded at all. The mustek messages explain what the mustek backend
578       is doing while the SCSI debugging shows the low level handling. If  you
579       can't find out what's going on by checking the messages carefully, con‐
580       tact the sane-devel mailing list for help (see REPORTING BUGS below).
581
582       Now that your scanner is found by scanimage -L, try to do a scan: scan‐
583       image  >image.pnm.   This command starts a scan for the default scanner
584       with default settings. All the available options are listed by  running
585       scanimage  --help.   If  scanning aborts with an error message, turn on
586       debugging as mentioned above. Maybe the configuration file  needs  some
587       tuning,  e.g.  to  setup  the path to a firmware that is needed by some
588       scanners. See the backend's manual page for details. If you can't  find
589       out what's wrong, contact sane-devel.
590
591       To  check  that  the SANE libraries are installed correctly you can use
592       the test backend, even if you  don't  have  a  scanner  or  other  SANE
593       device:
594
595              scanimage -d test -T
596
597       You  should  get  a list of PASSed tests. You can do the same with your
598       backend by changing "test" to your backend's name.
599
600       So now scanning with scanimage works and you want to  use  one  of  the
601       graphical  frontends  like  xsane, xscanimage, or quiteinsane but those
602       frontends don't detect  your  scanner?  One  reason  may  be  that  you
603       installed two versions of SANE.  E.g. the version that was installed by
604       your distribution  in  /usr  and  one  you  installed  from  source  in
605       /usr/local/.   Make  sure  that  only one version is installed. Another
606       possible reason is, that your system's dynamic loader  can't  find  the
607       SANE  libraries.  For  Linux,  make  sure that /etc/ld.so.conf contains
608       /usr/local/lib and does not contain /usr/local/lib/sane.  See also  the
609       documentation of the frontends.
610

HOW CAN YOU HELP SANE

612       We  appreciate  any help we can get. Please have a look at our web page
613       about contributing to SANE: http://www.sane-project.org/contrib.html
614

CONTACT

616       For reporting bugs or requesting new  features,  please  use  our  bug-
617       tracking  system:  http://www.sane-project.org/bugs.html.  You can also
618       contact the author of your backend directly. Usually the email  address
619       can  be  found  in the /usr/share/doc/sane-backends/AUTHORS file or the
620       backend's manpage. For general discussion about SANE,  please  use  the
621       SANE  mailing  list  sane-devel  (see http://www.sane-project.org/mail
622       ing-lists.html for details).
623

SEE ALSO

625       saned(8),    sane-find-scanner(1),    scanimage(1),     sane-abaton(5),
626       sane-agfafocus(5),             sane-apple(5),            sane-artec(5),
627       sane-artec_eplus48u(5),  sane-as6e(5),   sane-avision(5),   sane-bh(5),
628       sane-canon(5),  sane-canon630u(5),  sane-canon_dr(5), sane-canon_pp(5),
629       sane-cardscan(5), sane-coolscan2(5),  sane-coolscan(5),  sane-dc210(5),
630       sane-dc240(5),  sane-dc25(5),  sane-dll(5), sane-dmc(5), sane-epson(5),
631       sane-fujitsu(5),  sane-genesys(5),   sane-gphoto2(5),   sane-gt68xx(5),
632       sane-hp(5),     sane-hpsj5s(5),     sane-hp3500(5),     sane-hp3900(5),
633       sane-hp4200(5),   sane-hp5400(5),    sane-hpljm1005(5),    sane-ibm(5),
634       sane-kodak(5),  sane-leo(5), sane-lexmark(5), sane-ma1509(5), sane-mat‐
635       sushita(5),   sane-microtek2(5),   sane-microtek(5),    sane-mustek(5),
636       sane-mustek_pp(5),       sane-mustek_usb(5),       sane-mustek_usb2(5),
637       sane-nec(5),  sane-net(5),  sane-niash(5),  sane-pie(5),  sane-pint(5),
638       sane-plustek(5),    sane-plustek_pp(5),    sane-pnm(5),   sane-qcam(5),
639       sane-ricoh(5),    sane-ricoh2(5),    sane-s9036(5),    sane-sceptre(5),
640       sane-scsi(5), sane-sharp(5), sane-sm3600(5), sane-sm3840(5), sane-snap‐
641       scan(5),  sane-sp15c(5),  sane-st400(5),   sane-stv680(5),   sane-tama‐
642       rack(5),  sane-teco1(5),  sane-teco2(5),  sane-teco3(5),  sane-test(5),
643       sane-u12(5),    sane-umax1220u(5),    sane-umax(5),    sane-umax_pp(5),
644       sane-usb(5), sane-v4l(5), sane-xerox_mfp(5)
645
646

AUTHOR

648       David  Mosberger-Tang and many many more (see /usr/share/doc/sane-back‐
649       ends/AUTHORS for details).  This man page was written by Henning Meier-
650       Geinitz.  Quite a lot of text was taken from the SANE standard, several
651       man pages, and README files.
652
653
654
655                                  03 Jan 2020                          sane(7)
Impressum