[sane-devel] "no sane devices found"

[Christoph Kukulies]

On Wed, Sep 26, 2001 at 02:20:23PM -0700, Mark S Parrish wrote:
> Hi,
> 
> 
> An interesting thing is happening.  When I start xsane, it says something 
> like "xsane: no devices available."  Just for grins I did a:

I had the same problem with xsane not finding the device. 
There is a file in the xsane distribution named xsane.PROBLEMS and
xsane.INSTALL.
Study these file. 

 - For sane-1.0.1 you have to edit /etc/ld.so.conf and add a line with the path to the
     libraries (normally /usr/local/lib/sane), then call ldconfig.
     THIS MUST BE DONE AS ROOT!
   - For sane-1.0.2 (and later versions) the path to the xsane libs MUST NOT be listed
     in /etc/ld.so.conf

My ld.so.conf: (Redhat 6.1)

/usr/X11R6/lib
/usr/i486-linux-libc5/lib
/usr/lib/qt-1.44/lib
/usr/lib/qt-2.0.1/lib
/usr/local/lib

> 
> [root at msp mark]# sane-find-scanner
> # Note that sane-find-scanner will find any scanner that is connected
> # to a SCSI bus.  It will even find scanners that are not supported
> # at all by SANE. It won't find a scanner that is connected to a
> # parallel, USB or other non-SCSI port.
>  
> sane-find-scanner: found processor "HP C7670A 3945" at device /dev/sg0
> sane-find-scanner: found processor "HP C7670A 3945" at device /dev/sga
> 
> It took almost a full minute to come back with the above 2 lines. I am also 
> wondering why it is listed twice.

That it is listed twice is normal, I believe, since the devices are links.

With me here I get:

 sane-find-scanner

sane-find-scanner: found SCSI scanner "SCANNER  1.11" at device /dev/scanner
sane-find-scanner: found SCSI scanner "SCANNER  1.11" at device /dev/sg0
sane-find-scanner: found SCSI scanner "SCANNER  1.11" at device /dev/sga

> 
> Then I executed xsane again and it gave me the "xsane: no devices 
> available" ONCE.  The second time I executed xsane it started just fine.  It 


Hmm. I did read this before I made the notes above. Is your SCSI
connection OK? Termination etc.?

> is almost like I have to kick it to get it started.  Can anyone tell me why?
> 
-- 
Chris Christoph P. U. Kukulies kuku at gil.physik.rwth-aachen.de