[sane-devel] Sane and HP C6270A 3828

[Peter Kirchgessner]

Hi,

when generating scanimage from source, you usually do a ./configure 
without a --prefix. Then the executables are stored in /usr/local and 
also the configuration directory is at /usr/local/etc/sane.d. So maybe 
you have two version of SANE on your machine. The SANE-libraries from 
your distribution under /usr/lib and the libraries from your own 
compilation under /usr/local/lib.
You can try to remove the SANE-package using your administration tools 
of your Linux distribution. But it may complain that too many other 
packages require that.
A brute force to remove the SANE-libraries under /usr/lib is just to 
remove everything relating to sane below that directory.
Then you should add /usr/local/lib to the file /etc/ld.so.conf and run a 
ldconfig. Then the command

ldd scanimage

should show you from where the libraries are fetched. And then you 
should check again /usr/local/etc/sane.d/hp.conf and dll.conf if they 
fit your needs.

Sincerely

Peter

Yao Ko schrieb:
> On Tue, 2004-03-23 at 13:45, Peter Kirchgessner wrote:
> 
>>Hi,
>>
>>you can check if the hp-backend is called to open the scanner. To do
>>this do
>>
>>SANE_DEBUG_HP=17
>>export SANE_DEBUG_HP
>>
>>before starting scanimage. If the backend is called, it prints out 
>>messages to stderr.
>>If it is not called, scanimage may look in a different directory for
>>the 
>>configuration. You can do
>>
>>SANE_CONFIG_DIR=/etc/sane.d
>>export SANE_CONFIG_DIR
>>
>>and then start scanimage again.
>>If you don't succeed in getting the scanner running, redirect the
>>debug 
>>messages to a file
>>
>>scanimage -L 2>hp.lis
>>
>>gzip it and send it back to me.
> 
> 
> 
> Hi Peter,
> 
> I tried the above and it didn't open the HP backend. After many hours of
> tweaking, I found that doing this makes scanimage find the scanner:
> 
> "LD_LIBRARY_PATH=/usr/lib scanimage -L"
> 
> I'm not sure why this is happening. I'm using RH9. If I compile the
> newest sane-backends, scanimage works fine.
> 
> I'll investigate further and post more findings. Has anyone encountered
> similar problems with this scanner?
> 
> Thanks,
> 
> Yao
> 
> 


-- 
Peter Kirchgessner
http://www.kirchgessner.net
mailto:peter@kirchgessner.net