Mageia forum

My Canon scanner has always been recognised up until now (Mageia 1 &2 etc), but not with Mageia 3. Below are outputs indicating it's there, but not accessable by Xsane:

Code: Select all

# dmesg
[  469.288963] usb 3-9.4: new full-speed USB device number 7 using xhci_hcd
[  469.313438] usb 3-9.4: New USB device found, idVendor=04a9, idProduct=2206
[  469.313446] usb 3-9.4: New USB device strings: Mfr=64, Product=77, SerialNumber=0
[  469.313451] usb 3-9.4: Product: CanoScan
[  469.313455] usb 3-9.4: Manufacturer: Canon

Code: Select all

$ sane-find-scanner
found USB scanner (vendor=0x04a9, product=0x2206, chip=LM983x?) at libusb:003:007

Code: Select all

$ scanimage -L
No scanners were identified.

/lib/udev/rules.d/60-libsane.rules
# Canon CanoScan N650U/N656U
ATTRS{idVendor}=="04a9", ATTRS{idProduct}=="2206", MODE="0666", GROUP="usb", ENV{libsane_matched}="yes"

What do I do now???

When you run xsane as root, are you able to scan?

Code: Select all

su -
xsane

No. Running any of the above commands as root give same response.

theres some old posts on the gentwo forums that suggest that this scanner has had issues before in other editions of linux.

they seem to suggest that the file /etc/sane.d/canon.conf is missing some options.

can you get this file out of an mga2 system, and compare it.

see if anything has changed, try the older one if it has, etc.

regards peter

Thank you Peter.
I have used this scanner with all versions of Mandriva and several versions of Mandrake and others without any problems.

I compared the /etc/sane.d/canon.conf files in Mageia-1 and Mageia-3, they are the same.

If I fire up a Mint 13 XFCE live CD, it scans OK. The canon.conf file is the same as Mageia above. Doing scanimage -L in Mint:

Code: Select all

scanimage -L
device 'plustek:libusb:002:006' is a Canon CanoScan N650U/N565U flatbed scanner

which is what I cannot get in Mageia.

Try from root. You may need root permissions until you make the appropriate tweaks.

Thanks, but say per above I have already tried that.

I had the exact same issue before. I don't remember what the solution was, but I will offer you some hope that I will get back to this thread with a solution!...

I will now go and pickup my Canon Lide scanner and try to install and use it again

It has been awhile.

Do you see anything to download for plustek? I am not in Mageia atm to check. It might be something like libsane-plustek.

http://www.sane-project.org/cgi-bin/dri ... l=CanoScan

johng wrote:Thanks, but say per above I have already tried that.

it seems to rely on something called scannerdrake.

If you go to "Mageia control center", select "hardware" and "browse and configure hardware".. Then you SHOULD find your scanner in the list.
Select it and then you should be able to "run config tool".. When I did that it installed 2 scanner packages that I was completely would not have guessed and it now says "your scanner is available to the system"..

Actually, the option above does the same as "setup scanner" in the same hardware menu in Mageia control center.

Using "simple scan", my scanner now works.

I installed "sane-backends-iscan" manually also.

I believe the ones that installed during the above solution for my scanner was "task-scanning"..

I am using Canon Lide 210

Looking in Mageia 3 just now, I don't see anything for plustek, but I do see sane-backends. Have you installed sane-backends? If so, perhaps you should file a bug report on Mageia bugzilla.

I installed "task-printing-canon" and my canon multifunction printer will scan in Mageia. I wouldn't think that package would be needed for your scanner, but I couldn't say for sure.

Thank you for all the suggestions.
I already have sane-backends and task-scanning installed. And I have done the "setup scanner" in the same hardware menu in the Mageia control center, which at first tells me my scanner is not in the database. However it is listed when I do a manual, after which it tells me the has been configured and ready for use. scanimage -L tells me there is no scanner.

Strange. I was just searching for your scanner and sane to check its support and such. I found that, but I also found lots of people who had various issues with its connection.

Some forums seem to suggest you should add your user to the "scanner" group. But I found this posting, which might be helpful as a workaround:
http://forums.funtoo.org/viewtopic.php?id=1220


Ps. As someone above mentions, your scanner uses "plustek" while mine uses "genesys"... Check your plustek as he suggests. There is also a config file for plustek specifically.

I tried these:

Code: Select all

$ sane-find-scanner -q
found USB scanner (vendor=0x04a9, product=0x2206, chip=LM983x?) at libusb:003:005

$ xsane plustek:libusb:003:005
Gtk-Message: Failed to load module "canberra-gtk-module"

Failed to open device 'plustek:libusb:003:005'  Error during I/O

I added to /etc/sans.d/plustek.conf

Code: Select all

[usb]0x04a9 0x2206
device auto

but to no effect.

Comparing /etc/groups I noted these differences:

Mageia 1 /etc/groups:
usb:x:43:
cdwriter:x:80:

Mageia 3 /etc/groups:
usb:x:43:saned
cdwriter:x:80:saned
scanner:x:490:
saned:x:483:

I don't know if they are significant, or what they mean.

I don't think the GTK message is relevant, but it could prevent proper execution of the program. I also had it before I installed canberra libs, but in a completely different situation.

What seems to be relevant is "failed to open device 'plustek:libusb:003:005' Error during I/O"..
Try to get rid of that GTK bug first, just to see if it makes any difference. Otherwise also see what "dmesg | tail" says after trying the same thing again.

Did you execute the above command as root or user?

Additionally:
You can go into Mageia Control Center and System and then user management or something like that, and tick the groups your user should belong to. Add both USB and Scanner.

zeebra wrote:I don't think the GTK message is relevant, but it could prevent proper execution of the program. I also had it before I installed canberra libs, but in a completely different situation.

Nope it cannot, it's only about sound output and can be disregarded. For a solution see e.g. viewtopic.php?p=27036#p27036

Thank you Zeebra

Looking at Mageia Control Center/System/User and Groups:
saned User ID = 491, Primary Group = scanner, Full Name = system for saned, Login Shell = bin/false, Home Directory = /home/saned, Status = blank (was locked).

Running "scanimage -L", "sane-find-scanner -q", "xsane plustek:libusb:003:005", and "xsane" as user or root respond the same. Only "sane-find-scanner -q" identifies the scanner. After plugging in and out my GPS as a dmesg reference, none of these commands creates a dmesg output.

Plugging the scanner into my laptop with a fresh install Mint 15 Xfce, instantly produces a scan, just as did previous Mageia 1 and 2.

Hi, something has changed.

Up until now I had the following in /etc/udev/rules.d/60-libsane.rules:

Code: Select all

ATTRS{idVendor}=="04a9", ATTRS{idProduct}=="2206", MODE="0666", GROUP="usb", ENV{libsane_matched}="yes"

I have changed it to:

Code: Select all

ATTRS{idVendor}=="04a9", ATTRS{idProduct}=="2206", MODE="0666", OWNER="john",GROUP="users"

and now get a dsmeg output when executing these commands:
xsane

Code: Select all

[  172.970355] usb 3-9.4: usbfs: interface 0 claimed by usbfs while 'xsane' sets config #1

sane-find-scanner -q

Code: Select all

[  192.311582] usb 3-9.4: usbfs: interface 0 claimed by usbfs while 'xsane' sets config #1

xsane plustek:libusb:003:005

Code: Select all

[  292.847342] usb 3-9.4: usbfs: interface 0 claimed by usbfs while 'sane-find-scann' sets config #1

scanimage -L

Code: Select all

[  423.713777] lp: driver loaded but no devices found
[  423.715201] ppdev: user-space parallel port driver
[  611.716486] xhci_hcd 0000:00:14.0: URB transfer length is wrong, xHC issue? req. len = 0, act. len = 4294967288

Yes. Don't change the scanners groups.
Add groups "scanner" and "USB" to your username.

I am not sure if I can help you further. Hopefully someone else can read more out of this conversation to find a solution.

-Your scanner is detected by the USB. That's a good step 1.
-To me it seems the driver is not working correctly. This can be due to user/access issues, it can be due to lacking 'infrastructure', or possibly several other things as well.
Seemingly the correct components are installed. You can verify that by uninstalling all the scanner stuff in the control center. Then installing sane again, and then run the scanner setup on Mageia control center. That's there is an issue most likely on step 2. It all needs to work together.
-Step 3 is a good program for testing your scanner in. Personally I used "simple scan". If a program has some kind of special configurations that is required to work, it could possible create issues when you test the scanner.

You can get a lots of information by using "lsusb -v" in command line if you have usbutils installed. Probably also the loaded driver should show there under your scanner.

Please show the output of

Code: Select all

mount

Also seems the scanner is attached to an usb 3.0 controller, have you tried other ports (usb 2.0 only) ?

lsusb -v

Code: Select all

Bus 003 Device 005: ID 04a9:2206 Canon, Inc. CanoScan N650U/N656U
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x04a9 Canon, Inc.
  idProduct          0x2206 CanoScan N650U/N656U
  bcdDevice            1.00
  iManufacturer          64
  iProduct               77
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           39
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0
      bInterfaceProtocol    255
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0001  1x 1 bytes
        bInterval              16
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Device Status:     0x0001
  Self Powered


Mount

Code: Select all

$ mount
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,size=3929028k,nr_inodes=982257,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
/dev/sda1 on / type ext3 (rw,relatime,errors=continue,user_xattr,acl,commit=5,barrier=1,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=25,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
debugfs on /sys/kernel/debug type debugfs (rw,relatime,mode=755)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
tmpfs on /tmp type tmpfs (rw)
/dev/sdb3 on /home/sdb3 type ext3 (rw,relatime,errors=continue,user_xattr,acl,commit=5,barrier=1,data=ordered)
/dev/sdb1 on /home/sdb1 type ext3 (rw,relatime,errors=continue,user_xattr,acl,commit=5,barrier=1,data=ordered)
/dev/sda4 on /home/sda4 type ext3 (rw,relatime,errors=continue,user_xattr,acl,commit=5,barrier=1,data=ordered)
gvfsd-fuse on /run/user/500/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=500,group_id=500)

I tried removal of sane and scan stuff and install of xsane. Too many aps depended on sane-backends and lib64sane1 to remove.



Unplug scanner and re-plug. dmesg

Code: Select all

[ 2844.329336] usb 3-9.4: USB disconnect, device number 5
[ 2846.398714] usb 3-9.4: new full-speed USB device number 7 using xhci_hcd
[ 2846.423159] usb 3-9.4: New USB device found, idVendor=04a9, idProduct=2206
[ 2846.423167] usb 3-9.4: New USB device strings: Mfr=64, Product=77, SerialNumber=0
[ 2846.423172] usb 3-9.4: Product: CanoScan
[ 2846.423176] usb 3-9.4: Manufacturer: Canon

Simple-scan does not find the scanner. And I have tried the scanner in USB2 and USB3 ports.

I am speculating that you may be inadvertently using a built-in driver (kernel driver) instead of the plustek driver. You may need to blacklist the errant driver. Possibly xhci_hcd? If your scanner has a SD card reader built in, perhaps the device is seen as a drive rather than a scanner?

http://www.pcl-developers.org/xhci-hcd- ... 07949.html

Thanks David.
No SD card or slot, tried black listing xhci_hcd, still "no scanner found".

There are some things to try in the following reports...

http://translate.google.com/translate?h ... %3Dsuggest

http://translate.google.com/translate?h ... 6bih%3D642

https://bugs.launchpad.net/ubuntu/+sour ... bug/361278

http://forums.gentoo.org/viewtopic-t-84 ... art-0.html

http://forums.funtoo.org/viewtopic.php?id=1220