# Scanner problem Canon DR-3010C

**URL:** <https://forums.suse.com/t/scanner-problem-canon-dr-3010c/23337>\
**Category:** SLED Hardware\
**Created:** [November 26, 2012, 2:06pm UTC](https://forums.suse.com/t/scanner-problem-canon-dr-3010c/23337 "2012-11-26T14:06:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Simeonof](https://avatars.discourse-cdn.com/v4/letter/s/839c29/32.png) [@Simeonof](https://forums.suse.com/u/Simeonof)\
**Post date:** [November 26, 2012, 2:06pm UTC](https://forums.suse.com/t/scanner-problem-canon-dr-3010c/23337/1 "2012-11-26T14:06:23Z")

</div>

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`

---

<div class="post-metadata">

**Author:** ![mikewillis](https://avatars.discourse-cdn.com/v4/letter/m/b2d939/32.png) [@mikewillis](https://forums.suse.com/u/mikewillis)\
**Post date:** [November 26, 2012, 3:08pm UTC](https://forums.suse.com/t/scanner-problem-canon-dr-3010c/23337/2 "2012-11-26T15:08:41Z")

</div>

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

```auto
$ 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

---

<div class="post-metadata">

**Author:** ![Simeonof](https://avatars.discourse-cdn.com/v4/letter/s/839c29/32.png) [@Simeonof](https://forums.suse.com/u/Simeonof)\
**Post date:** [November 26, 2012, 4:32pm UTC](https://forums.suse.com/t/scanner-problem-canon-dr-3010c/23337/3 "2012-11-26T16:32:56Z")

</div>

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

```auto
$ 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]

---

<div class="post-metadata">

**Author:** ![mikewillis](https://avatars.discourse-cdn.com/v4/letter/m/b2d939/32.png) [@mikewillis](https://forums.suse.com/u/mikewillis)\
**Post date:** [November 26, 2012, 10:00pm UTC](https://forums.suse.com/t/scanner-problem-canon-dr-3010c/23337/4 "2012-11-26T22:00:08Z")

</div>

Have a look at this  
[http://old.nabble.com/umax1220u:-sane\_start:-Invalid-argument-td21060893.html](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

```auto
$ scanimage -x 100 -y 100 
```

to see if that causes an error or not.
