[sane-devel] Problem in setting up Xsane (problem half solved)

[Henning Meier-Geinitz]

Hi,

On Sat, Mar 01, 2003 at 11:45:57AM +0800, Stephen Liu wrote:
> sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN 310 1.90" at device /dev/scanner
> sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN 310 1.90" at device /dev/sg1
> sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN 310 1.90" at device /dev/sgb
> 
> 
> # ls -l /dev/sg1
> crwxrwxrwx    1 satimis  root      21,   1 Apr 11  2002 sg1
> # ls -l /dev/sgb
> lrwxrwxrwx    1 root     root            3 Aug 24  2002 sgb -> sg1
> 
> I think my scanner uses /dev/sg1 (If wrong, please correct me)

You are right. The two other files are just links.

> as safety measure I also did
> # chmod -c 0777 /dev/sg0
> mode of `sg0' changed to 0777 (rwxrwxrwx)

Not needed. If sane-find-scanner detects the scanner (as user), the
permissions are set up correctly.

> # SANE_DEBUG_SNAPSCAN=255 scanimage -L
> [sanei_debug] Setting debug level of snapscan to 255.
> [snapscan] sane_snapscan_init
> [snapscan] sane_snapscan_init: Snapscan backend version 1.4.7
> [snapscan] add_device(/dev/sg0)

The snapscan backend looks for "/dev/sg0" not "/dev/sg1" or
"/dev/scanner" for some reason. Check snapscan.conf (somewhere in
/etc/sane.d/ or /usr/local/etc/sane.d/) and change /dev/sg0 to /dev/sg1.

Current versions of sane-backends don't have this hardcoded path so
I'm a bit surprised.

Please also have a look at man sane-snapscan.

Bye,
  Henning