Hi,
I was having difficulty with a CanoScan 300 and sane-1.0.{1,2} (original
message appended). Someone in Germany (I think) mailed me wanting to know
the solution (if I found one) since they seemed to have the same problem
with a CanoScan 600, but I didn't keep the message and the mailing list
archive doesn't have a link for April yet.
Anyway, it's working now with 1.0.2 ...
I had to apply a patch to the sg.c device driver in the Linux kernel and
rebuild it. The patch is on the web site for the SANE Canon driver, and
relates to the size of SCSI command structures. [Has this patch been
submitted for more recent Linux kernels?]
I also cleared out all the drivers from dll.conf *except* canon. It was
taking scanimage/xscanimage about 30 seconds to try out all the drivers
(including the serial digital cameras) before it did anything, so it looked
like it was hung when it wasn't.
My CanoScan 300 is now working well -- thanks everyone!
Robin Kirkham CSIRO Manufacturing Science and Technology
Project Engineer Locked Bag 9, Preston 3072, Australia
robin.kirkham@cmst.csiro.au Phone: +61 3 9662-7756 Fax: +61 3 9662-7853
> From: Robin Kirkham <robin.kirkham@cmst.csiro.au>
> Subject: CanoScan 300 and sane-1.0.{1,2}
> Date: Fri, 14 Apr 2000 13:57:04 +1000
>
> Hi,
>
> I'm having trouble with this unit and both 1.0.1 and 1.0.2 (compiled
> from the standard distribution sources). It used to work fine with 1.00
> (or maybe it was earlier version) on an older system. I'm now running
> Mandrake (i.e., RHL) 6.1.
>
> 1. The canon.conf file does not get installed for either 1.0.1 or 1.0.2
> (but easily inserted by hand "scsi CANON"). tool/find-scanner finds
> the scanner OK. dll.conf contains just "canon".
>
> 2. With 1.0.1, xscanimage works fine, unless you save the scanner options.
> The next time you run it, it segfaults. The problem seems to be related
> to reading back the ~/.sane/xscanimage/canon+....rc file. If I delete
> this file, it works again (obviously the saved scanner options are lost).
> If you save them again, then the next time it segfaults ...
>
> 3. With 1.0.2, I don't get as far as that. scanimage hangs forever.
> I tried getting some debug output for scanimage -L (the debug level 7
> is a guess):
>
> % export SANE_DEBUG_CANON=7
> % scanimage -L
> [sanei_init_debug]: Setting debug level of canon to 7.
> [canon] >> sane_init
> [canon] sane_init: sane 1.0.2
> [canon] >> attach_one
> [canon] >> attach
> [canon] attach: opening /dev/sgb
> [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] attach: GET SCAN MODE for scan control conditions failed
> [canon] << attach_one
> [canon] << sane_init
> [canon] >> sane_get_devices
> [canon] << sane_get_devices
>
> The scanner does not appear to do anything.
> Obviously something was the matter with GET SCAN MODE but I don't know
> what that is. In any case, I don't think scanimage should hang...
>
> Can someone please offer some pointers for either or both of these problems?
>
> Thanks
>
> Robin Kirkham CSIRO Manufacturing Science and Technology
> Project Engineer Locked Bag 9, Preston 3072, Australia
> robin.kirkham@cmst.csiro.au Phone: +61 3 9662-7756 Fax: +61 3 9662-7853
-- 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 : Tue Apr 25 2000 - 21:07:43 PDT