[sane-devel] no scanners found (leo s3 scsi-scanner)
Hi, thanks for your tip. I compiled it without the spaces in leo.c and the scanner runs !!! Very much thanks for your good help. :-)) Bye, Axel Henning Meier-Geinitz schrieb: Hi, On Thu, Jan 16, 2003 at 11:01:54PM +0100, axel dammers wrote: But sane-find-scanner -v -v shows not a 0 behind the scanner name: Yes, it does: searching for SCSI scanners: checking /dev/scanner... open ok Inquiry for device: 000: 06 00 02 02 1f 00 00 00 4c 45 4f 00 00 00 00 00LEO. 016: 4c 45 4f 53 63 61 6e 2d 53 33 00 00 00 00 00 00LEOScan-S3.. There are the 00 00 ... after the text. The backend expects spaces (32 = 0x20). Have I to do anything in the sourcecode ? Try it. Remove the spaces as I mentioned. Bye, Henning ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] no scanners found (leo s3 scsi-scanner)
Hi, On Thu, Jan 16, 2003 at 11:01:54PM +0100, axel dammers wrote: But sane-find-scanner -v -v shows not a 0 behind the scanner name: Yes, it does: searching for SCSI scanners: checking /dev/scanner... open ok Inquiry for device: 000: 06 00 02 02 1f 00 00 00 4c 45 4f 00 00 00 00 00LEO. 016: 4c 45 4f 53 63 61 6e 2d 53 33 00 00 00 00 00 00LEOScan-S3.. There are the 00 00 ... after the text. The backend expects spaces (32 = 0x20). Have I to do anything in the sourcecode ? Try it. Remove the spaces as I mentioned. Bye, Henning
[sane-devel] no scanners found (leo s3 scsi-scanner)
Hi,
I've added an entry in the backend for this variant. You might as well wait for
sane 1.10.
But if you're in a hurry, remove the spaces and recompile sane.
eg change
{6, LEO , LEOScan-S3 ,
to
{6, LEO, LEOScan-S3,
Regards,
Frank.
Henning Meier-Geinitz wrote:
Hi,
On Thu, Jan 16, 2003 at 11:01:54PM +0100, axel dammers wrote:
But sane-find-scanner -v -v shows not a 0 behind the scanner name:
Yes, it does:
searching for SCSI scanners:
checking /dev/scanner... open ok
Inquiry for device:
000: 06 00 02 02 1f 00 00 00 4c 45 4f 00 00 00 00 00LEO.
016: 4c 45 4f 53 63 61 6e 2d 53 33 00 00 00 00 00 00LEOScan-S3..
There are the 00 00 ... after the text. The backend expects spaces (32
= 0x20).
Have I to do anything in the sourcecode ?
Try it. Remove the spaces as I mentioned.
Bye,
Henning
___
Sane-devel mailing list
sane-de...@www.mostang.com
http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] no scanners found (leo s3 scsi-scanner)
axel dammers wrote: Hi, thanks for your tip. I compiled it without the spaces in leo.c and the scanner runs !!! Very much thanks for your good help. :-)) Bye, Axel Thanks for the report. Frank.
[sane-devel] no scanners found (leo s3 scsi-scanner)
Hi,
thanks for your answers.
But sane-find-scanner -v -v shows not a 0 behind the scanner name:
searching for SCSI scanners:
checking /dev/scanner... open ok
Inquiry for device:
000: 06 00 02 02 1f 00 00 00 4c 45 4f 00 00 00 00 00LEO.
016: 4c 45 4f 53 63 61 6e 2d 53 33 00 00 00 00 00 00LEOScan-S3..
032: 31 2e 31 301.10
found SCSI scanner LEO LEOScan-S3 1.10 at /dev/scanner
checking /dev/sg0... open ok
Inquiry for device:
000: 06 00 02 02 1f 00 00 00 4c 45 4f 00 00 00 00 00LEO.
016: 4c 45 4f 53 63 61 6e 2d 53 33 00 00 00 00 00 00LEOScan-S3..
032: 31 2e 31 301.10
found SCSI scanner LEO LEOScan-S3 1.10 at /dev/sg0
checking /dev/sg1... failed to open (Invalid argument)
checking /dev/sg2... failed to open (Invalid argument)
- cut -
checking /dev/sgz... failed to open (Invalid argument)
# Your SCSI scanner was detected. It may or may not be supported by
SANE. Try
# scanimage -L and read the backend's manpage.
searching for USB scanners:
checking /dev/usb/scanner... failed to open (Invalid argument)
checking /dev/usb/scanner0... failed to open (Invalid argument)
- cut -
checking /dev/usbscanner15... failed to open (Invalid argument)
# No USB scanners found. If you expected something different, make sure
that
# you have loaded a driver for your USB host controller and have
installed a
# kernel scanner module.
# Scanners connected to the parallel port or other proprietary ports
can't be
# detected by this program.
done
Have I to do anything in the sourcecode ?
Bye
Axel
Henning Meier-Geinitz schrieb:
Hi,
On Wed, Jan 15, 2003 at 09:59:03PM +0100, axel dammers wrote:
It's right, the name of the scanner is LEO LEOScan-S3.
Here are the output of SANE_DEBUG_LEO=255 scanimage -L:
[sanei_debug] Setting debug level of leo to 255.
[leo] sane_init
[leo] This is sane-leo version 1.0-9
[leo] (C) 2002 by Frank Zago
[leo] attach_scanner: /dev/sg0
[leo] leo_init: enter
[leo] leo_init: exit
[leo] attach_scanner: opening /dev/sg0
[leo] leo_identify_scanner: enter
[leo] device is LEO LEOScan-S3 1.10
[leo] leo_identify_scanner: exit, device not supported
Looks like a detection problem. I don't know anything about the leo
backend, but here is part of the source code (backend/leo.c):
static const struct scanners_supported scanners[] = {
{6, ACROSS , ,
Across, FS-1130},
{6, LEO , LEOScan-S3 ,
Leo, S3}
};
So the backend expects spaces after the names but the SCSI inqiry
seems to put a 0 after the names (?).
You can verify that by running sane-find-scanner -v -v and looking at
the SCSI inqiry. If there is a 0 after the names, that's the problem.
You can try to modify the source code by removing the spaces after LEO
and LEOScan-S3 to find out,i ft this is the problem.
In the dll.conf I only uncomment the line with leo.
Ok.
Bye,
Henning
___
Sane-devel mailing list
sane-de...@www.mostang.com
http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] no scanners found (leo s3 scsi-scanner)
Hi, thanks for your answer, It's right, the name of the scanner is LEO LEOScan-S3. Here are the output of SANE_DEBUG_LEO=255 scanimage -L: [sanei_debug] Setting debug level of leo to 255. [leo] sane_init [leo] This is sane-leo version 1.0-9 [leo] (C) 2002 by Frank Zago [leo] attach_scanner: /dev/sg0 [leo] leo_init: enter [leo] leo_init: exit [leo] attach_scanner: opening /dev/sg0 [leo] leo_identify_scanner: enter [leo] device is LEO LEOScan-S3 1.10 [leo] leo_identify_scanner: exit, device not supported [leo] ERROR: attach_scanner: scanner-identification failed [leo] leo_free: enter [leo] leo_close: enter [leo] leo_close: exit [leo] leo_free: exit [leo] sane_init: leave [leo] sane_get_devices: enter [leo] sane_get_devices: exit 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). [leo] sane_exit: enter [leo] sane_exit: exit In the dll.conf I only uncomment the line with leo. When this is not a failure of sane, then it could only a problem with the SCSI cable. Bye Axel Henning Meier-Geinitz schrieb: Hi, On Tue, Jan 14, 2003 at 10:56:40PM +0100, axel dammers wrote: I am trying to make my old SCSI scanner Leo S3 work. sane-find-scanner (as root) say's: found SCSI scanner 2LEO LEOScan-S3 1.10 at /dev/scanner found SCSI scanner 2LEO LEOScan-S3 1.10 at /dev/sg0 Shouldn't this be a instead of the 2? scanimage -d leo:/dev/scanner or scanimage -d leo:/dev/sg0 say's (as root): scanimage: open of device leo failed: Invalid argument Use SANE_DEBUG_LEO=255 scanimage -L to get debug output. I am using sane-1.0.9-1 with SuSE8.1. This sane-Version should supports the scanner. Permissions on /dev/sg0: 640 Link: /dev/scanner - /dev/sg0 The contents of /etc/sane.d/leo.conf: scsi ACROSS * Scanner * * * 0 /dev/sg0 The Leo backend seems to expect the vendor id ACCROSS and no LEO. However in the source code, LEO is also detected, so it should work with the second line. Why does scanimage not recognize my scanner and why can't I scan ? If you can't find out by looking at the debug log, post it here. By the way, yast2 from SuSE-Linux don't know the LEO S3, only the LEO FS-1130. Tell SuSE about that :-) leo is listed in dll.conf? Bye, Henning ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] no scanners found (leo s3 scsi-scanner)
Henning Meier-Geinitz wrote:
Hi,
On Wed, Jan 15, 2003 at 09:59:03PM +0100, axel dammers wrote:
It's right, the name of the scanner is LEO LEOScan-S3.
Here are the output of SANE_DEBUG_LEO=255 scanimage -L:
[sanei_debug] Setting debug level of leo to 255.
[leo] sane_init
[leo] This is sane-leo version 1.0-9
[leo] (C) 2002 by Frank Zago
[leo] attach_scanner: /dev/sg0
[leo] leo_init: enter
[leo] leo_init: exit
[leo] attach_scanner: opening /dev/sg0
[leo] leo_identify_scanner: enter
[leo] device is LEO LEOScan-S3 1.10
[leo] leo_identify_scanner: exit, device not supported
Looks like a detection problem. I don't know anything about the leo
backend, but here is part of the source code (backend/leo.c):
static const struct scanners_supported scanners[] = {
{6, ACROSS , ,
Across, FS-1130},
{6, LEO , LEOScan-S3 ,
Leo, S3}
};
So the backend expects spaces after the names but the SCSI inqiry
seems to put a 0 after the names (?).
You can verify that by running sane-find-scanner -v -v and looking at
the SCSI inqiry. If there is a 0 after the names, that's the problem.
You can try to modify the source code by removing the spaces after LEO
and LEOScan-S3 to find out,i ft this is the problem.
Yes. That seems to be the problem. I have some scsi traces for that scanner,
and
there is spaces after the names. However the firmware version is not the same
(3.01 instead of 1.10 here).
I that fixes your issue, I'll add an entry for it before the next release of
SANE.
Frank.
[sane-devel] no scanners found (leo s3 scsi-scanner)
Hello, I am trying to make my old SCSI scanner Leo S3 work. sane-find-scanner (as root) say's: found SCSI scanner 2LEO LEOScan-S3 1.10 at /dev/scanner found SCSI scanner 2LEO LEOScan-S3 1.10 at /dev/sg0 scanimage -d leo:/dev/scanner or scanimage -d leo:/dev/sg0 say's (as root): scanimage: open of device leo failed: Invalid argument scanimage say's (at root): scanimage: no SANE device found cdrecord -scanbus say's: 0,2,0 2) 'LEO' 'LEOScan-S3' '1.10' Scanner all other SCSI-IDs are unused I am using sane-1.0.9-1 with SuSE8.1. This sane-Version should supports the scanner. Permissions on /dev/sg0: 640 Link: /dev/scanner - /dev/sg0 The contents of /etc/sane.d/leo.conf: scsi ACROSS * Scanner * * * 0 /dev/sg0 Why does scanimage not recognize my scanner and why can't I scan ? By the way, yast2 from SuSE-Linux don't know the LEO S3, only the LEO FS-1130. Much thanks.
