Canoscan 9000F mk II scanner not recognised

I have bought one since the Suse Hardware list says that it is fully supported. I use openSUSE 12.3.
When I connect it and use YaST - hardware - scanner it says no scanner recognized.

If I then select Add Scanner there is a line

Canon CanoScan 9000F : (Package sane-backends) Driver pixma should provide complete functionality (USB-ID 0x04a9:0x1908) [Full flatbed support up to 4800DPI (Note: flatbed does not have 9600DPI capability). Full TPU support (negatives and slides) up to 9600DPI.]

If I select this the response is pixma driver no scanner recognised.

When I select Hardware info in YaST I get (relevant bit)
usb device: name = 1-8:1.0
path = /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0
modalias = “usb:v04A9p190Dd0001dc00dsc00dp00icFFisc00ipFFin00”
bInterfaceNumber = 0
bInterfaceClass = 255
bInterfaceSubClass = 0
bInterfaceProtocol = 255
if: 1-8:1.0 @ /devices/pci0000:00/0000:00:1d.7/usb1/1-8
bDeviceClass = 0
bDeviceSubClass = 0
bDeviceProtocol = 0
idVendor = 0x04a9
idProduct = 0x190d
manufacturer = “Canon”
product = “CanoScan”
bcdDevice = 0001
speed = “480”

When I open a console and type lsusb I get

Bus 001 Device 005: ID 04a9:190d Canon, Inc.

If I look at file /etc/udev/rules.d/55 libsane rules it has two lines

Canon CanoScan 9000F

ATTR{idVendor}==“04a9”, ATTR{idProduct}==“1908”, MODE=“0664”, GROUP=“lp”, ENV{libsane_matched}=“yes”

Please note that the lsusb command gives

ID 04a9:190d whereas the udev/rules.d/55 libsane file gives
04a9: 1908

Please can anyone give advice? I get the same result if I use openSUSE 13.1.

Thank you in advance.

Yes, from a quick search online, it seems that the CanonScan 9000F Mark II uses a slightly different chipset. Create a new rule (eg /etc/udev/rules.d/50-CanonScan.rules) with the appropriate entry

# Canon CanoScan 9000F Mark II
ATTR{idVendor}=="04a9", ATTR{idProduct}=="190D", MODE="0664", GROUP="lp", ENV{libsane_matched}="yes"

Make sure that the user is a member of the ‘lp’ group for USB scanning. (Use YaST > Security and Users > User and Group Management)

You may also need to check that the pixma backend is uncommented in /etc/sane.d/dll.conf (as this is usually done by the YaST config tool, and you’re doing this manually).

Then you should be able to detect with

sane-find-scanner

or

scanimage -L

Try using your favourite scanning application. FWIW, I use ‘simple-scan’ as I’ve found xsane doesn’t play nice with my scanning hardware.

Thank you for your reply. I have added the lines that you suggest to /etc/udev/rules.d/55 libsane rules
and a corresponding line to etc/udev/rules.d/56-sane-backends-autoconfig.rules.

I checked that the pixma backend is uncommented in /etc/sane.d/dll.conf and that I was a member of the lp user group.

The results are as before.

The output from the two console commands that you suggest are:-
linux-g8as:/home/john # 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.

could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error

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

you have loaded a kernel driver for your USB host controller and have setup

the USB system correctly. See man sane-usb for details.

Not checking for parallel port scanners.

Most Scanners connected to the parallel port or other proprietary ports

can’t be detected by this program.

linux-g8as:/home/john # 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).
linux-g8as:/home/john #

I did note that when (in YaST) I tried to add a scanner the list of scanners that was offered did not include
the CanoScan 9000F Mark II that I had added above. It just gave the line:-

Canon CanoScan 9000F : (Package sane-backends) Driver pixma should provide complete functionality (USB-ID 0x04a9:0x1908) [Full flatbed support up to 4800DPI (Note: flatbed does not have 9600DPI capability). Full TPU support (negatives and slides) up to 9600DPI.]

Is there another file in which the 9000F Mark II data needs to be added? Do you have any other ideas?
Thank you again for your trouble.

My bad. I got the case wrong. It should be ‘190d’ rather than ‘190D’, so change like this

# Canon CanoScan 9000F Mark II
ATTR{idVendor}=="04a9", ATTR{idProduct}=="190d", MODE="0664", GROUP="lp", ENV{libsane_matched}="yes

BTW, it is preferable to add as a custom rule, rather than 55-libsane.rules, so that it doesn’t get overwritten by an update. That’s why I actually suggested ‘50-CanonScan.rules’.

Thank you again.
I checked and I had put lower case d in so that your suggestion was already in place. Have you any further ideas?

Plug it in and examine the kernel output

dmesg|tail

Thank you again. This is the result.

john@linux-g8as:/> dmesg | tail
462.709066] SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=fe80:0000:0000:0000:92fb:a6ff:fef0:0220 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44
590.769428] SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=fe80:0000:0000:0000:92fb:a6ff:fef0:0220 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44
846.846335] SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=fe80:0000:0000:0000:92fb:a6ff:fef0:0220 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44
1358.855517] SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=fe80:0000:0000:0000:92fb:a6ff:fef0:0220 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44
2382.939737] SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=fe80:0000:0000:0000:92fb:a6ff:fef0:0220 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44
3785.231021] usb 1-8: new high-speed USB device number 5 using ehci_hcd
3785.346719] usb 1-8: New USB device found, idVendor=04a9, idProduct=190d
3785.346724] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=0
3785.346729] usb 1-8: Product: CanoScan
3785.346733] usb 1-8: Manufacturer: Canon
john@linux-g8as:/>

Okay, the kernel messaging looks okay to me.

  1. Try running the following as root
scanimage -L
sane-find-scanner
  1. What happens if you attempt to run a scanning application via a terminal? Use whatever you have installed (as regular user) eg
xsane
simple-scan

Thank you again. In a terminal as root I get

linux-g8as:/home/john # 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).
linux-g8as:/home/john #

linux-g8as:/home/john # 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.

could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error

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

you have loaded a kernel driver for your USB host controller and have setup

the USB system correctly. See man sane-usb for details.

Not checking for parallel port scanners.

Most Scanners connected to the parallel port or other proprietary ports

can’t be detected by this program.

When I run as normal user
xsane I get a message scanning for devices - no scanners found.

It seems as though there is another look up table that the detection system is looking at that is not /etc/udev/rules.d/55-libsane.rules. The hardware - scanner function in Yast also fails to list the CanoScan 9000F Mark II in its list when using the “add scanner” option. I have checked and the 9000F Mark II is still in the /etc/udev/rules.d/55-libsane.rules file.

Did you set it up in Yast? Some scanners require firmware to be installed. Check your scanner on the sane web site

Hi wjohnk

Please make sure that you enclose your output within

....[/CO..] tags. It's the '#' symbol in the editor menu. It makes for easier reading.


> It seems as though there is another look up table that the detection system is looking at that is not /etc/udev/rules.d/55-libsane.rules. The hardware - scanner function in Yast also fails to list the CanoScan 9000F Mark II in its list when using the "add scanner" option. I have checked and the 9000F Mark II is still in the /etc/udev/rules.d/55-libsane.rules file.

No, I think that it is likely that the pxima backend is the wrong version to provide the necessary support for this model, and that you may need to upgrade. Reading the [sane-backends ChangeLog-1.0.24](https://github.com/bchallenor/sane-backends/blob/master/ChangeLog-1.0.24), I note that the 9000F Mark II is mentioned that support has been only recently added

2013-06-10 Rolf Bensch
* backend/pixma_mp810.c, doc/descriptions/pixma.desc, doc/sane-pixma.man:
New scanner Canon CanoScan 9000F Mark II.
* backend/pixma_mp810.c: Disable TPU negatives scan for CS8800F and CS9000F.
Negatives scan has no benefit for the user and disabling avoids confusion.


It might be worth a shot to upgrade sane-backends from 1.0.23 to 1.0.24, then try detecting again. To do that navigate to

https://software.opensuse.org/package/sane-backends

Select 'Show other versions', then 'Show unstable packages' and you'll see that 'home:jsmeix' offers the desired version. Install that with the package manager.

EUREKA :). Thank you very much. I installed 1.0.24 from the repository that you identified above and the scanner was automatically detected and the scanner now works.
Thank you very much indeed.

Fantabulous! I’m glad that you now have a working scanner. :smiley: