Help! OpenSuse won't recognize my Scanner!

English Hardware
#1

Yesterday I replaced my former operating system Fedora 20 with OpenSuse 13.1. But OpenSuse won’t recognize my Scanner (Brother DCP-135C).

My Brother DCP-135C is both, a printer and a scanner, but while printing works perfectly well, scanning doesn’t.
I already installed the brscan2 drivers from the brother download center.

“lsusb | grep Brother” gives the following output:

Bus 002 Device 003: ID 04f9:01ce Brother Industries, Ltd DCP-135C

So what I did next was to edit /etc/udev/rules.d/55-libsane.rules.

In there, I added the following lines:

# Brother DCP-135C
ATTR{idVendor}=="04f9", ATTR{idProduct}=="01ce", MODE="0664", GROUP="lp", ENV{libsane_matched}="yes"

However, it didn’t work either.

Fedora, however, did recognize the device as a scanner, although scanning itself didn’t work either.
So when I started xsane, I got offered two devices to choose from as a scanner: 1. the Brother device, 2. my webcam

On OpenSuse, xsane just tells me, that there are no scanners connected to my PC.

I’d really apprechiate any help of you guys!

Greetings

#2

Hi,

I’m not an expert but I’m fighting against my scanner too (see CanoScan Lide25 thread!), and maybe I can suggest you some more tests to do…

First, I’ve found some mail threads related to your scanner:
https://wiki.archlinux.org/index.php/Brother_DCP-135C
Linux Mint Forums • View topic - If your scanner doesn’t work

Verify (e.g. with “rpm -qa | grep sane”) that all necessary packages have been installed in your system, and that brscan2 backend has been enabled, that means uncommented, in system file /etc/sane.d/dll.conf.

Then try with some more test commands (from both user and root command line, to be sure), such as…
sane-find-scanner
****scanimage -L
****scanimage -T -d brscan2:libusb:xxx:yyy (where xxx and yyy are the same numbers logged by sane-find-scanner command)

a bit more information is always welcome!

BTW, I can’t find brscan2 backend in SANE official page (SANE: Backends (Drivers)) so it’s possible that you’ve to add it manually to /etc/sane.d/dll.conf …if I’m not completely wrong with backend name!

#3

Hi, and thanks for your answer!

rpm -qa | grep sane gives the following output:

sane-backends-1.0.23-9.2.3.x86_64hplip-sane-3.13.10-1.1.x86_64
sane-backends-devel-1.0.23-9.2.3.x86_64
sane-backends-autoconfig-1.0.23-9.2.3.x86_64
sane-backends-32bit-1.0.23-9.2.3.x86_64
xsane-0.998-19.1.4.x86_64

After that I checked */etc/sane.d/dll.conf.
*Brscan2 was not listed in there. Also every single line was commented:

# enable the next line if you want to allow access through the network:#net
#abaton
#agfafocus
#apple
#avision
#artec
#artec_eplus48u
#as6e
#bh
#canon
#canon630u
#canon_dr
#canon_pp
#cardscan
#coolscan
#coolscan2
#coolscan3
#dc25
#dc210
#dc240
#dell1600n_net
#dmc
#epjitsu
#epson
#epson2
#fujitsu
#gphoto2
#genesys
#gt68xx
#hp
#hp3900
#hpsj5s
#hp3500
#hp4200
#hp5400
#hp5590
#hpljm1005
#hs2p
#ibm
#kodak
#kodakaio
#kvs1025
#kvs20xx
#leo
#lexmark
#ma1509
#magicolor
#matsushita
#microtek
#microtek2
#mustek
#mustek_pp
#mustek_usb
#mustek_usb2
#nec
#niash
#p5
#pie
#pint
#pixma
#plustek
#plustek_pp
#pnm
#qcam
#ricoh
#rts8891
#s9036
#sceptre
#sharp
#sm3600
#sm3840
#snapscan
#sp15c
#st400
#stv680
#tamarack
#teco1
#teco2
#teco3
#test
#u12
#umax
#umax_pp
#umax1220u
#v4l
#xerox_mfp

As you suggested, I will now manually add brscan2.

output of “sane-find-scanners”:

 # 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.


  # 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.

“scanimage -L” also says, that there were no scanners found:

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).
#4

It seems that Brother backend has still not been integrated into SANE for some reasons… take a look at this thread, for example:
[sane-devel] Brother has already provided source code for brother scanner backends, should they go to sane-backends?](http://lists.alioth.debian.org/pipermail/sane-devel/2009-July/025101.html)

Neverthless, you can find it here:
Brother Solutions Center : Brother Driver for Linux Distributions

Maybe some distributions have integrated this backend driver into their external package sources…
You should download the rpm packages (brscan2 and scan-key-tool) for your architecture (command uname -m to check it) and try installing it manually with command *rpm -ivh --nodeps .rpm (from root, in the same directory where you downloaded the rpm packages).

They only declare these packages compatible with OpenSUSE 12.1, but hopefully they will be compatible with OpenSUSE 13.1, too…

Follow their own instructions, it seems to be straightforward:
Brother Solutions Center : Brother Driver for Linux Distributions
Brother Solutions Center : Brother Driver for Linux Distributions
Brother Solutions Center : Brother Driver for Linux Distributions

#5

I finally got it to work! Thank you very much for your help!

To get it to work, I opened the yast package management to uninstall all Brother packages, but during the uninstall process of “brother-udev-rule-type1-1.0.0-1.noarch.rpm” an error occured, that I wasn’t able to fix. I could neither uninstall brother-udev-rule-type1-1.0.0-1.noarch.rpm nor install it.

Also I thought I had installed all of the driver packages (rpm -ivh .), but it seems that there was a conflict between the x86_64 and the i386 versions, so rpm -ivh . just installed the i386 version of the packages. So I removed them and finally replaced them with the x86_64 version.

Then i ran “rpm -qa | grep -e brscan2”, which gave the following output:


brscan2-0.2.5-1.x86_64

I used this command to proof if the driver was installed or not.

Then I restarted the computer.

When I now run “sane-find-scanners”, it gives this output:

 # 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 open USB device 0x1d6b/0x0002 at 001:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0002 at 002:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0002 at 003:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0003 at 004:001: Access denied (insufficient permissions)
could not open USB device 0x0408/0x2fb1 at 001:003: Access denied (insufficient permissions)
could not open USB device 0x8086/0x0189 at 002:004: Access denied (insufficient permissions)
  # 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.


  # 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.

“scanimages -L” gives the following output:

device `brother2:bus2;dev3' is a Brother DCP-135C USB scanner

Scanning works now using xsane as well as simple-scan. (I didn’t test other programs, but I think they’ll work as well)

Thanks again!!