Brother DCP 7057

Hello,

I’m tryning to run Brother DCP 7057. No luck since the biginning. I have searched the internet, read the whole Brother site, followed the instructions provided there and nothing.

The sad thing is that now I’m running openSuse LXDE and no matter how hard I try it doesn’t work but on Lubuntu it worked without problems.

I used some testing tool and here is the output Page 1 (Scheduler not running?): {‘cups_connection_failure’: False} Page 2 (Is - Pastebin.com

I’m trying to fix this since houes now and stuck :frowning:

Wurger wrote:

> DCP 7057
Do you have a DCP7057 or a DCP7057WR since they have seperate listed
drivers on the Brothers website. Did you use the Brothers drivers
and follow the directions step by step.

Code

http://welcome.solutions.brother.com/bsc/public_s/id/linux/en/download_prn.html#DCP-7057
/Code

You should load bother the LPR and the cupswrapper versions. and for
openSUSE make sure you grab the rpm version.

Cannot help much more except to say on my MFC-J6710DW printer the
brothers drive works fine on openSUSE 12.2 and 12.3. I noticed the
ones for your printer are alittle older but should work.


openSUSE 12.3(Linux 3.9.8-1.gf3348a8-desktop)|KDE 4.10.5
“release 4”|Intel core2duo 2.5 MHZ,|8GB DDR3|GeForce
8400GS(NVIDIA-Linux-x86_64-319.32)

I have tried both and moved step by step very carefully not to miss something or mistype.No the funny thing is that at some point the printer was alive and printed one page so I though - lets move to the scanner and after reboot the scanners didn’t start working and the printer stopped working.Edit:To be more precise - when I hit Simple Scan I can hear that the scanner starts moving - just like a normal pre scan move of the scanning head but then it stops and an error in program pops out.

Try deleting the brother printer, uninstall the brother driver
then start from scratch follow the driver instruction from the brother site.

Note:
The most important part to follow is the command line config
in the brother driver installation instruction for usb connection or via network.

I did as you requested and here is what happened:I have triple checked on the back of the machine - it is DCP-7057 without any additions.The printer started to work with DCP-7057 when I did the procedure once again.This gave me hope but with the scanner - no luck.I did as in the brother page and started Simple-scan from terminal as root. As I wrote the scanner is started, the head moves and then an error pops out ;(

I have also did this:
Brother Solutions Center : Brother Driver for Linux Distributions

Here are the exact commands I did:

fw190@linux-nqcd:~> suHasło: 
linux-nqcd:/home/fw190 # rpm  -ihv  --nodeps /home/fw190/brscan4-0.4.1-5.i386.rpm
błąd: otwarcie /home/fw190/brscan4-0.4.1-5.i386.rpm się nie powiodło: Nie ma takiego pliku ani katalogu
linux-nqcd:/home/fw190 # rpm  -ihv  --nodeps /home/fw190/Pulpit/brscan4-0.4.1-5.i386.rpm
Przygotowywanie...                    ################################# [100%]
Aktualizowanie/instalowanie...
   1:brscan4-0.4.1-5                  ################################# [100%]
This software is based in part on the work of the Independent JPEG Group.
linux-nqcd:/home/fw190 # rpm  -qa  |  grep  -e brscan4
brscan4-0.4.1-5.i386
linux-nqcd:/home/fw190 # simple-scan
linux-nqcd:/home/fw190 # xsane
/usr/share/themes/Synchronicity/gtk-2.0/gtkrc:46: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored.
/usr/share/themes/Synchronicity/gtk-2.0/gtkrc:47: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored.
/usr/share/themes/Synchronicity/gtk-2.0/gtkrc:48: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored.
linux-nqcd:/home/fw190 # rpm  -ihv  --nodeps /home/fw190/Pulpit/brscan-skey-0.2.4-1.i386.rpm
Przygotowywanie...                    ################################# [100%]
Aktualizowanie/instalowanie...
   1:brscan-skey-0.2.4-1              ################################# [100%]
linux-nqcd:/home/fw190 # rpm  -qa  |  grep  -e brscan
brscan-skey-0.2.4-1.i386
brscan4-0.4.1-5.i386
linux-nqcd:/home/fw190 # brscan-skey
linux-nqcd:/home/fw190 # brscan-skey -l


 DCP-7057          : brother4:bus2;dev3  : USB                  Active


linux-nqcd:/home/fw190 # simple-scan



Still no luck. I have tested Simple Scan and XSane

I’m sory tat I,posting one post under an other but I can not edit my older posts:

Now a interesting thing. Here is what Yast is showing.
Image - TinyPic - Free Image Hosting, Photo Sharing & Video Hosting
As I understand it is seening two things. Is this supposed to be like this?

The scanner should work as your user not root. Did you installed the scanner driver too and did the brsaneconfig as stated in the brother site?

I didn’t do it as I only have a usb connection and it worked just fine on Lubuntu. The good thing is that the prnter works.As I wrote: starting the Simple Scan as root or user gives the same results ( I did the procedure for normal users - in my last post I wrote about root because brother asked to launch it like this in their tutorial - for the first time launch) - the scanning head starts to move like it is calibrating and the it stops. So there is some sort of connection but the question is why does it stop and blasts an error.

I’ve connected to a number of Brother printer/scanner devices over the years and have not yet experienced a driver issue, but I guess there is always a possibility of a bug, (in which case you’d need to contact Brother for support).

Some things to check/try:

  1. Confirm that the correct driver is explicitly listed in /etc/sane.d/dll.conf. You should find the brother4 entry uncommented like this

.
.
#umax
#umax_pp
#umax1220u
#v4l
#xerox_mfp
# The hpaio backend is provided by the hplip package:
#hpaio

brother4

  1. You mentioned that you have tried simple-scan…it might be worth giving iscan and/or xsane a shot too, although I doubt whether that will change anything.

As you configured the scanner via yast, (I always do by hand for scanners), I assume you have a udev rule for your scanner? Check in the /etc/udev/rules.d/ directory for the rules file

It should look like

# Brother DCP-7057
ATTR{idVendor}=="04f9", ATTR{idProduct}=="0257", MODE="0664", GROUP="lp", ENV{libsane_matched}="yes"

You may need to check with ‘lsusb’ command that this is the correct product ID first. (You can always create a ruled file manually if necessary eg 50-brother.rules)

Hello!

/etc/sane.d/dll.conf is set up as on your example.

lsusb showed:

Bus 002 Device 005: ID 04f9:0273 Brother Industries, Ltd 

so i have changed in libsane

Brother DCP-7057

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

I have tried xsane - it looks like that the head goes till the end not like with Simple scan bu an error pops out and it is a no go.

Creating a separate 50-brother.rules doesn’t help ;(

After each change I’m doeing a reboot just to be on the safe side.

Simple scan does see the scanner as I can hear the head calibrating and after it stops and after the error pops out there is an option to change the scanner and I can see that it recognizes Brother 7057.

The funny thing is that I think it can not be a brother bug as it worked on Lubuntu which is the same as openSuse LXDE (you know what I mean -it’s not KDE or GNOME). It has to be something with Suse but the question is what :wink:

Hmmm…what does the following report (with your scanner connected)?

scanimage -T

BTW, can you tell us which version of openSUSE you’re using?

You might also like to review this scanner troubleshooting guide

https://en.opensuse.org/SDB:Configuring_Scanners#Trouble-Shooting_.28Debugging.29

scanimage -T gives:

fw190@linux-nqcd:~> scanimage -Tscanimage: rounded value of br-x from 215.9 to 215.88
scanimage: rounded value of br-y from 355.6 to 355.567
scanimage: scanning image of size 1648x2291 pixels at 24 bits/pixel
scanimage: acquiring RGB frame, 8 bits/sample
scanimage: reading one scanline, 4944 bytes...	FAIL Error: Out of memory
fw190@linux-nqcd:~> 

deano ferrari wrote:

>
> As you configured the scanner via yast, (I always do by hand for
> scanners), I assume you have a udev rule for your scanner? Check
in
> the /etc/udev/rules.d/ directory for the rules file
>
> It should look like
>
> Code:
> --------------------
> # Brother DCP-7057
> ATTR{idVendor}==“04f9”, ATTR{idProduct}==“0257”, MODE=“0664”,
> GROUP=“lp”, ENV{libsane_matched}=“yes”
> --------------------
>
> You may need to check with ‘lsusb’ command that this is the
correct
> product ID first. (You can always create a ruled file manually if
> necessary eg 50-brother.rules)
>
>
Thanks deano, I was trying to remember where the change to Libsane
rules were. I remembered the .dll.conf change. In the install
instructions Brother left out the product ID for the rule change. I
thought I wrote it down but I cannot find it. I have an MFC-J6719DW.

on my 12.3 system there is no 50-brother rule. The entry was put in
55-libsane.rules. I also get the out of memory error when I run
scanimage -T command. I finally gave up trying to use scanner the
normal way and installed the Brother Scan-tool option. It works but
is a manual operation. If you fins a cure could you please post it?

Code

@linux-rpl7:~> sudo scanimage -T
scanimage: rounded value of br-x from 297 to 296.973
scanimage: rounded value of br-y from 420 to 419.962
scanimage: scanning image of size 2288x3306 pixels at 24 bits/pixel
scanimage: acquiring RGB frame, 8 bits/sample
scanimage: reading one scanline, 6864 bytes… FAIL Error: Out of
memory

@linux-rpl7:~> scanimage -L
device `brother4:bus1;dev1’ is a Brother MFC-J6710DW USB scanner
/Code

Thanks.


openSUSE 12.3(Linux 3.9.8-1.gf3348a8-desktop)|KDE 4.10.5
“release 4”|Intel core2duo 2.5 MHZ,|8GB DDR3|GeForce
8400GS(NVIDIA-Linux-x86_64-319.32)

Wurger wrote:

>
> Hello!
>
> /etc/sane.d/dll.conf is set up as on your example.
>
> lsusb showed:
> Code:
> --------------------
> Bus 002 Device 005: ID 04f9:0273 Brother Industries, Ltd
> --------------------
>
>
> so i have changed
> # Brother DCP-7057
> ATTR{idVendor}==“04f9”, ATTR{idProduct}==“0273”, MODE=“0664”,
> GROUP=“lp”, ENV{libsane_matched}=“yes”
I think you want to take the * out of the idProduct.
Here’s example of mine:
Code

Brother MFC-J6710DW

ATTR{idVendor}==“04f9”, ATTR{idProduct}==“0263”, MODE=“0664”,
GROUP=“lp”, ENV{libsane_matched}=“yes”
/Code

>
> I have tried xsane - it looks like that the head goes till the end
not
> like with Simple scan bu an error pops out and it is a no go.
>
> After each change I’m doeing a reboot just to be on the safe side.
>
> Simple scan does see the scanner as I can hear the head
calibrating
> and after it stops and after the error pops out there is an option
to
> change the scanner and I can see that it recognizes Brother 7057.
>
> The funny thing is that I think it can not be a brother bug as it
> worked on Lubuntu which is the same as openSuse LXDE (you know
what I
> mean -it’s not KDE or GNOME). It has to be something with Suse but
the
> question is what :wink:
>
>
Russ

openSUSE 12.3(Linux 3.9.8-1.gf3348a8-desktop)|KDE 4.10.5
“release 4”|Intel core2duo 2.5 MHZ,|8GB DDR3|GeForce
8400GS(NVIDIA-Linux-x86_64-319.32)

No, I suggested that as a custom (hand-edited rule).

The entry was put in
55-libsane.rules.

Yes, I think that entry is added by YaST if you use that utility for configuring your scanner. (I don’t).

OKHere I go again - did all the info from Brother site, changed everything as adviced here and no go. The **** thing doesn’t want to work.It worked as su but after rebbot stoped.I need this scaner in my work. Why is opensuse doeing this to me :frowning:

I have tried xsane and brother is uncomented.

For now I have jumped ship to xfce and will try to do everything again.

The funny thing is that it worked for su, and when doeing the steps to run as user it stopped working both for su and user and pops out the memory issue. I do not understand - which memory is to low?

And the cherry - everything worked like a charm o Lubuntu 13.04… but it stopped on 13.10, and then I went to openSuse and the same thing :smiley:

Brother live chat told me that they do not have a 7057 listed in USA and I should contact my country support but they have not responded me.