Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 1595 - sane-backends-1.0.7 config directory path
Summary: sane-backends-1.0.7 config directory path
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Seemant Kulleen (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-04-08 01:27 UTC by Michael v.Ostheim
Modified: 2002-04-14 02:06 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael v.Ostheim 2002-04-08 01:27:15 UTC
The default path sane is looking for it's configuration files is 
"/usr/local/etc/sane.d". If they are not there ("/etc/sane.d" in Gentoo) , you 
have to set the env variable SANE_CONFIG_DIR to the sane.d directory. For 
example,  "man sane-mustek" seems to be outdated, look here: 
http://ou800doc.caldera.com/cgi-bin/man/man?sane-mustek+5
Comment 1 Seemant Kulleen (RETIRED) gentoo-dev 2002-04-11 10:43:35 UTC
ok, from what I see, the man pages on gentoo are actually newer than your URL
shows.  December 2001on Gentoo versus June 2001 there.  

Also, can you show me some output about the configuration files issue please? 
Ido not have a scanner,  and I am totall unfamiliar with sane packages.
Comment 2 Michael v.Ostheim 2002-04-12 13:44:37 UTC
Fact is, with a fresh installed package, scanimage doesn't find the config 
files in "/etc/sane.d". Example ("scanimage -L" list all available scanner 
devices): 
 
---Snip--- 
ostheimm@hal9000 ostheimm $ scanimage -L 
 
No scanners were identified. If you were expecting something different, 
check that the scanner is plugged in, turned on and detected by the 
sane-find-scanner tool (if appropriate). Please read the documentation 
which came with this software (README, FAQ, manpages). 
ostheimm@hal9000 ostheimm $ export SANE_CONFIG_DIR="/etc/sane.d" 
ostheimm@hal9000 ostheimm $ scanimage -L 
device `mustek:/dev/scsi/host1/bus0/target0/lun0/generic' is a Mustek 
MFS-12000SP flatbed scanner 
---Snap--- 
 
To set this variable at boottime I have created this file: 
 
---Snip--- 
ostheimm@hal9000 ostheimm $ cat /etc/env.d/30sane 
SANE_CONFIG_DIR=/etc/sane.d 
---Snap--- 
 
Some details about the config files:  
In "/etc/sane.d/dll.conf" you have to list all scanner models you want to use. 
In my case, there is only one entry: 
 
---Snip--- 
ostheimm@hal9000 ostheimm $ cat /etc/sane.d/dll.conf 
mustek 
---Snap--- 
 
In the "/etc/sane.d/modelname.conf" files you have to set the correct device 
file names and you can set some model specific options. These are my settings: 
 
---Snip--- 
ostheimm@hal9000 ostheimm $ cat /etc/sane.d/mustek.conf 
# See sane-mustek(5) for documentation. 
 
#--------------------------- Global options --------------------------------- 
#option strip-height 1           # some SCSI adapters need this; scanning may 
                                 # be faster without this option 
#option force-wait               # wait for scanner to be ready (only 
necessary 
                                 # when scanner freezes) 
#option disable-double-buffering # try this if you have SCSI trouble 
 
#-------------------------- SCSI scanners ----------------------------------- 
 
/dev/scsi/host1/bus0/target0/lun0/generic 
#option linedistance-fix        # stripes may go away in color mode 
#option buffersize 1024         # set non standard buffer size (in kb) 
#option blocksize 2048          # set non standard block size (in kb) 
# option lineart-fix             # lineart may be faster with this option off. 
option disable-backtracking    # faster, but may produce stripes 
---Snap--- 
 
Hope this will help you... 
Comment 3 Seemant Kulleen (RETIRED) gentoo-dev 2002-04-14 02:06:29 UTC
Yes, that helped me a lot.  Actually it was your /etc/env.d entry which was the
trick :).  I have modified the ebuild to add a file in /etc/env.d to make a
value for the environment variable.

Thanks for your help on that one -- you actually sorted this bug :)