[SOLVED] Problems setting up scanner in Slackware 13.0

tallship · 03-05-2010, 12:01 AM

I'm having problems getting my Canon MP-210 printer/scanner recognized as a scanner device in Slackware 13.0.

CUPS setup was a breeze - in less than two seconds it was installed and within 10 more seconds it was printing a test page.

Its URI is here, according to CUPS: usb://Canon/MP210%20series (Printing works flawlessly).

My non-privileged user account is a member of the 'wheel', 'scanner', and 'plugdev' groups in /etc/group (among the others recommended by the adduser script. I've tried running xsane as root (Still no devices found) with no success, and the CLI 'scanimage -L' doesn't produce anything either.

They just report that there is no configured device.

I've run 'sane-find-scanner' and it reports the following:

Code:

found USB scanner (vendor=0x04a9 [Canon], product=0x1721 [MP210 series]) at libusb:001:003

Rebooting and unplugging/plugging in the scanner produces no positive results.

/etc/sane.d/dll.conf has the following canon lines in it:

Code:

canon
canon630u
#canon_pp

I believe the appropriate entry is the canon630u.

/etc/sane.d/canon630u.conf contains the following:

Code:

# Options for the canonusb backend

# Autodetect the Canon CanoScan FB630u
usb 0x04a9 0x2204

# device list for non-linux-systems (enable if autodetect fails):
#/dev/scanner
#/dev/usb/scanner0

The last entry in my /proc/bus/usb/devices is:

Code:

T:  Bus=01 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#=  3 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=04a9 ProdID=1721 Rev= 1.05
S:  Manufacturer=Canon
S:  Product=MP210 series
S:  SerialNumber=F32369
C:* #Ifs= 2 Cfg#= 1 Atr=c0 MxPwr=  2mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none)
E:  Ad=07(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=88(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=89(I) Atr=03(Int.) MxPS=  64 Ivl=128ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=07(print) Sub=01 Prot=02 Driver=usblp
E:  Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms

I've been reading the only thread I can find here or anywhere else related to Scanners and Slackware that are even remotely relevant, and the thread here is actually consistent with my problem, although it's almost three years old.

That thread is here:

http://www.linuxquestions.org/questi...ckware-450939/

It's a good starting point to follow what I've been going through while checking off the list. The one thing I've discovered inadvertently is that there is no longer an rc.hotplug, an /sbin/hotplug, etc. Not sure where hotplug has migrated to.

I've also tried Eric's (AlienBob), and Allend's suggestions to mount /proc/bus/usb, which seemed to fix the problem the OP in that thread had, although it was a seriously fugly kludge.

Here's what I put in /etc/fstab based on Allend's suggestion:

Code:

scanner          /proc/bus/usb    usbfs       auto,devmode=0666 0  0

That didn't seem to change anything. And here's what I put in /etc/fstab based on Alien Bob's, suggestion from that earlier thread:

Code:

usbfs            /proc/bus/usb    usbfs       devgid=10,devmode=0660         0   0

They both mount just fine, but no results still, even when I try to run 'scanimage', which continues to report (as root) that there is no device configured.

I've checked the driver on the SANE website, and the 'canon630u' driver shows that the MP210 is indeed a tested and supported scanner up to 600 DPI, and the device works fine when I *cough* plug it into a wyndoze box.

wrt Alien Bob's mount suggestions. 'mount' reports the following after a reboot:

Code:

usbfs on /proc/bus/usb type usbfs (rw,devgid=10,devmode=0660)

Everything seems to check out to me but still.... Grrrr

Well, I'm all ears and out of ideas and resources for this one. If anyone wants to chime in I'm all ears

mrclisdue · 03-05-2010, 05:04 AM

I set up a Canon MP240 2 days ago, using the debian *scanner* drivers found here:

http://ubuntuforums.org/showthread.php?t=953292&page=6

The printer set up fine with the cups/gutenburg drivers included with the installation (albeit, it would only function on *color* mode - for grayscale the setting was found only during the dialog when printing...)

I made no changes to anything in order to get the scanner going - ie. it worked out of the box once the driver was installed - I didn't add the user to any additional groups (just the default install groups), and made no changes to anything else - it simply worked....

Needless to say, after wresting with quite a few scanners over the years, I was pleasantly surprised at how simple this was.

hth,

dive · 03-05-2010, 05:48 AM

It sounds like udev isn't setting the correct permissions. The proper way would be to correct the rule to allow scanner group access.

I made a small shell script though which you can find here:

http://www.unrealize.co.uk/scripts/sane/scanperms

This would need to be sourced from /etc/rc.d/rc.local and changes the permissions to allow anyone in scanner group access.

gapan · 03-05-2010, 07:56 AM

Add your user to the lp group too.

allend · 03-05-2010, 08:20 AM

The Canon MP210 is listed in /lib/udev/rules.d/80-libsane.rules and your sane-find-scanner output shows that it is being detected. Do you have an appropriate driver installed? You may have to muck about with an rpm or deb package.
http://software.canon-europe.com/sof...481.asp?model=

[edit] Just reviewed the SANE page that you mentioned. It looks as though that scanner was supported in /usr/lib/sane/libsane-pixma.so since /usr/lib/sane/libsane-pixma.so.1.0.15.
What is the output of 'ls -l /usr/lib/sane/libsane-pixma*' ?
What is the output of 'ls -l /dev/bus/usb/001' ? [/edit]

Chuck56 · 03-05-2010, 08:50 AM

Do you have the Canon PIXMA MP-210? According to the SANE database it uses the sane "pixma" backend.

http://www.sane-project.org/sane-mfgs.html#Z-CANON

Checking the other critical files for scanning:

libsane rules has MP210
/lib/udev/rules.d/80-libsane.rules

dll.conf has pixma
/etc/sane.d/dll.conf

add your user to the scanner group
/etc/group

Test commands:

checks if sane is configured properly
scanimage -d test -T

checks out if pixma is configured properly
scanimage -d pixma -T

scanner should come to life
scanimage -L

allend · 03-05-2010, 09:03 AM

Another thought, perhaps you should comment out the canon* lines in /etc/sane.d/dll.conf so that they cannot conflict with the pixma entry.

dive · 03-05-2010, 09:54 AM

If it works as root then it is a permissions problem, not driver or conf.

allend · 03-05-2010, 07:21 PM

Good, your libsane-pixma entries look fine and the scanner is showing under /dev/bus/usb/001.
Have you tried 'scanimage --device-name pixma:04A91721_F32369' ? Perhaps the serial number is that reported in /proc/bus/usb/devices "S: SerialNumber=F32369".

tallship · 03-05-2010, 10:47 PM

Quote:

Originally Posted by allend

Good, your libsane-pixma entries look fine and the scanner is showing under /dev/bus/usb/001.
Have you tried 'scanimage --device-name pixma:04A91721_F32369' ? Perhaps the serial number is that reported in /proc/bus/usb/devices "S: SerialNumber=F32369".

When commenting out various lines in dll.conf, and the corresponding *.conf files in /etc/sane.d/, each followed by a reboot (very tedious) so that only one device is 'supposedly' enabled, (in order to avoid conflicts) I get the following responses, over and over:

Code:

# scanimage --device-name pixma:04A91721_F32369
scanimage: open of device pixma:04A91721_F32369 failed: Invalid argument


# scanimage -d pixma -T
scanimage: open of device pixma failed: Invalid argument


# scanimage -d canon -T
scanimage: open of device canon failed: Invalid argument


# scanimage -d canon630u -T
scanimage: open of device canon630u failed: Invalid argument


# scanimage -L

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).


# scanimage -d test -T
scanimage: scanning image of size 157x196 pixels at 8 bits/pixel
scanimage: acquiring gray frame, 8 bits/sample
scanimage: reading one scanline, 157 bytes...    PASS
scanimage: reading one byte...        PASS
scanimage: stepped read, 2 bytes...     PASS
scanimage: stepped read, 4 bytes...     PASS
scanimage: stepped read, 8 bytes...     PASS
scanimage: stepped read, 16 bytes...     PASS
scanimage: stepped read, 32 bytes...     PASS
scanimage: stepped read, 64 bytes...     PASS
scanimage: stepped read, 128 bytes...     PASS
scanimage: stepped read, 256 bytes...     PASS
scanimage: stepped read, 255 bytes...     PASS
scanimage: stepped read, 127 bytes...     PASS
scanimage: stepped read, 63 bytes...     PASS
scanimage: stepped read, 31 bytes...     PASS
scanimage: stepped read, 15 bytes...     PASS
scanimage: stepped read, 7 bytes...     PASS
scanimage: stepped read, 3 bytes...     PASS
root@condor:~#

I'm spending a ridiculous amount of time looking for a solution that is right in front of us.

Quote:

Originally Posted by dive

It sounds like udev isn't setting the correct permissions. The proper way would be to correct the rule to allow scanner group access.

I made a small shell script though which you can find here:

http://www.unrealize.co.uk/scripts/sane/scanperms

This would need to be sourced from /etc/rc.d/rc.local and changes the permissions to allow anyone in scanner group access.

At startup it's reporting that it worked:

Code:

Changing group ownership: /usr/bin/chgrp scanner /proc/bus/usb/001/003
Changing group read/write permissions: /usr/bin/chmod g+rw /proc/bus/usb/001/003
Permissions successfully set.

Any ideas? I've even posted this URL over at the SANE devel lists and posted on #sane on freenode. There doesn't seem to have been anyone home over there all day - no responses yet...

allend · 03-05-2010, 11:06 PM

You could try installing the latest 1.0.20 version of Sane library that is available in -current.
It has numerous fixes for Canon PIXMA according to this:
http://mp610.blogspot.com/

tallship · 03-06-2010, 01:29 AM

Well, following the upgradepkg to 1.0.20 I get the following error:

Code:

scanimage: error while loading shared libraries: libv4l1.so.0: cannot open shared object file: No such file or directory

I uninstalled and reinstalled 1.0.20, and then after receiving the same message of the missing library I uninstalled again and re-installed 1.0.19 now 'scanimage -d test -T' is reporting that everything is fine again.

so I hunted down the missing dependancies and had to install/upgrade two more packages (hoping this doesn't break anything else).

Code:

# installpkg /usr/local/packages/libv4l-0.6.1-i486-1.txz

# upgradepkg libjpeg-6b-i486-5%/usr/local/packages/libjpeg-v8-i486-1.txz

# 'scanimage -d test -T' once again reports that everything is okay. I'll be right back because now it's time for another reboot...

tallship · 03-06-2010, 02:46 AM

Okay then,

I want to extend a very special thanks to you @allend for sticking with me through thick and thin on this issue

Also thank you very much @Chuck56, for putting us on the right track, and although I'm not sure if it made a difference in this case or not (I'll test later), @dive for the perm script drop-in for rc.local

Thanks also goes out to @mrclisdue, even considering that I really didn't want to go down that route unless I absolutely had to; @gapan, although I think that the 'lp' group would have been more appropriate (or will be) when I decide to setup lpd, and CUPS was already working (btw, I'm a big fan of SalixOS and I'll be stopping by there again soon); and also Eric (Alien Bob) for the leads I got from the earlier thread back in -07- on this topic.

um.. and I would be remiss in my responsibilities if I didn't put out a big thanks to Patrick for bundling up the sane 1.0.20, lib4vl, and libjpeg-v8 packages that are now in slackware-current!!!!

Basically, what I did from that last post was to reboot (um... could I have just exited X and ./rc.messagebus restart 'ed instead?) and verify that even though I moved out all of the config files I had previously configured, that canon630u.conf indeed had autodetected the scanner again.

Once I did that, I created an entry for 'pixma' in dll.conf, removed the line:
usb 0x04a9 0x2204
from canon630u.conf and rebooted again.

Interestingly enough, pixma.conf still doesn't have ANY uncommented entries, although it's included in the 1.0.20 backend (and noting that there was still no entry for it in dll.conf until I put one there).

My only assumption at this point, is that I'm using the canon.conf file, which looks like this:

Code:

#canon.conf
/dev/scanner
#/dev/sg0

so perhaps it was the /etc/fstab and/or dive's perm setting script in combination with the new backend and libraries after all?

dmesg reports this:

Code:

usb 1-4: usbfs: interface 1 claimed by usblp while 'scanimage' sets config #1
usb 1-4: usbfs: interface 1 claimed by usblp while 'scanimage' sets config #1
usb 1-4: usbfs: interface 1 claimed by usblp while 'scanimage' sets config #1
usb 1-4: usbfs: interface 1 claimed by usblp while 'xsane' sets config #1
usb 1-4: usbfs: interface 1 claimed by usblp while 'xsane' sets config #1
usb 1-4: usbfs: interface 1 claimed by usblp while 'xsane' sets config #1

And I can't actually remember the name of the device from the console messages during boot, but I'll take note later.

Bottom line, everything works now, and as soon as I get a chance to start breaking things in a systematic way I'll be able to author a clear and concise fix

Once again, thanks all

Chuck56 · 03-06-2010, 07:11 AM

Glad you got it working! Consolidating your notes on the process is a good idea. Without my notes from installing my Epson scanner I would have fumbled through the same thing all over again when I upgraded from 32 to 64 bit.

allend · 03-06-2010, 08:12 AM

Also glad you got it working. Thanks for your kind words.
Please satisfy my curiosity about the correct device name by posting the output of 'scanimage -L'.