[sane-devel] device file for "canon" backend in sane-backends 1.0.17

Johannes Meixner jsmeix at suse.de
Wed May 24 10:18:36 UTC 2006


Hello,

we got a bug report from a customer:
https://bugzilla.novell.com/show_bug.cgi?id=177492
but we don't have a scanner which is supported by the "canon"
backend, therefore I ask here:

In sane-backends 1.0.17 /etc/sane.d/canon.conf is
-------------------------------------------------------------------
#canon.conf
/dev/scanner
#/dev/sg0
-------------------------------------------------------------------
This seems to force the canon backend to look only at /dev/scanner
to find one of its supported scanners because with
"SANE_DEBUG_SANEI_SCSI=128" there is only "/dev/scanner" shown:
-------------------------------------------------------------------
[sanei_scsi] sanei_scsi_open: open of `/dev/scanner' failed:
                              No such file or directory
No scanners were identified.
-------------------------------------------------------------------

To get auto-detection I changed /etc/sane.d/canon.conf to
-------------------------------------------------------------------
#canon.conf
#/dev/scanner
#/dev/sg0
-------------------------------------------------------------------
but this falls back to the above case (i.e. only "/dev/scanner").

It seems to work better with
-------------------------------------------------------------------
#canon.conf  
#/dev/scanner
/dev/sg0
-------------------------------------------------------------------
because now it tests the device which is assigned to /dev/sg0
(which is no such scanner but a USB mass-storage on my system)
and with "SANE_DEBUG_SANEI_SCSI=128" I get:
----------------------------------------------------------------------
[sanei_scsi] sanei_scsi_open: The device found for /dev/sg0 does
                              not look like a scanner
No scanners were identified.
----------------------------------------------------------------------
At least it doesn't crash if the device file is wrong.

Unfortunately something like
-------------------------------------------------------------------
#canon.conf
/dev/scanner
/dev/sg0
/dev/sg1
-------------------------------------------------------------------
does not work to get some kind of auto-detection because
the canon driver tests only the last device entry ("/dev/sg1"
in this case).


Kind Regards
Johannes Meixner
-- 
SUSE LINUX Products GmbH, Maxfeldstrasse 5      Mail: jsmeix at suse.de
90409 Nuernberg, Germany                    WWW: http://www.suse.de/



More information about the sane-devel mailing list