Fedora 13, xsane unable to find MFC-495CW scanner.

davdunc · 10-26-2010, 01:42 PM

Let me begin this by telling you that is it working fine from my Ubuntu 9.10 netbook. I would like to also have access to the scanner from my Fedora 13 laptop.

I have installed brsane3:

Code:

[davdunc@mps1530 ~]$ rpm -qa | grep brsca
brscan3-0.2.11-2.i386
brscan-skey-0.2.1-3.i386

I have identified the scanner using brsaneconfig3:

Code:

[davdunc@mps1530 ~]$ sudo cat /usr/local/Brother/sane/brsanenetdevice3.cfg 
DEVICE=SCANNER , "MFC-495CW" , 0x4f9:0x22a , IP-ADDRESS=192.168.1.74

The scanner appears to be active:

Code:

[davdunc@mps1530 ~]$ brscan-skey -l

 SCANNER           : brother3:net1;dev0  : 192.168.1.74         Active
[davdunc@mps1530 ~]$

But if I attempt to locate it with the command sane-find-scanner I get the following:

Code:

[davdunc@mps1530 ~]$ 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=0x0483 [STMicroelectronics], product=0x2016 [Biometric Coprocessor]) at libusb:003: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.

  # You may want to run this program as root to find all devices. Once you
  # found the scanner devices, be sure to adjust access permissions as
  # necessary.
[davdunc@mps1530 ~]$

Needless to say, the scanner is not located and xsane attempts to scan from my biometric scanner.

Other possible concerns:

Code:

[davdunc@mps1530 ~]$ sudo /sbin/service iptables status
Table: filter
Chain INPUT (policy ACCEPT)
num  target     prot opt source               destination         

Chain FORWARD (policy ACCEPT)
num  target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
num  target     prot opt source               destination         

[davdunc@mps1530 ~]$ cat /etc/redhat-release 
Fedora release 13 (Goddard)
[davdunc@mps1530 ~]$ lsb_release -a 
LSB Version:	:core-4.0-ia32:core-4.0-noarch
Distributor ID:	Fedora
Description:	Fedora release 13 (Goddard)
Release:	13
Codename:	Goddard
[davdunc@mps1530 ~]$

John VV · 10-26-2010, 05:07 PM

in fedora i would access the scanner from Gimp

dose Gimp "see" it ? if so dose it scan ?

davdunc · 10-26-2010, 09:15 PM

Thanks for the reply John. Unfortunately, Gimp uses the sane plugins, just as xsane does. So your suggestion actually points me back to the same tool that I am having problems with just with a different skin.

Gnome-scan I thought might be able to find it, and that is a different tool, but it doesn't.
I am thinking that there is something about the device that makes it appear for the tools from Brother, but prevents the creation of a device or something. There is a disconnect between the discovery of the device by brscan and the delivery of that information to the other tools as a device.

By the way, SELinux is disabled for all tests so far.