Canon scanner not recognized

Deutsch (German) Hardware
1

openSUSE 13.1 64bit KDE 4.11.5 - Canon LIDE 110 scanner connected via USB

Xsane and Scanlite report that no scanner is attached. YaST hardware reports a not configured USB scanner, identifies the vendor and product and USB location. I click on “Edit” and the correct model is highlighted and it tells me that “Driver genesys shoud provide complete functionality”. Yet when I click on “Next” it reports “genesys - No scanner recognized by this driver”. What am I doing wrong?

Thanks in advance.

P.S. Why does YaST not allow me to mark, copy or paste to this message?

2

It might be that a udev rule for your particular chipset is not included perhaps, although /etc/udev/rules.d/55-sane.rules and the associated 56-sane-backends-autoconfig.rules should take care of this if the chipset is recognised. You might want to check this and share

lsusb

The SANE page suggests it is indeed supported by the genesys driver:
http://www.sane-project.org/sane-mfgs.html#Z-CANON

Try configuring manually. You’ll need to edit /etc/sane.d/dll.conf (as root) like this

sudo kwrite /etc/sane.d/dll.conf

Uncomment the genesys driver (by removing the ‘#’ character).

You should be able to launch your favourite scanning application. I use simple-scan (with package of the same name), but skanlite, scangui, or even xsane should work.

Let us know how that goes.

3

I’m currently using a Canon Lide 110 with 64bit openSUSE 13.1 (KDE 4.13)

Recognised, installed and working without problem using the genesys driver.

/etc/udev/rules.d has

55-libsane.rules
56-sane-backends-autoconfig.rules

both dated 28-09-2013

If they are potentially of any use I’ll post them to susepaste.

There does seem to be a peculiarity with that particular model… I’d be interested if you now start getting:

kernel:     0.786019 pci 0000:00:13.1: OHCI: BIOS handoff failed (BIOS bug?)

errors logged on boot.

4

Sorry, with respect to editing I meant

kdesu kwrite /etc/sane.d/dll.conf

although typically use nano instead.

5

That worked, although I had to…

sudo joe /etc/sane.d/dll.conf

…as

sudo kwrite /etc/sane.d/dll.conf

produced…

kwrite: cannot connect to X server

…since the X server was running for “user”. I only mention that in case someone else encounters the same problem.

Thank you very much for the speedy solution.

6

I didn’t see your correction until I finished my response.

7

Yep, guessed as much. (I don’t usually use graphical editors. Just slipped in my quickly written post).

Anyway, you can scan okay now?

8

Yes. I like basic solutions such as editing *conf files. I learn more that way.

9

Same here. Anyway, glad to have been of help. :slight_smile: