Could comeone please have a look at the following debug output and give
me some clues to what the problem could be. It appears to find the canon
ok, but then down the bottom it appears to be trying to open another
<blank> device. Is this correct, and if so what could the causes be?
-------- Original Message --------
Subject: Re: [sane-os2] Canon 620 S Flatbed scanner
Date: Fri, 25 May 2001 22:32:04 +1000
From: Ed Durrant <edurrant@bigpond.net.au>
Reply-To: sane-os2@yahoogroups.com
To: sane-os2@yahoogroups.com
References:
<Pine.BSF.4.10.10105251054280.96858-100000@studenti.ing.unipi.it>
Mentore - You're right !!
Mike, I think we're getting closer !
I re-created my canon.conf using epm rather than e and running help
(or -L) scanimage can see the canon scanner ! The output is as follows:
[D:\temp]epm canon.conf
[D:\temp]scanimage.exe -d CANON --help
Usage: scanimage.exe [OPTION]...
Start image acquisition on a scanner device and write PNM image data to
standard output.
-b, --batch=FORMAT working in batch mode
--format=pnm|tiff file format of output file
-d, --device-name=DEVICE use a given scanner device (e.g.
hp:/dev/scanner)
-h, --help display this help message and exit
-L, --list-devices show available scanner devices
-T, --test test backend thoroughly
-v, --verbose give even more status messages
-V, --version print version information
--accept-md5-only only accept authorization requests using md5
scanimage.exe: open of device CANON failed: Operation not supported
Type ``scanimage.exe --help -d DEVICE'' to get list of all options for
DEVICE.
List of available devices:
pnm:0 pnm:1 canon:b2t2l0
Attempting a run of scanimage with debug enabled now gets further with
the
following output:
[D:\temp]scantest
[D:\temp]set SANE_DEBUG_CANON=16
[D:\temp]set SANE_DEBUG_SANEI_SCSI=255
[D:\temp]scanimage -d canon
[sanei_debug] Setting debug level of canon to 16.
[canon] >> sane_init
[canon] sane_init: sane-backends 1.0.4
[canon] >> attach_one
[canon] >> attach
[canon] attach: opening b2t2l0
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] OS/2: installed adapters 3
[sanei_scsi] OS/2: ASPI manager is 'OS2ASPI Dev Mgr ATA_ATAPI '
[sanei_scsi] OS/2: host adapter is 'ATA_ATAPI '
[sanei_scsi] OS/2: unique id is ''
[sanei_scsi] open_aspi: open temporary file 'asa00102'
[sanei_scsi] OS/2: adapter#00 'ATA_ATAPI '
[sanei_scsi] OS/2: id#00 status=82h
[sanei_scsi] OS/2: id#01 status=82h
[sanei_scsi] OS/2: id#02 status=82h
[sanei_scsi] OS/2: id#03 status=82h
[sanei_scsi] OS/2: id#04 status=82h
[sanei_scsi] OS/2: id#05 status=82h
[sanei_scsi] OS/2: id#06 status=82h
[sanei_scsi] OS/2: adapter#02 'ADPT AHA-2910 Ç'
[sanei_scsi] OS/2: id#00 status=82h
[sanei_scsi] OS/2: id#01 status=82h
[sanei_scsi] OS/2: id#02 status=01h
[sanei_scsi] OS/2: type is 'scanner'
[sanei_scsi] OS/2 'CANON IX-06035E 1.02'
[sanei_scsi] OS/2: id#03 status=82h
[sanei_scsi] OS/2: id#04 status=82h
[sanei_scsi] OS/2: id#05 status=82h
[sanei_scsi] OS/2: id#06 status=82h
[sanei_scsi] open_aspi: close temporary file 'asa00102'
[canon] attach: sending (standard) INQUIRY
[canon] attach: sending TEST_UNIT_READY
[canon] attach: sending RESERVE UNIT
[canon] attach: sending GET SCAN MODE for scan control conditions
[canon] scan mode byte[0] = 19
[canon] scan mode byte[1] = 0
[canon] scan mode byte[2] = 0
[canon] scan mode byte[3] = 0
[canon] scan mode byte[4] = 32
[canon] scan mode byte[5] = 14
[canon] scan mode byte[6] = 0
[canon] scan mode byte[7] = 0
[canon] scan mode byte[8] = 1
[canon] scan mode byte[9] = 244
[canon] scan mode byte[10] = 0
[canon] scan mode byte[11] = 1
[canon] scan mode byte[12] = 1
[canon] scan mode byte[13] = 1
[canon] scan mode byte[14] = 0
[canon] scan mode byte[15] = 0
[canon] scan mode byte[16] = 0
[canon] scan mode byte[17] = 0
[canon] scan mode byte[18] = 2
[canon] scan mode byte[19] = 0
[canon] scan mode byte[20] = 0
[canon] scan mode byte[21] = 32
[canon] scan mode byte[22] = 115
[canon] scan mode byte[23] = 0
[canon] scan mode byte[24] = 69
[canon] scan mode byte[25] = 32
[canon] scan mode byte[26] = 32
[canon] scan mode byte[27] = 32
[canon] scan mode byte[28] = 32
[canon] scan mode byte[29] = 32
[canon] scan mode byte[30] = 32
[canon] scan mode byte[31] = 32
[canon] scan mode byte[32] = 49
[canon] scan mode byte[33] = 46
[canon] scan mode byte[34] = 48
[canon] scan mode byte[35] = 50
[canon] scan mode byte[36] = 0
[canon] scan mode byte[37] = 0
[canon] scan mode byte[38] = 0
[canon] scan mode byte[39] = 0
[canon] scan mode byte[40] = 0
[canon] scan mode byte[41] = 0
[canon] scan mode byte[42] = 0
[canon] scan mode byte[43] = 0
[canon] scan mode byte[44] = 0
[canon] scan mode byte[45] = 0
[canon] scan mode byte[46] = 0
[canon] scan mode byte[47] = 0
[canon] scan mode byte[48] = 0
[canon] scan mode byte[49] = 0
[canon] scan mode byte[50] = 0
[canon] scan mode byte[51] = 0
[canon] scan mode byte[52] = 0
[canon] scan mode byte[53] = 0
[canon] scan mode byte[54] = 0
[canon] scan mode byte[55] = 0
[canon] scan mode byte[56] = 0
[canon] scan mode byte[57] = 0
[canon] scan mode byte[58] = 0
[canon] scan mode byte[59] = 0
[canon] scan mode byte[60] = 0
[canon] scan mode byte[61] = 0
[canon] scan mode byte[62] = 0
[canon] scan mode byte[63] = 0
[canon] scan mode byte[64] = 0
[canon] scan mode byte[65] = 0
[canon] scan mode byte[66] = 0
[canon] scan mode byte[67] = 0
[canon] scan mode byte[68] = 0
[canon] scan mode byte[69] = 0
[canon] scan mode byte[70] = 0
[canon] scan mode byte[71] = 0
[canon] scan mode byte[72] = 0
[canon] scan mode byte[73] = 0
[canon] attach: sending (extended) INQUIRY
[canon] attach: sending MODE SENSE
[canon] dev->sane.name = 'b2t2l0'
[canon] dev->sane.vendor = 'CANON'
[canon] dev->sane.model = 'IX-06035E '
[canon] dev->sane.type = 'flatbed scanner'
[canon] >> get tpu stat
[canon] >> get adf stat
[canon] bmu=0
[canon] mud=600
[canon] xres_default=600
[canon] xres_range.max=600
[canon] xres_range.min=75
[canon] xres_range.quant=1
[canon] yres_default=600
[canon] yres_range.max=600
[canon] yres_range.min=75
[canon] xres_range.quant=1
[canon] x_range.max=14157545
[canon] y_range.max=19462116
[canon] x_adf_range.max=-1
[canon] y_adf_range.max=-1
[sanei_scsi] OS/2: ASPI closed
[canon] << attach
[canon] << attach_one
[canon] << sane_init
[canon] >> sane_open
[canon] >> attach
[canon] attach: opening
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: device name is not valid
[canon] attach: open failed: Invalid argument
scanimage: open of device canon failed: Invalid argument
[canon] >> sane_exit
[canon] << sane_exit
[D:\temp]
But I still get "invalid argument" as you can see.
Any ideas ??
Ed Durrant.
Mentore Siesto wrote:
>
> On Thu, 24 May 2001, Yuri Dario wrote:
>
> YD >Hi,
> YD >
> YD >>But since I have aspi support loaded, doesn't this make the IDE
> YD >>channels look like SCSI ? I also run CD/Record and I'm pretty
> YD >>sure it sees my IDE attached burner as if it were a SCSI one.
> YD >
> YD >all people using SANE have ASPI support loaded. But I didn't verify
> YD >latest builds of aspirout.sys by Paul.
>
> IIRC seeing IDE as SCSI devices is a feature of DANIATAPI.FLT filter,
> valid only for IDE drives. ASPI is another thing.
>
> BTW, what editor did you use to build the canon.conf file? I use EPM, not
> E nor TEDIT (they leave a Ctrl-Z character at the end of the file, and
> AFAIK SANE doesn't like it).
>
> --
> Mentore Siesto
> Team OS/2 Italia
> Home page:
> http://www.geocities.com/Tokyo/Temple/8529/index.html
Unsubscribe: sane-os2-unsubscribe@egroups.com
List owner: sane-os2-owner@egroups.com
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Fri May 25 2001 - 18:41:40 PDT