[sane-devel] New to list - need help to understand sane

Henning Meier-Geinitz henning at meier-geinitz.de
Sat Nov 16 11:19:19 GMT 2002


Hi,

On Sat, Nov 16, 2002 at 01:54:58PM +1030, William Heidrich wrote:
> running xsane canon630u

It shouldn't be necessary to add the name of the backend. So if you
use xsane and your scanner isn't listed, something is wrong.

> I get: failed to open device - invalid argument

Hm. Are you sure, that you have only one installation of SANE on your
system?

> If there are any suggestions. Also, how do I connect the canon630u.conf
> file to sane?

No need to connect, it's read automatically by the backend.

> T:  Bus=01 Lev=02 Prnt=02 Port=01 Cnt=02 Dev#=  4 Spd=12  MxCh= 0
> D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
> P:  Vendor=04a9 ProdID=2204 Rev= 0.01
> S:  Product=CanoScan FB630U
> C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=500mA
> I:  If#= 0 Alt= 0 #EPs= 2 Cls=10(unk. ) Sub=01 Prot=00 Driver=(none)
> E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms

That's your scanner. It's not detected by the kernel scanner driver,
but that shouldn't matter, as libusb detects it.

> [root at localhost root]# sane-find-scanner
> found USB scanner (vendor=0x04a9, product=0x2204 [CanoScan FB630U]) at libusb:001:004

Ok, found by libusb.

> [root at localhost root]# SANE_DEBUG_CANON630U=255 scanimage -L
> [sanei_debug] Setting debug level of canon630u to 255.
> [canon630u] sane_init: version_code != 0, authorize != 0
> [canon630u] sane_init: SANE Canon630u backend version 1.0.1 from
> sane-backends-1.0.9
> 1.0.9
> [canon630u] reading configure file canon630u.conf
> [canon630u] attach_matching_devices(usb 0x04a9 0x2204)

Your first line in canon630u.conf is

usb 0x04a9 0x2204

That's ok. It will find your scanner.

> [canon630u] attach_scanner: libusb:001:004
> [canon630u] attach_scanner: opening libusb:001:004
> [canon630u] CANON_open_device: `libusb:001:004'
> [canon630u] CANON_close_device:
> [canon630u] finished reading configure file
> [canon630u] sane_get_devices(local_only = 0)
> device `canon630u:libusb:001:004' is a CANON Canoscan FB630U flatbed scanner

Ok, your scanner is found. Now does scanning work?

scanimage >image.pnm

> *** contents of canon630u.conf ****
> 
> # Autodetect the Canon CanoScan FB630u
> #usb 0x04a9 0x2204
> 
> device libusb:001:004
> 
> # device list for non-linux-systems (enable if autodetect fails):
> #/dev/scanner
> #/dev/usb/scanner0

No, sorry. This is not your canon630u.conf. At least not the one you
used when running scanimage -L.

Did you compile sane 1.0.9 yourself? Then the config files are in
/usr/local/etc/sane.d/ .

Don't touch the config file, the original one is correct and works, as
you've seen by scanimage -L.

"device" is not allowed in canon630u.conf. If you really want to add
device names, just do so without "device". See the examples at the end
of the file. But you don't need that.

I guess the real issue is that xsane doesn't work but scanimage does.
If you don't have two SANE installations, the only reason I can think
of are permission problems. E.g. if you run scanimage as root and
xsane as user. See man sane-usb for some hints about this.

Bye,
  Henning




More information about the sane-devel mailing list