Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.os.linux.hardware > #2926 > unrolled thread

xsane compatibility with scanner

Started byHaines Brown <haines@engels.histomat.net>
First post2015-10-18 19:08 -0400
Last post2015-10-20 15:41 +1100
Articles 5 — 4 participants

Back to article view | Back to comp.os.linux.hardware


Contents

  xsane compatibility with scanner Haines Brown <haines@engels.histomat.net> - 2015-10-18 19:08 -0400
    Re: xsane compatibility with scanner philo <philo@privacy.net> - 2015-10-18 18:49 -0500
      Re: xsane compatibility with scanner Haines Brown <haines@engels.histomat.net> - 2015-10-19 07:59 -0400
        Re: xsane compatibility with scanner "Juan R. de Silva" <juan.r.d.silva@gmail.com> - 2015-10-19 17:45 +0000
          Re: xsane compatibility with scanner faeychild <faeychild@nomail.afraid.org> - 2015-10-20 15:41 +1100

#2926 — xsane compatibility with scanner

FromHaines Brown <haines@engels.histomat.net>
Date2015-10-18 19:08 -0400
Subjectxsane compatibility with scanner
Message-ID<87k2qj93lg.fsf@engels.histomat.net>
For years I've used xsane with a flatbed scanner, but now want to do
scans with a Brothers MFC-7220 multi-function copier connected via USB
cable.

When xsane starts, all it detects and uses is my video cam. In principle
if both devices detected, I should be able to choose among them when
xsane starts. Instead it only sees the camera.

$ sane-find-scanner
found USB scanner (vendor=0x04f9, product=0x0185) at libusb:004:028
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.

$ scanimage -L
found USB scanner (vendor=0x04f9, product=0x0185) at libusb:004:028
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.

What program does "backend" refer to? Is a work-around possible, or do I
have to give up using my device as a scanner (and fax machine?). When I
try to use the Brothers machine to scan, it fails to connect to my
computer (debian wheezy).  

[toc] | [next] | [standalone]


#2927

Fromphilo <philo@privacy.net>
Date2015-10-18 18:49 -0500
Message-ID<n01b35$lob$2@dont-email.me>
In reply to#2926
On 10/18/2015 06:08 PM, Haines Brown wrote:
> For years I've used xsane with a flatbed scanner, but now want to do
> scans with a Brothers MFC-7220 multi-function copier connected via USB
> cable.
>
> When xsane starts, all it detects and uses is my video cam. In principle
> if both devices detected, I should be able to choose among them when
> xsane starts. Instead it only sees the camera.
>
> $ sane-find-scanner
> found USB scanner (vendor=0x04f9, product=0x0185) at libusb:004:028
>    # Your USB scanner was (probably) detected. It may or may not be supported by
>    # SANE. Try scanimage -L and read the backend's manpage.
>
> $ scanimage -L
> found USB scanner (vendor=0x04f9, product=0x0185) at libusb:004:028
>    # Your USB scanner was (probably) detected. It may or may not be supported by
>    # SANE. Try scanimage -L and read the backend's manpage.
>
> What program does "backend" refer to? Is a work-around possible, or do I
> have to give up using my device as a scanner (and fax machine?). When I
> try to use the Brothers machine to scan, it fails to connect to my
> computer (debian wheezy).
>



Go to the Brother website, they now have Linux support


http://support.brother.com/g/b/downloadtop.aspx?c=us&lang=en&prod=mfc7220_us_as

[toc] | [prev] | [next] | [standalone]


#2928

FromHaines Brown <haines@engels.histomat.net>
Date2015-10-19 07:59 -0400
Message-ID<87fv1783xw.fsf@engels.histomat.net>
In reply to#2927
Thanks. I should have suspected Brothers might have the needed driver.
Now when I start xsane, I an choose devices, my video cam or my Brother
copier.

Unfortunately, that was as far as I got. I can select:

  Brother MFC-7220 USB scanner [brother2:bus1;dev1]

but if I open this device, I get error

  Failed to open device `brother2:bus1;dev1': Invalid argument.

Is the driver generating the argument? Should the semicolon between bus
and device numbers be a colon?

I find much in /usr/local/Brother/sane/, but have no idea what to do
with it. There seem two versions of each file such as Brsane2.ini and
Brsane3.ini, which are binaries. Two empty net device config files (2 &
3). There are a pair of scan setup executables, but when run nothing
happens.

[toc] | [prev] | [next] | [standalone]


#2929

From"Juan R. de Silva" <juan.r.d.silva@gmail.com>
Date2015-10-19 17:45 +0000
Message-ID<n03a79$49h$1@speranza.aioe.org>
In reply to#2928
On Mon, 19 Oct 2015 07:59:07 -0400, Haines Brown wrote:

> I find much in /usr/local/Brother/sane/, but have no idea what to do
> with it. There seem two versions of each file such as Brsane2.ini and
> Brsane3.ini, which are binaries. Two empty net device config files (2 &
> 3). There are a pair of scan setup executables, but when run nothing
> happens.

The presence of both brsane2 and brsane3 suggest that you installed the 
newest driver version on top of the existing driver installed previously.

You need to read the instructions on the Brother web site carefully. I 
had to uninstall the old version before installing the new one.

My suggestion for you now is to uninstall whatever of Brother you have on 
your system. In you case you might want to follow up and to clean all 
remnants, if any, manually. And then re-install the new driver. The 
easiest way to do it is using Brother installer instead of installing 
drivers individually one by one.

[toc] | [prev] | [next] | [standalone]


#2930

Fromfaeychild <faeychild@nomail.afraid.org>
Date2015-10-20 15:41 +1100
Message-ID<n04ghs$tpc$2@dont-email.me>
In reply to#2929
Juan R. de Silva wrote:


> My suggestion for you now is to uninstall whatever of Brother you have on
> your system. In you case you might want to follow up and to clean all
> remnants, if any, manually. And then re-install the new driver. The
> easiest way to do it is using Brother installer instead of installing
> drivers individually one by one.

Agreed! That is how I cleared my problem.

Installing drivers is fraught with peril; use the installer script.


-- 
faeychild
Running kde on 3.14.43-desktop-1.mga4 kernel.
Mageia release 4 (Official) for x86_64

[toc] | [prev] | [standalone]


Back to top | Article view | comp.os.linux.hardware


csiph-web