Scanner problem Canon DR-3010C

We have few USB scanners Canon DR-3010C which for some reason do not work under SLED (sled11sp2x64).

sc02:~ # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 1083:161d Canon Electronics, Inc.

[CODE]sc02:~ # sane-find-scanner

sane-find-scanner will now attempt to detect your scanner. If the

result is different from what you expected, first make sure your

scanner is powered up and properly connected to your computer.

No SCSI scanners found. If you expected something different, make sure that

you have loaded a kernel SCSI driver for your SCSI adapter.

found USB scanner (vendor=0x1083, product=0x161d) at libusb:002:002

Your USB scanner was (probably) detected. It may or may not be supported by

SANE. Try scanimage -L and read the backend’s manpage.

Not checking for parallel port scanners.

Most Scanners connected to the parallel port or other proprietary ports

can’t be detected by this program.[/CODE]

And in /var/log/messages you can see:

Nov 26 14:49:20 sc02 kernel: [ 203.108275] usb 2-2: new high-speed USB device number 2 using ehci_hcd Nov 26 14:49:20 sc02 kernel: [ 203.243106] usb 2-2: New USB device found, idVendor=1083, idProduct=161d Nov 26 14:49:20 sc02 kernel: [ 203.243117] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Nov 26 14:49:20 sc02 kernel: [ 203.243124] usb 2-2: Product: CANON DR-3010C Nov 26 14:49:20 sc02 kernel: [ 203.243130] usb 2-2: Manufacturer: CANON

All looks fine, however:

sc02:~ # scanimage -d canon_dr:libusb:002:002 -v scanimage: sane_start: Invalid argument

Xsane gives out the same error.

Any ideas?

sc02:~ # rpm -qa | grep sane sane-backends-1.0.20-7.6.1 xsane-0.995-131.34.13 sane-backends-autoconfig-1.0.20-7.6.1 sc02:~ # sc02:~ # cat /etc/SuSE-release SUSE Linux Enterprise Desktop 11 (x86_64) VERSION = 11 PATCHLEVEL = 2

I think the problem is you’re not passing the correct argument to scanimage. If you look at the man page for scanimage the examples it gives for arguments to -d are in a different format.

What’s the output of

$ scanimage -L

Assuming you get your scanner listed, try using what’s listed as the argument to -d If there’s only one device listed I don’t think you even need to specify it with -d

The scanimage command is automatically generated by Yast when you click on the “Test” drop-down button.
Anyway, here’s more output:

sc02:~ # scanimage -v scanimage: sane_start: Invalid argument sc02:~ # sc02:~ # sc02:~ # scanimage -L device `canon_dr:libusb:002:003' is a CANON DR-3010C scanner sc02:~ # sc02:~ #

[QUOTE=mikewillis;10295]I think the problem is you’re not passing the correct argument to scanimage. If you look at the man page for scanimage the examples it gives for arguments to -d are in a different format.

What’s the output of

$ scanimage -L

Assuming you get your scanner listed, try using what’s listed as the argument to -d If there’s only one device listed I don’t think you even need to specify it with -d[/QUOTE]

Have a look at this
http://old.nabble.com/umax1220u:-sane_start:-Invalid-argument-td21060893.html
The relevant backend in your case appears to be canon_dr so for the debug I think you’d want to use SANE_DEBUG_CANON_DR=255

You could jump straight to trying

$ scanimage -x 100 -y 100 

to see if that causes an error or not.